[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190820165826.GF4738@sirena.co.uk>
Date: Tue, 20 Aug 2019 17:58:26 +0100
From: Mark Brown <broonie@...nel.org>
To: John Garry <john.garry@...wei.com>
Cc: Vignesh Raghavendra <vigneshr@...com>,
Schrempf Frieder <frieder.schrempf@...tron.de>,
"corbet@....net" <corbet@....net>,
"mchehab+samsung@...nel.org" <mchehab+samsung@...nel.org>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"marek.vasut@...il.com" <marek.vasut@...il.com>,
"tudor.ambarus@...rochip.com" <tudor.ambarus@...rochip.com>,
"miquel.raynal@...tlin.com" <miquel.raynal@...tlin.com>,
"richard@....at" <richard@....at>,
wanghuiqiang <wanghuiqiang@...wei.com>
Subject: Re: [PATCH] docs: mtd: Update spi nor reference driver
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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists