From: Mika Westerberg <mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Jarkko Nikula
<jarkko.nikula-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH RESEND] spi: spidev: Allow matching DT compatible strings from ACPI
Date: Fri, 1 Jul 2016 13:19:12 +0300 [thread overview]
Message-ID: <20160701101912.GL23527@lahna.fi.intel.com> (raw)
In-Reply-To: <20160630124931.GD23527-3PARRvDOhMZrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
On Thu, Jun 30, 2016 at 03:49:31PM +0300, Mika Westerberg wrote:
> On Wed, Jun 29, 2016 at 08:20:59PM +0100, Mark Brown wrote:
> > On Wed, Jun 29, 2016 at 09:51:55PM +0300, Mika Westerberg wrote:
> > > On Wed, Jun 29, 2016 at 07:31:01PM +0100, Mark Brown wrote:
> >
> > > > And we're *sure* that's going to be maintained? People do use the
> > > > fallback matching that DT does, I don't trust the ACPI maintainers not
> > > > to do the same thing.
> >
> > > That fallback matching does not even work in ACPI like I told you
> > > already. We have no plans to do anything like that either. That's the
> > > reason why we complain if there is PRP0001 without compatible string.
> >
> > No, you're completely missing the point here. The problem is someone
> > using something like linux,spidev as a compatible string and going into
> > fallback matching on SPI bus IDs rather than compatible strings. I just
> > don't have confidence that someone isn't going to try to add that
> > fallback path given that it's used for DT.
>
> If someone is using "linux,spidev" as compatible string it will not
> match anything and we are not going to add any kind of fallback to the
> ACPI core for that.
>
> Of course we cannot predict what happens in the future but is it really
> preventing merging of this patch?
>
> What I'm simply trying to achieve is to use the existing two DT
> compatible strings from ACPI. I've tested that it works fine and
> provided you all the evidence that it does not break the check for
> misusing DT.
Actually there seems to be alternative to this.
Windows seems to have a similar spidev raw interface in their MITT test
suite here:
https://msdn.microsoft.com/fi-fi/windows/hardware/drivers/spb/spi-tests-in-mitt
It exposes three ACPI SPI devices with ACPI IDs of SPT0001, SPT0002 and
SPT0003. I'm thinking that instead of using the existing DT compatible
strings we could use these ACPI IDs in the driver.
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-07-01 10:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 11:34 [PATCH RESEND] spi: spidev: Allow matching DT compatible strings from ACPI Mika Westerberg
[not found] ` <1467027248-6191-1-git-send-email-mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-06-27 12:24 ` Mark Brown
[not found] ` <20160627122448.GU28202-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-06-28 9:22 ` Mika Westerberg
[not found] ` <20160628092234.GG1711-3PARRvDOhMZrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2016-06-28 11:47 ` Mark Brown
[not found] ` <20160628114742.GM17217-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-06-28 14:35 ` Mika Westerberg
[not found] ` <20160628143528.GK1711-3PARRvDOhMZrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2016-06-28 15:07 ` Mark Brown
[not found] ` <20160628150752.GO17217-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-06-28 15:23 ` Mika Westerberg
[not found] ` <20160628152338.GN1711-3PARRvDOhMZrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2016-06-28 16:18 ` Mark Brown
[not found] ` <20160628161822.GQ17217-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-06-29 9:13 ` Mika Westerberg
[not found] ` <20160629091304.GP1711-3PARRvDOhMZrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2016-06-29 16:21 ` Mark Brown
[not found] ` <20160629162127.GA6247-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-06-29 16:34 ` Mika Westerberg
[not found] ` <20160629163420.GC1711-3PARRvDOhMZrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2016-06-29 18:31 ` Mark Brown
[not found] ` <20160629183101.GN6247-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-06-29 18:51 ` Mika Westerberg
[not found] ` <20160629185155.GG1711-3PARRvDOhMZrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2016-06-29 19:20 ` Mark Brown
[not found] ` <20160629192059.GV6247-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-06-30 12:49 ` Mika Westerberg
[not found] ` <20160630124931.GD23527-3PARRvDOhMZrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2016-07-01 10:12 ` Mark Brown
2016-07-01 10:19 ` Mika Westerberg [this message]
[not found] ` <20160701101912.GL23527-3PARRvDOhMZrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2016-07-01 14:50 ` Mark Brown
[not found] ` <20160701145035.GP6247-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-07-02 9:01 ` Mika Westerberg
[not found] ` <20160702090114.GS23527-3PARRvDOhMZrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2016-07-02 10:15 ` Mark Brown
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=20160701101912.GL23527@lahna.fi.intel.com \
--to=mika.westerberg-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=jarkko.nikula-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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).