From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
linux-acpi@vger.kernel.org, Xiaomeng.Hou@amd.com,
Aaron.Liu@amd.com, Ray.Huang@amd.com, hdegoede@redhat.com
Subject: Re: [PATCH v4 2/3] ACPI: bus: Allow negotiating OSC capabilities
Date: Tue, 1 Mar 2022 15:07:56 +0200 [thread overview]
Message-ID: <Yh4Yphj7mLhC1igw@lahna> (raw)
In-Reply-To: <20220301124908.1931221-2-mario.limonciello@amd.com>
On Tue, Mar 01, 2022 at 06:49:07AM -0600, Mario Limonciello wrote:
> Currently when capabilities have been masked by firmware during a
> negotiation with OSC_QUERY_ENABLE set they're silently ignored
> by the caller. If the caller calls `acpi_run_osc` again without
> query set and the same capabilities, then they instead get a failure
> possibly leading to downstream problems.
>
> So instead when query is set return AE_SUPPORT which callers can then
> use for determining that capabilities were masked.
>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2022-03-01 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 12:49 [PATCH v4 1/3] ACPI: APEI: Adjust for acpi_run_osc logic changes Mario Limonciello
2022-03-01 12:49 ` [PATCH v4 2/3] ACPI: bus: Allow negotiating OSC capabilities Mario Limonciello
2022-03-01 13:07 ` Mika Westerberg [this message]
2022-03-08 21:51 ` Qian Cai
2022-03-01 12:49 ` [PATCH v4 3/3] ACPI: bus: For platform OSC negotiate capabilities Mario Limonciello
2022-03-01 13:12 ` Mika Westerberg
2022-03-02 20:09 ` [PATCH v4 1/3] ACPI: APEI: Adjust for acpi_run_osc logic changes Rafael J. Wysocki
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=Yh4Yphj7mLhC1igw@lahna \
--to=mika.westerberg@linux.intel.com \
--cc=Aaron.Liu@amd.com \
--cc=Ray.Huang@amd.com \
--cc=Xiaomeng.Hou@amd.com \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=rjw@rjwysocki.net \
/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.