From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI / LPSS: add ACPI IDs for newer Intel PCHs
Date: Sat, 16 Nov 2013 02:30:54 +0100 [thread overview]
Message-ID: <1515846.jF908LkdoS@vostro.rjw.lan> (raw)
In-Reply-To: <1384249699-9493-1-git-send-email-mika.westerberg@linux.intel.com>
On Tuesday, November 12, 2013 11:48:19 AM Mika Westerberg wrote:
> Some recent Intel PCHs with LPSS have different ACPI IDs for the LPSS
> devices, so add these to the list as well.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Queued up for the next ACPI pull request, thanks!
> ---
> drivers/acpi/acpi_lpss.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/acpi/acpi_lpss.c b/drivers/acpi/acpi_lpss.c
> index fb78bb9ad8f6..242885715331 100644
> --- a/drivers/acpi/acpi_lpss.c
> +++ b/drivers/acpi/acpi_lpss.c
> @@ -157,6 +157,15 @@ static const struct acpi_device_id acpi_lpss_device_ids[] = {
> { "80860F41", (unsigned long)&byt_i2c_dev_desc },
> { "INT33B2", },
>
> + { "INT3430", (unsigned long)&lpt_dev_desc },
> + { "INT3431", (unsigned long)&lpt_dev_desc },
> + { "INT3432", (unsigned long)&lpt_dev_desc },
> + { "INT3433", (unsigned long)&lpt_dev_desc },
> + { "INT3434", (unsigned long)&lpt_uart_dev_desc },
> + { "INT3435", (unsigned long)&lpt_uart_dev_desc },
> + { "INT3436", (unsigned long)&lpt_sdio_dev_desc },
> + { "INT3437", },
> +
> { }
> };
>
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-11-16 1:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 9:48 [PATCH] ACPI / LPSS: add ACPI IDs for newer Intel PCHs Mika Westerberg
2013-11-16 1:30 ` Rafael J. Wysocki [this message]
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=1515846.jF908LkdoS@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/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