From: Mario Limonciello <mario.limonciello@amd.com>
To: Andy Shevchenko <andy@kernel.org>, Hans de Goede <hdegoede@redhat.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] platform/x86/amd: pmc: Use release_mem_region() to undo request_mem_region_muxed()
Date: Tue, 11 Jul 2023 16:32:14 -0500 [thread overview]
Message-ID: <a8a47091-1792-e10b-8a79-b931f410762a@amd.com> (raw)
In-Reply-To: <ZK05ReBRqbrggq/C@smile.fi.intel.com>
On 7/11/23 06:13, Andy Shevchenko wrote:
> On Tue, Jul 11, 2023 at 11:59:20AM +0200, Hans de Goede wrote:
>> Muxed (mem) regions will wait in request_mem_region_muxed() if the region
>> is busy (in use by another consumer) during the call.
>>
>> In order to wake-up possibly waiting other consumers of the region,
>> it must be released by a release_mem_region() call, which will actually
>> wake up any waiters.
>>
>> release_mem_region() also frees the resource created by
>> request_mem_region_muxed(), avoiding the need for the unmatched kfree().
>
> Seems reasonable to me.
> Do we need to have a Fixes tag?
> Reviewed-by: Andy Shevchenko <andy@kernel.org>
Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
I've gotten a positive test report with this as well, thanks!
>
>> Cc: Mario Limonciello <mario.limonciello@amd.com>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>> Mario, can you ask one of the reporters with a machine which needs the quirk
>> to test this ?
>> ---
>> drivers/platform/x86/amd/pmc-quirks.c | 8 ++------
>> 1 file changed, 2 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/platform/x86/amd/pmc-quirks.c b/drivers/platform/x86/amd/pmc-quirks.c
>> index 362e7c0097d7..ad702463a65d 100644
>> --- a/drivers/platform/x86/amd/pmc-quirks.c
>> +++ b/drivers/platform/x86/amd/pmc-quirks.c
>> @@ -11,7 +11,6 @@
>> #include <linux/dmi.h>
>> #include <linux/io.h>
>> #include <linux/ioport.h>
>> -#include <linux/slab.h>
>>
>> #include "pmc.h"
>>
>> @@ -135,12 +134,10 @@ static const struct dmi_system_id fwbug_list[] = {
>> */
>> static void amd_pmc_skip_nvme_smi_handler(u32 s2idle_bug_mmio)
>> {
>> - struct resource *res;
>> void __iomem *addr;
>> u8 val;
>>
>> - res = request_mem_region_muxed(s2idle_bug_mmio, 1, "amd_pmc_pm80");
>> - if (!res)
>> + if (!request_mem_region_muxed(s2idle_bug_mmio, 1, "amd_pmc_pm80"))
>> return;
>>
>> addr = ioremap(s2idle_bug_mmio, 1);
>> @@ -152,8 +149,7 @@ static void amd_pmc_skip_nvme_smi_handler(u32 s2idle_bug_mmio)
>>
>> iounmap(addr);
>> cleanup_resource:
>> - release_resource(res);
>> - kfree(res);
>> + release_mem_region(s2idle_bug_mmio, 1);
>> }
>>
>> void amd_pmc_process_restore_quirks(struct amd_pmc_dev *dev)
>> --
>> 2.41.0
>>
>
next prev parent reply other threads:[~2023-07-11 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 9:59 [PATCH] platform/x86/amd: pmc: Use release_mem_region() to undo request_mem_region_muxed() Hans de Goede
2023-07-11 11:13 ` Andy Shevchenko
2023-07-11 21:32 ` Mario Limonciello [this message]
2023-07-14 15:48 ` Hans de Goede
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=a8a47091-1792-e10b-8a79-b931f410762a@amd.com \
--to=mario.limonciello@amd.com \
--cc=andy@kernel.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox