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 1/2] Documentation: hwmon: coretemp: Update supported CPUs and TjMax values
Date: Mon, 12 Jan 2026 16:01:19 -0800	[thread overview]
Message-ID: <afac8d11-c70e-4479-9e04-2d502251ff15@roeck-us.net> (raw)
In-Reply-To: <20260106155426.547872-2-laveeshb@laveeshbansal.com>

On Tue, Jan 06, 2026 at 03:54:25PM +0000, Laveesh Bansal wrote:
> Update the coretemp documentation to reflect current driver capabilities:
> 
> - Extend the supported CPU model list to include Atom processors from
>   Bonnell through Jasper Lake, maintaining the original format with
>   model numbers and adding X86_FEATURE_DTHERM as the actual detection
>   mechanism. Added models: 0x37 (Bay Trail), 0x4a (Merrifield),
>   0x4c (Cherry Trail), 0x5a (Moorefield), 0x5c (Apollo Lake),
>   0x7a (Gemini Lake), 0x96 (Elkhart Lake), 0x9c (Jasper Lake)
> 
> - Update the description to note that per-package temperature sensing
>   is available on Sandy Bridge and all newer processors
> 
> - Clarify that TjMax is read from MSR_IA32_TEMPERATURE_TARGET on modern
>   CPUs (Nehalem and newer)
> 
> - Add TjMax values for newer Atom processor families to Appendix A:
>   - 22nm Silvermont/Bay Trail: E38xx at 110C, Z37xx at 90C
>   - 22nm Silvermont/Moorefield: Z35xx at 90C
>   - 14nm Airmont/Cherry Trail: Z8xxx at 90C
>   - 14nm Goldmont/Apollo Lake: 105C
>   - 14nm Goldmont Plus/Gemini Lake: 105C
>   - 10nm Tremont/Elkhart Lake: 105C
>   - 10nm Tremont/Jasper Lake: 105C
> 
> TjMax values obtained from Intel ARK and official datasheets:
> - E3845: https://www.intel.com/content/www/us/en/products/sku/78475/intel-atom-processor-e3845-2m-cache-1-91-ghz/specifications.html
> - Z3600/Z3700: https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/atom-z36xxx-z37xxx-datasheet-vol-1.pdf
> 
> Signed-off-by: Laveesh Bansal <laveeshb@laveeshbansal.com>

Applied.

Thanks,
Guenter

  reply	other threads:[~2026-01-13  0:01 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 [this message]
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

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=afac8d11-c70e-4479-9e04-2d502251ff15@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®