From: Rob Herring <robh@kernel.org>
To: Paul Cercueil <paul@crapouillou.net>
Cc: linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
list@opendingux.net, linux-kernel@vger.kernel.org,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: clk/ingenic: Add MDMA and BDMA clocks
Date: Wed, 22 Dec 2021 14:11:07 -0400 [thread overview]
Message-ID: <YcNqOwjYQT8GTwqD@robh.at.kernel.org> (raw)
In-Reply-To: <20211220193319.114974-2-paul@crapouillou.net>
On Mon, 20 Dec 2021 19:33:18 +0000, Paul Cercueil wrote:
> The Ingenic JZ4760 and JZ4770 both have an extra DMA core named BDMA
> dedicated to the NAND and BCH controller, but which can also do
> memory-to-memory transfers. The JZ4760 additionally has a DMA core named
> MDMA dedicated to memory-to-memory transfers. The programming manual for
> the JZ4770 does have a bit for a MDMA clock, but does not seem to have
> the hardware wired in.
>
> Add macros for the MDMA and BDMA clocks to the dt-bindings include
> files, so that they can be used within Device Tree files.
>
> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
> ---
>
> Notes:
> v3: New patch
>
> include/dt-bindings/clock/ingenic,jz4760-cgu.h | 2 ++
> include/dt-bindings/clock/ingenic,jz4770-cgu.h | 1 +
> 2 files changed, 3 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-12-22 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 19:33 [PATCH v3 0/2] clk: ingenic: Add MDMA and BDMA clocks Paul Cercueil
2021-12-20 19:33 ` [PATCH v3 1/2] dt-bindings: clk/ingenic: " Paul Cercueil
2021-12-22 18:11 ` Rob Herring [this message]
2022-01-07 1:51 ` Stephen Boyd
2021-12-20 19:33 ` [PATCH v3 2/2] clk: ingenic: " Paul Cercueil
2022-01-07 1:52 ` Stephen Boyd
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=YcNqOwjYQT8GTwqD@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=list@opendingux.net \
--cc=mturquette@baylibre.com \
--cc=paul@crapouillou.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).