On Tue, Jun 25, 2019 at 04:10:23PM +0200, Linus Walleij wrote: > On Tue, Jun 25, 2019 at 1:08 PM Andy Shevchenko > <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > > On Mon, Jun 24, 2019 at 11:39:42AM -0700, Alexander Ivanov wrote: > > > On Fri, 21 Jun 2019 10:39 -07:00, Alexander Ivanov <amivanov@xxxxxxxxxxxx> wrote: > > > > On Fri, 21 Jun 2019 03:12 -07:00, Andy Shevchenko > > > > <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > > There is no issue with kernel. ACPI tables provided by firmware, so, > > vendor of your firmware decided to turn off this device. > > In Linux we usually respect users and contributors more than > vendors, so if there are users that need to access this device > and the firmware doesn't let them, but there is a way for us to > fix that, then we should provide the tools. > > But I guess that would happen in the ACPI core? Linus, there is another problem, if we even work around this (you should ask Rafael, indeed), the MMIO resources, provided by the table is solely generated by BIOS. The IP, AFAIK, has a possibility to be reallocated in the address space. The user will need BIOS to clarify that, it can't be done in OS (GPIO is exposed as not a PCI device). -- With Best Regards, Andy Shevchenko _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
