linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@kernel.org>
To: Jerry Zhang <zhangjerry@google.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org
Cc: Michal Nazarewicz <mina86@mina86.com>,
	Krzysztof Opasiak <kopasiak90@gmail.com>,
	Badhri Jagan Sridharan <badhri@google.com>,
	Andrzej Pietrasiewicz <andrzej.p@samsung.com>,
	felixhaedicke@web.de
Subject: [V2,2/4] usb: gadget: configfs: Create control_config group
Date: Wed, 16 May 2018 09:13:52 +0300	[thread overview]
Message-ID: <87tvr886vz.fsf@linux.intel.com> (raw)

Jerry Zhang <zhangjerry@google.com> writes:

> Control_config is a group under gadget that acts
> as a normal config group, except it does not
> appear in cdev->configs.
>
> Functions that have exactly zero descriptors can
> be linked into control_config. These functions
> are bound and unbound with the rest of the gadget,
> but are never enabled. Also, functions with zero
> descriptors cannot be used in real configs.
>
> Create configfs_setup(), which will first attempt
> composite setup. If that fails, it will go through
> functions in control_config and use req_match to
> find and deliver the request to a function that can
> handle it.
>
> This allows the user to create a functionfs instance
> dedicated to handling non-standard control requests
> no matter what functions or configurations are
> currently active.
>
> Signed-off-by: Jerry Zhang <zhangjerry@google.com>

I didn't get patch 1

             reply	other threads:[~2018-05-16  6:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16  6:13 Felipe Balbi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-16  6:34 [V2,2/4] usb: gadget: configfs: Create control_config group Jerry Zhang
2018-04-24 21:29 Jerry Zhang

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=87tvr886vz.fsf@linux.intel.com \
    --to=balbi@kernel.org \
    --cc=andrzej.p@samsung.com \
    --cc=badhri@google.com \
    --cc=felixhaedicke@web.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=kopasiak90@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mina86@mina86.com \
    --cc=zhangjerry@google.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;
as well as URLs for NNTP newsgroup(s).