All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
	mgross@linux.intel.com, rrangel@chromium.org
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v5 3/7] platform/x86: amd-pmc: call dump registers only once
Date: Tue, 6 Jul 2021 11:59:46 +0200	[thread overview]
Message-ID: <5a5fcc11-1fdd-278a-d458-e10954e083b4@redhat.com> (raw)
In-Reply-To: <20210629084803.248498-4-Shyam-sundar.S-k@amd.com>

Hi,

On 6/29/21 10:47 AM, Shyam Sundar S K wrote:
> Currently amd_pmc_dump_registers() routine is being called at
> multiple places. The best to call it is after command submission
> to SMU.
> 
> Signed-off-by: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
> ---
> v2: split into multiple patches as suggested by Hans
> v3: No change
> v4: No change
> v5: No change

Thanks, patch looks good to me:

Reviewed-by: Hans de Goede <hdegoede@redhat.com>

Regards,

Hans

> 
>  drivers/platform/x86/amd-pmc.c | 5 +----
>  1 file changed, 1 insertion(+), 4 deletions(-)
> 
> diff --git a/drivers/platform/x86/amd-pmc.c b/drivers/platform/x86/amd-pmc.c
> index b1d6175a13b2..e5107e3b1911 100644
> --- a/drivers/platform/x86/amd-pmc.c
> +++ b/drivers/platform/x86/amd-pmc.c
> @@ -182,6 +182,7 @@ static int amd_pmc_send_cmd(struct amd_pmc_dev *dev, bool set)
>  
>  out_unlock:
>  	mutex_unlock(&dev->lock);
> +	amd_pmc_dump_registers(dev);
>  	return rc;
>  }
>  
> @@ -194,7 +195,6 @@ static int __maybe_unused amd_pmc_suspend(struct device *dev)
>  	if (rc)
>  		dev_err(pdev->dev, "suspend failed\n");
>  
> -	amd_pmc_dump_registers(pdev);
>  	return 0;
>  }
>  
> @@ -207,7 +207,6 @@ static int __maybe_unused amd_pmc_resume(struct device *dev)
>  	if (rc)
>  		dev_err(pdev->dev, "resume failed\n");
>  
> -	amd_pmc_dump_registers(pdev);
>  	return 0;
>  }
>  
> @@ -279,8 +278,6 @@ static int amd_pmc_probe(struct platform_device *pdev)
>  	if (!dev->regbase)
>  		return -ENOMEM;
>  
> -	amd_pmc_dump_registers(dev);
> -
>  	mutex_init(&dev->lock);
>  	platform_set_drvdata(pdev, dev);
>  	amd_pmc_dbgfs_register(dev);
> 


  reply	other threads:[~2021-07-06  9:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29  8:47 [PATCH v5 0/7] updates to amd-pmc driver Shyam Sundar S K
2021-06-29  8:47 ` [PATCH v5 1/7] platform/x86: amd-pmc: Fix command completion code Shyam Sundar S K
2021-07-06  9:58   ` Hans de Goede
2021-06-29  8:47 ` [PATCH v5 2/7] platform/x86: amd-pmc: Fix SMU firmware reporting mechanism Shyam Sundar S K
2021-07-06  9:59   ` Hans de Goede
2021-06-29  8:47 ` [PATCH v5 3/7] platform/x86: amd-pmc: call dump registers only once Shyam Sundar S K
2021-07-06  9:59   ` Hans de Goede [this message]
2021-06-29  8:48 ` [PATCH v5 4/7] platform/x86: amd-pmc: Add support for logging SMU metrics Shyam Sundar S K
2021-06-29  8:48 ` [PATCH v5 5/7] amd-pmc: Add support for logging s0ix counters Shyam Sundar S K
2021-06-29  8:48 ` [PATCH v5 6/7] platform/x86: amd-pmc: Add support for ACPI ID AMDI0006 Shyam Sundar S K
2021-06-29  8:48 ` [PATCH v5 7/7] platform/x86: amd-pmc: Add new acpi id for future PMC controllers Shyam Sundar S K
2021-07-14 13:12 ` [PATCH v5 0/7] updates to amd-pmc driver 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=5a5fcc11-1fdd-278a-d458-e10954e083b4@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=mgross@linux.intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rrangel@chromium.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.