X86 platform drivers
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Sanket.Goswami@amd.com,  platform-driver-x86@vger.kernel.org,
	 Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [PATCH v4 01/11] platform/x86/amd/pmc: Move STB block into amd_pmc_s2d_init()
Date: Thu, 7 Nov 2024 12:40:34 +0200 (EET)	[thread overview]
Message-ID: <abb0a98b-9563-2259-efff-63c3bc555748@linux.intel.com> (raw)
In-Reply-To: <20241107072714.943423-2-Shyam-sundar.S-k@amd.com>

On Thu, 7 Nov 2024, Shyam Sundar S K wrote:

> Transfer the support for STB-related file operations to the
> amd_pmc_s2d_init() function, thereby consolidating the STB and S2D
> (Spill to DRAM) functionality in one location.
> 
> For older platforms that supported S2D, exit immediately after creating
> debugfs. These platforms may not support the PMFW messages available on
> newer platforms. This adjustment is necessary due to the relocation of
> debugfs creation into amd_pmc_s2d_init().
> 
> Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
> Co-developed-by: Sanket Goswami <Sanket.Goswami@amd.com>
> Signed-off-by: Sanket Goswami <Sanket.Goswami@amd.com>
> Signed-off-by: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
> ---
>  drivers/platform/x86/amd/pmc/pmc.c | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/platform/x86/amd/pmc/pmc.c b/drivers/platform/x86/amd/pmc/pmc.c
> index bbb8edb62e00..54ceb2f9bf56 100644
> --- a/drivers/platform/x86/amd/pmc/pmc.c
> +++ b/drivers/platform/x86/amd/pmc/pmc.c
> @@ -648,15 +648,6 @@ static void amd_pmc_dbgfs_register(struct amd_pmc_dev *dev)
>  			    &s0ix_stats_fops);
>  	debugfs_create_file("amd_pmc_idlemask", 0644, dev->dbgfs_dir, dev,
>  			    &amd_pmc_idlemask_fops);
> -	/* Enable STB only when the module_param is set */
> -	if (enable_stb) {
> -		if (amd_pmc_is_stb_supported(dev))
> -			debugfs_create_file("stb_read", 0644, dev->dbgfs_dir, dev,
> -					    &amd_pmc_stb_debugfs_fops_v2);
> -		else
> -			debugfs_create_file("stb_read", 0644, dev->dbgfs_dir, dev,
> -					    &amd_pmc_stb_debugfs_fops);
> -	}
>  }
>  
>  static void amd_pmc_dump_registers(struct amd_pmc_dev *dev)
> @@ -982,6 +973,15 @@ static int amd_pmc_s2d_init(struct amd_pmc_dev *dev)
>  	u32 size = 0;
>  	int ret;
>  
> +	if (amd_pmc_is_stb_supported(dev)) {
> +		debugfs_create_file("stb_read", 0644, dev->dbgfs_dir, dev,
> +				    &amd_pmc_stb_debugfs_fops_v2);
> +	} else {
> +		debugfs_create_file("stb_read", 0644, dev->dbgfs_dir, dev,
> +				    &amd_pmc_stb_debugfs_fops);
> +		return 0;
> +	}
> +
>  	/* Spill to DRAM feature uses separate SMU message port */
>  	dev->msg_port = 1;

This now runs afoul the other issue you even mentioned yourself (IIRC), 
that is, dev->dbgfs_dir is initialized inside amd_pmc_dbgfs_register() 
which is only called after amd_pmc_s2d_init() until it is moved in patch 
2.

Thus, you need to combine patches 1 & 2 so you don't get a broken kernel
after this patch.

Please also move the enable_stb check inside amd_pmc_s2d_init() in this 
patch since that's another thing you've now broken in between patches 1 & 
3.

So to reiterate, in the first patch combine: Patch 1 + 2 + the if () logic 
move from amd_pmc_probe() into amd_pmc_s2d_init().

-- 
 i.


  reply	other threads:[~2024-11-07 10:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07  7:27 [PATCH v4 00/11] platform/x86/amd/pmc: Updates to AMD PMC driver Shyam Sundar S K
2024-11-07  7:27 ` [PATCH v4 01/11] platform/x86/amd/pmc: Move STB block into amd_pmc_s2d_init() Shyam Sundar S K
2024-11-07 10:40   ` Ilpo Järvinen [this message]
2024-11-07 15:32     ` Shyam Sundar S K
2024-11-07  7:27 ` [PATCH v4 02/11] platform/x86/amd/pmc: Invoke amd_pmc_s2d_init() Post Debugfs Registration Shyam Sundar S K
2024-11-07  7:27 ` [PATCH v4 03/11] platform/x86/amd/pmc: Move STB functionality to a new file for better code organization Shyam Sundar S K
2024-11-07  7:27 ` [PATCH v4 04/11] platform/x86/amd/pmc: Update function names to align with new STB file Shyam Sundar S K
2024-11-07  7:27 ` [PATCH v4 05/11] platform/x86/amd/pmc: Define enum for S2D/PMC msg_port and add helper function Shyam Sundar S K
2024-11-07 10:43   ` Ilpo Järvinen
2024-11-07  7:27 ` [PATCH v4 06/11] platform/x86/amd/pmc: Isolate STB code changes to a new file Shyam Sundar S K
2024-11-07  7:27 ` [PATCH v4 07/11] platform/x86/amd/pmc: Use ARRAY_SIZE() to fill num_ips information Shyam Sundar S K
2024-11-07 10:44   ` Ilpo Järvinen
2024-11-07  7:27 ` [PATCH v4 08/11] platform/x86/amd/pmc: Update IP information structure for newer SoCs Shyam Sundar S K
2024-11-07 11:02   ` Ilpo Järvinen
2024-11-07 15:34     ` Shyam Sundar S K
2024-11-07  7:27 ` [PATCH v4 09/11] platform/x86/amd/pmc: Update S2D message id for 1Ah Family 70h model Shyam Sundar S K
2024-11-07  7:27 ` [PATCH v4 10/11] platform/x86/amd/pmc: Add STB support for AMD Desktop variants Shyam Sundar S K
2024-11-07  7:27 ` [PATCH v4 11/11] MAINTAINERS: Change AMD PMC driver status to "Supported" Shyam Sundar S K

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=abb0a98b-9563-2259-efff-63c3bc555748@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=Sanket.Goswami@amd.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=hdegoede@redhat.com \
    --cc=mario.limonciello@amd.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