From: Flavio Suligoi <f.suligoi@asem.it>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: RE: How to add the "gpio-line-names" property in a PCI gpio expander
Date: Thu, 5 Nov 2020 16:24:32 +0000 [thread overview]
Message-ID: <942133825ef348d49a97a6bdc16a72e4@asem.it> (raw)
In-Reply-To: <20201105161919.GX4077@smile.fi.intel.com>
Hi Andy,
> > >
> > > Unfortunately there is bridge in the middle:
> > >
> > > root@debian:~# lspci -t
> > > -[0000:00]-+-00.0
> > > +-02.0
> > > +-0e.0
> > > +-0f.0
> > > +-12.0
> > > +-13.0-[01]----00.0
> > > +-13.1-[02]----00.0
> > > +-13.2-[03]--
> > > +-14.0-[04]----00.0
> > > +-14.1-[05-09]----00.0-[06-09]--+-01.0-[07]----00.0 <--
> Exar (bus 7, dev 0, funct 0)
> > > | +-02.0-[08]----00.0
> > > | \-03.0-[09]--
> > > +-15.0
> > > +-16.0
> > > +-16.1
> > > +-19.0
> > > +-19.1
> > > +-19.2
> > > +-1f.0
> > > \-1f.1
> > > root@debian:~#
> > >
> > > My changes in the ACPI:
> > >
> > > Scope (_SB.PCI0) {
> > > Device (EXAR)
> > > {
> > > Name (_ADR, 0x0000)
> >
> > _ADR should represent BDF (Bus:Device.Function)
> >
> > Something like 0x07000000
>
> Per documentation:
> "High word–Device #, Low word–Function #. (for example, device 3, function
> 2 is
> 0x00030002). To refer to all the functions on a device #, use a function
> number of FFFF)."
>
exactly, with the _ADR object we can specify only device and function.
The bus is implicit, that's way I used the:
Scope (_SB.PCI0) { ...
But it is the wrong bus, because of a bridge in the middle.
Best regards,
Flavio
next prev parent reply other threads:[~2020-11-05 16:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 9:46 How to add the "gpio-line-names" property in a PCI gpio expander Flavio Suligoi
2020-11-05 11:51 ` Rafael J. Wysocki
2020-11-05 11:59 ` Mika Westerberg
2020-11-05 14:01 ` Flavio Suligoi
2020-11-05 15:20 ` Mika Westerberg
2020-11-05 15:54 ` Flavio Suligoi
2020-11-05 16:09 ` Andy Shevchenko
2020-11-05 16:19 ` Andy Shevchenko
2020-11-05 16:24 ` Flavio Suligoi [this message]
2020-11-06 7:04 ` Mika Westerberg
2020-11-06 16:47 ` Flavio Suligoi
2020-11-06 17:17 ` Andy Shevchenko
2020-11-09 9:05 ` Flavio Suligoi
2020-11-09 10:34 ` Andy Shevchenko
2020-11-09 10:35 ` Flavio Suligoi
2020-11-09 10:37 ` Andy Shevchenko
2020-11-05 15:56 ` Andy Shevchenko
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=942133825ef348d49a97a6bdc16a72e4@asem.it \
--to=f.suligoi@asem.it \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.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