From: Andrzej Pietrasiewicz <andrzej.p@samsung.com>
To: Ruslan Bilovol <ruslan.bilovol@gmail.com>,
Krzysztof Opasiak <k.opasiak@samsung.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Peter Chen <peter.chen@freescale.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Balbi, Felipe" <balbi@ti.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 1/2] usb: gadget: udc-core: independent registration of gadgets and gadget drivers
Date: Mon, 16 Feb 2015 09:07:05 +0100 [thread overview]
Message-ID: <54E1A529.50705@samsung.com> (raw)
In-Reply-To: <CAB=otbQKFb9zZHdzm1POHvQh2w6aAKrp=Xojw6EKh_Ok-3NzeA@mail.gmail.com>
W dniu 15.02.2015 o 23:43, Ruslan Bilovol pisze:
<snip>
>>
>> In my opinion all things which you have described are working out-of-box
>> when you use configfs interface. It's mostly ready so you may create
>> equivalent of most legacy gadgets (apart from printer and tcm) and
>> just bind from one udc to another whenever you want.
>
> It's because legacy gadgets are easy to use and usually don't need any
> userspace-side configuration. Are there any plans to remove legacy
> drivers in the future?
>
I'm not going to express strong opinions here, but their name implies
that this can happen, some time in the future.
And I also think it will not happen before the userspace part
(libusbg, gt, gadgetd etc) is mature enough. My personal opinion
in that matter is that it will take at least a couple of years
to remove legacy gadgets entirely.
AP
next prev parent reply other threads:[~2015-02-16 8:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 1:25 [PATCH 0/2] usb/gadget: independent registration of gadgets and gadget Ruslan Bilovol
2015-01-29 1:25 ` [PATCH 1/2] usb: gadget: udc-core: independent registration of gadgets and gadget drivers Ruslan Bilovol
2015-01-29 15:56 ` Alan Stern
2015-02-08 19:04 ` Ruslan Bilovol
2015-02-09 8:46 ` Peter Chen
2015-02-09 16:35 ` Alan Stern
2015-02-09 18:06 ` Krzysztof Opasiak
2015-02-09 18:17 ` Krzysztof Opasiak
2015-02-09 20:00 ` Alan Stern
2015-02-09 23:46 ` Ruslan Bilovol
2015-02-10 8:47 ` Krzysztof Opasiak
2015-02-15 22:43 ` Ruslan Bilovol
2015-02-16 8:07 ` Andrzej Pietrasiewicz [this message]
2015-02-17 21:02 ` Ruslan Bilovol
2015-02-18 7:21 ` Andrzej Pietrasiewicz
2015-02-15 22:40 ` Ruslan Bilovol
2015-01-29 1:25 ` [PATCH 2/2] usb: gadget: legacy: don't use __init/__exit attributes for bind/unbind path Ruslan Bilovol
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=54E1A529.50705@samsung.com \
--to=andrzej.p@samsung.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=k.opasiak@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@freescale.com \
--cc=ruslan.bilovol@gmail.com \
--cc=stern@rowland.harvard.edu \
/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