From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
Bjorn Helgaas <helgaas@kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Hans de Goede <hansg@kernel.org>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [PATCH v1 3/8] ACPI: bus: Split _OSC evaluation out of acpi_run_osc()
Date: Fri, 19 Dec 2025 12:44:09 +0000 [thread overview]
Message-ID: <20251219124409.00002f4e@huawei.com> (raw)
In-Reply-To: <3407425.44csPzL39Z@rafael.j.wysocki>
On Thu, 18 Dec 2025 21:36:08 +0100
"Rafael J. Wysocki" <rafael@kernel.org> wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> Split a function for evaluating _OSL called acpi_eval_osc() out of
_OSC
> acpi_run_osc() to facilitate subsequent changes and add some more
> parameters sanity checks to the latter.
>
> No intentional functional impact.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
One comment on the fun static keyword usage. Next time I have
to ask/answer some silly C questions in an interview that one is definitely going
in :)
> ---
> drivers/acpi/bus.c | 89 ++++++++++++++++++++++++++++++-----------------------
> 1 file changed, 52 insertions(+), 37 deletions(-)
>
> --- a/drivers/acpi/bus.c
> +++ b/drivers/acpi/bus.c
> @@ -195,52 +195,67 @@ static void acpi_dump_osc_data(acpi_hand
> OSC_INVALID_REVISION_ERROR | \
> OSC_CAPABILITIES_MASK_ERROR)
>
> -acpi_status acpi_run_osc(acpi_handle handle, struct acpi_osc_context *context)
> +static int acpi_eval_osc(acpi_handle handle, guid_t *guid, int rev,
> + struct acpi_buffer *cap,
> + union acpi_object in_params[static 4],
This static usage has such non intuitive behavior maybe use
the new at_least marking in compiler_types.h to indicate
what protection against wrong sizes it can offer.
> + struct acpi_buffer *output)
> {
> - acpi_status status;
> struct acpi_object_list input;
> - union acpi_object in_params[4];
> union acpi_object *out_obj;
> + acpi_status status;
> +
> + in_params[0].type = ACPI_TYPE_BUFFER;
> + in_params[0].buffer.length = sizeof(*guid);
> + in_params[0].buffer.pointer = (u8 *)guid;
> + in_params[1].type = ACPI_TYPE_INTEGER;
> + in_params[1].integer.value = rev;
> + in_params[2].type = ACPI_TYPE_INTEGER;
> + in_params[2].integer.value = cap->length / sizeof(u32);
> + in_params[3].type = ACPI_TYPE_BUFFER;
> + in_params[3].buffer.length = cap->length;
> + in_params[3].buffer.pointer = cap->pointer;
> + input.pointer = in_params;
> + input.count = 4;
> +
> + output->length = ACPI_ALLOCATE_BUFFER;
> + output->pointer = NULL;
> +
> + status = acpi_evaluate_object(handle, "_OSC", &input, output);
> + if (ACPI_FAILURE(status) || !output->length)
> + return -ENODATA;
> +
> + out_obj = output->pointer;
> + if (out_obj->type != ACPI_TYPE_BUFFER ||
> + out_obj->buffer.length != cap->length) {
> + acpi_handle_debug(handle, "Invalid _OSC return buffer\n");
> + acpi_dump_osc_data(handle, guid, rev, cap);
> + ACPI_FREE(out_obj);
> + return -ENODATA;
> + }
> +
> + return 0;
> +}
next prev parent reply other threads:[~2025-12-19 12:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 20:29 [PATCH v1 0/8] ACPI: bus: Rework of the \_SB._OSC handling Rafael J. Wysocki
2025-12-18 20:34 ` [PATCH v1 1/8] ACPI: bus: Fix handling of _OSC errors in acpi_run_osc() Rafael J. Wysocki
2025-12-19 12:26 ` Jonathan Cameron
2025-12-19 20:38 ` Rafael J. Wysocki
2025-12-19 21:28 ` [PATCH v2] " Rafael J. Wysocki
2025-12-22 11:18 ` Jonathan Cameron
2025-12-22 17:57 ` Rafael J. Wysocki
2025-12-18 20:35 ` [PATCH v1 2/8] ACPI: bus: Rework printing debug messages on _OSC errors Rafael J. Wysocki
2025-12-19 12:33 ` Jonathan Cameron
2025-12-19 17:20 ` Rafael J. Wysocki
2025-12-18 20:36 ` [PATCH v1 3/8] ACPI: bus: Split _OSC evaluation out of acpi_run_osc() Rafael J. Wysocki
2025-12-19 12:44 ` Jonathan Cameron [this message]
2025-12-19 17:22 ` Rafael J. Wysocki
2025-12-18 20:36 ` [PATCH v1 4/8] ACPI: bus: Split _OSC error processing " Rafael J. Wysocki
2025-12-19 12:46 ` Jonathan Cameron
2025-12-19 17:24 ` Rafael J. Wysocki
2025-12-18 20:37 ` [PATCH v1 5/8] ACPI: bus: Rename label and use ACPI_FREE() in acpi_run_osc() Rafael J. Wysocki
2025-12-19 12:47 ` Jonathan Cameron
2025-12-18 20:39 ` [PATCH v1 6/8] ACPI: bus: Rework the handling of \_SB._OSC platform features Rafael J. Wysocki
2025-12-19 12:56 ` Jonathan Cameron
2025-12-19 17:48 ` Rafael J. Wysocki
2025-12-18 20:41 ` [PATCH v1 7/8] ACPI: bus: Adjust feature mask creation for \_SB._OSC Rafael J. Wysocki
2025-12-19 12:58 ` Jonathan Cameron
2025-12-18 20:42 ` [PATCH v1 8/8] ACPI: bus: Rework the handling of \_SB._OSC USB4 features Rafael J. Wysocki
2025-12-19 12:59 ` Jonathan Cameron
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=20251219124409.00002f4e@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=hansg@kernel.org \
--cc=helgaas@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@linux.intel.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.