From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Ray Jui <rjui@broadcom.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Scott Branden <sbranden@broadcom.com>,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Liviu Dudau <liviu.dudau@arm.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Dinh Nguyen <dinguyen@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Broadcom Kernel Team <bcm-kernel-feedback-list@broadcom.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Michal Simek <michal.simek@xilinx.com>,
linux-arm-kernel@lists.infradead.org
Cc: Rob Herring <robh@kernel.org>
Subject: Re: (subset) [PATCH v2 1/9] ARM: dts: zynq-7000: drop useless 'dma-channels/requests' properties
Date: Wed, 4 May 2022 10:30:30 +0200 [thread overview]
Message-ID: <165165303187.30033.4858903817618284357.b4-ty@linaro.org> (raw)
In-Reply-To: <20220430121902.59895-2-krzysztof.kozlowski@linaro.org>
On Sat, 30 Apr 2022 14:18:54 +0200, Krzysztof Kozlowski wrote:
> The pl330 DMA controller provides number of DMA channels and requests
> through its registers, so duplicating this information (with a chance of
> mistakes) in DTS is pointless. Additionally the DTS used always wrong
> property names which causes DT schema check failures - the bindings
> documented 'dma-channels' and 'dma-requests' properties without leading
> hash sign.
>
> [...]
Applied, thanks!
[1/9] ARM: dts: zynq-7000: drop useless 'dma-channels/requests' properties
commit: 0501eeca5aedab16a0dc4fd25135eb18d9408f80
Best regards,
--
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
next prev parent reply other threads:[~2022-05-04 8:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 12:18 [PATCH v2 0/9] ARM/arm64: dts: " Krzysztof Kozlowski
2022-04-30 12:18 ` [PATCH v2 1/9] ARM: dts: zynq-7000: " Krzysztof Kozlowski
2022-05-02 7:27 ` Michal Simek
2022-05-02 7:28 ` Krzysztof Kozlowski
2022-05-04 8:30 ` Krzysztof Kozlowski [this message]
2022-04-30 12:18 ` [PATCH v2 2/9] ARM: dts: socfpga: " Krzysztof Kozlowski
2022-05-04 8:30 ` (subset) " Krzysztof Kozlowski
2022-04-30 12:18 ` [PATCH v2 3/9] arm64: dts: stratix10/agilex: " Krzysztof Kozlowski
2022-05-04 8:30 ` (subset) " Krzysztof Kozlowski
2022-04-30 12:18 ` [PATCH v2 4/9] arm64: dts: juno: " Krzysztof Kozlowski
2022-05-03 8:04 ` (subset) " Sudeep Holla
2022-04-30 12:18 ` [PATCH v2 5/9] arm64: dts: broadcom: " Krzysztof Kozlowski
2022-05-04 8:30 ` (subset) " Krzysztof Kozlowski
2022-04-30 12:18 ` [PATCH v2 6/9] ARM: dts: s5pv210: " Krzysztof Kozlowski
2022-05-04 8:30 ` (subset) " Krzysztof Kozlowski
2022-04-30 12:19 ` [PATCH v2 7/9] ARM: dts: exynos: " Krzysztof Kozlowski
2022-05-04 8:30 ` (subset) " Krzysztof Kozlowski
2022-04-30 12:19 ` [PATCH v2 8/9] arm64: " Krzysztof Kozlowski
2022-05-04 8:30 ` (subset) " Krzysztof Kozlowski
2022-04-30 12:19 ` [PATCH v2 9/9] arm64: dts: fsd: " Krzysztof Kozlowski
2022-05-04 8:30 ` (subset) " Krzysztof Kozlowski
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=165165303187.30033.4858903817618284357.b4-ty@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=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=robh@kernel.org \
--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
all inboxes | Powered by JetHome®