From: Stefan Agner <stefan@agner.ch>
To: Chris Healy <cphealy@gmail.com>
Cc: srinivas.kandagatla@linaro.org, robh+dt@kernel.org,
gregkh@linuxfoundation.org, maitysanchayan@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
shawnguo@kernel.org, festevam@gmail.com, stable@vger.kernel.org,
andrew.smirnov@gmail.com
Subject: Re: [PATCH v4] dt-bindings: nvmem: Add syscon to Vybrid OCOTP driver
Date: Tue, 25 Aug 2020 14:44:11 +0200 [thread overview]
Message-ID: <a0a1958d393eb92ecc884be7a0dc0449@agner.ch> (raw)
In-Reply-To: <20200825030406.373623-1-cphealy@gmail.com>
On 2020-08-25 05:04, Chris Healy wrote:
> From: Chris Healy <cphealy@gmail.com>
>
> Add syscon compatibility with Vybrid OCOTP driver binding. This is
> required to access the UID.
>
> Fixes: 623069946952 ("nvmem: Add DT binding documentation for Vybrid
> OCOTP driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Chris Healy <cphealy@gmail.com>
Reviewed-by: Stefan Agner <stefan@agner.ch>
> ---
> Changes in v4:
> - Point to the appropriate commit for the Fixes: line
> - Update the Required Properties to add the "syscon" compatible
> ---
> Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt
> b/Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt
> index 56ed481c3e26..72ba628f6d0b 100644
> --- a/Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt
> +++ b/Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt
> @@ -2,7 +2,7 @@ On-Chip OTP Memory for Freescale Vybrid
>
> Required Properties:
> compatible:
> - - "fsl,vf610-ocotp" for VF5xx/VF6xx
> + - "fsl,vf610-ocotp", "syscon" for VF5xx/VF6xx
> #address-cells : Should be 1
> #size-cells : Should be 1
> reg : Address and length of OTP controller and fuse map registers
> @@ -11,7 +11,7 @@ Required Properties:
> Example for Vybrid VF5xx/VF6xx:
>
> ocotp: ocotp@400a5000 {
> - compatible = "fsl,vf610-ocotp";
> + compatible = "fsl,vf610-ocotp", "syscon";
> #address-cells = <1>;
> #size-cells = <1>;
> reg = <0x400a5000 0xCF0>;
next prev parent reply other threads:[~2020-08-25 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 3:04 [PATCH v4] dt-bindings: nvmem: Add syscon to Vybrid OCOTP driver Chris Healy
2020-08-25 12:44 ` Stefan Agner [this message]
2020-08-25 12:50 ` Fabio Estevam
2020-08-28 22:02 ` Rob Herring
2020-08-31 5:42 ` Shawn Guo
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=a0a1958d393eb92ecc884be7a0dc0449@agner.ch \
--to=stefan@agner.ch \
--cc=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maitysanchayan@gmail.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).