From: Heiko Stuebner <heiko@sntech.de>
To: ayaka <ayaka@soulik.info>
Cc: linux-usb@vger.kernel.org, John.Youn@synopsys.com, kishon@ti.com,
felipe.balbi@linux.intel.com, mark.rutland@arm.com,
devicetree@vger.kernel.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh+dt@kernel.org, randy.li@rock-chips.com
Subject: Re: [RESEND PATCH v7 0/4] the fix for the USB HOST1 at rk3288 platform
Date: Tue, 13 Sep 2016 16:30:32 +0200 [thread overview]
Message-ID: <10185436.tRUJHEj2GK@phil> (raw)
In-Reply-To: <29f7cb2a-139e-ee70-a9f0-0573111207d8@soulik.info>
Am Dienstag, 13. September 2016, 19:26:03 CEST schrieb ayaka:
> On 09/13/2016 07:06 PM, Heiko Stuebner wrote:
> > Hi Randy,
> >
> > could you check if the other host-only dwc2 are also affected by this
> > (rk3188, rk3036) please? Because they also seem to act up in some strange
> > way
> But I don't have those board currently. I would arrange them anyway.
> Btw, I would send a new version to correct the fault reported by the
> auto build machine.
What I meant was, if you could check with some hardware-people first, if the
other host-only dwc2 are supposedly also affected. Right now I'm trying to
determine if this effect is somehow related with the usb debounce issue
I'm seeing with some recent dwc2 patches [0].
Heiko
[0] http://lists.infradead.org/pipermail/linux-rockchip/2016-September/012141.html
https://git.kernel.org/cgit/linux/kernel/git/balbi/usb.git/commit/?h=testing/next&id=2938fc63e0c26bf694436ac81bc776c8b7eced0c
prev parent reply other threads:[~2016-09-13 14:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 18:59 [RESEND PATCH v7 0/4] the fix for the USB HOST1 at rk3288 platform Randy Li
2016-09-09 18:59 ` Randy Li
2016-09-09 18:59 ` [RESEND PATCH v7 2/4] phy: rockchip-usb: use rockchip_usb_phy_reset to reset phy during wakeup Randy Li
2016-09-19 21:28 ` Rob Herring
[not found] ` <1473447580-10369-1-git-send-email-ayaka-xPW3/0Ywev/iB9QmIjCX8w@public.gmane.org>
2016-09-09 18:59 ` [RESEND PATCH v7 1/4] phy: Add reset callback Randy Li
2016-09-09 18:59 ` Randy Li
[not found] ` <1473447580-10369-2-git-send-email-ayaka-xPW3/0Ywev/iB9QmIjCX8w@public.gmane.org>
2016-09-10 8:51 ` Heiko Stuebner
2016-09-10 8:51 ` Heiko Stuebner
2016-09-10 11:57 ` Kishon Vijay Abraham I
2016-09-09 18:59 ` [RESEND PATCH v7 3/4] usb: dwc2: assert phy reset when waking up in rk3288 platform Randy Li
2016-09-09 18:59 ` Randy Li
[not found] ` <1473447580-10369-4-git-send-email-ayaka-xPW3/0Ywev/iB9QmIjCX8w@public.gmane.org>
2016-09-09 19:40 ` Sergei Shtylyov
2016-09-09 19:40 ` Sergei Shtylyov
2016-09-11 10:03 ` kbuild test robot
2016-09-11 10:03 ` kbuild test robot
2016-09-09 18:59 ` [RESEND PATCH v7 4/4] ARM: dts: rockchip: Point rk3288 dwc2 usb at the full PHY reset Randy Li
2016-09-09 18:59 ` Randy Li
2016-09-13 11:06 ` [RESEND PATCH v7 0/4] the fix for the USB HOST1 at rk3288 platform Heiko Stuebner
2016-09-13 11:06 ` Heiko Stuebner
2016-09-13 11:26 ` ayaka
2016-09-13 11:26 ` ayaka
2016-09-13 14:30 ` Heiko Stuebner [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=10185436.tRUJHEj2GK@phil \
--to=heiko@sntech.de \
--cc=John.Youn@synopsys.com \
--cc=ayaka@soulik.info \
--cc=devicetree@vger.kernel.org \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=randy.li@rock-chips.com \
--cc=robh+dt@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.