From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
To: balbi@ti.com
Cc: Peter Chen <Peter.Chen@freescale.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tim Bird <tbird20d@gmail.com>,
linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] usb: chipidea: msm: Use USB PHY API to control PHY state
Date: Mon, 25 Aug 2014 11:49:30 +0300 [thread overview]
Message-ID: <1408956570.1629.2.camel@iivanov-dev> (raw)
In-Reply-To: <20140819190643.GF22003@saruman.home>
On Tue, 2014-08-19 at 14:06 -0500, Felipe Balbi wrote:
> On Fri, Aug 15, 2014 at 12:21:19PM +0300, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
> >
> > PHY drivers keep track of the current state of the hardware,
> > so don't change PHY settings under it.
> >
> > Signed-off-by: Ivan T. Ivanov <iivanov@mm-sol.com>
>
> looks correct to me from a PHY API perspective, so:
>
> Acked-by: Felipe Balbi <balbi@ti.com>
>
Thanks.
> However, it doesn't look like msm_phy_init() is equivalent to the lines
> removes. Care to comment ?
>
What I have to actually do is just add phy_init(). No need to remove
controller reinitialization. Tested and is working. Will post 2 new
patches shortly.
Regards,
Ivan
> > ---
> > drivers/usb/chipidea/ci_hdrc_msm.c | 9 ++-------
> > 1 file changed, 2 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/usb/chipidea/ci_hdrc_msm.c b/drivers/usb/chipidea/ci_hdrc_msm.c
> > index d72b9d2..81de834 100644
> > --- a/drivers/usb/chipidea/ci_hdrc_msm.c
> > +++ b/drivers/usb/chipidea/ci_hdrc_msm.c
> > @@ -20,13 +20,11 @@
> > static void ci_hdrc_msm_notify_event(struct ci_hdrc *ci, unsigned event)
> > {
> > struct device *dev = ci->gadget.dev.parent;
> > - int val;
> >
> > switch (event) {
> > case CI_HDRC_CONTROLLER_RESET_EVENT:
> > dev_dbg(dev, "CI_HDRC_CONTROLLER_RESET_EVENT received\n");
> > - writel(0, USB_AHBBURST);
> > - writel(0, USB_AHBMODE);
> > + usb_phy_init(ci->transceiver);
> > break;
> > case CI_HDRC_CONTROLLER_STOPPED_EVENT:
> > dev_dbg(dev, "CI_HDRC_CONTROLLER_STOPPED_EVENT received\n");
> > @@ -34,10 +32,7 @@ static void ci_hdrc_msm_notify_event(struct ci_hdrc *ci, unsigned event)
> > * Put the transceiver in non-driving mode. Otherwise host
> > * may not detect soft-disconnection.
> > */
> > - val = usb_phy_io_read(ci->transceiver, ULPI_FUNC_CTRL);
> > - val &= ~ULPI_FUNC_CTRL_OPMODE_MASK;
> > - val |= ULPI_FUNC_CTRL_OPMODE_NONDRIVING;
> > - usb_phy_io_write(ci->transceiver, val, ULPI_FUNC_CTRL);
> > + usb_phy_notify_disconnect(ci->transceiver, USB_SPEED_UNKNOWN);
> > break;
> > default:
> > dev_dbg(dev, "unknown ci_hdrc event\n");
> > --
> > 1.8.3.2
> >
>
prev parent reply other threads:[~2014-08-25 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 9:21 [PATCH RESEND] usb: chipidea: msm: Use USB PHY API to control PHY state Ivan T. Ivanov
2014-08-19 19:06 ` Felipe Balbi
2014-08-25 8:49 ` Ivan T. Ivanov [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=1408956570.1629.2.camel@iivanov-dev \
--to=iivanov@mm-sol.com \
--cc=Peter.Chen@freescale.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=tbird20d@gmail.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;
as well as URLs for NNTP newsgroup(s).