From: Pavel Machek <pavel@nabladev.com>
To: john.madieu.xa@bp.renesas.com
Cc: cip-dev@lists.cip-project.org,
Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
Pavel Machek <pavel@nabladev.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
john.madieu@gmail.com
Subject: Re: [cip-dev] [PATCH 6.1.y-cip 0/2] ADD RZ/G3E TSU support
Date: Tue, 3 Feb 2026 12:23:22 +0100 [thread overview]
Message-ID: <aYHaqqXncpyY45B5@duo.ucw.cz> (raw)
In-Reply-To: <20260203091201.98565-1-john.madieu.xa@bp.renesas.com>
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
Hi!
> This series adds the TSU (thermal sensor) support for Renesas RZ/G3E and
> addresses an unbind issue seen with the TSU device.
>
> Patch 1 extends the PM domain detach allowlist to include the RZ/G3E SoC
> compatible, avoiding asynchronous aborts when the TSU is unbound.
>
> Patch 2 backports the upstream RZ/G3E TSU DTSI support (TSU node, thermal zone,
> and CPU cooling maps). It also adds a "syscon" fallback compatible to the
> system-controller node so the TSU driver can access calibration data via
> syscon_regmap_lookup_by_phandle_args().
>
> This has been tested on an RZ/G3E SMARC platform.
Same as 6.12, this looks okay to me.
Reviewed-by: Pavel Machek <pavel@nabladev.com>
I can apply the series if it passes testing and there are no other
comments.
Best regards,
Pavel
--
In cooperation with Nabla.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-02-03 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 9:11 [PATCH 6.1.y-cip 0/2] ADD RZ/G3E TSU support John Madieu
2026-02-03 9:12 ` [PATCH 6.1.y-cip 1/2] PM: domains: Add RZ/G3E compatible to PM domain detach list John Madieu
2026-02-03 9:12 ` [PATCH 6.1.y-cip 2/2] arm64: dts: renesas: r9a09g047: Add TSU node John Madieu
2026-02-03 11:23 ` Pavel Machek [this message]
2026-02-05 4:06 ` [cip-dev] [PATCH 6.1.y-cip 0/2] ADD RZ/G3E TSU support nobuhiro.iwamatsu.x90
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=aYHaqqXncpyY45B5@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=john.madieu.xa@bp.renesas.com \
--cc=john.madieu@gmail.com \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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