[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6252026b-15c8-4243-8db7-efa0ef0b2fd7@ti.com>
Date: Tue, 16 Dec 2025 08:13:04 +0530
From: "Kumar, Udit" <u-kumar1@...com>
To: "Thomas Richard (TI.com)" <thomas.richard@...tlin.com>, Nishanth Menon
<nm@...com>, Tero Kristo <kristo@...nel.org>, Santosh Shilimkar
<ssantosh@...nel.org>, Michael Turquette <mturquette@...libre.com>, "Stephen
Boyd" <sboyd@...nel.org>
CC: Gregory CLEMENT <gregory.clement@...tlin.com>,
<richard.genoud@...tlin.com>, Prasanth Mantena <p-mantena@...com>, "Abhash
Kumar" <a-kumar2@...com>, Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
<linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
<linux-clk@...r.kernel.org>, <u-kumar1@...com>
Subject: Re: [PATCH v3 1/4] firmware: ti_sci: add BOARDCFG_MANAGED mode
support
On 12/5/2025 7:58 PM, Thomas Richard (TI.com) wrote:
> In BOARDCFG_MANAGED mode, the low power mode configuration is done
> statically for the DM via the boardcfg. Constraints are not supported, and
> prepare_sleep() is not needed.
>
> Signed-off-by: Thomas Richard (TI.com) <thomas.richard@...tlin.com>
> ---
> drivers/firmware/ti_sci.c | 10 +++++++---
> drivers/firmware/ti_sci.h | 2 ++
> 2 files changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/firmware/ti_sci.c b/drivers/firmware/ti_sci.c
> index 4a277937211f6..d77b631d9c855 100644
> --- a/drivers/firmware/ti_sci.c
> +++ b/drivers/firmware/ti_sci.c
> @@ -3772,8 +3772,11 @@ static int ti_sci_prepare_system_suspend(struct ti_sci_info *info)
> return ti_sci_cmd_prepare_sleep(&info->handle,
> TISCI_MSG_VALUE_SLEEP_MODE_DM_MANAGED,
> 0, 0, 0);
> + } else if (info->fw_caps & MSG_FLAG_CAPS_LPM_BOARDCFG_MANAGED) {
> + /* Nothing to do in the BOARDCFG_MANAGED mode */
> + return 0;
> } else {
> - /* DM Managed is not supported by the firmware. */
> + /* DM Managed and BoardCfg Managed are not supported by the firmware. */
> dev_err(info->dev, "Suspend to memory is not supported by the firmware\n");
> return -EOPNOTSUPP;
> }
> @@ -4011,12 +4014,13 @@ static int ti_sci_probe(struct platform_device *pdev)
> }
>
> ti_sci_msg_cmd_query_fw_caps(&info->handle, &info->fw_caps);
> - dev_dbg(dev, "Detected firmware capabilities: %s%s%s%s%s\n",
> + dev_dbg(dev, "Detected firmware capabilities: %s%s%s%s%s%s\n",
> info->fw_caps & MSG_FLAG_CAPS_GENERIC ? "Generic" : "",
> info->fw_caps & MSG_FLAG_CAPS_LPM_PARTIAL_IO ? " Partial-IO" : "",
> info->fw_caps & MSG_FLAG_CAPS_LPM_DM_MANAGED ? " DM-Managed" : "",
> info->fw_caps & MSG_FLAG_CAPS_LPM_ABORT ? " LPM-Abort" : "",
> - info->fw_caps & MSG_FLAG_CAPS_IO_ISOLATION ? " IO-Isolation" : ""
> + info->fw_caps & MSG_FLAG_CAPS_IO_ISOLATION ? " IO-Isolation" : "",
> + info->fw_caps & MSG_FLAG_CAPS_LPM_BOARDCFG_MANAGED ? " BoardConfig-Managed" : ""
> );
>
> ti_sci_setup_ops(info);
> diff --git a/drivers/firmware/ti_sci.h b/drivers/firmware/ti_sci.h
> index 91f234550c438..5f5c1ae7a19a8 100644
> --- a/drivers/firmware/ti_sci.h
> +++ b/drivers/firmware/ti_sci.h
> @@ -150,6 +150,7 @@ struct ti_sci_msg_req_reboot {
> * MSG_FLAG_CAPS_LPM_DM_MANAGED: LPM can be managed by DM
> * MSG_FLAG_CAPS_LPM_ABORT: Abort entry to LPM
> * MSG_FLAG_CAPS_IO_ISOLATION: IO Isolation support
> + * MSG_FLAG_CAPS_LPM_BOARDCFG_MANAGED: LPM config done statically for the DM via boardcfg
> *
> * Response to a generic message with message type TI_SCI_MSG_QUERY_FW_CAPS
> * providing currently available SOC/firmware capabilities. SoC that don't
> @@ -162,6 +163,7 @@ struct ti_sci_msg_resp_query_fw_caps {
> #define MSG_FLAG_CAPS_LPM_DM_MANAGED TI_SCI_MSG_FLAG(5)
> #define MSG_FLAG_CAPS_LPM_ABORT TI_SCI_MSG_FLAG(9)
> #define MSG_FLAG_CAPS_IO_ISOLATION TI_SCI_MSG_FLAG(7)
> +#define MSG_FLAG_CAPS_LPM_BOARDCFG_MANAGED TI_SCI_MSG_FLAG(10)
I think, you already noticed, this should be bit-12
> #define MSG_MASK_CAPS_LPM GENMASK_ULL(4, 1)
> u64 fw_caps;
> } __packed;
>
Powered by blists - more mailing lists