From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-phy@lists.infradead.org
Subject: Re: [PATCH] phy: renesas: rcar-gen3-usb2: Fix an error handling path in rcar_gen3_phy_usb2_probe()
Date: Sat, 7 Sep 2024 13:54:15 +0300 [thread overview]
Message-ID: <31112ec9-43cc-403b-a6c0-7e7804fdcda5@tuxon.dev> (raw)
In-Reply-To: <fc9f7b444f0ca645411868992bbe16514aeccfed.1725652654.git.christophe.jaillet@wanadoo.fr>
Hi, Christophe,
On 06.09.2024 22:57, Christophe JAILLET wrote:
> If an error occurs after the rcar_gen3_phy_usb2_init_bus(),
> reset_control_assert() must be called, as already done in the remove
> function.
>
> Fixes: 4eae16375357 ("phy: renesas: rcar-gen3-usb2: Add support to initialize the bus")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> drivers/phy/renesas/phy-rcar-gen3-usb2.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/phy/renesas/phy-rcar-gen3-usb2.c b/drivers/phy/renesas/phy-rcar-gen3-usb2.c
> index 58e123305152..8577056491de 100644
> --- a/drivers/phy/renesas/phy-rcar-gen3-usb2.c
> +++ b/drivers/phy/renesas/phy-rcar-gen3-usb2.c
> @@ -770,7 +770,7 @@ static int rcar_gen3_phy_usb2_probe(struct platform_device *pdev)
> if (IS_ERR(channel->rphys[i].phy)) {
> dev_err(dev, "Failed to create USB2 PHY\n");
> ret = PTR_ERR(channel->rphys[i].phy);
> - goto error;
> + goto err_control_assert;
> }
> channel->rphys[i].ch = channel;
> channel->rphys[i].int_enable_bits = rcar_gen3_int_enable[i];
> @@ -784,7 +784,7 @@ static int rcar_gen3_phy_usb2_probe(struct platform_device *pdev)
> if (IS_ERR(channel->vbus)) {
> if (PTR_ERR(channel->vbus) == -EPROBE_DEFER) {
> ret = PTR_ERR(channel->vbus);
> - goto error;
> + goto err_control_assert;
> }
> channel->vbus = NULL;
> }
> @@ -793,15 +793,17 @@ static int rcar_gen3_phy_usb2_probe(struct platform_device *pdev)
> if (IS_ERR(provider)) {
> dev_err(dev, "Failed to register PHY provider\n");
> ret = PTR_ERR(provider);
> - goto error;
> + goto err_control_assert;
> } else if (channel->is_otg_channel) {
> ret = device_create_file(dev, &dev_attr_role);
> if (ret < 0)
> - goto error;
> + goto err_control_assert;
> }
>
> return 0;
>
> +err_control_assert:
> + reset_control_assert(channel->rstc);
> error:
It would be simpler to fix it by calling here:
reset_control_assert(channel->rstc);
as it's the case for rcar_gen3_phy_usb2_remove().
Thank you,
Claudiu Beznea
> pm_runtime_disable(dev);
>
prev parent reply other threads:[~2024-09-07 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 19:57 Christophe JAILLET
2024-09-07 10:54 ` claudiu beznea [this message]
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=31112ec9-43cc-403b-a6c0-7e7804fdcda5@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=christophe.jaillet@wanadoo.fr \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=vkoul@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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®