All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
To: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: [PATCH v3 0/4] allwinner: a64: add SRAM controller / system control
Date: Fri, 15 Jun 2018 11:14:13 +0200	[thread overview]
Message-ID: <20180615091413.pbdtrpa7txe6i4ee@flea> (raw)
In-Reply-To: <20180614153548.9644-1-wens-jdAy2FN1RRM@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

On Thu, Jun 14, 2018 at 11:35:44PM +0800, Chen-Yu Tsai wrote:
> Hi,
> 
> This series is the remaining A64 syscon changes from the R40 DWMAC
> series. The series aligns how the A64 system control exports a regmap
> for the sun8i DWMAC driver to access with what we've done for the R40.
> 
> Originally the A64 used the generic syscon for this bit of hardware.
> But this block also contains mapping bits for the onboard SRAM, used
> by various peripherals, and other vendor specific bits we may use in
> the future. It is by no means generic. And we already have a device
> tree binding and driver for the SRAM part.
> 
> The first patch make the SRAM control device export a regmap, exposing
> a single EMAC control register, for the DWMAC driver to consume.
> 
> The second and third patches rename the A64 compatible string to read
> "system control", which is what the block is named in the user manual.
> 
> The last patch fixes up the device node, and also adds the lone mappable
> SRAM block, which is needed by the Display Engine.

For the serie:
Acked-by: Maxime Ripard <maxime.ripard-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>

Maxime

-- 
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

WARNING: multiple messages have this Message-ID (diff)
From: maxime.ripard@bootlin.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] allwinner: a64: add SRAM controller / system control
Date: Fri, 15 Jun 2018 11:14:13 +0200	[thread overview]
Message-ID: <20180615091413.pbdtrpa7txe6i4ee@flea> (raw)
In-Reply-To: <20180614153548.9644-1-wens@csie.org>

On Thu, Jun 14, 2018 at 11:35:44PM +0800, Chen-Yu Tsai wrote:
> Hi,
> 
> This series is the remaining A64 syscon changes from the R40 DWMAC
> series. The series aligns how the A64 system control exports a regmap
> for the sun8i DWMAC driver to access with what we've done for the R40.
> 
> Originally the A64 used the generic syscon for this bit of hardware.
> But this block also contains mapping bits for the onboard SRAM, used
> by various peripherals, and other vendor specific bits we may use in
> the future. It is by no means generic. And we already have a device
> tree binding and driver for the SRAM part.
> 
> The first patch make the SRAM control device export a regmap, exposing
> a single EMAC control register, for the DWMAC driver to consume.
> 
> The second and third patches rename the A64 compatible string to read
> "system control", which is what the block is named in the user manual.
> 
> The last patch fixes up the device node, and also adds the lone mappable
> SRAM block, which is needed by the Display Engine.

For the serie:
Acked-by: Maxime Ripard <maxime.ripard@bootlin.com>

Maxime

-- 
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180615/9fbf8015/attachment.sig>

  parent reply	other threads:[~2018-06-15  9:14 UTC|newest]

Thread overview: 40+ 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 ` Chen-Yu Tsai
     [not found] ` <20180614153548.9644-1-wens-jdAy2FN1RRM@public.gmane.org>
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     ` 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-14 15:35     ` Chen-Yu Tsai
     [not found]     ` <20180614153548.9644-3-wens-jdAy2FN1RRM@public.gmane.org>
2018-06-20 18:04       ` Rob Herring
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     ` 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 15:35     ` Chen-Yu Tsai
     [not found]     ` <20180614153548.9644-5-wens-jdAy2FN1RRM@public.gmane.org>
2018-06-14 17:09       ` Jagan Teki
2018-06-14 17:09         ` [linux-sunxi] " Jagan Teki
     [not found]         ` <CAMty3ZARNpBOQKvS7knH8kWE2+bvjuJoAA4cFGZK8+GzTUQ5zA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-06-14 17:27           ` Jernej Škrabec
2018-06-14 17:27             ` [linux-sunxi] " Jernej Škrabec
2018-06-14 23:09             ` Icenowy Zheng
2018-06-14 23:09               ` [linux-sunxi] " Icenowy Zheng
     [not found]               ` <5C14D945-0795-4100-86E2-6FBF04350715-h8G6r0blFSE@public.gmane.org>
2018-06-19  7:36                 ` Jagan Teki
2018-06-19  7:36                   ` [linux-sunxi] " Jagan Teki
     [not found]                   ` <CAMty3ZCsPXh7Fhmhtd7UjTmJ9id+NeaZDVqkix1iQz7-fDqoUw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-06-19 14:27                     ` Icenowy Zheng
2018-06-19 14:27                       ` [linux-sunxi] " Icenowy Zheng
2018-06-15  9:14   ` Maxime Ripard [this message]
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  2:11       ` Chen-Yu Tsai
     [not found]       ` <CAGb2v64Ar+rOgiXbjtRrQojHUZteLa9N7OwM3XY7ZcpS87Qpmw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-06-18  7:34         ` Maxime Ripard
2018-06-18  7:34           ` Maxime Ripard
2018-06-19 15:20           ` Chen-Yu Tsai
2018-06-19 15:20             ` Chen-Yu Tsai
2018-08-20  7:42 ` Emmanuel Vadot
2018-08-20  7:42   ` Emmanuel Vadot
     [not found]   ` <20180820094210.6d856029d51dad480782a783-xXdDKFdH5B3kFDPD4ZthVA@public.gmane.org>
2018-08-20  8:41     ` Chen-Yu Tsai
2018-08-20  8:41       ` Chen-Yu Tsai
2018-08-20 14:01       ` Emmanuel Vadot
2018-08-20 14:01         ` Emmanuel Vadot
     [not found]         ` <20180820160149.65771a35c5b46f5ddb483428-xXdDKFdH5B3kFDPD4ZthVA@public.gmane.org>
2018-08-20 14:25           ` Chen-Yu Tsai
2018-08-20 14:25             ` Chen-Yu Tsai
2018-08-20 14:29             ` Emmanuel Vadot
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=20180615091413.pbdtrpa7txe6i4ee@flea \
    --to=maxime.ripard-ldxbnhwyfcjbdgjk7y7tuq@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=wens-jdAy2FN1RRM@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.