From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linyu Yuan <quic_linyyuan@quicinc.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v3 6/6] usb: gadget: f_fs: show instance name in debug message
Date: Wed, 29 Mar 2023 10:21:35 +0200 [thread overview]
Message-ID: <ZCP1D16oOaGZowCz@kroah.com> (raw)
In-Reply-To: <c9d9b452-d6d9-027a-b1fa-ee3471689bca@quicinc.com>
On Wed, Mar 29, 2023 at 03:42:08PM +0800, Linyu Yuan wrote:
>
> On 3/29/2023 3:37 PM, Greg Kroah-Hartman wrote:
> > On Wed, Mar 29, 2023 at 03:11:14PM +0800, Linyu Yuan wrote:
> > > On 3/29/2023 2:54 PM, Greg Kroah-Hartman wrote:
> > > > On Mon, Mar 27, 2023 at 06:12:20PM +0800, Linyu Yuan wrote:
> > > > > show ffs->dev_name in all possible debug message.
> > > > >
> > > > > Signed-off-by: Linyu Yuan <quic_linyyuan@quicinc.com>
> > > > > ---
> > > > > v3: change according comments
> > > > > v2: split to several changes according to v1 comments
> > > > > v1: https://lore.kernel.org/linux-usb/1679481369-30094-1-git-send-email-quic_linyyuan@quicinc.com/
> > > > >
> > > > > drivers/usb/gadget/function/f_fs.c | 141 ++++++++++++++++++++-----------------
> > > > > 1 file changed, 75 insertions(+), 66 deletions(-)
> > > > >
> > > > > diff --git a/drivers/usb/gadget/function/f_fs.c b/drivers/usb/gadget/function/f_fs.c
> > > > > index 0761eaa..383343d 100644
> > > > > --- a/drivers/usb/gadget/function/f_fs.c
> > > > > +++ b/drivers/usb/gadget/function/f_fs.c
> > > > > @@ -317,12 +317,12 @@ static int __ffs_ep0_queue_wait(struct ffs_data *ffs, char *data, size_t len)
> > > > > static int __ffs_ep0_stall(struct ffs_data *ffs)
> > > > > {
> > > > > if (ffs->ev.can_stall) {
> > > > > - dev_vdbg(ffs->dev, "ep0 stall\n");
> > > > > + dev_vdbg(ffs->dev, "%s: ep0 stall\n", ffs->dev_name);
> > > > You already have the name here, it's in the usb-gadget structure, why do
> > > > you need to print it out again?
> > > >
> > > > What is the before and after output of this change? I think it should
> > > > have the same information already in it.
> > >
> > > you have wrong understanding of usb_gadget->dev and ffs->dev_name,
> > >
> > > this is output example,
> > >
> > > [11.046519] configfs-gadget.g1 gadget.0: adb: interface descriptor
> > >
> > > usb_gadget->dev is gadget.0,
> > >
> > > but ffs->dev_name is adb.
> > Isn't there some mapping of gadget name to "dev_name" somewhere else in
> > the logs? And what sets dev_name, why isn't that part of the gadget
> > name already?
>
>
> ffs->dev_name should be different from gadget name,
>
> as we can create multiple ffs instances (adb, MTP, PTP ...) which work on
> one gadget device (gadget.0).
Shouldn't all of those instances have their own struct device pointer?
thanks,
greg k-h
next prev parent reply other threads:[~2023-03-29 8:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 10:12 [PATCH v3 1/6] usb: gadget: ffs: remove ENTER() macro Linyu Yuan
2023-03-27 10:12 ` [PATCH v3 2/6] usb: gadget: f_fs: add more function with struct ffs_data *ffs parameter Linyu Yuan
2023-03-27 10:12 ` [PATCH v3 3/6] usb: gadget: f_fs: remove struct ffs_data *ffs from struct ffs_desc_helper Linyu Yuan
2023-03-27 10:12 ` [PATCH v3 4/6] usb: gadget: f_fs: add a device reference of usb_gadget->dev Linyu Yuan
2023-03-29 6:53 ` Greg Kroah-Hartman
2023-03-29 7:00 ` Linyu Yuan
2023-03-29 7:31 ` Greg Kroah-Hartman
2023-03-29 7:46 ` Linyu Yuan
2023-03-29 8:21 ` Greg Kroah-Hartman
2023-03-29 9:20 ` Linyu Yuan
2023-03-27 10:12 ` [PATCH v3 5/6] usb: gadget: f_fs: replace private pr_vdebug() with dev_vdbg Linyu Yuan
2023-03-29 6:55 ` Greg Kroah-Hartman
2023-03-29 7:01 ` Linyu Yuan
2023-03-29 7:31 ` Greg Kroah-Hartman
2023-03-27 10:12 ` [PATCH v3 6/6] usb: gadget: f_fs: show instance name in debug message Linyu Yuan
2023-03-29 6:54 ` Greg Kroah-Hartman
2023-03-29 7:11 ` Linyu Yuan
2023-03-29 7:37 ` Greg Kroah-Hartman
2023-03-29 7:42 ` Linyu Yuan
2023-03-29 8:21 ` Greg Kroah-Hartman [this message]
2023-03-29 8:46 ` Linyu Yuan
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=ZCP1D16oOaGZowCz@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_linyyuan@quicinc.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).