From: Maxime Ripard <maxime@cerno.tech>
To: Jernej Skrabec <jernej.skrabec@siol.net>
Cc: wens@csie.org, mchehab@kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: Re: [PATCH 3/5] arm64: dts: allwinner: a64: Add MBUS controller node
Date: Mon, 27 Jan 2020 15:59:31 +0100 [thread overview]
Message-ID: <20200127145931.rjewha4awnlorfvb@gilmour.lan> (raw)
In-Reply-To: <20200125110353.591658-4-jernej.skrabec@siol.net>
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
Hi,
On Sat, Jan 25, 2020 at 12:03:51PM +0100, Jernej Skrabec wrote:
> A64 contains MBUS, which is the bus used by DMA devices to access
> system memory.
>
> MBUS controller is responsible for arbitration between channels based
> on set priority and can do some other things as well, like report
> bandwidth used. It also maps RAM region to different address than CPU.
>
> Signed-off-by: Jernej Skrabec <jernej.skrabec@siol.net>
> ---
> arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi b/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi
> index 862b47dc9dc9..d225ea1f3b87 100644
> --- a/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi
> +++ b/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi
> @@ -1061,6 +1061,14 @@ pwm: pwm@1c21400 {
> status = "disabled";
> };
>
> + mbus: dram-controller@1c62000 {
> + compatible = "allwinner,sun50i-a64-mbus";
> + reg = <0x01c62000 0x1000>;
> + clocks = <&ccu CLK_MBUS>;
We're merging the clock header patch and the DT through two different
trees, so you can't use it right away. You should use the raw ID here.
(also, as a general remark, it's easier on us to not send the patches
during the rc6 <-> rc1 phase), so if you can resend them as soon as
rc1 is out, that would be great :)
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2020-01-27 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 11:03 [PATCH 0/5] arm64: dts: allwinner: a64: Enable deinterlace core Jernej Skrabec
2020-01-25 11:03 ` [PATCH 1/5] dt-bindings: interconnect: sunxi: Add A64 MBUS compatible Jernej Skrabec
2020-02-03 15:49 ` Rob Herring
2020-01-25 11:03 ` [PATCH 2/5] clk: sunxi-ng: a64: Export MBUS clock Jernej Skrabec
2020-01-25 11:03 ` [PATCH 3/5] arm64: dts: allwinner: a64: Add MBUS controller node Jernej Skrabec
2020-01-27 14:59 ` Maxime Ripard [this message]
2020-01-27 19:05 ` Jernej Škrabec
2020-01-25 11:03 ` [PATCH 4/5] media: dt-bindings: media: Add Allwinner A64 deinterlace compatible Jernej Skrabec
2020-02-03 15:50 ` Rob Herring
2020-01-25 11:03 ` [PATCH 5/5] arm64: dts: allwinner: a64: Add deinterlace core node Jernej Skrabec
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=20200127145931.rjewha4awnlorfvb@gilmour.lan \
--to=maxime@cerno.tech \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).