From: Kieran Bingham <kieran@bingham.xyz>
To: horms@verge.net.au, linux-renesas-soc@vger.kernel.org
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
catalin.marinas@arm.com, magnus.damm@gmail.com,
linux-kernel@vger.kernel.org, will.deacon@arm.com,
robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] arm64: dts: r8a7795: add FDP1 device nodes
Date: Fri, 1 Jul 2016 15:37:23 +0100 [thread overview]
Message-ID: <57768023.8010507@bingham.xyz> (raw)
In-Reply-To: <1467293563-940-3-git-send-email-kieran@bingham.xyz>
Hi Simon,
The bindings for this have now been acked by RobH.
--
Cheers
Kieran
On 30/06/16 14:32, Kieran Bingham wrote:
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Signed-off-by: Kieran Bingham <kieran@bingham.xyz>
> --
> changes for v2
> - channel labels dropped
>
> arch/arm64/boot/dts/renesas/r8a7795.dtsi | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> index a451bd217f05..8bc87e09efd7 100644
> --- a/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> @@ -1443,5 +1443,32 @@
> clocks = <&cpg CPG_MOD 613>;
> power-domains = <&sysc R8A7795_PD_A3VP>;
> };
> +
> + fdp1@fe940000 {
> + compatible = "renesas,fdp1";
> + reg = <0 0xfe940000 0 0x2400>;
> + interrupts = <GIC_SPI 262 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&cpg CPG_MOD 119>;
> + power-domains = <&sysc R8A7795_PD_A3VP>;
> + renesas,fcp = <&fcpf0>;
> + };
> +
> + fdp1@fe944000 {
> + compatible = "renesas,fdp1";
> + reg = <0 0xfe944000 0 0x2400>;
> + interrupts = <GIC_SPI 263 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&cpg CPG_MOD 118>;
> + power-domains = <&sysc R8A7795_PD_A3VP>;
> + renesas,fcp = <&fcpf1>;
> + };
> +
> + fdp1@fe948000 {
> + compatible = "renesas,fdp1";
> + reg = <0 0xfe948000 0 0x2400>;
> + interrupts = <GIC_SPI 264 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&cpg CPG_MOD 117>;
> + power-domains = <&sysc R8A7795_PD_A3VP>;
> + renesas,fcp = <&fcpf2>;
> + };
> };
> };
>
next prev parent reply other threads:[~2016-07-01 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 13:32 [PATCH v2 0/2] arm64: dts: r8a7795: FCPF and FDP1 device nodes Kieran Bingham
2016-06-30 13:32 ` [PATCH 1/2] arm64: dts: r8a7795: add FCPF " Kieran Bingham
2016-06-30 13:32 ` [PATCH 2/2] arm64: dts: r8a7795: add FDP1 " Kieran Bingham
2016-07-01 14:37 ` Kieran Bingham [this message]
2016-07-04 12:45 ` Simon Horman
-- strict thread matches above, loose matches on Subject: below --
2016-06-09 16:56 [RESEND PATCH 0/2] arm64: dts: r8a7795: Add FCPF and " Kieran Bingham
2016-06-09 16:56 ` [PATCH 2/2] arm64: dts: r8a7795: add " Kieran Bingham
2016-06-10 7:31 ` Geert Uytterhoeven
[not found] <1465490569-31177-1-git-send-email-kieran@bingham.xyz>
2016-06-09 16:42 ` Kieran Bingham
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=57768023.8010507@bingham.xyz \
--to=kieran@bingham.xyz \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.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).