All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 201885] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
Date: Thu, 29 Sep 2022 18:21:38 +0000	[thread overview]
Message-ID: <bug-201885-215701-n4m8yNPIbN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201885-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=201885

--- Comment #20 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
During the architectural design of the WMI subsystem an assumption was made
that there was a 1:1 mapping of WMI GUIDs (that is they're unique).  This
hasn't caused MAJOR functional problems, but this was proven wrong, as it's
possible to fetch multiple BMOFs.

This change makes it so that if you have the wmi-bmof driver loaded on your
system you'll be able to fetch all of the BMOFs.  If you look in
/sys/bus/wmi/devices, you should see more entries with this patch in place.

If the same GUID is used multiple times on a system for any reason beside
wmi-bmof, that driver may need to be changed too.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2022-09-29 18:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-201885-215701@https.bugzilla.kernel.org/>
2021-08-21 23:17 ` [Bug 201885] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) bugzilla-daemon
2021-11-16 23:46 ` bugzilla-daemon
2021-11-26 18:39 ` bugzilla-daemon
2021-12-04 16:09 ` bugzilla-daemon
2022-01-21 17:26 ` bugzilla-daemon
2022-09-29 16:50 ` bugzilla-daemon
2022-09-29 17:46 ` bugzilla-daemon
2022-09-29 18:17 ` bugzilla-daemon
2022-09-29 18:21 ` bugzilla-daemon [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=bug-201885-215701-n4m8yNPIbN@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --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 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.