From: Pavel Machek <pavel@nabladev.com>
To: nobuhiro.iwamatsu.x90@mail.toshiba
Cc: cosmin-gabriel.tanislav.xa@renesas.com,
cip-dev@lists.cip-project.org, pavel@nabladev.com
Subject: Re: [cip-dev] [PATCH 6.12.y-cip 00/11] Add TSU support for RZ/T2H and RZ/N2H
Date: Wed, 15 Apr 2026 11:39:16 +0200 [thread overview]
Message-ID: <ad9cxLietTNoOoZ2@duo.ucw.cz> (raw)
In-Reply-To: <TY7PR01MB148184B2C1FBF41C6718DBD1CCD222@TY7PR01MB14818.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
Hi!
> > Renesas RZ/T2H (R9A09G077) and RZ/N2H (R9A09G087) SoCs expose the temperature calibration via SMC SIP and do
> > not have a reset for the TSU peripheral, and use different minimum and maximum temperature values compared to
> > RZ/G3E.
> >
> > Patches were cherry-picked from upstream kernel, except for patch
> > 7/11 which is needed to fix asynchronous aborts during unbind.
> >
> > See the MSTOP series for more details:
> > https://lore.kernel.org/cip-dev/20260115083451.1064048-1-claudiu.beznea.uj@bp.renesas.com/
>
> I reviewed this series, looks good to me.
> I can apply, if tests are OK and there is no comment,
> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/2453844182
>
> Reviewed-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.x90@mail.toshiba>
This looks okay to me.
Reviewed-by: Pavel Machek <pavel@nabladev.com>
Best regards,
Pavel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-04-15 9:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 17:02 [PATCH 6.12.y-cip 00/11] Add TSU support for RZ/T2H and RZ/N2H Cosmin Tanislav
2026-04-10 17:02 ` [PATCH 6.12.y-cip 01/11] clk: renesas: r9a09g077: Add TSU module clock Cosmin Tanislav
2026-04-10 17:02 ` [PATCH 6.12.y-cip 02/11] thermal: renesas: rzg3e: make reset optional Cosmin Tanislav
2026-04-10 17:02 ` [PATCH 6.12.y-cip 03/11] thermal: renesas: rzg3e: make min and max temperature per-chip Cosmin Tanislav
2026-04-10 17:02 ` [PATCH 6.12.y-cip 04/11] thermal: renesas: rzg3e: make calibration value retrieval per-chip Cosmin Tanislav
2026-04-10 17:02 ` [PATCH 6.12.y-cip 05/11] dt-bindings: thermal: r9a09g047-tsu: document RZ/T2H and RZ/N2H Cosmin Tanislav
2026-04-10 17:02 ` [PATCH 6.12.y-cip 06/11] thermal: renesas: rzg3e: add support for " Cosmin Tanislav
2026-04-10 17:02 ` [PATCH 6.12.y-cip 07/11] PM: domains: Add RZ/T2H and RZ/N2H compatibles to PM domain detach list Cosmin Tanislav
2026-04-10 17:02 ` [PATCH 6.12.y-cip 08/11] arm64: dts: renesas: r9a09g077: Add OPP table Cosmin Tanislav
2026-04-10 17:02 ` [PATCH 6.12.y-cip 09/11] arm64: dts: renesas: r9a09g077: Add TSU and thermal zones support Cosmin Tanislav
2026-04-15 21:10 ` Pavel Machek
2026-04-10 17:02 ` [PATCH 6.12.y-cip 10/11] arm64: dts: renesas: r9a09g087: Add OPP table Cosmin Tanislav
2026-04-10 17:02 ` [PATCH 6.12.y-cip 11/11] arm64: dts: renesas: r9a09g087: Add TSU and thermal zones support Cosmin Tanislav
2026-04-15 3:21 ` [PATCH 6.12.y-cip 00/11] Add TSU support for RZ/T2H and RZ/N2H nobuhiro.iwamatsu.x90
2026-04-15 9:39 ` Pavel Machek [this message]
2026-04-16 4:47 ` [cip-dev] " 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=ad9cxLietTNoOoZ2@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=cip-dev@lists.cip-project.org \
--cc=cosmin-gabriel.tanislav.xa@renesas.com \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
/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