From: Felipe Balbi <balbi@ti.com>
To: Felipe Balbi <balbi@ti.com>
Cc: 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>,
<k.opasiak@samsung.com>
Subject: Re: [PATCH v4] usb: gadget: f_fs: add "no_disconnect" mode
Date: Wed, 12 Nov 2014 20:44:14 -0600 [thread overview]
Message-ID: <20141113024414.GA19072@saruman> (raw)
In-Reply-To: <20141105194321.GS6548@saruman>
[-- Attachment #1: Type: text/plain, Size: 2268 bytes --]
HI,
On Wed, Nov 05, 2014 at 01:43:21PM -0600, Felipe Balbi wrote:
> On Mon, Nov 03, 2014 at 10:11:02AM -0600, Felipe Balbi wrote:
> > Hi,
> >
> > On Thu, Oct 09, 2014 at 03:21:51PM +0200, Robert Baldyga wrote:
> > > Since we can compose gadgets from many functions, there is the problem
> > > related to gadget breakage while FunctionFS daemon being closed. FFS
> > > function is userspace code so there is no way to know when it will close
> > > files (it doesn't matter what is the reason of this situation, it can
> > > be daemon logic, program breakage, process kill or any other). So when
> > > we have another function in gadget which, for example, sends some amount
> > > of data, does some software update or implements some real-time functionality,
> > > we may want to keep the gadget connected despite FFS function is no longer
> > > functional.
> > >
> > > We can't just remove one of functions from gadget since it has been
> > > enumerated, so the only way to keep entire gadget working is to make
> > > broken FFS function deactivated but still visible to host. For this
> > > purpose this patch introduces "no_disconnect" mode. It can be enabled
> > > by setting mount option "no_disconnect=1", and results with defering
> > > function disconnect to the moment of reopen ep0 file or filesystem
> > > unmount. After closing all endpoint files, FunctionFS is set to state
> > > FFS_DEACTIVATED.
> > >
> > > When ffs->state == FFS_DEACTIVATED:
> > > - function is still bound and visible to host,
> > > - setup requests are automatically stalled,
> > > - transfers on other endpoints are refused,
> > > - epfiles, except ep0, are deleted from the filesystem,
> > > - opening ep0 causes the function to be closes, and then FunctionFS
> > > is ready for descriptors and string write,
> > > - unmounting of the FunctionFS instance causes the function to be closed.
> > >
> > > Signed-off-by: Robert Baldyga <r.baldyga@samsung.com>
> >
> > 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).
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-13 2:44 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 [this message]
2014-11-13 16:28 ` Krzysztof Opasiak
2014-11-21 15:56 ` 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=20141113024414.GA19072@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