| Message ID | 20180827074545.5009-3-hdegoede@redhat.com (mailing list archive) |
|---|---|
| State | Accepted |
| Headers | show |
| Series | ACPI + dma: Add alternative ACPI HIDs for Cherry Trail DMA controllers | expand |
On 27-08-18, 09:45, Hans de Goede wrote: > Bay and Cherry Trail DSTDs represent a different set of devices depending > on which OS the device think it is booting. One set of decices for Windows > and another set of devices for Android which targets the Android-x86 Linux > kernel fork (which e.g. used to have its own display driver instead of > using the i915 driver). > > Which set of devices we are actually going to get is out of our control, > this is controlled by the ACPI OSID variable, which gets either set through > an EFI setup option, or sometimes is autodetected. So we need to support > both. > > This commit adds support for the 80862286 and 808622C0 ACPI HIDs which we > get for the first resp. second DMA controller on Cherry Trail devices when > OSID is set to Android. Applied, thanks
On Mon, Aug 27, 2018 at 09:45:45AM +0200, Hans de Goede wrote: > Bay and Cherry Trail DSTDs represent a different set of devices depending > on which OS the device think it is booting. One set of decices for Windows > and another set of devices for Android which targets the Android-x86 Linux > kernel fork (which e.g. used to have its own display driver instead of > using the i915 driver). > > Which set of devices we are actually going to get is out of our control, > this is controlled by the ACPI OSID variable, which gets either set through > an EFI setup option, or sometimes is autodetected. So we need to support > both. > > This commit adds support for the 80862286 and 808622C0 ACPI HIDs which we > get for the first resp. second DMA controller on Cherry Trail devices when > OSID is set to Android. > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> > Signed-off-by: Hans de Goede <hdegoede@redhat.com> > --- > drivers/dma/dw/platform.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/dma/dw/platform.c b/drivers/dma/dw/platform.c > index f62dd0944908..f01b2c173fa6 100644 > --- a/drivers/dma/dw/platform.c > +++ b/drivers/dma/dw/platform.c > @@ -284,6 +284,8 @@ MODULE_DEVICE_TABLE(of, dw_dma_of_id_table); > #ifdef CONFIG_ACPI > static const struct acpi_device_id dw_dma_acpi_id_table[] = { > { "INTL9C60", 0 }, > + { "80862286", 0 }, > + { "808622C0", 0 }, > { } > }; > MODULE_DEVICE_TABLE(acpi, dw_dma_acpi_id_table); > -- > 2.18.0 >
diff --git a/drivers/dma/dw/platform.c b/drivers/dma/dw/platform.c index f62dd0944908..f01b2c173fa6 100644 --- a/drivers/dma/dw/platform.c +++ b/drivers/dma/dw/platform.c @@ -284,6 +284,8 @@ MODULE_DEVICE_TABLE(of, dw_dma_of_id_table); #ifdef CONFIG_ACPI static const struct acpi_device_id dw_dma_acpi_id_table[] = { { "INTL9C60", 0 }, + { "80862286", 0 }, + { "808622C0", 0 }, { } }; MODULE_DEVICE_TABLE(acpi, dw_dma_acpi_id_table);
Bay and Cherry Trail DSTDs represent a different set of devices depending on which OS the device think it is booting. One set of decices for Windows and another set of devices for Android which targets the Android-x86 Linux kernel fork (which e.g. used to have its own display driver instead of using the i915 driver). Which set of devices we are actually going to get is out of our control, this is controlled by the ACPI OSID variable, which gets either set through an EFI setup option, or sometimes is autodetected. So we need to support both. This commit adds support for the 80862286 and 808622C0 ACPI HIDs which we get for the first resp. second DMA controller on Cherry Trail devices when OSID is set to Android. Signed-off-by: Hans de Goede <hdegoede@redhat.com> --- drivers/dma/dw/platform.c | 2 ++ 1 file changed, 2 insertions(+)