On Mon, Nov 09, 2020 at 12:34:32PM +0200, Andy Shevchenko wrote: > 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@xxxxxxxxxxxxxxx/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]; More precise here is to extend the existing documentation with the examples and explanation how GPIO subsystem in Linux is expecting those names to be (as I explained in one thread to you that the property covers only line names from the beginning to the first hole, when no name is provided, i.o.w. holes are not accepted). > 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
