From: "Tanya Brokhman" <tlinder@codeaurora.org>
To: 'Mike Frysinger' <vapier.adi@gmail.com>
Cc: greg@kroah.com, linux-usb@vger.kernel.org,
linux-arm-msm@vger.kernel.org, balbi@ti.com,
ablay@codeaurora.org, 'open list' <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v13 5/8] usb:gadget: Add SuperSpeed support to the Gadget Framework
Date: Wed, 25 May 2011 16:27:29 +0300 [thread overview]
Message-ID: <01f801cc1adf$81059e40$8310dac0$@org> (raw)
In-Reply-To: <BANLkTi=0Esm7w-TJ03ugPfVTuCr158=Y1Q@mail.gmail.com>
Hi Mike
> On Tue, May 24, 2011 at 06:02, Tatyana Brokhman wrote:
> > +config USB_GADGET_SUPERSPEED
> > + boolean "Gadget operating in Super Speed"
>
> perhaps better phrasing would be: Enable Super Speed support
Np. Will update.
> maybe i didnt look too closely, but it seems like very little even
> depends upon this Kconfig option in the actual source. only the
> "gadget_is_superspeed()", and that is used lightly. so i wonder how
> useful this is even having ...
No, this flag is VERY important :) If it's set the driver speed is updated to USB_SPEED_SUPER. Look at usb_composite_probe()
> > + value = min(w_length, (u16) value);
>
> i know you're just following existing style, but i wonder if these all
> shouldnt just be min_t(u16, ...)
Perhaps, but it seems to me that this change also isn't related to these patch series so I prefer to follow existing style and maybe post a follow up patch to update all.
> > + ERROR(cdev, "func_suspend() returned
> "
> > + "error %d\n", value);
>
> please dont split string literals over multiple lines
Done.
>
> > + default:
> > + break;
> > + }
>
> isnt that the default behavior already ? so these two lines are
> pointless ?
Removed.
>
> > --- a/include/linux/usb/ch9.h
> > +++ b/include/linux/usb/ch9.h
> > @@ -142,8 +142,6 @@
> > #define USB_DEVICE_LTM_ENABLE 50 /* dev may send LTM */
> > #define USB_INTRF_FUNC_SUSPEND 0 /* function suspend */
> >
> > -#define USB_INTR_FUNC_SUSPEND_OPT_MASK 0xFF00
> > -
> > #define USB_ENDPOINT_HALT 0 /* IN/OUT will STALL
> */
> >
> > /* Bit array elements as returned by the USB_REQ_GET_STATUS request.
> */
>
> erm, seems unrelated to this patchset ? did this sneak in by accident
> ?
You're right. It seems so...
> > +static inline int gadget_is_superspeed(struct usb_gadget *g)
> > +{
> > +#ifdef CONFIG_USB_GADGET_SUPERSPEED
> > + /* runtime test would check "g->is_superspeed" ... that might
> be
> > + * useful to work around hardware bugs, but is mostly
> pointless
> > + */
>
> multiline comments should read:
> /*
> * foo .....
> */
Done. Thanks for catching that! (checkpatch didn't for some reason...)
Best regards,
Tanya Brokhman
Consultant for Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
WARNING: multiple messages have this Message-ID (diff)
From: "Tanya Brokhman" <tlinder@codeaurora.org>
To: "'Mike Frysinger'" <vapier.adi@gmail.com>
Cc: <greg@kroah.com>, <linux-usb@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>, <balbi@ti.com>,
<ablay@codeaurora.org>,
"'open list'" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v13 5/8] usb:gadget: Add SuperSpeed support to the Gadget Framework
Date: Wed, 25 May 2011 16:27:29 +0300 [thread overview]
Message-ID: <01f801cc1adf$81059e40$8310dac0$@org> (raw)
In-Reply-To: <BANLkTi=0Esm7w-TJ03ugPfVTuCr158=Y1Q@mail.gmail.com>
Hi Mike
> On Tue, May 24, 2011 at 06:02, Tatyana Brokhman wrote:
> > +config USB_GADGET_SUPERSPEED
> > + boolean "Gadget operating in Super Speed"
>
> perhaps better phrasing would be: Enable Super Speed support
Np. Will update.
> maybe i didnt look too closely, but it seems like very little even
> depends upon this Kconfig option in the actual source. only the
> "gadget_is_superspeed()", and that is used lightly. so i wonder how
> useful this is even having ...
No, this flag is VERY important :) If it's set the driver speed is updated to USB_SPEED_SUPER. Look at usb_composite_probe()
> > + value = min(w_length, (u16) value);
>
> i know you're just following existing style, but i wonder if these all
> shouldnt just be min_t(u16, ...)
Perhaps, but it seems to me that this change also isn't related to these patch series so I prefer to follow existing style and maybe post a follow up patch to update all.
> > + ERROR(cdev, "func_suspend() returned
> "
> > + "error %d\n", value);
>
> please dont split string literals over multiple lines
Done.
>
> > + default:
> > + break;
> > + }
>
> isnt that the default behavior already ? so these two lines are
> pointless ?
Removed.
>
> > --- a/include/linux/usb/ch9.h
> > +++ b/include/linux/usb/ch9.h
> > @@ -142,8 +142,6 @@
> > #define USB_DEVICE_LTM_ENABLE 50 /* dev may send LTM */
> > #define USB_INTRF_FUNC_SUSPEND 0 /* function suspend */
> >
> > -#define USB_INTR_FUNC_SUSPEND_OPT_MASK 0xFF00
> > -
> > #define USB_ENDPOINT_HALT 0 /* IN/OUT will STALL
> */
> >
> > /* Bit array elements as returned by the USB_REQ_GET_STATUS request.
> */
>
> erm, seems unrelated to this patchset ? did this sneak in by accident
> ?
You're right. It seems so...
> > +static inline int gadget_is_superspeed(struct usb_gadget *g)
> > +{
> > +#ifdef CONFIG_USB_GADGET_SUPERSPEED
> > + /* runtime test would check "g->is_superspeed" ... that might
> be
> > + * useful to work around hardware bugs, but is mostly
> pointless
> > + */
>
> multiline comments should read:
> /*
> * foo .....
> */
Done. Thanks for catching that! (checkpatch didn't for some reason...)
Best regards,
Tanya Brokhman
Consultant for Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2011-05-25 13:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 10:01 [PATCH v13 0/8] usb gadget: Add SuperSpeed support to the Gadget Framework Tatyana Brokhman
2011-05-24 10:01 ` [PATCH/RESEND v13 1/8] usb: Add usb_endpoint_descriptor to be part of the struct usb_ep Tatyana Brokhman
2011-05-24 10:01 ` Tatyana Brokhman
2011-05-24 10:01 ` [PATCH/RESEND v13 2/8] usb: Configure endpoint according to gadget speed Tatyana Brokhman
2011-05-24 10:01 ` Tatyana Brokhman
2011-05-24 10:02 ` [PATCH/RESEND v13 3/8] usb: Modify existing gadget drivers to use config_ep_by_speed() instead of ep_choose Tatyana Brokhman
2011-05-24 10:02 ` Tatyana Brokhman
2011-05-24 10:02 ` [PATCH v13 4/8] usb: coding style fix Tatyana Brokhman
2011-05-24 10:02 ` Tatyana Brokhman
2011-05-24 10:02 ` [PATCH v13 5/8] usb:gadget: Add SuperSpeed support to the Gadget Framework Tatyana Brokhman
2011-05-24 10:02 ` Tatyana Brokhman
2011-05-24 17:20 ` Mike Frysinger
2011-05-25 13:27 ` Tanya Brokhman [this message]
2011-05-25 13:27 ` Tanya Brokhman
2011-05-24 10:02 ` [PATCH/RESEND v13 6/8] usb: Add streams support to the gadget framework Tatyana Brokhman
2011-05-24 10:02 ` Tatyana Brokhman
2011-05-24 10:02 ` [PATCH/RESEND v13 7/8] usb:dummy_hcd: use the shared_hcd infrastructure Tatyana Brokhman
2011-05-24 10:02 ` Tatyana Brokhman
[not found] ` <1306231330-11158-1-git-send-email-tlinder-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2011-05-24 10:02 ` [PATCH v13 8/8] usb: Adding SuperSpeed support to dummy_hcd Tatyana Brokhman
2011-05-24 10:02 ` Tatyana Brokhman
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='01f801cc1adf$81059e40$8310dac0$@org' \
--to=tlinder@codeaurora.org \
--cc=ablay@codeaurora.org \
--cc=balbi@ti.com \
--cc=greg@kroah.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=vapier.adi@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.