From: Vinod Koul <vkoul@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Viresh Kumar <vireshk@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-acpi@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org
Subject: [2/2] dmaengine: dw: Add alternative ACPI HIDs for Cherry Trail DMA controllers
Date: Wed, 29 Aug 2018 21:55:06 +0530 [thread overview]
Message-ID: <20180829162506.GJ2388@vkoul-mobl> (raw)
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
next reply other threads:[~2018-08-29 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 16:25 Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-29 16:50 [2/2] dmaengine: dw: Add alternative ACPI HIDs for Cherry Trail DMA controllers Andy Shevchenko
2018-08-27 7:45 Hans de Goede
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=20180829162506.GJ2388@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=vireshk@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