From: "Rob Herring (Arm)" <robh@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Nuno Sa <nuno.sa@analog.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>,
Vinod Koul <vkoul@kernel.org>,
devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v2 2/2] dt-bindings: dma: adi,axi-dmac: deprecate adi,channels node
Date: Wed, 30 Oct 2024 16:19:34 -0500 [thread overview]
Message-ID: <173032314856.2055121.10271317801673936435.robh@kernel.org> (raw)
In-Reply-To: <20241029-axi-dma-dt-yaml-v2-2-52a6ec7df251@baylibre.com>
On Tue, 29 Oct 2024 14:29:15 -0500, David Lechner wrote:
> Deprecate the adi,channels node in the adi,axi-dmac binding. Prior to
> IP version 4.3.a, this information was required. Since then, there are
> memory-mapped registers that can be read to get the same information.
>
> Acked-by: Nuno Sa <nuno.sa@analog.com>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
> ---
>
> For context, the adi,channels node has not been required in the Linux
> kernel since [1].
>
> [1]: https://lore.kernel.org/all/20200825151950.57605-7-alexandru.ardelean@analog.com/
> ---
> .../devicetree/bindings/dma/adi,axi-dmac.yaml | 19 +++++--------------
> 1 file changed, 5 insertions(+), 14 deletions(-)
>
With 'required' fixed:
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
prev parent reply other threads:[~2024-10-30 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 19:29 [PATCH v2 0/2] dt-bindings: dma: adi,axi-dmac: convert to yaml and update David Lechner
2024-10-29 19:29 ` [PATCH v2 1/2] dt-bindings: dma: adi,axi-dmac: convert to yaml schema David Lechner
2024-10-29 20:42 ` Rob Herring (Arm)
2024-10-30 21:18 ` Rob Herring (Arm)
2024-10-29 19:29 ` [PATCH v2 2/2] dt-bindings: dma: adi,axi-dmac: deprecate adi,channels node David Lechner
2024-10-29 20:42 ` Rob Herring (Arm)
2024-10-29 21:00 ` David Lechner
2024-10-30 21:19 ` Rob Herring (Arm) [this message]
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=173032314856.2055121.10271317801673936435.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=dmaengine@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=vkoul@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
all inboxes | Powered by JetHome®