mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Kuppuswamy Sathyanarayanan
	<sathyanarayanan.kuppuswamy@linux.intel.com>,
	"Rafael J . Wysocki"	 <rafael@kernel.org>
Cc: Zhang Rui <rui.zhang@intel.com>,
	linux-pm@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] powercap: intel_rapl_tpmi: Remove FW_BUG from invalid version check
Date: Wed, 11 Feb 2026 17:02:36 -0800	[thread overview]
Message-ID: <42845834adf97303b19f421965d4f694732b8980.camel@linux.intel.com> (raw)
In-Reply-To: <20260211223401.1575776-1-sathyanarayanan.kuppuswamy@linux.intel.com>

On Wed, 2026-02-11 at 14:34 -0800, Kuppuswamy Sathyanarayanan wrote:
> On partitioned systems, multiple TPMI instances may exist per
> package,
> but RAPL registers are only valid on one instance since RAPL has
> package-scope control. Other instances return invalid versions during
> domain parsing, which is expected behavior on such systems.
> 
> Currently this generates a firmware bug warning:
>   intel_rapl_tpmi: [Firmware Bug]: Invalid version
> 
> Remove the FW_BUG tag, downgrade to pr_debug(), and update the
> message
> to clarify that invalid versions are expected on partitioned systems
> where only one instance can be valid.
> 
> Fixes: 9eef7f9da928 ("powercap: intel_rapl: Introduce RAPL TPMI
> interface driver")
> Reported-by: Zhang Rui <rui.zhang@intel.com>
> Signed-off-by: Kuppuswamy Sathyanarayanan
> <sathyanarayanan.kuppuswamy@linux.intel.com>

 Reviewed-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>

> ---
>  drivers/powercap/intel_rapl_tpmi.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/powercap/intel_rapl_tpmi.c
> b/drivers/powercap/intel_rapl_tpmi.c
> index 0a0b85f4528b..0f8abdc592bc 100644
> --- a/drivers/powercap/intel_rapl_tpmi.c
> +++ b/drivers/powercap/intel_rapl_tpmi.c
> @@ -157,7 +157,7 @@ static int parse_one_domain(struct
> tpmi_rapl_package *trp, u32 offset)
>  	tpmi_domain_flags = tpmi_domain_header >> 32 & 0xffff;
>  
>  	if (tpmi_domain_version == TPMI_VERSION_INVALID) {
> -		pr_warn(FW_BUG "Invalid version\n");
> +		pr_debug("Invalid version, other instances may be
> valid\n");
>  		return -ENODEV;
>  	}
>  

      reply	other threads:[~2026-02-12  1:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11 22:34 Kuppuswamy Sathyanarayanan
2026-02-12  1:02 ` srinivas pandruvada [this message]

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=42845834adf97303b19f421965d4f694732b8980.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=sathyanarayanan.kuppuswamy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®