Devicetree
 help / color / mirror / Atom feed
From: Vitaliy Sochnev <sochnev.v.74@gmail.com>
To: daniel.lezcano@kernel.org
Cc: rafael@kernel.org, rui.zhang@intel.com, lukasz.luba@arm.com,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	ansuelsmth@gmail.com, linux-pm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Vitaliy Sochnev <sochnev.v.74@gmail.com>
Subject: [PATCH 0/2] thermal: airoha: Expose EN7581 CPU temperature
Date: Sat, 31 Oct 2026 16:19:10 +0200	[thread overview]
Message-ID: <20261031141912.1664575-1-sochnev.v.74@gmail.com> (raw)

EN7581 has a second thermal ADC for the CPU die at SCU offsets 0x2fc/0x308.
Expose it as sensor index 1 while keeping the main ADC at index 0 and
retaining zero-cell device tree compatibility. The hardware temperature
monitor and its trips continue to use only the main ADC.

Tested on Nokia XG-040G-MD (EN7581, OpenWrt 6.18.55): both zones read
successfully before and after reboot; temperatures tracked CPU load and
cooling, and matched direct ADC readings within 0.3 C. Twenty driver
unbind/bind cycles with an IRQ pending preserved both zones and handled
the interrupt each time. The driver builds for arm64 with W=1 and the
binding passes dt_binding_check.

Vitaliy Sochnev (2):
  dt-bindings: thermal: airoha: Allow sensor indices for EN7581
  thermal/drivers/airoha: Read the EN7581 CPU ADC

 .../thermal/airoha,en7581-thermal.yaml        |   6 +-
 drivers/thermal/airoha_thermal.c              | 157 ++++++++++++++++--
 2 files changed, 152 insertions(+), 11 deletions(-)


base-commit: 2dc1f296b5754dd2441fc8b6613a362a47f6b98f
-- 
2.55.0

             reply	other threads:[~2026-10-31 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-31 14:19 Vitaliy Sochnev [this message]
2026-10-31 14:19 ` [PATCH 1/2] dt-bindings: thermal: airoha: Allow sensor indices for EN7581 Vitaliy Sochnev
2026-10-31 14:19 ` [PATCH 2/2] thermal/drivers/airoha: Read the EN7581 CPU ADC Vitaliy Sochnev

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=20261031141912.1664575-1-sochnev.v.74@gmail.com \
    --to=sochnev.v.74@gmail.com \
    --cc=ansuelsmth@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.lezcano@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=rui.zhang@intel.com \
    /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