From: Randy Li <ayaka@soulik.info>
To: linux-usb@vger.kernel.org
Cc: John.Youn@synopsys.com, kishon@ti.com,
felipe.balbi@linux.intel.com, mark.rutland@arm.com,
devicetree@vger.kernel.org, heiko@sntech.de,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, randy.li@rock-chips.com,
Randy Li <ayaka@soulik.info>
Subject: [PATCH v9 0/2] the fixup for the USB HOST1 at rk3288 platform
Date: Fri, 21 Oct 2016 02:37:05 +0800 [thread overview]
Message-ID: <1476988627-14953-1-git-send-email-ayaka@soulik.info> (raw)
changelog:
v9
use a work_queue to reset usb phy to prevent access mutex lock at interrupter
runtime.
v8
minior fixup
v7
add the forgot dummy phy_reset() for the generic phy is disabled.
v7
Some minor fixup
v6
Send the last two patches
v5
A few modification at style, add the missing doc in the last
commit.
v4
1. Adding the reset callback in struct phy_ops.
2. Moving the reset into phy rockchip usb.
3. Trying to call a reset when dwc2 wakeup in rk3288.
v3
Rebased from previous commit
v2
Rebased from previous commit
v1
orignal from google
Randy Li (2):
usb: dwc2: assert phy reset when waking up in rk3288 platform
ARM: dts: rockchip: Point rk3288 dwc2 usb at the full PHY reset
arch/arm/boot/dts/rk3288.dtsi | 4 ++++
drivers/usb/dwc2/core.h | 1 +
drivers/usb/dwc2/core_intr.c | 11 +++++++++++
drivers/usb/dwc2/platform.c | 9 +++++++++
4 files changed, 25 insertions(+)
--
2.7.4
next reply other threads:[~2016-10-20 18:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 18:37 Randy Li [this message]
2016-10-20 18:37 ` [PATCH v9 1/2] usb: dwc2: assert phy reset when waking up in rk3288 platform Randy Li
2016-10-20 18:37 ` Randy Li
2016-10-21 19:27 ` John Youn
2016-10-23 9:33 ` ayaka
2016-10-23 9:33 ` ayaka
2016-10-25 1:30 ` John Youn
2016-12-06 12:00 ` Ayaka
2016-12-06 12:00 ` Ayaka
2016-12-06 19:43 ` John Youn
2016-12-06 19:43 ` John Youn
2016-10-20 18:37 ` [PATCH v9 2/2] ARM: dts: rockchip: Point rk3288 dwc2 usb at the full PHY reset Randy Li
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=1476988627-14953-1-git-send-email-ayaka@soulik.info \
--to=ayaka@soulik.info \
--cc=John.Youn@synopsys.com \
--cc=devicetree@vger.kernel.org \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.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.