From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Flavio Suligoi <f.suligoi@asem.it>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: How to add the "gpio-line-names" property in a PCI gpio expander
Date: Thu, 5 Nov 2020 17:56:39 +0200 [thread overview]
Message-ID: <20201105155639.GV4077@smile.fi.intel.com> (raw)
In-Reply-To: <CAJZ5v0g7POp1Lp05RcJJ8ZD1ZiaetN0_SfbAjnQg0kCw4aQukQ@mail.gmail.com>
On Thu, Nov 05, 2020 at 12:51:18PM +0100, Rafael J. Wysocki wrote:
> CC Mika and Andy who should be more familiar with that problem space than I am.
I believe I have explained this in the [1]. Perhaps it's about how to find
proper device node / ACPI path of the devices in question?
[1]: https://lore.kernel.org/linux-gpio/9152bb8be33e4192a7766eb53c6ca9af@asem.it/
> On Thu, Nov 5, 2020 at 10:46 AM Flavio Suligoi <f.suligoi@asem.it> wrote:
> >
> > Hi all,
> >
> > I'm working to introduce the "gpio-line-names" property in the ACPI
> > configuration of the BIOS of our x86 boards (we can customize the BIOS of our
> > boards).
> >
> > All is ok for the gpiochips related to the Intel chipset and some I2C gpio
> > expanders. I have inserted the _DSD as described in the Linux documentation.
> >
> > In one of our boards we have an add-on PCI board, with a PCI serial device
> > Exar XR17V352. This device also contains 16 gpios.
> > The exar device drivers work good, both the "8250_exar" and the "gpio_exar", and
> > I can manage the exar's gpios correctly.
> > The problem is how to assign the gpio-line-names property to a PCI gpio
> > expanders like this.
> >
> > I tried adding a new device in my ACPI configuration, as:
> >
> > Device (EXAR)
> > {
> > Name (_HID, "13A80352")
> > Name (_STR, Unicode ("STR - Exar GPIOs")) // _STR: Description String
> >
> > Name (_DSD, Package () {
> > ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
> > Package () {
> > Package () {
> > "gpio-line-names",
> > Package () {
> > "exar_0",
> > "exar_1",
> > "exar_2",
> > "exar_3",
> > ...
> > }
> > }
> > }
> > })
> > }
> >
> > but I have no result.
> > Does anyone have a suggestion?
> >
> > Thanks,
> >
> > Flavio
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2020-11-05 15:55 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
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 [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=20201105155639.GV4077@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=f.suligoi@asem.it \
--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