[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200826184253.GQ4965@sirena.org.uk>
Date: Wed, 26 Aug 2020 19:42:53 +0100
From: Mark Brown <broonie@...nel.org>
To: Vladimir Oltean <olteanv@...il.com>
Cc: Qiang Zhao <qiang.zhao@....com>,
kuldip dwivedi <kuldip.dwivedi@...esoftware.com>,
"linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Pankaj Bansal <pankaj.bansal@....com>,
Varun Sethi <V.Sethi@....com>,
Tanveer Alam <tanveer.alam@...esoftware.com>
Subject: Re: [PATCH] spi: spi-fsl-dspi: Add ACPI support
On Wed, Aug 26, 2020 at 09:33:38PM +0300, Vladimir Oltean wrote:
> On Wed, Aug 26, 2020 at 05:55:52PM +0100, Mark Brown wrote:
> > > On Wed, Aug 26, 2020 at 03:23:12PM +0100, Mark Brown wrote:
> > > Showing my ignorance here, but is there something equivalent to
> > > of_machine_is_compatible() for ACPI?
> > The NXP0005 is the ACPI equivalent of a compatible (comprehensibility is
> > not ACPI's forte) and they're tying driver data to it there.
> Where I was trying to get here is that we could have a single _HID for
> the DSPI controller, and corroborate that with the ACPI equivalent of
> of_machine_is_compatible("fsl,ls2085a") at driver probe time before
> assigning the driver data.
Oh, there isn't an ACPI equivalent of that. DMI information doesn't
capture anything useful about the chipset, only the system as a whole
(assuming it's usefully filled). See for example
sound/soc/intel/common/soc-intel-quirks.h
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists