From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: soc@kernel.org, Arnd Bergmann <arnd@arndb.de>,
Viresh Kumar <vireshk@kernel.org>,
Shiraz Hashim <shiraz.linux.kernel@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: dts: spear13xx: Update SPI dma properties
Date: Mon, 14 Mar 2022 12:24:34 +0530 [thread overview]
Message-ID: <20220314065434.GA43329@9a2d8922b8f1> (raw)
In-Reply-To: <20220314035118.gbjbrwbsywxljjti@vireshk-i7>
On Mon, Mar 14, 2022 at 09:21:18AM +0530, Viresh Kumar wrote:
> On 12-03-22, 23:36, Kuldeep Singh wrote:
> > Reorder dmas and dma-names property for spi controller node to make it
> > compliant with bindings.
> >
> > Signed-off-by: Kuldeep Singh <singh.kuldeep87k@gmail.com>
>
> What about a fixes tag ?
Sure, will add one.
> > ---
> > arch/arm/boot/dts/spear13xx.dtsi | 5 ++---
> > 1 file changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/spear13xx.dtsi b/arch/arm/boot/dts/spear13xx.dtsi
> > index c87b881b2c8b..45f0b2a33e02 100644
> > --- a/arch/arm/boot/dts/spear13xx.dtsi
> > +++ b/arch/arm/boot/dts/spear13xx.dtsi
> > @@ -284,9 +284,8 @@ spi0: spi@e0100000 {
> > #size-cells = <0>;
> > interrupts = <0 31 0x4>;
> > status = "disabled";
> > - dmas = <&dwdma0 4 0 0>,
> > - <&dwdma0 5 0 0>;
> > - dma-names = "tx", "rx";
> > + dmas = <&dwdma0 5 0 0>, <&dwdma0 4 0 0>;
> > + dma-names = "rx", "tx";
>
> Why does the order matter here since we have dma-names anyway, which
> was correct earlier ?
Dma-names order matters here.
As per pl022 binding, dma-names order specify rx,tx and all DTs which
have tx,rx as order start raising dtbs_chek warning. Thus, need to
reverse this order. Please note, no functional change in this patch
apart from just fixing warning.
Warning:
'rx' was expected
'tx' was expected
Regards
Kuldeep
next prev parent reply other threads:[~2022-03-14 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 18:06 [PATCH 0/2] More DT fixes for arm,pl022 Kuldeep Singh
2022-03-12 18:06 ` [PATCH 1/2] ARM: dts: spear13xx: Update SPI dma properties Kuldeep Singh
2022-03-14 3:51 ` Viresh Kumar
2022-03-14 6:54 ` Kuldeep Singh [this message]
2022-03-14 7:31 ` Viresh Kumar
2022-03-14 10:27 ` Arnd Bergmann
2022-03-14 10:43 ` Viresh Kumar
2022-03-12 18:06 ` [PATCH 2/2] ARM: dts: lpc18xx: " Kuldeep Singh
2022-03-23 17:52 ` Kuldeep Singh
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=20220314065434.GA43329@9a2d8922b8f1 \
--to=singh.kuldeep87k@gmail.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shiraz.linux.kernel@gmail.com \
--cc=soc@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@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).