From: Rob Herring <robh@kernel.org>
To: Zong Li <zong.li@sifive.com>
Cc: robh+dt@kernel.org, dmaengine@vger.kernel.org,
geert@linux-m68k.org, green.wan@sifive.com,
aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
palmer@dabbelt.com, vkoul@kernel.org, devicetree@vger.kernel.org,
bin.meng@windriver.com, Palmer Dabbelt <palmer@rivosinc.com>,
krzysztof.kozlowski@canonical.com, conor.dooley@microchip.com,
paul.walmsley@sifive.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/3] dt-bindings: Add dma-channels property and modify compatible
Date: Mon, 7 Feb 2022 14:09:41 -0600 [thread overview]
Message-ID: <YgF8hR7YO3B3QI+S@robh.at.kernel.org> (raw)
In-Reply-To: <30430019105af445d52b7a48331c106f8e6d6816.1644215230.git.zong.li@sifive.com>
On Mon, 07 Feb 2022 14:30:38 +0800, Zong Li wrote:
> Add dma-channels property, then we can determine how many channels there
> by device tree, rather than statically defining it in PDMA driver.
> In addition, we also modify the compatible for PDMA versioning scheme.
>
> Signed-off-by: Zong Li <zong.li@sifive.com>
> Suggested-by: Palmer Dabbelt <palmer@rivosinc.com>
> ---
> .../bindings/dma/sifive,fu540-c000-pdma.yaml | 19 +++++++++++++++++--
> 1 file changed, 17 insertions(+), 2 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-02-07 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 6:30 [PATCH v5 0/3] Determine the number of DMA channels by 'dma-channels' property Zong Li
2022-02-07 6:30 ` [PATCH v5 1/3] dt-bindings: Add dma-channels property and modify compatible Zong Li
2022-02-07 20:09 ` Rob Herring [this message]
2022-03-03 20:43 ` Palmer Dabbelt
2022-02-07 6:30 ` [PATCH v5 2/3] riscv: dts: " Zong Li
2022-02-07 6:30 ` [PATCH v5 3/3] dmaengine: sf-pdma: Get number of channel by device tree Zong Li
2022-02-15 12:06 ` Vinod Koul
2022-02-16 6:52 ` Zong Li
2022-03-03 20:43 ` Palmer Dabbelt
2022-03-04 8:52 ` Zong Li
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=YgF8hR7YO3B3QI+S@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=bin.meng@windriver.com \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=green.wan@sifive.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
--cc=zong.li@sifive.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