From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Dinh Nguyen <dinguyen@kernel.org>,
Michal Simek <michal.simek@xilinx.com>,
Liviu Dudau <liviu.dudau@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Broadcom Kernel Team <bcm-kernel-feedback-list@broadcom.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: [PATCH 00/10] ARM/arm64: dts: use proper 'dma-channels/requests' properties
Date: Wed, 27 Apr 2022 17:58:30 +0200 [thread overview]
Message-ID: <20220427155840.596535-1-krzysztof.kozlowski@linaro.org> (raw)
Hi,
Rob reported [1] that many (all?) PL330 device nodes use wrong dma-channels and
dma-requests properties. The proper ones are without leading '#'.
I guess everything started with 42cf20980cde ("ARM: dts: pl330: Add #dma-cells for
generic dma binding support").
Patches are independent and can be picked-up as is. Otherwise please ack and
I'll push it to SoC.
[1] https://lore.kernel.org/linux-devicetree/fedb56be-f275-aabb-cdf5-dbd394b8a7bd@linaro.org/T/#m6235f451045c337d70a62dc65eab9a716618550b
Best regards,
Krzysztof
Krzysztof Kozlowski (10):
ARM: dts: zynq-7000: use proper 'dma-channels/requests' properties
ARM: dts: socfpga: use proper 'dma-channels/requests' properties
arm64: dts: stratix10/agilex: use proper 'dma-channels/requests'
properties
arm64: dts: juno: use proper 'dma-channels/requests' properties
arm64: dts: broadcom: use proper 'dma-channels/requests' properties
dt-bindings: mfd: samsung,exynos5433-lpass: fix
'dma-channels/requests' properties
ARM: dts: s5pv210: use proper 'dma-channels/requests' properties
ARM: dts: exynos: use proper 'dma-channels/requests' properties
arm64: dts: exynos: use proper 'dma-channels/requests' properties
arm64: dts: fsd: use proper 'dma-channels/requests' properties
.../mfd/samsung,exynos5433-lpass.yaml | 4 ++--
arch/arm/boot/dts/exynos3250.dtsi | 8 ++++----
arch/arm/boot/dts/exynos4.dtsi | 12 +++++------
.../boot/dts/exynos4210-universal_c210.dts | 4 ++--
arch/arm/boot/dts/exynos5250.dtsi | 16 +++++++--------
arch/arm/boot/dts/exynos5410.dtsi | 8 ++++----
arch/arm/boot/dts/exynos5420.dtsi | 20 +++++++++----------
arch/arm/boot/dts/s5pv210.dtsi | 12 +++++------
arch/arm/boot/dts/socfpga.dtsi | 4 ++--
arch/arm/boot/dts/socfpga_arria10.dtsi | 4 ++--
arch/arm/boot/dts/zynq-7000.dtsi | 4 ++--
.../boot/dts/altera/socfpga_stratix10.dtsi | 4 ++--
arch/arm64/boot/dts/arm/juno-base.dtsi | 4 ++--
.../boot/dts/broadcom/northstar2/ns2.dtsi | 4 ++--
.../boot/dts/broadcom/stingray/stingray.dtsi | 4 ++--
arch/arm64/boot/dts/exynos/exynos5433.dtsi | 12 +++++------
arch/arm64/boot/dts/exynos/exynos7.dtsi | 8 ++++----
arch/arm64/boot/dts/intel/socfpga_agilex.dtsi | 4 ++--
arch/arm64/boot/dts/tesla/fsd.dtsi | 16 +++++++--------
19 files changed, 76 insertions(+), 76 deletions(-)
--
2.32.0
next reply other threads:[~2022-04-27 15:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 15:58 Krzysztof Kozlowski [this message]
2022-04-27 15:58 ` [PATCH 01/10] ARM: dts: zynq-7000: use proper 'dma-channels/requests' properties Krzysztof Kozlowski
2022-04-28 6:24 ` Michal Simek
2022-04-27 15:58 ` [PATCH 02/10] ARM: dts: socfpga: " Krzysztof Kozlowski
2022-04-27 15:58 ` [PATCH 03/10] arm64: dts: stratix10/agilex: " Krzysztof Kozlowski
2022-04-27 15:58 ` [PATCH 04/10] arm64: dts: juno: " Krzysztof Kozlowski
2022-04-28 10:43 ` Robin Murphy
2022-04-28 10:45 ` Krzysztof Kozlowski
2022-04-27 15:58 ` [PATCH 05/10] arm64: dts: broadcom: " Krzysztof Kozlowski
2022-04-27 15:58 ` [PATCH 06/10] dt-bindings: mfd: samsung,exynos5433-lpass: fix " Krzysztof Kozlowski
2022-04-27 16:41 ` Alim Akhtar
2022-04-27 18:25 ` Rob Herring
2022-04-28 9:53 ` Lee Jones
2022-04-27 15:58 ` [PATCH 07/10] ARM: dts: s5pv210: use proper " Krzysztof Kozlowski
2022-04-27 16:45 ` Alim Akhtar
2022-04-27 15:58 ` [PATCH 08/10] ARM: dts: exynos: " Krzysztof Kozlowski
2022-04-27 16:44 ` Alim Akhtar
2022-04-28 9:50 ` Marek Szyprowski
2022-04-28 9:54 ` Krzysztof Kozlowski
2022-04-28 9:57 ` Marek Szyprowski
2022-04-28 10:00 ` Krzysztof Kozlowski
2022-04-28 10:05 ` Marek Szyprowski
2022-04-28 10:09 ` Krzysztof Kozlowski
2022-04-28 13:33 ` Rob Herring
2022-04-28 9:55 ` Alim Akhtar
2022-04-27 15:58 ` [PATCH 09/10] arm64: " Krzysztof Kozlowski
2022-04-27 16:46 ` Alim Akhtar
2022-04-27 15:58 ` [PATCH 10/10] arm64: dts: fsd: " Krzysztof Kozlowski
2022-04-27 16:49 ` Alim Akhtar
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=20220427155840.596535-1-krzysztof.kozlowski@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=michal.simek@xilinx.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=sbranden@broadcom.com \
--cc=sudeep.holla@arm.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: 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).