From: Felipe Balbi <balbi@ti.com>
To: Tim Bird <tim.bird@sonymobile.com>,
Peter Chen <peter.chen@freescale.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"Andersson, Björn" <Bjorn.Andersson@sonymobile.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tbird20d@gmail.com" <tbird20d@gmail.com>
Subject: Re: [PATCH 2/2] usb: phy: msm: fix connect/disconnect bug for dragonboard OTG port
Date: Fri, 20 Nov 2015 18:58:59 -0600 [thread overview]
Message-ID: <87mvu8b224.fsf@saruman.tx.rr.com> (raw)
In-Reply-To: <564FA087.5050807@sonymobile.com>
[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]
Hi,
Tim Bird <tim.bird@sonymobile.com> writes:
> On 11/16/2015 09:21 AM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Peter Chen <peter.chen@freescale.com> writes:
>>> On Wed, Nov 11, 2015 at 09:48:00AM -0800, Tim Bird wrote:
>>>>
>>>>
>>>> On 11/10/2015 07:14 PM, Peter Chen wrote:
>>>>> On Tue, Nov 10, 2015 at 04:46:51PM -0800, Tim Bird wrote:
>>>>>> This fixes a bug where if you disconnect and re-connect the USB cable,
>>>>>> the gadget driver stops working.
>>>>>>
>>>>>> Add support for async_irq to wake up driver from low power mode.
>>>>>> Without this, the power management code never calls resume.
>>>>>> Also, have the phy driver kick the gadget driver (chipidea otg)
>>>>>> by having the chipidea driver register with it, for vbus connect
>>>>>> notifications.
>>>>>>
>>>>>> Signed-off-by: Tim Bird <tim.bird@sonymobile.com>
>>>>>> ---
>>>>>> drivers/usb/chipidea/udc.c | 6 ++++++
>>>>>> drivers/usb/phy/phy-msm-usb.c | 16 ++++++++++++++++
>>>>>> include/linux/usb/msm_hsusb.h | 1 +
>>>>>> 3 files changed, 23 insertions(+)
>>
>> I just wanna know how you guys want this to be handled ? Through my tree
>> or chipidea's ? Or do we break the dependencies between the changes ?
>
> I'm fine with splitting it up. I'm sending a new series with 3 patches
> right after this message. Do both trees go to linux-next?
I have my fixes and next branches both on next. Not sure about chipidea.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2015-11-21 0:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 0:46 [PATCH 1/2] Documentation: dt-bindings: add async_irq to msm_hsusb Tim Bird
2015-11-11 0:46 ` [PATCH 2/2] usb: phy: msm: fix connect/disconnect bug for dragonboard OTG port Tim Bird
2015-11-11 3:14 ` Peter Chen
2015-11-11 17:48 ` Tim Bird
2015-11-12 9:13 ` Peter Chen
2015-11-16 17:21 ` Felipe Balbi
2015-11-20 22:36 ` Tim Bird
2015-11-21 0:58 ` Felipe Balbi [this message]
2015-11-23 2:10 ` Peter Chen
2015-11-11 20:33 ` [PATCH 1/2] Documentation: dt-bindings: add async_irq to msm_hsusb Rob Herring
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=87mvu8b224.fsf@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=Bjorn.Andersson@sonymobile.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=peter.chen@freescale.com \
--cc=robh+dt@kernel.org \
--cc=tbird20d@gmail.com \
--cc=tim.bird@sonymobile.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