From: Dhruva Gole <d-gole@ti.com>
To: "Thomas Richard (TI)" <thomas.richard@bootlin.com>
Cc: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
"Santosh Shilimkar" <ssantosh@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
<richard.genoud@bootlin.com>, Udit Kumar <u-kumar1@ti.com>,
Prasanth Mantena <p-mantena@ti.com>,
Abhash Kumar <a-kumar2@ti.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>
Subject: Re: [PATCH v4 0/4] firmware: ti_sci: Introduce BOARDCFG_MANAGED mode for Jacinto family
Date: Mon, 9 Feb 2026 15:21:59 +0530 [thread overview]
Message-ID: <20260209095159.pfcthh5a4yo4q2em@lcpd911> (raw)
In-Reply-To: <20260204-ti-sci-jacinto-s2r-restore-irq-v4-0-67820af39eac@bootlin.com>
On Feb 04, 2026 at 16:03:37 +0100, Thomas Richard (TI) wrote:
> The fourth iteration of this series adds support for two new firmware
> capabilities:
> - MSG_FLAG_CAPS_LPM_IRQ_CONTEXT_LOST: Indicates that DM-Firmware is not
> able to restore IRQ context during resume after suspend-to-ram.
> - MSG_FLAG_CAPS_LPM_CLK_CONTEXT_LOST: Indicates that DM-Firmware is not
> able to restore clock context (rate and parent configuration) during
> resume after suspend-to-ram.
>
> Now, ti_sci driver determines whether to restore IRQs based on the
> MSG_FLAG_CAPS_LPM_IRQ_CONTEXT_LOST capability rather than the
> BOARDCFG_MANAGED mode. The same logic applies to the clock context.
>
> Both J784s4 and J7200 platforms support these new capabilities. A
> corresponding pull request has been submitted on DM-Firmware side to
> define and enable these capabilities.
>
> The value for the BOARDCFG_MANAGED mode has also been fixed.
>
> Public documentation for BOARDCFG_MANAGED mode and these new capabilities
> is currently unavailable. I will update the series with relevant
> documentation references as soon as they become available.
>
> I rebased the series on linux-next next-20260202.
>
> Best Regards,
> Thomas
>
> Signed-off-by: Thomas Richard (TI) <thomas.richard@bootlin.com>
> ---
> Changes in v4:
> - rebase on linux-next next-20260202.
> - fix BOARDCFG_MANAGED value.
> - add MSG_FLAG_CAPS_LPM_IRQ_CONTEXT_LOST firmware capability.
> - add MSG_FLAG_CAPS_LPM_CLK_CONTEXT_LOST firmware capability.
> - Link to v3: https://lore.kernel.org/r/20251205-ti-sci-jacinto-s2r-restore-irq-v3-0-d06963974ad4@bootlin.com
>
> Changes in v3:
> - rebased on linux-next
> - sci-clk: context_restore() operation restores also rate.
> - Link to v2: https://lore.kernel.org/r/20251127-ti-sci-jacinto-s2r-restore-irq-v2-0-a487fa3ff221@bootlin.com
>
> Changes in v2:
> - ti_sci: use hlist to store IRQs.
> - sci-clk: add context_restore operation
> - ti_sci: restore clock parents during resume
> - Link to v1: https://lore.kernel.org/r/20251017-ti-sci-jacinto-s2r-restore-irq-v1-0-34d4339d247a@bootlin.com
>
> ---
> Thomas Richard (TI) (4):
> firmware: ti_sci: add BOARDCFG_MANAGED mode support
> firmware: ti_sci: add support for restoring IRQs during resume
> clk: keystone: sci-clk: add restore_context() operation
> firmware: ti_sci: add support for restoring clock context during resume
The series looks good to me, just checking if maintainer prefers the 2/4
PATCH on IRQ restore to be split up. IMO similar to how you've split up
the clk restore support and then actually restored clk context in
another patch, you can do similar split up for IRQ.
No strong opinions from my side though.
Reviewed-by: Dhruva Gole <d-gole@ti.com>
>
> drivers/clk/keystone/sci-clk.c | 42 +++++++++--
> drivers/firmware/ti_sci.c | 164 ++++++++++++++++++++++++++++++++++++++---
> drivers/firmware/ti_sci.h | 6 ++
> 3 files changed, 192 insertions(+), 20 deletions(-)
> ---
> base-commit: c6fb8985458d675f32a22788f30afcba754b6d78
> change-id: 20251010-ti-sci-jacinto-s2r-restore-irq-428e008fd10c
>
> Best regards,
> --
> Thomas Richard (TI) <thomas.richard@bootlin.com>
>
>
--
Best regards,
Dhruva Gole
Texas Instruments Incorporated
next prev parent reply other threads:[~2026-02-09 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 15:03 [PATCH v4 0/4] firmware: ti_sci: Introduce BOARDCFG_MANAGED mode for Jacinto family Thomas Richard (TI)
2026-02-04 15:03 ` [PATCH v4 1/4] firmware: ti_sci: add BOARDCFG_MANAGED mode support Thomas Richard (TI)
2026-02-04 15:03 ` [PATCH v4 2/4] firmware: ti_sci: add support for restoring IRQs during resume Thomas Richard (TI)
2026-02-04 15:03 ` [PATCH v4 3/4] clk: keystone: sci-clk: add restore_context() operation Thomas Richard (TI)
2026-02-04 15:03 ` [PATCH v4 4/4] firmware: ti_sci: add support for restoring clock context during resume Thomas Richard (TI)
2026-02-09 9:51 ` Dhruva Gole [this message]
2026-03-31 14:28 ` [PATCH v4 0/4] firmware: ti_sci: Introduce BOARDCFG_MANAGED mode for Jacinto family Thomas Richard
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=20260209095159.pfcthh5a4yo4q2em@lcpd911 \
--to=d-gole@ti.com \
--cc=a-kumar2@ti.com \
--cc=gregory.clement@bootlin.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nm@ti.com \
--cc=p-mantena@ti.com \
--cc=richard.genoud@bootlin.com \
--cc=sboyd@kernel.org \
--cc=ssantosh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=thomas.richard@bootlin.com \
--cc=u-kumar1@ti.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