From: Mark Brown <broonie@kernel.org>
To: John Garry <john.garry@huawei.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"richard@nod.at" <richard@nod.at>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Schrempf Frieder <frieder.schrempf@kontron.de>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"tudor.ambarus@microchip.com" <tudor.ambarus@microchip.com>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"mchehab+samsung@kernel.org" <mchehab+samsung@kernel.org>,
wanghuiqiang <wanghuiqiang@huawei.com>
Subject: Re: [PATCH] docs: mtd: Update spi nor reference driver
Date: Tue, 20 Aug 2019 17:58:26 +0100 [thread overview]
Message-ID: <20190820165826.GF4738@sirena.co.uk> (raw)
In-Reply-To: <c5e063e8-5025-8206-f819-6ce5228ef0fb@huawei.com>
[-- Attachment #1.1: Type: text/plain, Size: 919 bytes --]
On Tue, Aug 20, 2019 at 03:09:15PM +0100, John Garry wrote:
> On 19/08/2019 05:39, Vignesh Raghavendra wrote:
> > On 16/08/19 3:50 PM, John Garry wrote:
> > > About the child spi flash devices, is the recommendation to just use
> > > PRP0001 HID and "jedec,spi-nor" compatible?
> > I am not quite familiar with ACPI systems, but child flash device should
> > use "jedec,spi-nor" as compatible.
> Right, so to use SPI MEM framework, it looks like I will have to use PRP0001
> and "jedec,spi-nor" as compatible.
> My reluctance in using PRP0001 and compatible "jedec,spi-nor" is how other
> OS can understand this.
Last I heard Windows wasn't doing anything with PRP0001 but on the other
hand the idiomatic way to handle this for ACPI is as far as I can tell
to have what is essentially a board file loaded based on DMI information
without any real enumerability so there's no real conflict between the
two methods.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 144 bytes --]
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-08-20 16:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 16:06 [PATCH] docs: mtd: Update spi nor reference driver John Garry
2019-08-06 16:35 ` John Garry
2019-08-06 16:40 ` Schrempf Frieder
2019-08-16 10:20 ` John Garry
2019-08-19 4:39 ` Vignesh Raghavendra
2019-08-20 14:09 ` John Garry
2019-08-20 16:58 ` Mark Brown [this message]
2019-08-21 13:39 ` John Garry
2019-09-06 14:52 ` Jonathan Corbet
2019-09-06 14:58 ` John Garry
2019-09-06 15:03 ` Jonathan Corbet
2019-09-06 15:10 ` Tudor.Ambarus
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=20190820165826.GF4738@sirena.co.uk \
--to=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=frieder.schrempf@kontron.de \
--cc=john.garry@huawei.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mchehab+samsung@kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--cc=vigneshr@ti.com \
--cc=wanghuiqiang@huawei.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;
as well as URLs for NNTP newsgroup(s).