All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Limonciello, Mario" <Mario.Limonciello@amd.com>
To: "Daniel Dadap" <ddadap@nvidia.com>,
	"Barnabás Pőcze" <pobrn@protonmail.com>
Cc: "platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>,
	Alexandru Dinu <alex.dinu07@gmail.com>,
	Hans de Goede <hdegoede@redhat.com>,
	"markgross@kernel.org" <markgross@kernel.org>,
	"Deucher, Alexander" <Alexander.Deucher@amd.com>
Subject: RE: [PATCH] nvidia-wmi-ec-backlight: Add workarounds for confused firmware
Date: Wed, 16 Mar 2022 19:25:37 +0000	[thread overview]
Message-ID: <BL1PR12MB515799AD192C4DDD25EFF990E2119@BL1PR12MB5157.namprd12.prod.outlook.com> (raw)
In-Reply-To: <884d57c1-5f41-ea80-dfaa-ab5b2f310891@nvidia.com>

[Public]



> -----Original Message-----
> From: Daniel Dadap <ddadap@nvidia.com>
> Sent: Wednesday, March 16, 2022 14:24
> To: Limonciello, Mario <Mario.Limonciello@amd.com>; Barnabás Pőcze
> <pobrn@protonmail.com>
> Cc: platform-driver-x86@vger.kernel.org; Alexandru Dinu
> <alex.dinu07@gmail.com>; Hans de Goede <hdegoede@redhat.com>;
> markgross@kernel.org; Deucher, Alexander
> <Alexander.Deucher@amd.com>
> Subject: Re: [PATCH] nvidia-wmi-ec-backlight: Add workarounds for
> confused firmware
> 
> On 3/16/22 13:25, Limonciello, Mario wrote:
> > [Public]
> >
> >
> > I guess when we see backlight issues on these A+N designs the checks
> should be:
> > 1) Are they supposed to be using the nvidia-wmi-ec-backlight driver?
> > 2) Is their kernel new enough to have it?
> > 3) Do they have the config enabled?
> >
> > Do you have a script or could you perhaps include some documentation we
> can
> > point people to check "1" so we don't always have to go tear apart ACPI
> tables
> > and make guesses?
> >
> > I guess it's something like grab _WDG and then parse it to see if there is an
> entry.
> 
> 
> Probably the most foolproof way would be to check for the GUID
> 603E9613-EF25-4338-A3D0-C46177516DB7 in /sys/bus/wmi/devices. (2)
> should
> be true for vanilla 5.16 and later, and many recent pre-5.16 distro
> kernels with HWE backports.

Perfect, thanks!

  reply	other threads:[~2022-03-16 19:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16  1:25 [PATCH] nvidia-wmi-ec-backlight: Add workarounds for confused firmware Daniel Dadap
2022-03-16  2:50 ` Barnabás Pőcze
2022-03-16 15:11   ` Daniel Dadap
2022-03-16 15:29     ` Limonciello, Mario
2022-03-16 17:08       ` Daniel Dadap
2022-03-16 17:21         ` Limonciello, Mario
2022-03-16 17:37           ` Daniel Dadap
2022-03-16 18:25             ` Limonciello, Mario
2022-03-16 19:23               ` Daniel Dadap
2022-03-16 19:25                 ` Limonciello, Mario [this message]
2022-03-16 20:33     ` [PATCH v2] " Daniel Dadap
2022-03-16 21:28       ` Daniel Dadap
2022-03-16 22:09         ` Alexandru Dinu
2022-03-16 22:14           ` Alexandru Dinu
2023-01-30 22:00           ` Daniel Dadap
2023-01-31 19:56             ` Alexandru Dinu
2023-02-07 23:23               ` Daniel Dadap
2022-03-17 12:17       ` Hans de Goede
2022-03-17 13:28         ` Daniel Dadap
2022-03-17 16:42           ` Hans de Goede
2022-03-17 16:42             ` Hans de Goede
2022-03-17 17:35             ` Alex Deucher
2022-03-17 18:50               ` Daniel Dadap
2022-03-17 18:50                 ` Daniel Dadap
2022-03-17 18:36             ` Daniel Dadap
2022-03-17 18:36               ` Daniel Dadap
2022-03-18 17:42               ` Hans de Goede
2022-03-18 17:42                 ` Hans de Goede
2022-03-16 16:09 ` [PATCH] " Hans de Goede
2022-03-16 17:22   ` Daniel Dadap
2022-03-16 20:13 Alexandru Dinu

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=BL1PR12MB515799AD192C4DDD25EFF990E2119@BL1PR12MB5157.namprd12.prod.outlook.com \
    --to=mario.limonciello@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=alex.dinu07@gmail.com \
    --cc=ddadap@nvidia.com \
    --cc=hdegoede@redhat.com \
    --cc=markgross@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=pobrn@protonmail.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 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.