public inbox for linux-hwmon@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Sohil Mehta <sohil.mehta@intel.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	linux-kernel@vger.kernel.org
Cc: Borislav Petkov <bp@alien8.de>,
	Guenter Roeck <linux@roeck-us.net>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
	Iwona Winiarska <iwona.winiarska@intel.com>,
	linux-hwmon@vger.kernel.org, openbmc@lists.ozlabs.org,
	Thomas Gleixner <tglx@kernel.org>,
	Tony Luck <tony.luck@intel.com>,
	x86@kernel.org
Subject: Re: [PATCH] peci: Remove dependency on x86 CPU variables
Date: Wed, 18 Feb 2026 11:30:06 -0800	[thread overview]
Message-ID: <5cfea5f4-1ced-4559-8de1-4e96116536f4@intel.com> (raw)
In-Reply-To: <02494c50-8239-4e9d-b653-451728e5b5fc@intel.com>

On 2/18/26 11:26, Sohil Mehta wrote:
>> diff -puN include/linux/peci.h~peci-sanity include/linux/peci.h
>> --- a/include/linux/peci.h~peci-sanity	2026-02-18 08:19:42.371396743 -0800
>> +++ b/include/linux/peci.h	2026-02-18 08:19:42.388397383 -0800
>> @@ -72,7 +72,7 @@ static inline struct peci_controller *to
>>  struct peci_device {
>>  	struct device dev;
>>  	struct {
>> -		u32 x86_vfm;
>> +		u32 device_id;
> 
> There is a kernel-doc comment on top of this struct as well that needs
> to reflect the change.

Thanks, I'll fix it up.

>> diff -puN include/linux/peci-cpu.h~peci-sanity include/linux/peci-cpu.h
>> -#include "../../arch/x86/include/asm/intel-family.h"
>> +/*
>> + * These are in the format of and match the values of the x86
>> + * CPUID.01H:EAX[19:4]. They encode the model and family of
> 
> Can we include the extended family bits in the *comment* to say
> EAX[27:4]? I expect Family 19 (DMR) will be added soonish, which will
> make the comment stale.

Right now, all the constants are 16 bits long, that's 19:4. If a future
CPU model needs more bits, they'll make all the constants bigger and can
change the comment.

>> + * the CPU with which the driver is interfacing.
>> + *
>> + * All driver functionality is common across all CPU steppings
>> + * of a given model, so the lower 4 stepping bits are excluded
>> + * from these IDs.
>> + */
>> +#define PECI_INTEL_HASWELL_X		0x306C
>> +#define PECI_INTEL_BROADWELL_X		0x406F
>> +#define PECI_INTEL_BROADWELL_D		0x5066
>> +#define PECI_INTEL_SKYLAKE_X		0x5065
>> +#define PECI_INTEL_ICELAKE_X		0x606A
>> +#define PECI_INTEL_ICELAKE_D		0x606C
>> +#define PECI_INTEL_SAPPHIRERAPIDS_X	0x806F
>> +#define PECI_INTEL_EMERALDRAPIDS_X	0xC06F
>>  
> 
> The _D has been used in Intel official product names such as "XEON D".
> AFAIU, The _X notation is specific to intel-family.h. Should that be
> explained in the comment above?
> 
> Something like:
> 
>  *	_X	- regular server parts
>  *	_D	- micro server parts

I think I just verbatim copied the intel-family.h names and added PECI_.
Are you seeing something different.

BTW, we should probably comment the naming scheme and at least mention
that it should be consistent with the x86 code.

  reply	other threads:[~2026-02-18 19:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-18 17:03 [PATCH] peci: Remove dependency on x86 CPU variables Dave Hansen
2026-02-18 19:26 ` Sohil Mehta
2026-02-18 19:30   ` Dave Hansen [this message]
2026-02-18 19:36     ` Sohil Mehta
2026-02-18 19:43       ` Sohil Mehta
2026-02-18 19:46         ` Dave Hansen
2026-02-19 10:20 ` David Laight
2026-02-19 14:57   ` Dave Hansen

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=5cfea5f4-1ced-4559-8de1-4e96116536f4@intel.com \
    --to=dave.hansen@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=iwona.winiarska@intel.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mingo@redhat.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=sohil.mehta@intel.com \
    --cc=tglx@kernel.org \
    --cc=tony.luck@intel.com \
    --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