From: David Cohen <david.a.cohen@linux.intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: balbi@ti.com, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH v2 1/3] usb: gadget: add quirks field to struct usb_gadget
Date: Wed, 30 Oct 2013 09:26:39 -0700 [thread overview]
Message-ID: <5271333F.9040500@linux.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1310301033040.1312-100000@iolanthe.rowland.org>
>> diff --git a/include/linux/usb/gadget.h b/include/linux/usb/gadget.h
>> index 942ef5e..7014ad9 100644
>> --- a/include/linux/usb/gadget.h
>> +++ b/include/linux/usb/gadget.h
>> @@ -540,6 +540,11 @@ struct usb_gadget {
>> struct device dev;
>> unsigned out_epnum;
>> unsigned in_epnum;
>> +
>> + u32 quirks;
>> +/* epout requires buffer size to be aligned to MaxPacketSize */
>> +#define USB_GADGET_QUIRK_EP_OUT_ALIGNED_SIZE (1 << 0)
>
> If you decide to go through with this, it might be better to define a
> series of single-bit flags instead of a single "quirks" field. For
> example:
>
> unsigned quirk_ep_out_aligned_size:1;
>
> Yes, other people (including me!) have done it your way in the past,
> but now this seems to make more sense.
It would be less error-prone. I'll change it.
Thanks,
David
next prev parent reply other threads:[~2013-10-30 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 21:52 [RFC/PATCH v2 0/3] add gadget quirk to adapt f_fs for DWC3 David Cohen
2013-10-29 21:52 ` [RFC/PATCH v2 1/3] usb: gadget: add quirks field to struct usb_gadget David Cohen
2013-10-30 14:35 ` Alan Stern
2013-10-30 16:26 ` David Cohen [this message]
2013-10-29 21:52 ` [RFC/PATCH v2 2/3] usb: ffs: check quirk to pad epout buf size when not aligned to maxpacketsize David Cohen
2013-10-29 21:52 ` [RFC/PATCH v2 3/3] usb: dwc3: add quirk USB_GADGET_QUIRK_EP_OUT_ALIGNED_SIZE to gadget driver David Cohen
2013-10-29 22:47 ` [RFC/PATCH v2 0/3] add gadget quirk to adapt f_fs for DWC3 Paul Zimmerman
2013-10-30 9:41 ` David Laight
2013-10-30 15:23 ` Alan Stern
2013-10-30 16:36 ` David Cohen
2013-10-30 17:24 ` 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=5271333F.9040500@linux.intel.com \
--to=david.a.cohen@linux.intel.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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