public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Flavio Suligoi <f.suligoi@asem.it>
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: Mon, 9 Nov 2020 12:34:32 +0200	[thread overview]
Message-ID: <20201109103432.GU4077@smile.fi.intel.com> (raw)
In-Reply-To: <dfeb12b6c53a49a2afc8cf381b066999@asem.it>

On Mon, Nov 09, 2020 at 09:05:36AM +0000, Flavio Suligoi wrote:

> > Glad to hear this! So, maybe you can add some bits to the documentation
> > [1]
> > based on your experience?
> 
> Yes, I can! Thanks you for asking me!
> 
> > Note, I have sent a series [2] to amend it a bit, and your input welcome!
> > 
> > [1]: Documentation/firmware-guide/acpi/gpio-properties.rst
> > [2]: https://lore.kernel.org/linux-acpi/20201029193243.61546-1-
> > andriy.shevchenko@linux.intel.com/T/#u
> 
> Ok, I'll see how to integrate my PCI "investigation" about the
> identification of the correct path from the CPU to the final PCI
> device, through the various bridges of the board.
> I think that a general discourse about it can be useful to
> other people, too.

I realized that here we have two items to document:
1) the gpio-line-names property in [1];
2) PCI hierarchy in ACPI tables, which can be added into [3] under
   the "PCI hierarchy representation" title or so.

[3]: Documentation/firmware-guide/acpi/enumeration.rst

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2020-11-09 10:33 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 [this message]
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=20201109103432.GU4077@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