mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@ti.com>
To: Pawel Laszczak <pawell@cadence.com>,
	Felipe Balbi <felipe.balbi@linux.intel.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: Wed, 9 Oct 2019 16:50:48 +0300	[thread overview]
Message-ID: <80047a82-4b01-8f54-7efa-c32f696ced43@ti.com> (raw)
In-Reply-To: <BYAPR07MB4709490136F8F65A008C219EDD950@BYAPR07MB4709.namprd07.prod.outlook.com>

Pawel,

On 09/10/2019 06:58, Pawel Laszczak wrote:
> Hi,
> 
>>
>> Hi,
>>
>> 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.

cheers,
-roger

> 
> The legacy gadget drivers remains in the kernel only to support the old
> products.
> 
> So because we introduce new driver we should not worry  about legacy
> gadget drivers.
> 
> Is my understanding correct ?
> 
> pawell
>   
>>
>>>> Endpoint can defer transition to Halted state if endpoint has pending
>>>> requests.
>>>
>>> The implementation of halt handling is a little complicated, you may
>>> consider return -EAGAIN for functional stall through usb_ep_set_halt
>>> from function driver if the requests are pending, it doesn't need to
>>> defer such kinds of functional stall.
>>
>> -EAGAIN, IIRC is only supposed to be used for IN endpoint stalls.
>>
>> --
>> balbi

-- 
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

  reply	other threads:[~2019-10-09 13:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07  6:39 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 [this message]
2019-10-10 10:17         ` 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=80047a82-4b01-8f54-7efa-c32f696ced43@ti.com \
    --to=rogerq@ti.com \
    --cc=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=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

all inboxes | Powered by JetHome®