From: Luca Weiss <luca@z3ntu.xyz>
To: gregkh@linuxfoundation.org, Peter Chen <peter.chen@kernel.org>
Cc: linux-usb@vger.kernel.org, Peter Chen <peter.chen@kernel.org>,
Michael Grzeschik <m.grzeschik@pengutronix.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Wouter Franken <wouter@franken-peeters.be>
Subject: Re: [PATCH 1/1] Revert "usb: chipidea: move ci_ulpi_init after the phy initialization"
Date: Sat, 01 Jun 2024 15:42:29 +0200 [thread overview]
Message-ID: <4894045.GXAFRqVoOG@g550jk> (raw)
In-Reply-To: <20240517023648.3459188-1-peter.chen@kernel.org>
On Freitag, 17. Mai 2024 04:36:48 MESZ Peter Chen wrote:
> This reverts commit 22ffd399e6e7aa18ae0314278ed0b7f05f8ab679.
> People report this commit causes the driver defer probed, and never
> back to work[1][2].
>
> [1] https://lore.kernel.org/lkml/20240407011913.GA168730@nchen-desktop/T/#mc2b93bc11a8b01ec7cd0d0bf6b0b03951d9ef751
> [2] https://lore.kernel.org/lkml/20240407011913.GA168730@nchen-desktop/T/#me87d9a2a76c07619d83b3879ea14780da89fbbbf
>
Hi all,
the original commit appears to break USB on Qualcomm msm8974 also (and
probably other platforms), as reported in
https://lore.kernel.org/all/87546d93-3fe7-4459-b44a-47cbcab9da74@me.ssier.org/
Could this get picked up?
Regards
Luca
> Cc: Michael Grzeschik <m.grzeschik@pengutronix.de>
> Cc: Marek Szyprowski <m.szyprowski@samsung.com>
> Cc: Wouter Franken <wouter@franken-peeters.be>
> Signed-off-by: Peter Chen <peter.chen@kernel.org>
> ---
> drivers/usb/chipidea/core.c | 8 ++++----
> drivers/usb/chipidea/ulpi.c | 5 +++++
> 2 files changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/usb/chipidea/core.c b/drivers/usb/chipidea/core.c
> index bada13f704b6..835bf2428dc6 100644
> --- a/drivers/usb/chipidea/core.c
> +++ b/drivers/usb/chipidea/core.c
> @@ -1084,6 +1084,10 @@ static int ci_hdrc_probe(struct platform_device *pdev)
> return -ENODEV;
> }
>
> + ret = ci_ulpi_init(ci);
> + if (ret)
> + return ret;
> +
> if (ci->platdata->phy) {
> ci->phy = ci->platdata->phy;
> } else if (ci->platdata->usb_phy) {
> @@ -1138,10 +1142,6 @@ static int ci_hdrc_probe(struct platform_device *pdev)
> goto ulpi_exit;
> }
>
> - ret = ci_ulpi_init(ci);
> - if (ret)
> - return ret;
> -
> ci->hw_bank.phys = res->start;
>
> ci->irq = platform_get_irq(pdev, 0);
> diff --git a/drivers/usb/chipidea/ulpi.c b/drivers/usb/chipidea/ulpi.c
> index 89fb51e2c3de..dfec07e8ae1d 100644
> --- a/drivers/usb/chipidea/ulpi.c
> +++ b/drivers/usb/chipidea/ulpi.c
> @@ -68,6 +68,11 @@ int ci_ulpi_init(struct ci_hdrc *ci)
> if (ci->platdata->phy_mode != USBPHY_INTERFACE_MODE_ULPI)
> return 0;
>
> + /*
> + * Set PORTSC correctly so we can read/write ULPI registers for
> + * identification purposes
> + */
> + hw_phymode_configure(ci);
>
> ci->ulpi_ops.read = ci_ulpi_read;
> ci->ulpi_ops.write = ci_ulpi_write;
>
prev parent reply other threads:[~2024-06-01 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 2:36 [PATCH 1/1] Revert "usb: chipidea: move ci_ulpi_init after the phy initialization" Peter Chen
2024-06-01 13:42 ` Luca Weiss [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=4894045.GXAFRqVoOG@g550jk \
--to=luca@z3ntu.xyz \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.grzeschik@pengutronix.de \
--cc=m.szyprowski@samsung.com \
--cc=peter.chen@kernel.org \
--cc=wouter@franken-peeters.be \
/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;
as well as URLs for NNTP newsgroup(s).