lkml.org 
[lkml]   [2020]   [Jan]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH v2 2/3] spi: Add HiSilicon v3xx SPI NOR flash controller driver
    On Mon, Jan 13, 2020 at 02:27:54PM +0000, Mark Brown wrote:
    > On Mon, Jan 13, 2020 at 04:17:32PM +0200, Andy Shevchenko wrote:
    > > On Mon, Jan 13, 2020 at 4:07 PM Mark Brown <broonie@kernel.org> wrote:
    > > > On Mon, Jan 13, 2020 at 01:01:06PM +0000, John Garry wrote:
    > > > > On 13/01/2020 11:42, Mark Brown wrote:
    >
    > > > > > 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.
    >
    > > > > But I am not sure how appropriate that same approach would be for some 3rd
    > > > > party memory part which we're simply wiring up on our board. Maybe it is.
    >
    > > > It seems to be quite common for Intel reference designs to assign
    > > > Intel IDs to non-Intel parts on the board (which is where I
    > > > became aware of this practice).
    >
    > > Basically vendor of component in question is responsible for ID, but
    > > it seems they simple don't care.
    >
    > AFAICT a lot of the time it seems to be that whoever is writing
    > the software ends up assigning an ID, that may not be the silicon
    > vendor.

    ...which is effectively abusing the ACPI ID allocation procedure.

    (And yes, Intel itself did it in the past — see badly created ACPI IDs
    in the drivers)

    --
    With Best Regards,
    Andy Shevchenko


    \
     
     \ /
      Last update: 2020-01-13 15:35    [W:4.551 / U:0.020 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site