From: Felipe Balbi <balbi@ti.com>
To: Krzysztof Opasiak <k.opasiak@samsung.com>
Cc: <balbi@ti.com>, "'Robert Baldyga'" <r.baldyga@samsung.com>,
"'David Cohen'" <david.a.cohen@linux.intel.com>,
<gregkh@linuxfoundation.org>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <mina86@mina86.com>,
<andrzej.p@samsung.com>, <m.szyprowski@samsung.com>
Subject: Re: [PATCH v4] usb: gadget: f_fs: add "no_disconnect" mode
Date: Fri, 21 Nov 2014 09:56:41 -0600 [thread overview]
Message-ID: <20141121155641.GK7508@saruman> (raw)
In-Reply-To: <0b1401cfff5e$d86dd8c0$89498a40$%opasiak@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 2093 bytes --]
On Thu, Nov 13, 2014 at 05:28:22PM +0100, Krzysztof Opasiak wrote:
> Hello,
>
> > -----Original Message-----
> > From: Felipe Balbi [mailto:balbi@ti.com]
> > Sent: Thursday, November 13, 2014 3:44 AM
> > To: Felipe Balbi
> > Cc: Robert Baldyga; David Cohen; gregkh@linuxfoundation.org; linux-
> > usb@vger.kernel.org; linux-kernel@vger.kernel.org;
> > mina86@mina86.com; andrzej.p@samsung.com; m.szyprowski@samsung.com;
> > k.opasiak@samsung.com
> > Subject: Re: [PATCH v4] usb: gadget: f_fs: add "no_disconnect" mode
>
> (...)
>
> > > > David, you have been messing with ffs lately, can I get a
> > Tested-by
> > > > from you on this patch ?
> > >
> > > ping. David ? Any chance you can test this one out ?
> >
> > a reminder on this request, it's getting close to tree lockdown
> > (probably another 2 to 3 weeks).
>
> I have tested this patch today but I'm afraid that I can't give
> tested-by tag:
>
> When I kill the daemon and then reconnect my device I get on my host:
>
> [776092.877175] usb 1-1.1: can't set config #1, error -32
>
> While on device there is only:
>
> [ 2147.035340] configfs-gadget gadget: high-speed config #1: The only
> one
>
> Moreover, I'm not very enthusiastic about the convention in which we
> allow
> to reconnect the device without any changes.
>
> In my opinion when daemon has been killed we should allow user to finish
> communication with other functions and then simply unbind our gadget.
> This should happen not only on reconnection but also when host is trying
> to enable configuration which contains this function "zombie".
> This function is not fully operational so it is very good idea to
> allow user to finish his job with other functions but when he reconnects
> the
> device we should unbind gadget to notify userspace that something is
> wrong.
> The same when we switch configuration.
>
> What do you think about this Michal and Felipe?
let's wait another merge window to discuss this one better. If it's
causing confusion/regressions, we better delay it.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-11-21 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 13:21 [PATCH v4] usb: gadget: f_fs: add "no_disconnect" mode Robert Baldyga
2014-11-03 16:11 ` Felipe Balbi
2014-11-05 19:43 ` Felipe Balbi
2014-11-13 2:44 ` Felipe Balbi
2014-11-13 16:28 ` Krzysztof Opasiak
2014-11-21 15:56 ` Felipe Balbi [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=20141121155641.GK7508@saruman \
--to=balbi@ti.com \
--cc=andrzej.p@samsung.com \
--cc=david.a.cohen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=k.opasiak@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mina86@mina86.com \
--cc=r.baldyga@samsung.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