U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Tom Rini <trini@konsulko.com>
Cc: Vincent Jardin <vjardin@free.fr>,
	u-boot@lists.denx.de,
	Alif Zakuan Yuslaimi <alif.zakuan.yuslaimi@altera.com>,
	Jerome Forissier <jerome.forissier@arm.com>,
	Kory Maincent <kory.maincent@bootlin.com>,
	Kuan-Wei Chiu <visitorckw@gmail.com>,
	Marek Vasut <marek.vasut@mailbox.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Peng Fan <peng.fan@nxp.com>,
	Philip Molloy <philip.molloy@analog.com>,
	Quentin Schulz <quentin.schulz@cherry.de>,
	Raymond Mao <raymond.mao@riscstar.com>,
	Simon Glass <sjg@chromium.org>,
	Stefan Roese <stefan.roese@mailbox.org>, Yao Zi <me@ziyao.cc>
Subject: Re: [PATCH v1] thermal: qoriq: add Layerscape on-die TMU
Date: Thu, 28 May 2026 09:36:23 +0800	[thread overview]
Message-ID: <ahecFy5DsUzm/+aG@shlinux89> (raw)
In-Reply-To: <20260527150459.GG1858239@bill-the-cat>

On Wed, May 27, 2026 at 09:04:59AM -0600, Tom Rini wrote:
>On Wed, May 27, 2026 at 03:46:45PM +0200, Vincent Jardin wrote:
>> Add the support for lx2160 and other layerscape for:
>>   => temperature list
>>      | cluster67-thermal   | qoriq_thermal | tmu@1f80000
>>      | ddr1-cluster5-...   | qoriq_thermal | tmu@1f80000
>>      ...
>> 
>>   => temperature get cluster67-thermal
>>      cluster67-thermal: 56000 mC
>> 
>> It is designed as a generic UCLASS_THERMAL driver for the
>> QorIQ/Layerscape on-die Thermal Monitoring Unit (TMU).
>> 
>> It is similar to the "regs_v1" variant already implemented in
>> drivers/thermal/imx_tmu.c, but the i.MX driver depends
>> on <asm/arch/clock.h>, is_imx8m*() arch helpers, and OCOTP fuse
>> reads that do not exist on Layerscape.
>> 
>> Rather than #ifdef the QorIQ bits, this driver is a clean Layerscape
>> counterpart binding the standard "fsl,qoriq-tmu" compatible used by
>> the Linux qoriq_thermal driver and by the existing fsl-ls10{28,88}a
>> DTSIs too!
>
>Are there parts of the other driver that could be split out to a new
>file/header and shared? Or are the i.MX portions too deeply embedded and
>cannot be easily abstracted? Thanks!

QorIQ TMU and i.MX8MQ TMU shares same IP, with only minor differences.
As I recall, the differences are in calibration part.

Current imx_thermal driver is too deeply embedded, not in a good shape.
Need to give a look to clean it up.

Thanks,
Peng

>
>-- 
>Tom



  reply	other threads:[~2026-05-28  1:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27 13:46 [PATCH v1] thermal: qoriq: add Layerscape on-die TMU Vincent Jardin
2026-05-27 15:04 ` Tom Rini
2026-05-28  1:36   ` Peng Fan [this message]
2026-05-28 12:55     ` Vincent Jardin
     [not found] <"<20260527134744.511819-1-vjardin@free.fr>
2026-05-28 12:57 ` [PATCH v2] thermal: imx_tmu: extend with QorIQ/Layerscape TMU Vincent Jardin
2026-06-09 16:10   ` Peng Fan

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=ahecFy5DsUzm/+aG@shlinux89 \
    --to=peng.fan@oss.nxp.com \
    --cc=alif.zakuan.yuslaimi@altera.com \
    --cc=jerome.forissier@arm.com \
    --cc=kory.maincent@bootlin.com \
    --cc=marek.vasut@mailbox.org \
    --cc=me@ziyao.cc \
    --cc=neil.armstrong@linaro.org \
    --cc=peng.fan@nxp.com \
    --cc=philip.molloy@analog.com \
    --cc=quentin.schulz@cherry.de \
    --cc=raymond.mao@riscstar.com \
    --cc=sjg@chromium.org \
    --cc=stefan.roese@mailbox.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=visitorckw@gmail.com \
    --cc=vjardin@free.fr \
    /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