[1/3] clk: qoriq: add t1023 soc support

From: Yuantian Tang <andy.tang@nxp.com>

Add t1023 clock compatible string to the bindings.

Signed-off-by: Tang Yuantian <andy.tang@nxp.com>
---
 .../devicetree/bindings/clock/qoriq-clock.txt      |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

Hi,

Appreciate if you can take a look at this patch set.

BR,
Andy

> -----Original Message-----
> From: andy.tang@nxp.com <andy.tang@nxp.com>
> Sent: 2018年9月19日 15:39
> To: mturquette@baylibre.com; oss@buserror.net
> Cc: sboyd@kernel.org; robh+dt@kernel.org; mark.rutland@arm.com;
> linux-clk@vger.kernel.org; devicetree@vger.kernel.org; Andy Tang
> <andy.tang@nxp.com>
> Subject: [PATCH 1/3] clk: qoriq: add t1023 soc support
> 
> From: Yuantian Tang <andy.tang@nxp.com>
> 
> Add t1023 clock compatible string to the bindings.
> 
> Signed-off-by: Tang Yuantian <andy.tang@nxp.com>
> ---
>  .../devicetree/bindings/clock/qoriq-clock.txt      |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/clock/qoriq-clock.txt
> b/Documentation/devicetree/bindings/clock/qoriq-clock.txt
> index 97f46ad..34e1933 100644
> --- a/Documentation/devicetree/bindings/clock/qoriq-clock.txt
> +++ b/Documentation/devicetree/bindings/clock/qoriq-clock.txt
> @@ -37,6 +37,7 @@ Required properties:
>  	* "fsl,ls1046a-clockgen"
>  	* "fsl,ls1088a-clockgen"
>  	* "fsl,ls2080a-clockgen"
> +	* "fsl,t1023-clockgen"
>  	Chassis-version clock strings include:
>  	* "fsl,qoriq-clockgen-1.0": for chassis 1.0 clocks
>  	* "fsl,qoriq-clockgen-2.0": for chassis 2.0 clocks
> --
> 1.7.1

Quoting Andy Tang (2018-10-15 23:17:18)
> Hi,
> 
> Appreciate if you can take a look at this patch set.
> 

I can pick the clk patches, but not the dts bits. Sound good?

> -----Original Message-----
> From: Stephen Boyd <sboyd@kernel.org>
> Sent: 2018年10月17日 23:28
> To: mturquette@baylibre.com; oss@buserror.net; Andy Tang
> <andy.tang@nxp.com>
> Cc: robh+dt@kernel.org; mark.rutland@arm.com;
> linux-clk@vger.kernel.org; devicetree@vger.kernel.org
> Subject: RE: [PATCH 1/3] clk: qoriq: add t1023 soc support
> 
> Quoting Andy Tang (2018-10-15 23:17:18)
> > Hi,
> >
> > Appreciate if you can take a look at this patch set.
> >
> 
> I can pick the clk patches, but not the dts bits. Sound good?

Let's see what Scott say.

Hi Scott,

Do you have any comments about this patch set?

Do you thinik it is ok if Stephen picks up the clk patch and you pick up the rest of two patches?
Or one of you Acked the patch and the other one apply them all?

Thanks
Andy

On Thu, 2018-10-18 at 01:00 +0000, Andy Tang wrote:
> > -----Original Message-----
> > From: Stephen Boyd <sboyd@kernel.org>
> > Sent: 2018年10月17日 23:28
> > To: mturquette@baylibre.com; oss@buserror.net; Andy Tang
> > <andy.tang@nxp.com>
> > Cc: robh+dt@kernel.org; mark.rutland@arm.com;
> > linux-clk@vger.kernel.org; devicetree@vger.kernel.org
> > Subject: RE: [PATCH 1/3] clk: qoriq: add t1023 soc support
> > 
> > Quoting Andy Tang (2018-10-15 23:17:18)
> > > Hi,
> > > 
> > > Appreciate if you can take a look at this patch set.
> > > 
> > 
> > I can pick the clk patches, but not the dts bits. Sound good?
> 
> Let's see what Scott say.
> 
> Hi Scott,
> 
> Do you have any comments about this patch set?
> 
> Do you thinik it is ok if Stephen picks up the clk patch and you pick up the
> rest of two patches?
> Or one of you Acked the patch and the other one apply them all?

I can take the dts patches.

-Scott

> -----Original Message-----
> From: Scott Wood <oss@buserror.net>
> Sent: 2018年10月19日 14:28
> To: Andy Tang <andy.tang@nxp.com>; Stephen Boyd <sboyd@kernel.org>;
> mturquette@baylibre.com
> Cc: robh+dt@kernel.org; mark.rutland@arm.com;
> linux-clk@vger.kernel.org; devicetree@vger.kernel.org
> Subject: Re: [PATCH 1/3] clk: qoriq: add t1023 soc support
> 
> On Thu, 2018-10-18 at 01:00 +0000, Andy Tang wrote:
> > > -----Original Message-----
> > > From: Stephen Boyd <sboyd@kernel.org>
> > > Sent: 2018年10月17日 23:28
> > > To: mturquette@baylibre.com; oss@buserror.net; Andy Tang
> > > <andy.tang@nxp.com>
> > > Cc: robh+dt@kernel.org; mark.rutland@arm.com;
> > > linux-clk@vger.kernel.org; devicetree@vger.kernel.org
> > > Subject: RE: [PATCH 1/3] clk: qoriq: add t1023 soc support
> > >
> > > Quoting Andy Tang (2018-10-15 23:17:18)
> > > > Hi,
> > > >
> > > > Appreciate if you can take a look at this patch set.
> > > >
> > >
> > > I can pick the clk patches, but not the dts bits. Sound good?
> >
> > Let's see what Scott say.
> >
> > Hi Scott,
> >
> > Do you have any comments about this patch set?
> >
> > Do you thinik it is ok if Stephen picks up the clk patch and you pick
> > up the rest of two patches?
> > Or one of you Acked the patch and the other one apply them all?
> 
> I can take the dts patches.
> 
Thanks Scott. Please take the dts patches.

Hi Stephen,
Please take the clk patch.

Thanks you all.
BR,
Andy

> -Scott

On Wed, 2018-09-19 at 15:39 +0800, andy.tang@nxp.com wrote:
> +clockgen: global-utilities@e1000 {
> +	compatible = "fsl,qoriq-clockgen";

Where does this compatible string come from?

> +		compatible = "fsl,t1023-clockgen";
>  	};

And here you overwrite it with only the chip-specific compatible?

Is t1023 incompatible with both fsl,qoriq-clockgen-1.0 and fsl,qoriq-clockgen-
2.0?  The existing dts says 2.0; is that wrong?

BTW, assuming it is 2.0 compatible and thus the use of qoriq-clockgen2.dtsi is
correct, the best course of action is probably to to remove the legacy stuff
from all fsl chips, rather than introduce a new dtsi.  In fact it'd be nice to
see it all removed in any case. :-)

Also, please post any patches that you want me to apply to the linuxppc-dev
mailing list.

-Scott

Hi Scott,

Please see my reply inline.

> -----Original Message-----
> From: Scott Wood <oss@buserror.net>
> Sent: 2018年10月21日 7:54
> To: Andy Tang <andy.tang@nxp.com>; mturquette@baylibre.com
> Cc: sboyd@kernel.org; robh+dt@kernel.org; mark.rutland@arm.com;
> linux-clk@vger.kernel.org; devicetree@vger.kernel.org
> Subject: Re: [PATCH 2/3] powerpc: t102x: upgrade the legacy clock node
> 
> On Wed, 2018-09-19 at 15:39 +0800, andy.tang@nxp.com wrote:
> > +clockgen: global-utilities@e1000 {
> > +	compatible = "fsl,qoriq-clockgen";
> 
> Where does this compatible string come from?
> 
> > +		compatible = "fsl,t1023-clockgen";
> >  	};
> 
> And here you overwrite it with only the chip-specific compatible?
> 
> Is t1023 incompatible with both fsl,qoriq-clockgen-1.0 and
> fsl,qoriq-clockgen- 2.0?  The existing dts says 2.0; is that wrong?
> 
> BTW, assuming it is 2.0 compatible and thus the use of
> qoriq-clockgen2.dtsi is correct, the best course of action is probably to to
> remove the legacy stuff from all fsl chips, rather than introduce a new dtsi.
> In fact it'd be nice to see it all removed in any case. :-)
qoriq-clockgen*.dtsi are used by legacy bindings. The contents are all of legacy bindings.
To use new framework, I introduce a new dtsi which contains new bindings and used for all PPC soc.
A chip-specific compatible is needed because driver will use it to get chip-specific clock tree information.
The clock information was defined in driver not in dts in new framework, remember?

This patch set is the first step to convert it to using new framework. After all the chips have been updated,
the legacy stuff will be removed. Including qoriq-clockgen*.dtsi.
> 
> Also, please post any patches that you want me to apply to the
> linuxppc-dev mailing list.
Sure, no problem.

BR,
Andy
> 
> -Scott

On Mon, 2018-10-22 at 01:34 +0000, Andy Tang wrote:
> Hi Scott,
> 
> Please see my reply inline.
> 
> > -----Original Message-----
> > From: Scott Wood <oss@buserror.net>
> > Sent: 2018年10月21日 7:54
> > To: Andy Tang <andy.tang@nxp.com>; mturquette@baylibre.com
> > Cc: sboyd@kernel.org; robh+dt@kernel.org; mark.rutland@arm.com;
> > linux-clk@vger.kernel.org; devicetree@vger.kernel.org
> > Subject: Re: [PATCH 2/3] powerpc: t102x: upgrade the legacy clock node
> > 
> > On Wed, 2018-09-19 at 15:39 +0800, andy.tang@nxp.com wrote:
> > > +clockgen: global-utilities@e1000 {
> > > +	compatible = "fsl,qoriq-clockgen";
> > 
> > Where does this compatible string come from?
> > 
> > > +		compatible = "fsl,t1023-clockgen";
> > >  	};
> > 
> > And here you overwrite it with only the chip-specific compatible?
> > 
> > Is t1023 incompatible with both fsl,qoriq-clockgen-1.0 and
> > fsl,qoriq-clockgen- 2.0?  The existing dts says 2.0; is that wrong?
> > 
> > BTW, assuming it is 2.0 compatible and thus the use of
> > qoriq-clockgen2.dtsi is correct, the best course of action is probably to
> > to
> > remove the legacy stuff from all fsl chips, rather than introduce a new
> > dtsi.
> > In fact it'd be nice to see it all removed in any case. :-)
> 
> qoriq-clockgen*.dtsi are used by legacy bindings. The contents are all of
> legacy bindings.
> To use new framework, I introduce a new dtsi which contains new bindings and
> used for all PPC soc.
> A chip-specific compatible is needed because driver will use it to get chip-
> specific clock tree information.
> The clock information was defined in driver not in dts in new framework,
> remember?

I'm aware that a chip-specific compatible is required.  What is unusual (on
PPC) is providing *only* the chip-specific compatible.  I was expecting
something more along the lines of https://patchwork.ozlabs.org/patch/486565/

Granted, the driver requiring two different compatibles to be present is odd,
and was a convenience based on what was already in the device trees, but the
fsl,qoriq-clockgen-2.0 compatible is part of the new binding (albeit an
optional part).  I guess I don't mind no longer relying on it, but at least
remove the "fsl,qoriq-clockgen" string.

-Scott

Hi Scott,

Please see my reply inline.

> -----Original Message-----
> From: Scott Wood <oss@buserror.net>
> Sent: 2018年10月22日 13:21
> To: Andy Tang <andy.tang@nxp.com>; mturquette@baylibre.com
> Cc: sboyd@kernel.org; robh+dt@kernel.org; mark.rutland@arm.com;
> linux-clk@vger.kernel.org; devicetree@vger.kernel.org
> Subject: Re: [PATCH 2/3] powerpc: t102x: upgrade the legacy clock node
> 
> On Mon, 2018-10-22 at 01:34 +0000, Andy Tang wrote:
> > Hi Scott,
> >
> > Please see my reply inline.
> >
> > > -----Original Message-----
> > > From: Scott Wood <oss@buserror.net>
> > > Sent: 2018年10月21日 7:54
> > > To: Andy Tang <andy.tang@nxp.com>; mturquette@baylibre.com
> > > Cc: sboyd@kernel.org; robh+dt@kernel.org; mark.rutland@arm.com;
> > > linux-clk@vger.kernel.org; devicetree@vger.kernel.org
> > > Subject: Re: [PATCH 2/3] powerpc: t102x: upgrade the legacy clock
> > > node
> > >
> > > On Wed, 2018-09-19 at 15:39 +0800, andy.tang@nxp.com wrote:
> > > > +clockgen: global-utilities@e1000 {
> > > > +	compatible = "fsl,qoriq-clockgen";
> > >
> > > Where does this compatible string come from?
> > >
> > > > +		compatible = "fsl,t1023-clockgen";
> > > >  	};
> > >
> > > And here you overwrite it with only the chip-specific compatible?
> > >
> > > Is t1023 incompatible with both fsl,qoriq-clockgen-1.0 and
> > > fsl,qoriq-clockgen- 2.0?  The existing dts says 2.0; is that wrong?
> > >
> > > BTW, assuming it is 2.0 compatible and thus the use of
> > > qoriq-clockgen2.dtsi is correct, the best course of action is
> > > probably to to remove the legacy stuff from all fsl chips, rather
> > > than introduce a new dtsi.
> > > In fact it'd be nice to see it all removed in any case. :-)
> >
> > qoriq-clockgen*.dtsi are used by legacy bindings. The contents are all
> > of legacy bindings.
> > To use new framework, I introduce a new dtsi which contains new
> > bindings and used for all PPC soc.
> > A chip-specific compatible is needed because driver will use it to get
> > chip- specific clock tree information.
> > The clock information was defined in driver not in dts in new
> > framework, remember?
> 
> I'm aware that a chip-specific compatible is required.  What is unusual (on
> PPC) is providing *only* the chip-specific compatible.  I was expecting
> something more along the lines of
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fp
> atchwork.ozlabs.org%2Fpatch%2F486565%2F&amp;data=02%7C01%7Can
> dy.tang%40nxp.com%7Ceaf46e43620b45a19eb408d637de20cb%7C686e
> a1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C636757824505667539
> &amp;sdata=T5yRSWtHYO2yLMjsZRIxZT%2BM82xuGQm2VGX7MRB8MJA%
> 3D&amp;reserved=0
> 
> Granted, the driver requiring two different compatibles to be present is
> odd, and was a convenience based on what was already in the device
> trees, but the
> fsl,qoriq-clockgen-2.0 compatible is part of the new binding (albeit an
> optional part).  I guess I don't mind no longer relying on it, but at least
> remove the "fsl,qoriq-clockgen" string.
After saw your previous patch, I plan to work out a similar patch. The fsl,qoriq-clockgen-2.0 and fsl,qoriq-clockgen-1.0 will be retained.

Thanks,
Andy

> 
> -Scott