From: maitysanchayan@gmail.com (maitysanchayan at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 4/4] nvmem: Add DT binding documentation for Vybrid OCOTP driver
Date: Sun, 6 Sep 2015 15:58:13 +0530 [thread overview]
Message-ID: <20150906102813.GA13499@Sanchayan-Arch> (raw)
In-Reply-To: <20150906081334.GK30746@tiger>
On 15-09-06 16:13:35, Shawn Guo wrote:
> On Wed, Aug 12, 2015 at 06:49:21PM +0530, Sanchayan Maity wrote:
> > Add the devicetree bindings for the Freescale Vybrid On-Chip
> > OTP driver.
> >
> > Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
> > Acked-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> > ---
> > .../devicetree/bindings/nvmem/vf610-ocotp.txt | 21 +++++++++++++++++++++
> > 1 file changed, 21 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt
> >
> > diff --git a/Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt b/Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt
> > new file mode 100644
> > index 0000000..b29f65f
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt
> > @@ -0,0 +1,21 @@
> > +On-Chip OTP Memory for Freescale Vybrid
> > +
> > +Required Properties:
> > + compatible:
> > + - "fsl,vf610-ocotp" for VF5xx/VF6xx
> > + #address-cells : Should be 1
> > + #size-cells : Should be 1
> > + reg : Address and length of OTP controller and fuse map registers
> > + clocks : ipg clock we associate with the OCOTP peripheral
> > + clock-names : Must contain "ocotp" as matching entry
>
> I'm not sure "ocotp" is a good name for describing a clock from OCOTP
> internal point of view. "ipg" might be better. But I would suggest you
> drop clock-names property completely, if "ipg" is the only clock you
> need to describe here. The clock-names is necessary only when there are
> multiple clocks to distinguish.
>
> With clock-names dropped, the driver works by passing NULL as the second
> parameter to devm_clk_get() call.
Ok. Will drop the clock-names property retest and try sending it by tomorrow.
- Sanchayan.
>
> Shawn
>
> > +
> > +Example for Vybrid VF5xx/VF6xx:
> > +
> > + ocotp: ocotp at 400a5000 {
> > + compatible = "fsl,vf610-ocotp";
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + reg = <0x400a5000 0xCF0>;
> > + clocks = <&clks VF610_CLK_OCOTP>;
> > + clock-names = "ocotp";
> > + };
> > --
> > 2.5.0
> >
WARNING: multiple messages have this Message-ID (diff)
From: maitysanchayan@gmail.com
To: Shawn Guo <shawnguo@kernel.org>
Cc: gregkh@linuxfoundation.org, srinivas.kandagatla@linaro.org,
maxime.ripard@free-electrons.com,
linux-arm-kernel@lists.infradead.org, stefan@agner.ch,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 4/4] nvmem: Add DT binding documentation for Vybrid OCOTP driver
Date: Sun, 6 Sep 2015 15:58:13 +0530 [thread overview]
Message-ID: <20150906102813.GA13499@Sanchayan-Arch> (raw)
In-Reply-To: <20150906081334.GK30746@tiger>
On 15-09-06 16:13:35, Shawn Guo wrote:
> On Wed, Aug 12, 2015 at 06:49:21PM +0530, Sanchayan Maity wrote:
> > Add the devicetree bindings for the Freescale Vybrid On-Chip
> > OTP driver.
> >
> > Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
> > Acked-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> > ---
> > .../devicetree/bindings/nvmem/vf610-ocotp.txt | 21 +++++++++++++++++++++
> > 1 file changed, 21 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt
> >
> > diff --git a/Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt b/Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt
> > new file mode 100644
> > index 0000000..b29f65f
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt
> > @@ -0,0 +1,21 @@
> > +On-Chip OTP Memory for Freescale Vybrid
> > +
> > +Required Properties:
> > + compatible:
> > + - "fsl,vf610-ocotp" for VF5xx/VF6xx
> > + #address-cells : Should be 1
> > + #size-cells : Should be 1
> > + reg : Address and length of OTP controller and fuse map registers
> > + clocks : ipg clock we associate with the OCOTP peripheral
> > + clock-names : Must contain "ocotp" as matching entry
>
> I'm not sure "ocotp" is a good name for describing a clock from OCOTP
> internal point of view. "ipg" might be better. But I would suggest you
> drop clock-names property completely, if "ipg" is the only clock you
> need to describe here. The clock-names is necessary only when there are
> multiple clocks to distinguish.
>
> With clock-names dropped, the driver works by passing NULL as the second
> parameter to devm_clk_get() call.
Ok. Will drop the clock-names property retest and try sending it by tomorrow.
- Sanchayan.
>
> Shawn
>
> > +
> > +Example for Vybrid VF5xx/VF6xx:
> > +
> > + ocotp: ocotp@400a5000 {
> > + compatible = "fsl,vf610-ocotp";
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + reg = <0x400a5000 0xCF0>;
> > + clocks = <&clks VF610_CLK_OCOTP>;
> > + clock-names = "ocotp";
> > + };
> > --
> > 2.5.0
> >
next prev parent reply other threads:[~2015-09-06 10:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 13:19 [PATCH v9 0/4] Implement OCOTP driver for Vybrid using NVMEM Sanchayan Maity
2015-08-12 13:19 ` Sanchayan Maity
2015-08-12 13:19 ` [PATCH v9 1/4] clk: clk-vf610: Add clock for Vybrid OCOTP controller Sanchayan Maity
2015-08-12 13:19 ` Sanchayan Maity
2015-09-06 8:15 ` Shawn Guo
2015-09-06 8:15 ` Shawn Guo
2015-09-06 10:28 ` maitysanchayan at gmail.com
2015-09-06 10:28 ` maitysanchayan
2015-08-12 13:19 ` [PATCH v9 2/4] ARM: dts: vfxxx: Add OCOTP node Sanchayan Maity
2015-08-12 13:19 ` Sanchayan Maity
2015-08-12 13:19 ` [PATCH v9 3/4] drivers: nvmem: Add Vybrid OCOTP support Sanchayan Maity
2015-08-12 13:19 ` Sanchayan Maity
2015-08-12 13:19 ` [PATCH v9 4/4] nvmem: Add DT binding documentation for Vybrid OCOTP driver Sanchayan Maity
2015-08-12 13:19 ` Sanchayan Maity
2015-09-06 8:13 ` Shawn Guo
2015-09-06 8:13 ` Shawn Guo
2015-09-06 10:28 ` maitysanchayan at gmail.com [this message]
2015-09-06 10:28 ` maitysanchayan
2015-08-24 8:32 ` [PATCH v9 0/4] Implement OCOTP driver for Vybrid using NVMEM maitysanchayan at gmail.com
2015-08-24 8:32 ` maitysanchayan
2015-09-04 5:50 ` maitysanchayan at gmail.com
2015-09-04 5:50 ` maitysanchayan
2015-09-04 8:21 ` Srinivas Kandagatla
2015-09-04 8:21 ` Srinivas Kandagatla
2015-09-04 8:21 ` maitysanchayan at gmail.com
2015-09-04 8:21 ` maitysanchayan
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=20150906102813.GA13499@Sanchayan-Arch \
--to=maitysanchayan@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.