From: "Pali Rohár" <pali.rohar@gmail.com>
To: balbi@ti.com
Cc: Linux USB Mailing List <linux-usb@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>, Aaro Koskinen <aaro.koskinen@iki.fi>,
Sebastian Reichel <sre@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] usb: gadget: function: phonet: balance usb_ep_disable calls
Date: Tue, 3 Feb 2015 20:27:52 +0100 [thread overview]
Message-ID: <201502032027.52712@pali> (raw)
In-Reply-To: <20150203191859.GA6508@saruman.tx.rr.com>
[-- Attachment #1: Type: Text/Plain, Size: 2014 bytes --]
On Tuesday 03 February 2015 20:18:59 Felipe Balbi wrote:
> On Tue, Feb 03, 2015 at 05:17:28PM +0100, Pali Rohár wrote:
> > On Tuesday 03 February 2015 16:43:45 Felipe Balbi wrote:
> > > Hi,
> > >
> > > On Tue, Feb 03, 2015 at 04:31:51PM +0100, Pali Rohár wrote:
> > > > On Tuesday 03 February 2015 00:15:19 Felipe Balbi wrote:
> > > > > f_phonet's ->set_alt() method will call
> > > > > usb_ep_disable() potentially on an endpoint which is
> > > > > already disabled. That's something the
> > > > > gadget/function driver must guarantee that it's
> > > > > always balanced.
> > > > >
> > > > > In order to balance the calls, just make sure the
> > > > > endpoint was enabled before by means of checking the
> > > > > validity of driver_data.
> > > > >
> > > > > Reported-by: Pali Rohár <pali.rohar@gmail.com>
> > > > > Signed-off-by: Felipe Balbi <balbi@ti.com>
> > > > > ---
> > > >
> > > > Your patches cause that kernel does not print any error
> > > > message to n900 screen anymore and reboot device in 10
> > > > seconds. I did not loaded any external modules.
> > >
> > > > In qemu I see this crash in early boot:
> > > alright, so n900's working fine. I'll wait until you debug
> > > qemu a little more, thank you
> >
> > NO! It does not working, see ^^^^. It break n900 totally!
>
> settle down a bit more. I don't have the HW you have and
> things are working fine on boards I _do_ have, there's not
> much more I can do to help without you doing your homework.
> Debug a bit more and bring more information as to what's
> going on, until then you're on your own.
And what more do you need? It crash on my n900 and also in qemu.
I sent you kernel crash dump from qemu which introduced *your*
patches. Before applying your patches there was no crash in early
boot stage.
In current state I review all 3 patches as:
Rejected-by: Pali Rohár <pali.rohar@gmail.com>
[It breaks booting Nokia N900 device]
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next parent reply other threads:[~2015-02-03 19:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1422918921-5472-1-git-send-email-balbi@ti.com>
[not found] ` <201502031717.28789@pali>
[not found] ` <20150203191859.GA6508@saruman.tx.rr.com>
2015-02-03 19:27 ` Pali Rohár [this message]
2015-02-03 19:35 ` [PATCH 1/3] usb: gadget: function: phonet: balance usb_ep_disable calls Felipe Balbi
2015-02-03 19:51 ` Felipe Balbi
2015-02-03 20:03 ` Pali Rohár
2015-02-03 19:57 ` Pali Rohár
2015-02-03 20:02 ` Felipe Balbi
2015-02-05 12:38 ` Pali Rohár
2015-02-20 0:09 ` Pali Rohár
2015-02-20 3:06 ` Felipe Balbi
2015-02-20 8:27 ` Pavel Machek
2015-02-20 14:39 ` Felipe Balbi
2015-02-20 21:15 ` Pavel Machek
2015-02-21 7:14 ` Felipe Balbi
2015-02-21 7:18 ` Felipe Balbi
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=201502032027.52712@pali \
--to=pali.rohar@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=balbi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sre@kernel.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