From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] drivers: soc: sunxi: Introduce SoC driver to map SRAMs
Date: Mon, 01 Jun 2015 17:58:26 +0200 [thread overview]
Message-ID: <4341126.tsXmi47bFP@wuerfel> (raw)
In-Reply-To: <1433149466-17013-1-git-send-email-maxime.ripard@free-electrons.com>
On Monday 01 June 2015 11:04:26 Maxime Ripard wrote:
> The Allwinner SoCs have a handful of SRAM that can be either mapped to be
> accessible by devices or the CPU.
>
> That mapping is controlled by an SRAM controller, and that mapping might
> not be set by the bootloader, for example if the device wasn't used at all,
> or if we're using solutions like the U-Boot's Falcon Boot.
>
> We could also imagine changing this at runtime for example to change the
> mapping of these SRAMs to use them for suspend/resume or runtime memory
> rate change, if that ever happens.
>
> These use cases require some API in the kernel to control that mapping,
> exported through a drivers/soc driver.
>
> This driver also implement a debugfs file that shows the SRAM found in the
> system, the current mapping and the SRAM that have been claimed by some
> drivers in the kernel.
>
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
> Acked-by: Hans de Goede <hdegoede@redhat.com>
> Tested-by: Hans de Goede <hdegoede@redhat.com>
> ---
>
> Hi Arnd, Kevin, Olof,
>
> Could you please apply directly this patch to your tree?
>
> It's the only driver related patch that should come in for this release
> cycle.
>
Applied to next/drivers. Thanks for your hard work to get it adapted to all
my wishes over your weekend, very much appreciated.
Arnd
next prev parent reply other threads:[~2015-06-01 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 9:04 [PATCH v4] drivers: soc: sunxi: Introduce SoC driver to map SRAMs Maxime Ripard
2015-06-01 15:58 ` Arnd Bergmann [this message]
2015-06-01 16:07 ` Maxime Ripard
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=4341126.tsXmi47bFP@wuerfel \
--to=arnd@arndb.de \
--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