From: "Heiko Stübner" <heiko@sntech.de>
To: Huibin Hong <huibin.hong@rock-chips.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
catalin.marinas@arm.com, will.deacon@arm.com, wxt@rock-chips.com,
andy.yan@rock-chips.com, felipe.balbi@linux.intel.com,
jic23@kernel.org, jh80.chung@samsung.com, johnyoun@synopsys.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: add dmac nodes for rk3368 SoCs
Date: Wed, 22 Mar 2017 13:49:36 +0100 [thread overview]
Message-ID: <6714315.k8UebLJmJU@diego> (raw)
In-Reply-To: <1490184194-32051-1-git-send-email-huibin.hong@rock-chips.com>
Hi,
Am Mittwoch, 22. März 2017, 20:03:14 CET schrieb Huibin Hong:
> Add dmac bus and dmac peri dts nodes for peripherals,
> such as I2S, SPI, UART and so on.
>
> Signed-off-by: Huibin Hong <huibin.hong@rock-chips.com>
I applied that patch already in [0], did something change?
[0] https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/commit/?id=4b4c0db538fa6e3f31bc40ddc17c1d5facb49d36
> ---
> arch/arm64/boot/dts/rockchip/rk3368.dtsi | 29 +++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3368.dtsi
> b/arch/arm64/boot/dts/rockchip/rk3368.dtsi index a635adc..2a0422f 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3368.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3368.dtsi
> @@ -189,6 +189,35 @@
> };
> };
>
> + amba {
> + compatible = "simple-bus";
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + dmac_peri: dma-controller@ff250000 {
> + compatible = "arm,pl330", "arm,primecell";
> + reg = <0x0 0xff250000 0x0 0x4000>;
> + interrupts = <GIC_SPI 2 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 3 IRQ_TYPE_LEVEL_HIGH>;
> + #dma-cells = <1>;
> + clocks = <&cru ACLK_DMAC_PERI>;
> + clock-names = "apb_pclk";
> + arm,pl330-broken-no-flushp;
> + };
> +
> + dmac_bus: dma-controller@ff600000 {
> + compatible = "arm,pl330", "arm,primecell";
> + reg = <0x0 0xff600000 0x0 0x4000>;
> + interrupts = <GIC_SPI 0 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 1 IRQ_TYPE_LEVEL_HIGH>;
> + #dma-cells = <1>;
> + clocks = <&cru ACLK_DMAC_BUS>;
> + clock-names = "apb_pclk";
> + arm,pl330-broken-no-flushp;
> + };
> + };
> +
> arm-pmu {
> compatible = "arm,armv8-pmuv3";
> interrupts = <GIC_SPI 112 IRQ_TYPE_LEVEL_HIGH>,
next prev parent reply other threads:[~2017-03-22 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 12:03 [PATCH] arm64: dts: rockchip: add dmac nodes for rk3368 SoCs Huibin Hong
2017-03-22 12:49 ` Heiko Stübner [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-03 9:49 Huibin Hong
2017-03-17 11:04 ` Heiko Stuebner
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=6714315.k8UebLJmJU@diego \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=felipe.balbi@linux.intel.com \
--cc=huibin.hong@rock-chips.com \
--cc=jh80.chung@samsung.com \
--cc=jic23@kernel.org \
--cc=johnyoun@synopsys.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.com \
--cc=wxt@rock-chips.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;
as well as URLs for NNTP newsgroup(s).