From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Roger Quadros <rogerq@ti.com>,
Pawel Laszczak <pawell@cadence.com>,
Peter Chen <peter.chen@nxp.com>
Cc: "gregkh\@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jbergsagel\@ti.com" <jbergsagel@ti.com>,
"nsekhar\@ti.com" <nsekhar@ti.com>, "nm\@ti.com" <nm@ti.com>,
Suresh Punnoose <sureshp@cadence.com>,
Rahul Kumar <kurahul@cadence.com>
Subject: Re: [PATCH] usb:cdns3: Fix for CV CH9 running with g_zero driver.
Date: Thu, 10 Oct 2019 13:17:15 +0300 [thread overview]
Message-ID: <87a7a8vr9w.fsf@gmail.com> (raw)
In-Reply-To: <80047a82-4b01-8f54-7efa-c32f696ced43@ti.com>
hi,
Roger Quadros <rogerq@ti.com> writes:
>>> Peter Chen <peter.chen@nxp.com> writes:
>>>> On 19-10-07 07:39:11, Pawel Laszczak wrote:
>>>>> Patch fixes issue with Halt Endnpoint Test observed
>>>>
>>>> %s/Endnpoint/Endpoint
>>>>
>>>>>
>>>>> during using g_zero
>>>>> driver as DUT. Bug occurred only on some testing board.
>>>>
>>>> g_zero is legacy, please use configfs function source_sink or loopback
>>>> instead.
>>>
>>> We still want fixes for those ;-)
>>
>> So, if my understanding is correct in new production systems
>> using legacy gadget drivers is not recommended and we are not going to fix
>> any more bugs there.
>
> We can't really control who uses what. So we need to support legacy
> drivers as well.
>
> The issue detected by using g_zero is a controller driver issue and not an
> issue with g_zero itself.
thanks for clarifying, Roger.
Pawel, Roger is correct here. But in any case, if *real* bugs are found
on the legacy gadget drivers, let's see if they happen with
configfs-based interface as well. They should behave exactly the same
nowadays since legacy driver were converted to simply programmatically
spawn the configfs interface.
If there are bugs in legacy gadget drivers, we *WANT* to fix those.
--
balbi
prev parent reply other threads:[~2019-10-10 10:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 6:39 [PATCH] usb:cdns3: Fix for CV CH9 running with g_zero driver Pawel Laszczak
2019-10-07 8:40 ` Roger Quadros
2019-10-08 6:56 ` Peter Chen
2019-10-08 7:57 ` Pawel Laszczak
2019-10-08 8:44 ` Peter Chen
2019-10-08 9:43 ` Roger Quadros
2019-10-08 12:58 ` Felipe Balbi
2019-10-09 2:28 ` Peter Chen
2019-10-09 3:58 ` Pawel Laszczak
2019-10-09 13:50 ` Roger Quadros
2019-10-10 10:17 ` 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=87a7a8vr9w.fsf@gmail.com \
--to=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbergsagel@ti.com \
--cc=kurahul@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=pawell@cadence.com \
--cc=peter.chen@nxp.com \
--cc=rogerq@ti.com \
--cc=sureshp@cadence.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).