public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Peng Fan <peng.fan@nxp.com>
Cc: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org"
	<krzysztof.kozlowski+dt@linaro.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"sboyd@kernel.org" <sboyd@kernel.org>,
	"abelvesa@kernel.org" <abelvesa@kernel.org>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"estevam@gmail.com" <estevam@gmail.com>,
	dl-linux-imx <linux-imx@nxp.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"inux-clk@vger.kernel.org" <inux-clk@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: clock: support i.MX93 Anatop
Date: Thu, 19 Oct 2023 14:32:10 +0100	[thread overview]
Message-ID: <20231019-president-gallantly-1b509e6eb2eb@spud> (raw)
In-Reply-To: <DU0PR04MB9417CD64DDD5238BCBC5B3E588D4A@DU0PR04MB9417.eurprd04.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 2826 bytes --]

On Thu, Oct 19, 2023 at 10:05:54AM +0000, Peng Fan wrote:
> > Subject: Re: [PATCH 1/2] dt-bindings: clock: support i.MX93 Anatop
> > 
> > On Wed, Oct 18, 2023 at 04:44:13PM +0800, Peng Fan (OSS) wrote:
> > > From: Peng Fan <peng.fan@nxp.com>
> > >
> > > Support i.MX93 Anatop which generates PLL and feeds into CCM.
> > 
> > What is "CCM". How do you "generate" a PLL?
> 
>  
> CCM: Clock Controller Module.

> I may use produces PLL

No, almost certainly it _is_ a PLL and produces a clock.

> > > Signed-off-by: Peng Fan <peng.fan@nxp.com>
> > > ---
> > >  .../bindings/clock/fsl,imx93-anatop.yaml      | 41 +++++++++++++++++++
> > >  1 file changed, 41 insertions(+)
> > >  create mode 100644
> > > Documentation/devicetree/bindings/clock/fsl,imx93-anatop.yaml
> > >
> > > diff --git
> > > a/Documentation/devicetree/bindings/clock/fsl,imx93-anatop.yaml
> > > b/Documentation/devicetree/bindings/clock/fsl,imx93-anatop.yaml
> > > new file mode 100644
> > > index 000000000000..9585c9e4ee40
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/clock/fsl,imx93-anatop.yaml
> > > @@ -0,0 +1,41 @@
> > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2
> > > +---
> > > +$id: http://devicetree.org/schemas/clock/fsl,imx93-anatop.yaml#
> > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > +
> > > +title: NXP i.MX93 Anatop Module
> > 
> > I see there are also "anatop regulators" on some imx SoCs, just calling this
> > "anatop module" does not seem sufficiently descriptive.
> 
> Analog Module? How do you think?

It'd probably more be descriptive, but really putting the PLL bit in the
title would be helpful.

I assume "anatop" is what this thing is called in the RTL for the
device.

Cheers,
Conor.

>  
> > 
> > > +
> > > +maintainers:
> > > +  - Peng Fan <peng.fan@nxp.com>
> > > +
> > > +description: |
> > 
> > Drop the |, you don't need it.
> 
> Ok.
> 
> > 
> > > +  NXP i.MX93 anatop PLL module which generates PLL to CCM root.
> > > +
> > > +properties:
> > > +  compatible:
> > > +    items:
> > > +      - const: fsl,imx93-anatop
> > > +
> > > +  reg:
> > > +    maxItems: 1
> > > +
> > > +  '#clock-cells':
> > > +    const: 1
> > > +
> > > +required:
> > > +  - compatible
> > > +  - reg
> > > +  - '#clock-cells'
> > > +
> > > +additionalProperties: false
> > > +
> > > +examples:
> > > +  - |
> > > +    anatop: clock-controller@44480000 {
> > 
> > and the label is is not used, so should be dropped.
> 
> Ok.
> 
> Thanks,
> Peng.
> 
> > 
> > Thanks,
> > Conor.
> > 
> > > +        compatible = "fsl,imx93-anatop";
> > > +        reg = <0x44480000 0x2000>;
> > > +        #clock-cells = <1>;
> > > +    };
> > > +
> > > +...
> > > --
> > > 2.37.1
> > >

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-10-19 13:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18  8:44 [PATCH 1/2] dt-bindings: clock: support i.MX93 Anatop Peng Fan (OSS)
2023-10-18  8:44 ` [PATCH 2/2] arm64: dts: imx93: update anatop node Peng Fan (OSS)
2023-10-18 13:55 ` [PATCH 1/2] dt-bindings: clock: support i.MX93 Anatop Conor Dooley
2023-10-19 10:05   ` Peng Fan
2023-10-19 13:32     ` Conor Dooley [this message]
     [not found]       ` <CALCWtBeJSFCUiYP47sb=XZObY_bQ=9jhh4i-5PNN4o1YbaQPqw@mail.gmail.com>
2023-10-19 14:39         ` Conor Dooley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231019-president-gallantly-1b509e6eb2eb@spud \
    --to=conor@kernel.org \
    --cc=abelvesa@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=estevam@gmail.com \
    --cc=inux-clk@vger.kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sboyd@kernel.org \
    --cc=shawnguo@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox