From: peter.chen@freescale.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Add PHY nofity for some i.mx SoCs
Date: Fri, 14 Sep 2012 11:18:51 +0800 [thread overview]
Message-ID: <1347592731-12998-1-git-send-email-peter.chen@freescale.com> (raw)
At some i.mx SoCs, when controller works at host mode, the PHY
register needs to be changed at device connect, disconnect, bus
suspend and resume due to the SoC limitations.
The phy notification should be added according to below rules:
1. Only set HW_USBPHY_CTRL.ENHOSTDISCONDETECT
during high speed host mode.
2. Do not set HW_USBPHY_CTRL.ENHOSTDISCONDETECT
during the reset and speed negotiation period.
3. Do not set HW_USBPHY_CTRL.ENHOSTDISCONDETECT
during host suspend/resume sequence.
Please refer: i.mx23RM(page 413) for detail.
http://www.freescale.com/files/dsp/doc/ref_manual/IMX23RM.pdf
Freescale i.MX SoC, i.mx23, i.mx28 and i.mx6(i.mx6SL does not
need to follow the 3rd rule) need to follow above rules.
The correct notification setting method should be:
1. Set connect notify after the second bus reset.
2. Set disconnect notify after disconnection.
3. Set suspend nofity after bus goes to suspend (portsc.suspendM=1).
4. Set resume notify after resume (portsc.fpr=0).
Peter Chen (4):
usb: phy: add notify_suspend/notify_resume callback
usb: mxs-phy: implement notify_suspend/notify_resume callback
usb: chipidea: add phy notify at suspend/resume procedure
usb: refine phy notify operation during connection and disconnection
drivers/usb/chipidea/host.c | 75 +++++++++++++++++++++++++++++++++++++++++-
drivers/usb/core/hub.c | 14 ++++----
drivers/usb/otg/mxs-phy.c | 56 +++++++++++++++++++++++++-------
include/linux/usb/phy.h | 44 +++++++++++++++++++++----
4 files changed, 161 insertions(+), 28 deletions(-)
next reply other threads:[~2012-09-14 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 3:18 Peter Chen [this message]
2012-09-19 19:58 ` [PATCH 0/4] Add PHY nofity for some i.mx SoCs Mike Thompson
2012-09-20 2:56 ` Chen Peter-B29397
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=1347592731-12998-1-git-send-email-peter.chen@freescale.com \
--to=peter.chen@freescale.com \
--cc=linux-arm-kernel@lists.infradead.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 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).