From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Peter Chen <hzpeterchen@gmail.com>
Cc: Peter Chen <peter.chen@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
USB list <linux-usb@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: (EXT) Re: [RFC 1/1] usb: chipidea: ci_hdrc_imx: disable runtime pm for HSIC interface
Date: Tue, 29 Mar 2022 10:14:36 +0200 [thread overview]
Message-ID: <1891703.PYKUYFuaPT@steina-w> (raw)
In-Reply-To: <CAL411-o8TPNv8vAfdPtzTaFkOGc7EmwNJv1Jxc-YUv1wc_vq0g@mail.gmail.com>
Hello Peter,
Am Dienstag, 15. März 2022, 02:23:23 CEST schrieb Peter Chen:
> On Wed, Mar 2, 2022 at 5:42 PM Alexander Stein
>
> <alexander.stein@ew.tq-group.com> wrote:
> > With the add of power-domain support in commit 02f8eb40ef7b ("ARM: dts:
> > imx7s: Add power domain for imx7d HSIC") runtime suspend will disable
> > the power-domain. This prevents IRQs to occur when a new device is
> > attached
> > on a downstream hub.
> >
> > Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> > ---
> > Our board TQMa7x + MBa7x (i.MX7 based) uses a HSIC link to mounted USB HUB
> > on usbh device. Cold plugging an USB mass storage device is working fine.
> > But once the last non-HUB device is disconnected the ci_hdrc device goes
> > into runtime suspend.
>
> Would you please show the difference between cold boot and runtime
> suspend after disconnecting
> the last USB device?
>
> - Power domain on/off status for HUB device
> - Runtime suspend status at /sys entry for HUB device
> - "/sys/..power/wakeup" /sys entry for HUB device
I hope I got all entries you requested.
For reference this is the bus topology:
lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M
Bus 2 is a different connector and doesn't matter here. I'm disconnecting 'Dev
3' in this scenario.
After boot up with the bus as shown above:
$ cat /sys/bus/usb/devices/1-1/power/wakeup
disabled
$ cat /sys/bus/usb/devices/1-1/power/runtime_status
active
$ cat /sys/kernel/debug/pm_genpd/usb-hsic-phy/current_state
on
After disconnecting Dev 3 from the bus ('usb 1-1.2: USB disconnect, device
number 3' in dmesg) the status changes as follows (without the patch):
$ cat /sys/bus/usb/devices/1-1/power/wakeup
disabled
$ cat /sys/bus/usb/devices/1-1/power/runtime_status
suspended
$ cat /sys/kernel/debug/pm_genpd/usb-hsic-phy/current_state
off-0
For the record, when applying the posted patch this changes into:
$ cat /sys/bus/usb/devices/1-1/power/wakeup
disabled
$ cat /sys/bus/usb/devices/1-1/power/runtime_status
suspended
$ cat /sys/kernel/debug/pm_genpd/usb-hsic-phy/current_state
on
Regards,
Alexander
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Peter Chen <hzpeterchen@gmail.com>
Cc: Peter Chen <peter.chen@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
USB list <linux-usb@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: (EXT) Re: [RFC 1/1] usb: chipidea: ci_hdrc_imx: disable runtime pm for HSIC interface
Date: Tue, 29 Mar 2022 10:14:36 +0200 [thread overview]
Message-ID: <1891703.PYKUYFuaPT@steina-w> (raw)
In-Reply-To: <CAL411-o8TPNv8vAfdPtzTaFkOGc7EmwNJv1Jxc-YUv1wc_vq0g@mail.gmail.com>
Hello Peter,
Am Dienstag, 15. März 2022, 02:23:23 CEST schrieb Peter Chen:
> On Wed, Mar 2, 2022 at 5:42 PM Alexander Stein
>
> <alexander.stein@ew.tq-group.com> wrote:
> > With the add of power-domain support in commit 02f8eb40ef7b ("ARM: dts:
> > imx7s: Add power domain for imx7d HSIC") runtime suspend will disable
> > the power-domain. This prevents IRQs to occur when a new device is
> > attached
> > on a downstream hub.
> >
> > Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> > ---
> > Our board TQMa7x + MBa7x (i.MX7 based) uses a HSIC link to mounted USB HUB
> > on usbh device. Cold plugging an USB mass storage device is working fine.
> > But once the last non-HUB device is disconnected the ci_hdrc device goes
> > into runtime suspend.
>
> Would you please show the difference between cold boot and runtime
> suspend after disconnecting
> the last USB device?
>
> - Power domain on/off status for HUB device
> - Runtime suspend status at /sys entry for HUB device
> - "/sys/..power/wakeup" /sys entry for HUB device
I hope I got all entries you requested.
For reference this is the bus topology:
lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M
Bus 2 is a different connector and doesn't matter here. I'm disconnecting 'Dev
3' in this scenario.
After boot up with the bus as shown above:
$ cat /sys/bus/usb/devices/1-1/power/wakeup
disabled
$ cat /sys/bus/usb/devices/1-1/power/runtime_status
active
$ cat /sys/kernel/debug/pm_genpd/usb-hsic-phy/current_state
on
After disconnecting Dev 3 from the bus ('usb 1-1.2: USB disconnect, device
number 3' in dmesg) the status changes as follows (without the patch):
$ cat /sys/bus/usb/devices/1-1/power/wakeup
disabled
$ cat /sys/bus/usb/devices/1-1/power/runtime_status
suspended
$ cat /sys/kernel/debug/pm_genpd/usb-hsic-phy/current_state
off-0
For the record, when applying the posted patch this changes into:
$ cat /sys/bus/usb/devices/1-1/power/wakeup
disabled
$ cat /sys/bus/usb/devices/1-1/power/runtime_status
suspended
$ cat /sys/kernel/debug/pm_genpd/usb-hsic-phy/current_state
on
Regards,
Alexander
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-29 8:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 9:42 [RFC 1/1] usb: chipidea: ci_hdrc_imx: disable runtime pm for HSIC interface Alexander Stein
2022-03-02 9:42 ` Alexander Stein
2022-03-15 1:23 ` Peter Chen
2022-03-15 1:23 ` Peter Chen
2022-03-29 8:14 ` Alexander Stein [this message]
2022-03-29 8:14 ` (EXT) " Alexander Stein
2022-04-09 2:19 ` Peter Chen
2022-04-09 2:19 ` Peter Chen
2022-04-09 4:49 ` Jun Li
2022-04-09 4:49 ` Jun Li
2022-04-11 13:52 ` (EXT) " Alexander Stein
2022-04-11 13:52 ` Alexander Stein
2022-04-12 11:36 ` Jun Li
2022-04-12 11:36 ` Jun Li
2022-05-04 7:06 ` Alexander Stein
2022-05-04 7:06 ` Alexander Stein
2022-05-06 7:09 ` Jun Li
2022-05-06 7:09 ` Jun Li
2022-05-06 7:38 ` (EXT) " Alexander Stein
2022-05-06 7:38 ` Alexander Stein
2022-05-09 8:16 ` Jun Li
2022-05-09 8:16 ` Jun Li
2022-05-09 9:27 ` Frieder Schrempf
2022-05-09 9:27 ` Frieder Schrempf
2022-05-09 9:53 ` Jun Li
2022-05-09 9:53 ` Jun Li
2022-05-09 10:53 ` (EXT) " Alexander Stein
2022-05-09 10:53 ` Alexander Stein
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=1891703.PYKUYFuaPT@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hzpeterchen@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.