From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
Andy Shevchenko <andy@kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH] ACPI: LPSS: Add 80862289 ACPI HID for second PWM controller on Cherry Trail
Date: Tue, 18 Apr 2023 09:07:17 +0300 [thread overview]
Message-ID: <20230418060717.GD66750@black.fi.intel.com> (raw)
In-Reply-To: <20230417211128.588008-1-hdegoede@redhat.com>
Hi Hans,
On Mon, Apr 17, 2023 at 11:11:28PM +0200, Hans de Goede wrote:
> On some Cherry Trail devices the second PWM controller uses
> 80862289 as ACPI HID, rather then using 80862288 as is done
ACPI _HID (ditto in $subjet)
> for both controllers on most models.
>
> Add the missing 80862289 ACPI HID, note this uses its own
ACPI _HID
> lpss_device_desc, without ".setup = bsw_pwm_setup" so that
> the pwm_lookup is not added for it.
> On devices where both controllers use the 80862288 HID bsw_pwm_setup()
_HID
> does a UID check to avoid registering the lookup for the second
_UID
> controller but that will not work here.
>
> Adding the missing id fixes the second PWM controller no longer
> working after the entire LPSS1 island has been in D3 at least
> once, which causes the contents of the LPSS private registers
> to get lost. Adding the HID makes acpi_lpss restore these
_HID
> when the controller moves from D3 to D0.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
With the above changes, feel free to add
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
prev parent reply other threads:[~2023-04-18 6:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 21:11 [PATCH] ACPI: LPSS: Add 80862289 ACPI HID for second PWM controller on Cherry Trail Hans de Goede
2023-04-18 6:07 ` Mika Westerberg [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=20230418060717.GD66750@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andy@kernel.org \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.