public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: jernej.skrabec@gmail.com (Jernej Škrabec)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] [PATCH v3 4/4] arm64: dts: allwinner: a64: add SRAM controller device tree node
Date: Thu, 14 Jun 2018 19:27:21 +0200	[thread overview]
Message-ID: <2687631.x8iGEoiUx5@jernej-laptop> (raw)
In-Reply-To: <CAMty3ZARNpBOQKvS7knH8kWE2+bvjuJoAA4cFGZK8+GzTUQ5zA@mail.gmail.com>

Dne ?etrtek, 14. junij 2018 ob 19:09:56 CEST je Jagan Teki napisal(a):
> On Thu, Jun 14, 2018 at 9:05 PM, Chen-Yu Tsai <wens@csie.org> wrote:
> > From: Icenowy Zheng <icenowy@aosc.io>
> > 
> > Allwinner A64 has a SRAM controller, and in the device tree currently
> > we have a syscon node to enable EMAC driver to access the EMAC clock
> > register. As SRAM controller driver can now export regmap for this
> > register, replace the syscon node to the SRAM controller device node,
> > and let EMAC driver to acquire its EMAC clock regmap.
> > 
> > Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
> > [wens at csie.org: Updated compatible string]
> > Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> > ---
> > 
> >  arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 19 +++++++++++++++++--
> >  1 file changed, 17 insertions(+), 2 deletions(-)
> > 
> > diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi
> > b/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi index
> > 1b2ef28c42bd..87968dafe1dc 100644
> > --- a/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi
> > +++ b/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi
> > @@ -169,9 +169,24 @@
> > 
> >                 ranges;
> >                 
> >                 syscon: syscon at 1c00000 {
> > 
> > -                       compatible =
> > "allwinner,sun50i-a64-system-controller", -                              
> > "syscon";
> > +                       compatible =
> > "allwinner,sun50i-a64-system-control";
> > 
> >                         reg = <0x01c00000 0x1000>;
> > 
> > +                       #address-cells = <1>;
> > +                       #size-cells = <1>;
> > +                       ranges;
> > +
> > +                       sram_c: sram at 18000 {
> > +                               compatible = "mmio-sram";
> > +                               reg = <0x00018000 0x28000>;
> > +                               #address-cells = <1>;
> > +                               #size-cells = <1>;
> > +                               ranges = <0 0x00018000 0x28000>;
> > +
> > +                               de2_sram: sram-section at 0 {
> 
> So, this can attach to display-engine node through allwinner,sram and
> add support to claim the sram on sun4i/sun4i_drv.c, correct?

Actually, it has to be added to display_clocks node and claimed in drivers/
clk/sunxi-ng/ccu-sun8i-de2.c

Best regards,
Jernej

  reply	other threads:[~2018-06-14 17:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-14 15:35 [PATCH v3 0/4] allwinner: a64: add SRAM controller / system control Chen-Yu Tsai
2018-06-14 15:35 ` [PATCH v3 1/4] soc: sunxi: export a regmap for EMAC clock reg on A64 Chen-Yu Tsai
2018-06-14 15:35 ` [PATCH v3 2/4] dt-bindings: sram: Rename A64 SRAM controller compatible Chen-Yu Tsai
2018-06-20 18:04   ` Rob Herring
2018-06-14 15:35 ` [PATCH v3 3/4] soc: sunxi: sram: Add updated compatible string for A64 system control Chen-Yu Tsai
2018-06-14 15:35 ` [PATCH v3 4/4] arm64: dts: allwinner: a64: add SRAM controller device tree node Chen-Yu Tsai
2018-06-14 17:09   ` [linux-sunxi] " Jagan Teki
2018-06-14 17:27     ` Jernej Škrabec [this message]
2018-06-14 23:09       ` Icenowy Zheng
2018-06-19  7:36         ` Jagan Teki
2018-06-19 14:27           ` Icenowy Zheng
2018-06-15  9:14 ` [PATCH v3 0/4] allwinner: a64: add SRAM controller / system control Maxime Ripard
2018-06-18  2:11   ` Chen-Yu Tsai
2018-06-18  7:34     ` Maxime Ripard
2018-06-19 15:20       ` Chen-Yu Tsai
2018-08-20  7:42 ` Emmanuel Vadot
2018-08-20  8:41   ` Chen-Yu Tsai
2018-08-20 14:01     ` Emmanuel Vadot
2018-08-20 14:25       ` Chen-Yu Tsai
2018-08-20 14:29         ` Emmanuel Vadot

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=2687631.x8iGEoiUx5@jernej-laptop \
    --to=jernej.skrabec@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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