From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: soc@kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] DT updates for dma-names ordering checks
Date: Sat, 26 Mar 2022 09:53:08 +0530 [thread overview]
Message-ID: <20220326042313.97862-1-singh.kuldeep87k@gmail.com> (raw)
This patchset attempts to fix DTs possessing dma ordering issues.
The motivation of the series is taken from a discussion done before.
Link: https://lore.kernel.org/linux-devicetree/20220323175920.93155-1-singh.kuldeep87k@gmail.com/
Just a quick summary for new visitors.
There are few DTs which require dma ordering in order to resolve below
'make dtbs_check' issues and this patchset is in direction to fix that.
dma-names:0: 'rx' was expected
dma-names:0: 'tx' was expected
Kuldeep Singh (4):
ARM: dts: spear13xx: Update SPI dma properties
ARM: dts: spear1340: Update serial node properties
arm64: dts: ls1043a: Update i2c dma properties
arm64: dts: ls1046a: Update i2c node dma properties
arch/arm/boot/dts/spear1340.dtsi | 6 +++---
arch/arm/boot/dts/spear13xx.dtsi | 6 +++---
arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi | 6 +++---
arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 6 +++---
4 files changed, 12 insertions(+), 12 deletions(-)
--
2.25.1
next reply other threads:[~2022-03-26 4:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 4:23 Kuldeep Singh [this message]
2022-03-26 4:23 ` [PATCH 1/4] ARM: dts: spear13xx: Update SPI dma properties Kuldeep Singh
2022-03-26 4:23 ` [PATCH 2/4] ARM: dts: spear1340: Update serial node properties Kuldeep Singh
2022-03-28 2:08 ` Viresh Kumar
2022-03-26 4:23 ` [PATCH 3/4] arm64: dts: ls1043a: Update i2c dma properties Kuldeep Singh
2022-03-26 4:23 ` [PATCH 4/4] arm64: dts: ls1046a: Update i2c node " 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=20220326042313.97862-1-singh.kuldeep87k@gmail.com \
--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=soc@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).