mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Maciej Wieczor-Retman <m.wieczorretman@pm.me>,
	Artem Bityutskiy <dedekind1@gmail.com>
Cc: hansg@kernel.org, ilpo.jarvinen@linux.intel.com,
	 linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v1 0/2] platform/x86/intel-uncore-freq: Expose instance ID in the sysfs
Date: Sun, 29 Mar 2026 12:30:59 -0700	[thread overview]
Message-ID: <edb2d0df79c1b29b83bfa0e5a36a70814ceee505.camel@linux.intel.com> (raw)
In-Reply-To: <acbwMA43StTa7kCM@wieczorr-mobl1.localdomain>

On Fri, 2026-03-27 at 21:03 +0000, Maciej Wieczor-Retman wrote:
> On 2026-03-27 at 19:51:54 +0200, Artem Bityutskiy wrote:
> > On Fri, 2026-03-27 at 15:36 +0000, Maciej Wieczor-Retman wrote:
> > > on newer systems that can have multiple clusters on a single die,
> > > the
> > > intel-uncore-freq driver behaves differently and the domain_id is
> > > a
> > > globally unique value - unique on all TPMI devices. Therefore
> > > it's
> > > difficult to match a specific instance to a set of UFS registers
> > > for
> > > example visible through /sys/kernel/debug/tpmi directories.
> > 
> > Although, I'd say that the key point isn't that "domain_id is
> > globally
> > unique" (though this is true), but that it's a synthetic value
> > generated by the driver rather than representing an actual HW
> > instance
> > ID.
> > 
> > Artem.
> 
> Right, that's worth emphasizing. I'll try to rephrase it when
> updating the
> patches.

I think the purpose is not clear. Also need to update the
documentation.
Let me write one tomorrow.

Thanks,
Srinivas



  reply	other threads:[~2026-03-29 19:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27 15:36 Maciej Wieczor-Retman
2026-03-27 15:36 ` [PATCH v1 1/2] platform/x86/intel-uncore-freq: Rename instance_id Maciej Wieczor-Retman
2026-03-27 17:56   ` Artem Bityutskiy
2026-03-27 21:06     ` Maciej Wieczor-Retman
2026-03-27 15:36 ` [PATCH v1 2/2] platform/x86/intel-uncore-freq: Expose instance ID in the sysfs Maciej Wieczor-Retman
2026-03-27 17:51 ` [PATCH v1 0/2] " Artem Bityutskiy
2026-03-27 21:03   ` Maciej Wieczor-Retman
2026-03-29 19:30     ` srinivas pandruvada [this message]
2026-03-30  8:11       ` Maciej Wieczor-Retman
2026-03-30 17:10         ` srinivas pandruvada
2026-03-30 17:52           ` Maciej Wieczor-Retman

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=edb2d0df79c1b29b83bfa0e5a36a70814ceee505.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=dedekind1@gmail.com \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.wieczorretman@pm.me \
    --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