linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: defconfig: enable Generic on-chip SRAM driver
Date: Mon, 20 Jun 2016 17:34:49 +0100	[thread overview]
Message-ID: <1466440489.2833.41.camel@linaro.org> (raw)
In-Reply-To: <1466437295-30553-1-git-send-email-sudeep.holla@arm.com>

On Mon, 2016-06-20 at 16:41 +0100, Sudeep Holla wrote:
> Most of the ARM SoCs have small SRAM memory used for various purposes
> that require faster access to data compared to normal DDR.
> 
> This patch enables the Generic on-chip SRAM driver on ARM64.

Would this cause things in the kernel to automatically start using SRAM
found in device-tree, or would each use need to be added explicitly?
I'm just wondering if we might start seeing new bugs caused by firmware
using SRAM for special purposes but that memory not being properly
reserved or hidden from the kernel.

-- 
Tixy

  reply	other threads:[~2016-06-20 16:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 15:41 [PATCH] arm64: defconfig: enable Generic on-chip SRAM driver Sudeep Holla
2016-06-20 16:34 ` Jon Medhurst (Tixy) [this message]
2016-06-20 16:39   ` Sudeep Holla

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=1466440489.2833.41.camel@linaro.org \
    --to=tixy@linaro.org \
    --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;
as well as URLs for NNTP newsgroup(s).