From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Gwendal Grignou <gwendal@chromium.org>, hdegoede@redhat.com
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 2/2] platform/x86: intel-vbtn: Update tablet mode switch at end of probe
Date: Fri, 29 Mar 2024 11:50:18 -0700 [thread overview]
Message-ID: <c26ca604-a812-4030-bdae-79e6e2b7b17b@linux.intel.com> (raw)
In-Reply-To: <20240329143206.2977734-3-gwendal@chromium.org>
On 3/29/24 7:32 AM, Gwendal Grignou wrote:
> ACER Vivobook Flip (TP401NAS) virtual intel switch is implemented as
> follow:
>
> Device (VGBI)
> {
> Name (_HID, EisaId ("INT33D6") ...
> Name (VBDS, Zero)
> Method (_STA, 0, Serialized) // _STA: Status ...
> Method (VBDL, 0, Serialized)
> {
> PB1E |= 0x20
> VBDS |= 0x40
> }
> Method (VGBS, 0, Serialized)
> {
> Return (VBDS) /* \_SB_.PCI0.SBRG.EC0_.VGBI.VBDS */
> }
> ...
> }
>
> By default VBDS is set to 0. At boot it is set to clamshell (bit 6 set)
> only after method VBDL is executed.
>
> Since VBDL is now evaluated in the probe routine later, after the device
> is registered, the retrieved value of VBDS was still 0 ("tablet mode")
> when setting up the virtual switch.
>
> Make sure to evaluate VGBS after VBDL, to ensure the
> convertible boots in clamshell mode, the expected default.
>
> Fixes: 26173179fae1 ("platform/x86: intel-vbtn: Eval VBDL after registering our notifier")
> Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
> ---
Reviewed-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
> drivers/platform/x86/intel/vbtn.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/intel/vbtn.c b/drivers/platform/x86/intel/vbtn.c
> index 48f0ac19d6ddf..79bb2c801daa9 100644
> --- a/drivers/platform/x86/intel/vbtn.c
> +++ b/drivers/platform/x86/intel/vbtn.c
> @@ -136,8 +136,6 @@ static int intel_vbtn_input_setup(struct platform_device *device)
> priv->switches_dev->id.bustype = BUS_HOST;
>
> if (priv->has_switches) {
> - detect_tablet_mode(&device->dev);
> -
> ret = input_register_device(priv->switches_dev);
> if (ret)
> return ret;
> @@ -312,6 +310,9 @@ static int intel_vbtn_probe(struct platform_device *device)
> if (ACPI_FAILURE(status))
> dev_err(&device->dev, "Error VBDL failed with ACPI status %d\n", status);
> }
> + // Check switches after buttons since VBDL may have side effects.
> + if (has_switches)
> + detect_tablet_mode(&device->dev);
>
> device_init_wakeup(&device->dev, true);
> /*
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
next prev parent reply other threads:[~2024-03-29 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 14:32 [PATCH 0/2] platform/x86: intel-vbtn: Fix ASUS VivoBook boot state Gwendal Grignou
2024-03-29 14:32 ` [PATCH 1/2] platform/x86: intel-vbtn: Use acpi_has_method to check for switch Gwendal Grignou
2024-03-29 18:49 ` Kuppuswamy Sathyanarayanan
2024-04-08 15:44 ` Ilpo Järvinen
2024-03-29 14:32 ` [PATCH 2/2] platform/x86: intel-vbtn: Update tablet mode switch at end of probe Gwendal Grignou
2024-03-29 18:50 ` Kuppuswamy Sathyanarayanan [this message]
2024-04-08 13:17 ` [PATCH 0/2] platform/x86: intel-vbtn: Fix ASUS VivoBook boot state 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=c26ca604-a812-4030-bdae-79e6e2b7b17b@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=gwendal@chromium.org \
--cc=hdegoede@redhat.com \
--cc=platform-driver-x86@vger.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