From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
To: Tim Bird <tim.bird@sonymobile.com>
Cc: Felipe Balbi <balbi@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux USB List <linux-usb@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Bjorn Andersson <Bjorn.Andersson@sonymobile.com>
Subject: Re: repeat... Re: BUG: usb: phy: msm: problem with EPROBE defer and extcon cleanup
Date: Tue, 18 Aug 2015 11:04:32 +0300 [thread overview]
Message-ID: <1439885072.2328.1.camel@mm-sol.com> (raw)
In-Reply-To: <55D2723F.4020709@sonymobile.com>
On Mon, 2015-08-17 at 16:46 -0700, Tim Bird wrote:
> Sorry - I mistyped Ivan's e-mail the first time.
>
> On 08/17/2015 04:43 PM, Tim Bird wrote:
> > Ivan,
> >
> > I'm seeing a bug in the phy-msm-usb.c code, when I get an EPROBE defer during probing the driver.
> > The code is statically linked in the kernel, and the dts for my board is specifying an extcon phandle
> > for the ID pin.
> >
> > Below is a fragment of the kernel output for a boot of this code. Messages prefixed with TRB
> > are my own debug printks. Note that the notifier block (at ee23513c) that gets registered
> > with extcon before the first probe failure, ultimately gets used during an ID pin event
> > (status change) by raw_notifier_call_chain(). This notifier block should be unregistered
> > if the probe fails, so that only the second one registered is on the call chain.
Right, I have missed to send one patch, sorry. Please, could you try this one [1].
Regards,
Ivan
[1] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg957405.html
prev parent reply other threads:[~2015-08-18 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 23:43 Tim Bird
2015-08-17 23:46 ` repeat... " Tim Bird
2015-08-18 8:04 ` 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=1439885072.2328.1.camel@mm-sol.com \
--to=iivanov@mm-sol.com \
--cc=Bjorn.Andersson@sonymobile.com \
--cc=balbi@ti.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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
Powered by JetHome