From: Nishanth Menon <nm@ti.com> To: Sinthu Raja <sinthu.raja@mistralsolutions.com> Cc: Suman Anna <s-anna@ti.com>, Rob Herring <robh+dt@kernel.org>, Baolin Wang <baolin.wang7@gmail.com>, Bjorn Andersson <bjorn.andersson@linaro.org>, Ohad Ben-Cohen <ohad@wizery.com>, <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-remoteproc@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, Sinthu Raja <sinthu.raja@ti.com> Subject: Re: [PATCH V2] dt-bindings: hwlock: omap: Remove redundant binding example Date: Sat, 18 Sep 2021 13:52:56 -0500 [thread overview] Message-ID: <20210918185256.jcjvlmgftycwf7lo@repeal> (raw) In-Reply-To: <20210917170805.5079-1-sinthu.raja@ti.com> On 22:38-20210917, Sinthu Raja wrote: > From: Sinthu Raja <sinthu.raja@ti.com> > > The example includes a board-specific compatible property, this is wrong > as the example should be board agnostic and should represent the particular > binding. Also, the file includes two similar examples, but with a different > compatible. So, drop the entire second example > > Fixes: d8db9dc34871 ("dt-bindings: hwlock: omap: Convert binding to YAML") Since we are cleaning up, You should probably drop the fixes. Esp when adding fixes, checkout the specific commit and attempt to git am this patch.. you would notice it wont apply.. and per stable rules, it is probably too trivial to backport to so many stable kernels. The later commit 891adc1303fe ("dt-bindings: hwlock: omap: Fix warnings with k3.yaml") attempted to fixup by making it board-specific, which was'nt solving the underlying problem either as this patch is doing.. Also it would be nice if you could attribute this to Bjorn by adding: Suggested-by: Bjorn Andersson <bjorn.andersson@linaro.org> > Signed-off-by: Sinthu Raja <sinthu.raja@ti.com> > --- > > Changes in V2: > Addressed review comments, that includes dropping the redundant example, > updates to commit message and $subject. I like this version much better. Thanks Bjorn for pointing the same out, the yaml is much cleaner now and easier to maintain. > > V1: https://lore.kernel.org/all/20210917094740.18891-1-sinthu.raja@ti.com/ > > .../bindings/hwlock/ti,omap-hwspinlock.yaml | 32 +------------------ > 1 file changed, 1 insertion(+), 31 deletions(-) > > diff --git a/Documentation/devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml b/Documentation/devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml > index ae1b37dbee75..4feebd90bff1 100644 > --- a/Documentation/devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml > +++ b/Documentation/devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml > @@ -40,38 +40,8 @@ examples: > > - | > /* OMAP4 SoCs */ ^^ Drop this? > - hwspinlock: spinlock@4a0f6000 { > + spinlock@4a0f6000 { > compatible = "ti,omap4-hwspinlock"; > reg = <0x4a0f6000 0x1000>; > #hwlock-cells = <1>; > }; > - > - - | > - / { > - /* K3 AM65x SoCs */ > - model = "Texas Instruments K3 AM654 SoC"; > - compatible = "ti,am654-evm", "ti,am654"; > - #address-cells = <2>; > - #size-cells = <2>; > - > - bus@100000 { > - compatible = "simple-bus"; > - #address-cells = <2>; > - #size-cells = <2>; > - ranges = <0x00 0x00100000 0x00 0x00100000 0x00 0x00020000>, /* ctrl mmr */ > - <0x00 0x30800000 0x00 0x30800000 0x00 0x0bc00000>; /* Main NavSS */ > - > - bus@30800000 { > - compatible = "simple-mfd"; > - #address-cells = <2>; > - #size-cells = <2>; > - ranges = <0x00 0x30800000 0x00 0x30800000 0x00 0x0bc00000>; > - > - spinlock@30e00000 { > - compatible = "ti,am654-hwspinlock"; > - reg = <0x00 0x30e00000 0x00 0x1000>; > - #hwlock-cells = <1>; > - }; > - }; > - }; > - }; > -- > 2.31.1 > -- Regards, Nishanth Menon Key (0xDDB5849D1736249D)/Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com> To: Sinthu Raja <sinthu.raja@mistralsolutions.com> Cc: Ohad Ben-Cohen <ohad@wizery.com>, devicetree@vger.kernel.org, Sinthu Raja <sinthu.raja@ti.com>, linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org, Bjorn Andersson <bjorn.andersson@linaro.org>, Rob Herring <robh+dt@kernel.org>, Baolin Wang <baolin.wang7@gmail.com>, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH V2] dt-bindings: hwlock: omap: Remove redundant binding example Date: Sat, 18 Sep 2021 13:52:56 -0500 [thread overview] Message-ID: <20210918185256.jcjvlmgftycwf7lo@repeal> (raw) In-Reply-To: <20210917170805.5079-1-sinthu.raja@ti.com> On 22:38-20210917, Sinthu Raja wrote: > From: Sinthu Raja <sinthu.raja@ti.com> > > The example includes a board-specific compatible property, this is wrong > as the example should be board agnostic and should represent the particular > binding. Also, the file includes two similar examples, but with a different > compatible. So, drop the entire second example > > Fixes: d8db9dc34871 ("dt-bindings: hwlock: omap: Convert binding to YAML") Since we are cleaning up, You should probably drop the fixes. Esp when adding fixes, checkout the specific commit and attempt to git am this patch.. you would notice it wont apply.. and per stable rules, it is probably too trivial to backport to so many stable kernels. The later commit 891adc1303fe ("dt-bindings: hwlock: omap: Fix warnings with k3.yaml") attempted to fixup by making it board-specific, which was'nt solving the underlying problem either as this patch is doing.. Also it would be nice if you could attribute this to Bjorn by adding: Suggested-by: Bjorn Andersson <bjorn.andersson@linaro.org> > Signed-off-by: Sinthu Raja <sinthu.raja@ti.com> > --- > > Changes in V2: > Addressed review comments, that includes dropping the redundant example, > updates to commit message and $subject. I like this version much better. Thanks Bjorn for pointing the same out, the yaml is much cleaner now and easier to maintain. > > V1: https://lore.kernel.org/all/20210917094740.18891-1-sinthu.raja@ti.com/ > > .../bindings/hwlock/ti,omap-hwspinlock.yaml | 32 +------------------ > 1 file changed, 1 insertion(+), 31 deletions(-) > > diff --git a/Documentation/devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml b/Documentation/devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml > index ae1b37dbee75..4feebd90bff1 100644 > --- a/Documentation/devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml > +++ b/Documentation/devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml > @@ -40,38 +40,8 @@ examples: > > - | > /* OMAP4 SoCs */ ^^ Drop this? > - hwspinlock: spinlock@4a0f6000 { > + spinlock@4a0f6000 { > compatible = "ti,omap4-hwspinlock"; > reg = <0x4a0f6000 0x1000>; > #hwlock-cells = <1>; > }; > - > - - | > - / { > - /* K3 AM65x SoCs */ > - model = "Texas Instruments K3 AM654 SoC"; > - compatible = "ti,am654-evm", "ti,am654"; > - #address-cells = <2>; > - #size-cells = <2>; > - > - bus@100000 { > - compatible = "simple-bus"; > - #address-cells = <2>; > - #size-cells = <2>; > - ranges = <0x00 0x00100000 0x00 0x00100000 0x00 0x00020000>, /* ctrl mmr */ > - <0x00 0x30800000 0x00 0x30800000 0x00 0x0bc00000>; /* Main NavSS */ > - > - bus@30800000 { > - compatible = "simple-mfd"; > - #address-cells = <2>; > - #size-cells = <2>; > - ranges = <0x00 0x30800000 0x00 0x30800000 0x00 0x0bc00000>; > - > - spinlock@30e00000 { > - compatible = "ti,am654-hwspinlock"; > - reg = <0x00 0x30e00000 0x00 0x1000>; > - #hwlock-cells = <1>; > - }; > - }; > - }; > - }; > -- > 2.31.1 > -- Regards, Nishanth Menon Key (0xDDB5849D1736249D)/Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-09-18 18:53 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-17 17:08 [PATCH V2] dt-bindings: hwlock: omap: Remove redundant binding example Sinthu Raja 2021-09-17 17:08 ` Sinthu Raja 2021-09-18 18:52 ` Nishanth Menon [this message] 2021-09-18 18:52 ` Nishanth Menon
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=20210918185256.jcjvlmgftycwf7lo@repeal \ --to=nm@ti.com \ --cc=baolin.wang7@gmail.com \ --cc=bjorn.andersson@linaro.org \ --cc=devicetree@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-remoteproc@vger.kernel.org \ --cc=ohad@wizery.com \ --cc=robh+dt@kernel.org \ --cc=s-anna@ti.com \ --cc=sinthu.raja@mistralsolutions.com \ --cc=sinthu.raja@ti.com \ /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: linkBe 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.