[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200113114256.GH3897@sirena.org.uk>
Date: Mon, 13 Jan 2020 11:42:56 +0000
From: Mark Brown <broonie@...nel.org>
To: John Garry <john.garry@...wei.com>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
tudor.ambarus@...rochip.com, linux-kernel@...r.kernel.org,
chenxiang66@...ilicon.com, linuxarm@...wei.com,
linux-spi@...r.kernel.org, marek.vasut@...il.com,
linux-mtd@...ts.infradead.org, xuejiancheng@...ilicon.com,
fengsheng5@...wei.com,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
wanghuiqiang <wanghuiqiang@...wei.com>, liusimin4@...wei.com
Subject: Re: [PATCH v2 2/3] spi: Add HiSilicon v3xx SPI NOR flash controller
driver
On Mon, Jan 13, 2020 at 10:09:27AM +0000, John Garry wrote:
> On 10/01/2020 19:31, Andy Shevchenko wrote:
> > PRP method is only for vendors to *test* the hardware in ACPI environment.
> > The proper method is to allocate correct ACPI ID.
> Yes, that would seem the proper thing to do. So the SPI NOR driver is based
> on micron m25p80 and compatible string is "jedec,spi-nor", so I don't know
> who should or would do this registration.
The idiomatic approach appears to be for individual board vendors
to allocate IDs, you do end up with multiple IDs from multiple
vendors for the same thing.
> BTW, Do any of these sensors you mention have any ACPI standardization?
In general there's not really much standardizaiton for devices,
the bindings that do exist aren't really centrally documented and
the Windows standard is just to have the basic device
registration in the firmware and do all properties based on
quirking based on DMI information.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists