public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: "Peter Chen (CIX)" <peter.chen@kernel.org>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: gregkh@linuxfoundation.org, shawnguo@kernel.org,
	s.hauer@pengutronix.d, kernel@pengutronix.de, festevam@gmail.com,
	jun.li@nxp.com, linux-usb@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] implement workaround for ERR051725
Date: Tue, 17 Jun 2025 16:19:45 +0800	[thread overview]
Message-ID: <20250617081945.GA1716298@nchen-desktop> (raw)
In-Reply-To: <20250614125645.207732-1-xu.yang_2@nxp.com>

On 25-06-14 20:56:42, Xu Yang wrote:
> Currently, the USB2.0 phy on some imx7d compliant Soc has below issue.
> 
> ERR051725:
> USB: With the USB controller configured as device mode, Clearing the RS
> bit of USBCMD register fails to cause USB device to be detached
> 
> Description
> 1. USB controller working as high speed device mode with USB gadget
>    function enabled
> 2. Cable plugged into USB host
> 3. Use case is software-controlled detach from USB device side
> 
> The expected result is device side terminations removed, increase in USB
> signal amplitude, USB host detect device is detached. But the issue is
> that the clear RS bit of USBCMD register cannot cause device detach event.
> 
> Workaround
>   - Use the below steps to detach from the host:
>       write USBCMD.RS = 0b
>       write CTRL2[7:6] = 01b
>       write CTRL2[8] = 1b
>   - As CTRL2[8] is set at detach case, so attach the steps should add clear
>     CTRL2[8]:
>       write USBCMD.RS = 1b
>       write CTRL2[8] = 0b
> 
> This will add workaround for it.

Is it imx7d specific PHY issue, since other i.mx SoCs which use chipidea
IP don't have such issue?

Peter
> 
> Xu Yang (3):
>   usb: chipidea: udc: add CI_HDRC_CONTROLLER_PULLUP_EVENT event
>   usb: chipidea: imx: add imx_usbmisc_pullup() hook
>   usb: chipidea: imx: implement workaround for ERR051725
> 
>  drivers/usb/chipidea/ci_hdrc_imx.c |  5 ++++
>  drivers/usb/chipidea/ci_hdrc_imx.h |  1 +
>  drivers/usb/chipidea/udc.c         |  5 ++++
>  drivers/usb/chipidea/usbmisc_imx.c | 39 ++++++++++++++++++++++++++++++
>  include/linux/usb/chipidea.h       |  1 +
>  5 files changed, 51 insertions(+)
> 
> -- 
> 2.34.1
> 

-- 

Best regards,
Peter


  parent reply	other threads:[~2025-06-17  8:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-14 12:56 [PATCH 0/3] implement workaround for ERR051725 Xu Yang
2025-06-14 12:56 ` [PATCH 1/3] usb: chipidea: udc: add CI_HDRC_CONTROLLER_PULLUP_EVENT event Xu Yang
2025-06-18 10:35   ` Peter Chen (CIX)
2025-06-14 12:56 ` [PATCH 2/3] usb: chipidea: imx: add imx_usbmisc_pullup() hook Xu Yang
2025-06-18 10:36   ` Peter Chen (CIX)
2025-06-14 12:56 ` [PATCH 3/3] usb: chipidea: imx: implement workaround for ERR051725 Xu Yang
2025-06-18 10:40   ` Peter Chen (CIX)
2025-06-17  8:19 ` Peter Chen (CIX) [this message]
2025-06-18  6:06   ` [PATCH 0/3] " Xu Yang

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=20250617081945.GA1716298@nchen-desktop \
    --to=peter.chen@kernel.org \
    --cc=festevam@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=imx@lists.linux.dev \
    --cc=jun.li@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=s.hauer@pengutronix.d \
    --cc=shawnguo@kernel.org \
    --cc=xu.yang_2@nxp.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