From: Frank Li <Frank.li@nxp.com>
To: Roger Quadros <rogerq@kernel.org>
Cc: "r-gunasekaran@ti.com" <r-gunasekaran@ti.com>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"Jun Li" <jun.li@nxp.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Elson Roy Serrao" <quic_eserrao@quicinc.com>,
"Thinh Nguyen" <Thinh.Nguyen@synopsys.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Jó Ágila Bitsch" <jgilab@gmail.com>,
"Prashanth K" <quic_prashk@quicinc.com>,
"Peter Chen" <peter.chen@kernel.org>,
"open list:USB SUBSYSTEM" <linux-usb@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [EXT] Re: [PATCH 1/1] usb: gadget: call usb_gadget_check_config() to verify UDC capability
Date: Fri, 30 Jun 2023 15:57:54 -0400 [thread overview]
Message-ID: <ZJ8zwiTHKIaH5pFB@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <158f9975-afff-25b8-130c-2a8381ce21ee@kernel.org>
On Fri, Jun 30, 2023 at 10:43:14PM +0300, Roger Quadros wrote:
>
>
> > .check_config = dwc3_gadget_check_config,
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/dwc3/gadget.c
>
> I meant gadget drivers not UDC drivers.
>
> e.g.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/gadget/legacy/dbgp.c
>
This is for EHCI host controller debug port, specially implement simple
tty gadget devices. Generally used for PC. This driver suppose will not
use UDC at all.
next prev parent reply other threads:[~2023-06-30 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 22:24 [PATCH 1/1] usb: gadget: call usb_gadget_check_config() to verify UDC capability Frank Li
2023-06-29 3:23 ` Roger Quadros
2023-06-29 3:40 ` [EXT] " Frank Li
2023-06-30 19:43 ` Roger Quadros
2023-06-30 19:57 ` Frank Li [this message]
2023-06-29 5:11 ` Ravi Gunasekaran
2023-06-29 14:48 ` [EXT] " Frank Li
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=ZJ8zwiTHKIaH5pFB@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=jgilab@gmail.com \
--cc=jun.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@kernel.org \
--cc=quic_eserrao@quicinc.com \
--cc=quic_prashk@quicinc.com \
--cc=r-gunasekaran@ti.com \
--cc=rogerq@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