From: Mika Westerberg <mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Alexander Stein
<alexander.stein-93q1YBGzJSMe9JSWTWOYM3xStJ4P+DSV@public.gmane.org>
Cc: Andy Shevchenko
<andy.shevchenko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-spi <linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: x86: Add SPI slaves to PCIe SPI master?
Date: Thu, 12 Jan 2017 15:47:29 +0200 [thread overview]
Message-ID: <20170112134729.GZ2330@lahna.fi.intel.com> (raw)
In-Reply-To: <26043741.eW6UMG2Gj5@ws-stein>
On Thu, Jan 12, 2017 at 02:39:04PM +0100, Alexander Stein wrote:
> result: \_SB_.PCI0.D023
>
> The node itself is just:
> > Device (D023)
> > {
> > Name (_ADR, 0x001E0005) // _ADR: Address
> > }
>
> Well, I'm not experienced with ACPI tables at all, but adding a device like in
> the 1st post I got my spi slave device, to my surprise I have to admit.
>
> Thanks for that hint about the, kinda dummy, node for the PCIe device node. I
> didn't expect adding a slave device there would result in having a linux
> device too.
That node is needed because it provides _ADR that ACPI core uses to bind
the PCI device to the ACPI node. This further allows the SPI core ACPI
enumeration code to find your slave device under \_SB_.PCI0.D023.
--
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
prev parent reply other threads:[~2017-01-12 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 15:08 x86: Add SPI slaves to PCIe SPI master? Alexander Stein
2017-01-12 11:48 ` Andy Shevchenko
[not found] ` <CAHp75VePTOd9WhkOTxW6GwKE2X3VR39J-7Song-P6iKsi7V6Ww-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-12 12:01 ` Mika Westerberg
[not found] ` <20170112120111.GY2330-3PARRvDOhMZrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2017-01-12 13:39 ` Alexander Stein
2017-01-12 13:47 ` Mika Westerberg [this message]
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=20170112134729.GZ2330@lahna.fi.intel.com \
--to=mika.westerberg-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=alexander.stein-93q1YBGzJSMe9JSWTWOYM3xStJ4P+DSV@public.gmane.org \
--cc=andy.shevchenko-Re5JQEeQqe8AvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.