mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Laveesh Bansal <laveeshb@laveeshbansal.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] hwmon: (coretemp) Add TjMax for Silvermont through Tremont Atoms
Date: Mon, 12 Jan 2026 16:02:04 -0800	[thread overview]
Message-ID: <b2c19a52-3795-457e-a9f3-b23d86164802@roeck-us.net> (raw)
In-Reply-To: <20260106155426.547872-3-laveeshb@laveeshbansal.com>

On Tue, Jan 06, 2026 at 03:54:26PM +0000, Laveesh Bansal wrote:
> Add fallback TjMax values for Intel Atom processors based on Silvermont,
> Airmont, Goldmont, and Tremont microarchitectures. These processors
> support MSR_IA32_TEMPERATURE_TARGET for reading TjMax directly, so these
> table entries serve as fallback values only when the MSR read fails
> (e.g., in some virtualization scenarios).
> 
> Added processors and TjMax values:
> 
> - INTEL_ATOM_SILVERMONT (0x37, Bay Trail):
>   - Stepping 9 (E38xx embedded): 110C
>   - Other steppings (Z37xx tablet): 90C
>   Stepping identified from Intel E3800 Specification Update.
> 
> - INTEL_ATOM_SILVERMONT_MID (0x4a, Merrifield): 90C
> 
> - INTEL_ATOM_SILVERMONT_MID2 (0x5a, Moorefield): 90C
> 
> - INTEL_ATOM_AIRMONT (0x4c, Cherry Trail): 90C
> 
> - INTEL_ATOM_GOLDMONT (0x5c, Apollo Lake): 105C
> 
> - INTEL_ATOM_GOLDMONT_PLUS (0x7a, Gemini Lake): 105C
> 
> - INTEL_ATOM_TREMONT (0x96, Elkhart Lake): 105C
> 
> - INTEL_ATOM_TREMONT_L (0x9c, Jasper Lake): 105C
> 
> Not included (MSR reads work reliably, server/specialized chips):
> - INTEL_ATOM_SILVERMONT_D (Avoton): Server, Tcase 97C
> - INTEL_ATOM_GOLDMONT_D (Denverton): Server, Tcase 82C
> - INTEL_ATOM_AIRMONT_NP (Lightning Mountain): Network processor
> - INTEL_ATOM_TREMONT_D (Jacobsville): Server
> - INTEL_ATOM_GRACEMONT (Alder Lake-N): Very new, MSR works
> 
> Reference: Intel datasheets and ARK processor specifications
> - Z3600/Z3700 datasheet: https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/atom-z36xxx-z37xxx-datasheet-vol-1.pdf
> - E3845 ARK: https://www.intel.com/content/www/us/en/products/sku/78475/intel-atom-processor-e3845-2m-cache-1-91-ghz/specifications.html
> - E3800 Spec Update: https://community.intel.com/cipcp26785/attachments/cipcp26785/embedded-atom-processors/4708/1/600834-329901-intel-atom-processor-e3800-product-family-su-rev015.pdf
> 
> Signed-off-by: Laveesh Bansal <laveeshb@laveeshbansal.com>

Applied.

Thanks,
Guenter

      reply	other threads:[~2026-01-13  0:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 15:54 [PATCH 0/2] hwmon: (coretemp) Documentation and TjMax table updates Laveesh Bansal
2026-01-06 15:54 ` [PATCH 1/2] Documentation: hwmon: coretemp: Update supported CPUs and TjMax values Laveesh Bansal
2026-01-13  0:01   ` Guenter Roeck
2026-01-06 15:54 ` [PATCH 2/2] hwmon: (coretemp) Add TjMax for Silvermont through Tremont Atoms Laveesh Bansal
2026-01-13  0:02   ` Guenter Roeck [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=b2c19a52-3795-457e-a9f3-b23d86164802@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=corbet@lwn.net \
    --cc=laveeshb@laveeshbansal.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®