Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Andrew Davis <afd@ti.com>
Cc: "Markus Schneider-Pargmann (TI.com)" <msp@baylibre.com>,
	Tero Kristo <kristo@kernel.org>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	Vishal Mahaveer <vishalm@ti.com>,
	Kevin Hilman <khilman@baylibre.com>, Dhruva Gole <d-gole@ti.com>,
	Sebin Francis <sebin.francis@ti.com>,
	Kendall Willis <k-willis@ti.com>, Akashdeep Kaur <a-kaur@ti.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v10 3/3] firmware: ti_sci: Remove constant 0 function arguments
Date: Wed, 12 Nov 2025 09:28:53 -0600	[thread overview]
Message-ID: <20251112152853.3ad5co4usxu7hiyl@ultimate> (raw)
In-Reply-To: <bc987a5f-ee3f-4722-92e5-056bef4d84f9@ti.com>

On 09:26-20251112, Andrew Davis wrote:
> On 11/3/25 6:42 AM, Markus Schneider-Pargmann (TI.com) wrote:
> > ti_sci_cmd_prepare_sleep takes three arguments ctx_lo, ctx_hi and
> > debug_flags which are always 0 for the caller. Remove these arguments as
> > they are basically unused.
> > 
> 
> Does that matter? The functionality is still available and when we do
> use those arguments we will just have to revert this patch.

I agree. please leave the existing params alone. no point in optimizing
it.

> 
> > Signed-off-by: Markus Schneider-Pargmann (TI.com) <msp@baylibre.com>
> > ---
> >   drivers/firmware/ti_sci.c | 17 ++++++-----------
> >   1 file changed, 6 insertions(+), 11 deletions(-)
> > 
> > diff --git a/drivers/firmware/ti_sci.c b/drivers/firmware/ti_sci.c
> > index 811507ded63ac784ad6c6ad77b2f827768f3f3c7..023c603ae58cb5df176c66eec429bd0b4037b798 100644
> > --- a/drivers/firmware/ti_sci.c
> > +++ b/drivers/firmware/ti_sci.c
> > @@ -1664,14 +1664,10 @@ static int ti_sci_cmd_clk_get_freq(const struct ti_sci_handle *handle,
> >    * ti_sci_cmd_prepare_sleep() - Prepare system for system suspend
> >    * @handle:		pointer to TI SCI handle
> >    * @mode:		Device identifier
> > - * @ctx_lo:		Low part of address for context save
> > - * @ctx_hi:		High part of address for context save
> > - * @debug_flags:	Debug flags to pass to firmware
> >    *
> >    * Return: 0 if all went well, else returns appropriate error value.
> >    */
> > -static int ti_sci_cmd_prepare_sleep(const struct ti_sci_handle *handle, u8 mode,
> > -				    u32 ctx_lo, u32 ctx_hi, u32 debug_flags)
> > +static int ti_sci_cmd_prepare_sleep(const struct ti_sci_handle *handle, u8 mode)
> >   {
> >   	u32 msg_flags = mode == TISCI_MSG_VALUE_SLEEP_MODE_PARTIAL_IO ?
> >   			TI_SCI_FLAG_REQ_GENERIC_NORESPONSE :
> > @@ -1702,9 +1698,9 @@ static int ti_sci_cmd_prepare_sleep(const struct ti_sci_handle *handle, u8 mode,
> >   	req = (struct ti_sci_msg_req_prepare_sleep *)xfer->xfer_buf;
> >   	req->mode = mode;
> > -	req->ctx_lo = ctx_lo;
> > -	req->ctx_hi = ctx_hi;
> > -	req->debug_flags = debug_flags;
> > +	req->ctx_lo = 0;
> > +	req->ctx_hi = 0;
> > +	req->debug_flags = 0;
> >   	ret = ti_sci_do_xfer(info, xfer);
> >   	if (ret) {
> > @@ -3729,7 +3725,7 @@ static int ti_sci_sys_off_handler(struct sys_off_data *data)
> >   	dev_info(info->dev, "Entering Partial-IO because a powered wakeup-enabled device was found.\n");
> > -	ret = ti_sci_cmd_prepare_sleep(handle, TISCI_MSG_VALUE_SLEEP_MODE_PARTIAL_IO, 0, 0, 0);
> > +	ret = ti_sci_cmd_prepare_sleep(handle, TISCI_MSG_VALUE_SLEEP_MODE_PARTIAL_IO);
> >   	if (ret) {
> >   		dev_err(info->dev,
> >   			"Failed to enter Partial-IO %pe, trying to do an emergency restart\n",
> > @@ -3768,8 +3764,7 @@ static int ti_sci_prepare_system_suspend(struct ti_sci_info *info)
> >   			 * internal use and can be 0
> >   			 */
> >   			return ti_sci_cmd_prepare_sleep(&info->handle,
> > -							TISCI_MSG_VALUE_SLEEP_MODE_DM_MANAGED,
> > -							0, 0, 0);
> > +							TISCI_MSG_VALUE_SLEEP_MODE_DM_MANAGED);
> >   		} else {
> >   			/* DM Managed is not supported by the firmware. */
> >   			dev_err(info->dev, "Suspend to memory is not supported by the firmware\n");
> > 
> 

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource


  reply	other threads:[~2025-11-12 15:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 12:42 [PATCH v10 0/3] firmware: ti_sci: Partial-IO support Markus Schneider-Pargmann (TI.com)
2025-11-03 12:42 ` [PATCH v10 1/3] firmware: ti_sci: Support transfers without response Markus Schneider-Pargmann (TI.com)
2025-11-13  6:13   ` Dhruva Gole
2025-11-03 12:42 ` [PATCH v10 2/3] firmware: ti_sci: Partial-IO support Markus Schneider-Pargmann (TI.com)
2025-11-13  6:21   ` Dhruva Gole
2025-11-03 12:42 ` [PATCH v10 3/3] firmware: ti_sci: Remove constant 0 function arguments Markus Schneider-Pargmann (TI.com)
2025-11-12 15:26   ` Andrew Davis
2025-11-12 15:28     ` Nishanth Menon [this message]
2025-11-13  6:10       ` Dhruva Gole
2025-11-10 12:54 ` [PATCH v10 0/3] firmware: ti_sci: Partial-IO support Sebin Francis
2025-11-10 22:55 ` Kendall Willis
2025-11-13 19:05 ` (subset) " Nishanth Menon

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=20251112152853.3ad5co4usxu7hiyl@ultimate \
    --to=nm@ti.com \
    --cc=a-kaur@ti.com \
    --cc=afd@ti.com \
    --cc=d-gole@ti.com \
    --cc=k-willis@ti.com \
    --cc=khilman@baylibre.com \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msp@baylibre.com \
    --cc=sebin.francis@ti.com \
    --cc=ssantosh@kernel.org \
    --cc=vishalm@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