From: "Wilczynski, Michal" <michal.wilczynski@intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: <linux-acpi@vger.kernel.org>, <andriy.shevchenko@intel.com>,
<artem.bityutskiy@linux.intel.com>, <mingo@redhat.com>,
<bp@alien8.de>, <dave.hansen@linux.intel.com>, <hpa@zytor.com>,
<lenb@kernel.org>, <jgross@suse.com>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>
Subject: Re: [PATCH v3 4/5] acpi: Use _OSC method to convey processor OSPM capabilities
Date: Fri, 30 Jun 2023 11:18:37 +0200 [thread overview]
Message-ID: <4de5c2da-5bdd-68fe-fa80-e96f778f7fd2@intel.com> (raw)
In-Reply-To: <CAJZ5v0ig9=5wgQbH__q6BJU=p2uryReS_Lmq7s7HdWoDX6eXsQ@mail.gmail.com>
On 6/29/2023 4:23 PM, Rafael J. Wysocki wrote:
> On Tue, Jun 13, 2023 at 6:12 PM Michal Wilczynski
> <michal.wilczynski@intel.com> wrote:
>> Change acpi_early_processor_osc() to return value in case of the failure.
>> Make it more generic - previously it served only to execute workaround
>> for buggy BIOS in Skylake systems. Now it will walk through ACPI
>> namespace looking for processor objects and will convey OSPM processor
>> capabilities using _OSC method.
>>
>> Prefer using _OSC method over deprecated _PDC in the acpi_bus_init(). In
>> case of the failure of the _OSC, try using _PDC as a fallback.
>>
>> Suggested-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>> Signed-off-by: Michal Wilczynski <michal.wilczynski@intel.com>
>> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>> ---
>> drivers/acpi/acpi_processor.c | 23 +++++++++++++----------
>> drivers/acpi/bus.c | 13 +++++++++----
>> drivers/acpi/internal.h | 9 +--------
>> 3 files changed, 23 insertions(+), 22 deletions(-)
>>
>> diff --git a/drivers/acpi/acpi_processor.c b/drivers/acpi/acpi_processor.c
>> index 0de0b05b6f53..8965e01406e0 100644
>> --- a/drivers/acpi/acpi_processor.c
>> +++ b/drivers/acpi/acpi_processor.c
>> @@ -669,17 +669,20 @@ static acpi_status __init acpi_hwp_native_thermal_lvt_osc(acpi_handle handle,
>> return AE_OK;
>> }
>>
>> -void __init acpi_early_processor_osc(void)
> I would rename this to something like
> acpi_early_processor_control_setup() and would make it attempt to call
> _PDC if _OSC doesn't work.
>
> Then it could remain void and it could be put under a
> CONFIG_ARCH_MIGHT_HAVE_ACPI_PDC #ifdef.
Sure, makes sense to me
>
>> +acpi_status __init acpi_early_processor_osc(void)
>> {
>> - if (boot_cpu_has(X86_FEATURE_HWP)) {
>> - acpi_walk_namespace(ACPI_TYPE_PROCESSOR, ACPI_ROOT_OBJECT,
>> - ACPI_UINT32_MAX,
>> - acpi_hwp_native_thermal_lvt_osc,
>> - NULL, NULL, NULL);
>> - acpi_get_devices(ACPI_PROCESSOR_DEVICE_HID,
>> - acpi_hwp_native_thermal_lvt_osc,
>> - NULL, NULL);
>> - }
>> + acpi_status status;
>> +
>> + processor_dmi_check();
>> +
>> + status = acpi_walk_namespace(ACPI_TYPE_PROCESSOR, ACPI_ROOT_OBJECT,
>> + ACPI_UINT32_MAX, acpi_processor_osc, NULL,
>> + NULL, NULL);
>> + if (ACPI_FAILURE(status))
>> + return status;
>> +
>> + return acpi_get_devices(ACPI_PROCESSOR_DEVICE_HID, acpi_processor_osc,
>> + NULL, NULL);
>> }
>> #endif
>>
>> diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
>> index d161ff707de4..e8d1f645224f 100644
>> --- a/drivers/acpi/bus.c
>> +++ b/drivers/acpi/bus.c
>> @@ -1317,9 +1317,6 @@ static int __init acpi_bus_init(void)
>> goto error1;
>> }
>>
>> - /* Set capability bits for _OSC under processor scope */
>> - acpi_early_processor_osc();
>> -
>> /*
>> * _OSC method may exist in module level code,
>> * so it must be run after ACPI_FULL_INITIALIZATION
>> @@ -1335,7 +1332,15 @@ static int __init acpi_bus_init(void)
>>
>> acpi_sysfs_init();
>>
>> - acpi_early_processor_set_pdc();
>> +#ifdef CONFIG_ARCH_MIGHT_HAVE_ACPI_PDC
>> + status = acpi_early_processor_osc();
>> + if (ACPI_FAILURE(status)) {
>> + pr_err("_OSC methods failed, trying _PDC\n");
>> + acpi_early_processor_set_pdc();
>> + } else {
>> + pr_info("_OSC methods ran successfully\n");
>> + }
>> +#endif
>>
>> /*
>> * Maybe EC region is required at bus_scan/acpi_get_devices. So it
>> diff --git a/drivers/acpi/internal.h b/drivers/acpi/internal.h
>> index f979a2f7077c..e7cc41313997 100644
>> --- a/drivers/acpi/internal.h
>> +++ b/drivers/acpi/internal.h
>> @@ -151,17 +151,10 @@ int acpi_wakeup_device_init(void);
>> -------------------------------------------------------------------------- */
>> #ifdef CONFIG_ARCH_MIGHT_HAVE_ACPI_PDC
>> void acpi_early_processor_set_pdc(void);
>> +acpi_status acpi_early_processor_osc(void);
>>
>> void processor_dmi_check(void);
>> bool processor_physically_present(acpi_handle handle);
>> -#else
>> -static inline void acpi_early_processor_set_pdc(void) {}
>> -#endif
>> -
>> -#ifdef CONFIG_X86
>> -void acpi_early_processor_osc(void);
>> -#else
>> -static inline void acpi_early_processor_osc(void) {}
>> #endif
>>
>> /* --------------------------------------------------------------------------
>> --
next prev parent reply other threads:[~2023-06-30 9:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 16:10 [PATCH v3 0/5] Prefer using _OSC method over deprecated _PDC Michal Wilczynski
2023-06-13 16:10 ` [PATCH v3 1/5] acpi: Move logic responsible for conveying processor OSPM capabilities Michal Wilczynski
2023-06-13 16:10 ` [PATCH v3 2/5] acpi: Refactor arch_acpi_set_pdc_bits() Michal Wilczynski
2023-06-29 10:48 ` Rafael J. Wysocki
2023-06-13 16:10 ` [PATCH v3 3/5] acpi: Introduce new function callback for _OSC Michal Wilczynski
2023-06-29 11:04 ` Rafael J. Wysocki
2023-06-29 13:15 ` Rafael J. Wysocki
2023-06-30 9:02 ` Wilczynski, Michal
2023-06-30 9:10 ` Rafael J. Wysocki
2023-06-30 9:23 ` Wilczynski, Michal
2023-07-03 9:51 ` Wilczynski, Michal
2023-07-03 15:22 ` Rafael J. Wysocki
2023-07-06 13:25 ` Wilczynski, Michal
2023-06-30 8:46 ` Wilczynski, Michal
2023-07-03 8:54 ` Wilczynski, Michal
2023-07-03 15:20 ` Rafael J. Wysocki
2023-06-13 16:10 ` [PATCH v3 4/5] acpi: Use _OSC method to convey processor OSPM capabilities Michal Wilczynski
2023-06-29 14:23 ` Rafael J. Wysocki
2023-06-30 9:18 ` Wilczynski, Michal [this message]
2023-06-13 16:10 ` [PATCH v3 5/5] acpi: Remove acpi_hwp_native_thermal_lvt_osc() Michal Wilczynski
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=4de5c2da-5bdd-68fe-fa80-e96f778f7fd2@intel.com \
--to=michal.wilczynski@intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=x86@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