From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
Cc: "Philipp Zabel" <p.zabel@pengutronix.de>,
"Heiko Stübner" <heiko@sntech.de>,
"Arnd Bergmann" <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: sram: extend usage of reserved partitions
Date: Sun, 20 Sep 2015 22:30:14 -0700 [thread overview]
Message-ID: <20150921053014.GE24350@kroah.com> (raw)
In-Reply-To: <1439156402-10207-2-git-send-email-vladimir_zapolskiy@mentor.com>
On Mon, Aug 10, 2015 at 12:40:02AM +0300, Vladimir Zapolskiy wrote:
> This change adds functionality to operate on reserved SRAM partitions
> described in device tree file. Two partition properties are added,
> "pool" and "export", the first one allows to share a specific partition
> for usage by a kernel consumer in the same manner as it is done for
> the whole SRAM device, and "export" property provides access to some
> SRAM area from userspace over sysfs interface. Practically it is
> possible to specify both properties for an SRAM partition, however
> simultaneous access from a kernel consumer and from userspace is not
> serialized, but still the combination may be useful for debugging
> purpose.
This scares me, why do we need to partition sram off in this manner?
What uses it in this way?
I need some other people to weigh in on this, and at the very least, I
need some DT people to bless the changes there...
thanks,
greg k-h
next prev parent reply other threads:[~2015-09-21 5:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-09 21:40 [PATCH] misc: sram: extend usage of reserved partitions Vladimir Zapolskiy
2015-08-09 21:40 ` Vladimir Zapolskiy
2015-08-10 3:27 ` Greg Kroah-Hartman
2015-08-10 10:47 ` Vladimir Zapolskiy
2015-09-15 14:47 ` Vladimir Zapolskiy
2015-09-21 5:30 ` Greg Kroah-Hartman [this message]
2015-09-21 12:40 ` Vladimir Zapolskiy
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=20150921053014.GE24350@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=vladimir_zapolskiy@mentor.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