linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Chen <peter.chen@freescale.com>
To: Tim Bird <tbird20d@gmail.com>
Cc: "Ivan T. Ivanov" <iivanov@mm-sol.com>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Fwd: Status of chipidea msm USB reset patch
Date: Fri, 5 Sep 2014 08:50:12 +0800	[thread overview]
Message-ID: <20140905005011.GC3105@peterchendt> (raw)
In-Reply-To: <CA+bK7J6f-0OH-EnH2HbKEo+PZUf_At1TPgqyLVRg2RUVKQC9yg@mail.gmail.com>

On Thu, Sep 04, 2014 at 07:47:40AM -0700, Tim Bird wrote:
> On Fri, Aug 15, 2014 at 12:08 AM, Ivan T. Ivanov <iivanov@mm-sol.com> wrote:
> > On Fri, 2014-08-15 at 08:23 +0800, Peter Chen wrote:
> >> On Thu, Aug 14, 2014 at 11:54:02AM -0500, Felipe Balbi wrote:
> >> > Hi,
> >> >
> >> > On Thu, Aug 14, 2014 at 09:53:10AM -0700, Tim Bird wrote:
> >> > > Ping.  Anybody know the status of this patch?  Is it queued in someone's tree?
> >> > > Without it the USB driver for the Qualcomm 8974 (hsusb phy) doesn't
> >> > > work (at least for me).
> >> > > It looks like it got dropped from Ivan's original patch series, back in May.
> >> >
> >> > I don't maintain chipidea, Peter's the guy you want
> >>
> >> Below patch was not at msm chipidea patchset Ivan sent me.
> >>
> >> http://markmail.org/search/?q=%5BPATCH+v4+0%2F3%5D+usb%3A+chipidea%3A+msm%3A+Clean+and+fix+#query:%5BPATCH%20v4%200%2F3%5D%20usb%3A%20chipidea%3A%20msm%3A%20Clean%20and%20fix%20from%3A%22Ivan%20T.%20Ivanov%22+page:1+mid:mt7hgr7yamyzegg3+state:results
> >>
> >
> >
> > My fault. I have waiting PHY patches to be accepted to send this one.
> > Will rebase and resend.
> 
> Peter,
> 
> There appears to be no progress on this.
> 
> Can we just add the existing patch, get it into Linus' tree asap as
> a bugfix (preferably in this RC cycle)? Then ask Ivan to rebase his
> patches on top of this, instead of rebasing this patch as part of a
> larger effort with an unclear delivery date?
> 
> Note that without this patch, the driver in mainline doesn't work at all,
> so adding it couldn't possibly make mainline worse.
> 
> IMHO this should be CC:'ed to stable for the 3.16 kernel as well.  No
> other files are affected, and it applies and builds on 3.16 without problems.
> 
> Please let me know.
> 

OK, in fact, this patch is in my next chipidea next tree, and will be in 3.18-rc1.
(From the commit log, it doesn't show it is a bugfix:))
If it is a bugfix for you, I will send it go Greg.

Peter

>  -- Tim Bird
> Senior Software Engineer, Sony Mobile
> Architecture Group Chair, CE Workgroup, Linux Foundation
> 
> Patch follows for reference:
> Subject: [PATCH] usb: chipidea: msm: Use USB PHY API to control PHY state
> 
> 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>
> ---
>  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.2.2

-- 
Best Regards,
Peter Chen

  reply	other threads:[~2014-09-05  0:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25 21:38 Status of chipidea msm USB reset patch Tim Bird
2014-08-14 16:53 ` Fwd: " Tim Bird
2014-08-14 16:54   ` Felipe Balbi
     [not found]     ` <20140814165402.GA1445-HgARHv6XitL9zxVx7UNMDg@public.gmane.org>
2014-08-15  0:23       ` Peter Chen
2014-08-15  7:08         ` Ivan T. Ivanov
2014-09-04 14:47           ` Tim Bird
2014-09-05  0:50             ` Peter Chen [this message]
2014-09-05  1:01             ` Peter Chen
2014-09-10  9:36               ` Ivan T. Ivanov
2014-09-10 10:56                 ` Peter Chen

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=20140905005011.GC3105@peterchendt \
    --to=peter.chen@freescale.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=iivanov@mm-sol.com \
    --cc=linux-arm-msm@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).