From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Piyush Mehta <piyush.mehta@amd.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"michal.simek@amd.com" <michal.simek@amd.com>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"git@amd.com" <git@amd.com>
Subject: Re: [PATCH] usb: dwc3: xilinx: improve error handling for PM APIs
Date: Fri, 10 Nov 2023 23:39:11 +0000 [thread overview]
Message-ID: <20231110233810.ojsvcg3tqmim3lzg@synopsys.com> (raw)
In-Reply-To: <20231108043441.2103940-1-piyush.mehta@amd.com>
On Wed, Nov 08, 2023, Piyush Mehta wrote:
> Improve error handling for PM APIs in the dwc3_xlnx_probe function by
> introducing devm_pm_runtime_enable and error label. Removed unnecessary
> API pm_runtime_disable call in dwc3_xlnx_remove.
>
> Signed-off-by: Piyush Mehta <piyush.mehta@amd.com>
> ---
> drivers/usb/dwc3/dwc3-xilinx.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/usb/dwc3/dwc3-xilinx.c b/drivers/usb/dwc3/dwc3-xilinx.c
> index 5b7e92f476de..9cf26e9a1c3d 100644
> --- a/drivers/usb/dwc3/dwc3-xilinx.c
> +++ b/drivers/usb/dwc3/dwc3-xilinx.c
> @@ -294,10 +294,15 @@ static int dwc3_xlnx_probe(struct platform_device *pdev)
>
> pm_runtime_set_active(dev);
> pm_runtime_enable(dev);
> + ret = devm_pm_runtime_enable(dev);
You just did pm_runtime_enable() right above, why
devm_pm_runtime_enable() again?
> + if (ret < 0)
> + goto err_pm_set_suspended;
> +
> pm_suspend_ignore_children(dev, false);
> - pm_runtime_get_sync(dev);
> + return pm_runtime_resume_and_get(dev);
>
> - return 0;
> +err_pm_set_suspended:
> + pm_runtime_set_suspended(dev);
This doesn't look right. why set status suspended here?
BR,
Thinh
>
> err_clk_put:
> clk_bulk_disable_unprepare(priv_data->num_clocks, priv_data->clks);
> @@ -315,7 +320,6 @@ static void dwc3_xlnx_remove(struct platform_device *pdev)
> clk_bulk_disable_unprepare(priv_data->num_clocks, priv_data->clks);
> priv_data->num_clocks = 0;
>
> - pm_runtime_disable(dev);
> pm_runtime_put_noidle(dev);
> pm_runtime_set_suspended(dev);
> }
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-11-10 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 4:34 Piyush Mehta
2023-11-10 23:39 ` Thinh Nguyen [this message]
2023-11-14 5:47 ` Pandey, Radhey Shyam
2023-12-05 2:24 ` Thinh Nguyen
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=20231110233810.ojsvcg3tqmim3lzg@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=git@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=piyush.mehta@amd.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
all inboxes | Powered by JetHome®