From: Krzysztof Opasiak <k.opasiak@samsung.com>
To: changbin.du@intel.com, balbi@kernel.org
Cc: gregkh@linuxfoundation.org, corbet@lwn.net,
linux-usb@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, "Du,
Changbin" <changbin.du@gmail.com>,
Du@vger.kernel.org
Subject: Re: [PATCH 1/2] usb: configfs: allow UDC binding rule configured as binding to *any* UDC
Date: Wed, 04 May 2016 10:14:46 +0200 [thread overview]
Message-ID: <5729AF76.7080508@samsung.com> (raw)
In-Reply-To: <1462244665-27681-2-git-send-email-changbin.du@intel.com>
On 05/03/2016 05:04 AM, changbin.du@intel.com wrote:
> From: "Du, Changbin" <changbin.du@gmail.com>
>
> On most platforms, there is only one device controller available.
> In this case, we desn't care the UDC's name. So let's ignore the
> name by setting 'UDC' to 'any'.
Hmm libubsgx allows to do this for a very long time. You simply pass
NULL instead of pointer to usbg_udc.
It is also possible to do this from command line, just simply:
$ echo `ls -1 /sys/class/udc | head -n 1` > UDC
So if we can easily do this from user space what's the benefit of adding
this special "any" keyword to kernel?
> And also we can change UDC name
> at any time if it is not binded (no need set to "" first).
>
Not sure if:
$ echo "" > UDC
is really a problem. Personally I'm quite used to situation in which I
have to turn the light off before turning it on once again;)
Cheers,
--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2016-05-04 8:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 3:04 [PATCH 0/2] Add binding rule *any* support for USB Gadget Configfs changbin.du
2016-05-03 3:04 ` [PATCH 1/2] usb: configfs: allow UDC binding rule configured as binding to *any* UDC changbin.du
2016-05-04 8:14 ` Krzysztof Opasiak [this message]
2016-05-05 5:46 ` Du, Changbin
2016-05-05 7:31 ` Krzysztof Opasiak
2016-05-06 2:46 ` Du, Changbin
2016-05-06 5:49 ` Krzysztof Opasiak
2016-06-04 20:56 ` Pavel Machek
2016-06-06 2:21 ` Du, Changbin
2016-05-03 3:04 ` [PATCH 2/2] Documentation: gadget_configfs: update UDC binding changbin.du
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=5729AF76.7080508@samsung.com \
--to=k.opasiak@samsung.com \
--cc=Du@vger.kernel.org \
--cc=balbi@kernel.org \
--cc=changbin.du@gmail.com \
--cc=changbin.du@intel.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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