From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: gregkh@suse.de, linux-usb@vger.kernel.org, sshtylyov@mvista.com
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, plagnioj@jcrosoft.com
Subject: [PATCH V2] usb/gadget: at91sam9g20 fix end point max packet size
Date: Fri, 13 May 2011 17:03:02 +0200 [thread overview]
Message-ID: <1305298982-5789-1-git-send-email-plagnioj@jcrosoft.com> (raw)
In-Reply-To: <1305042888-19401-1-git-send-email-plagnioj@jcrosoft.com>
on 9g20 they are the same as the 9260
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
---
Resent upon Greg's request.
Based on current linux-next.
Applies cleanly on current linus' tree (2.6.39-rc7+)
BTW, can we imagine it going to mainline before .39-final in a "fixes" pull
request to Linus from a at91 tree?
drivers/usb/gadget/at91_udc.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/gadget/at91_udc.c b/drivers/usb/gadget/at91_udc.c
index 9b7cdb1..41dc093 100644
--- a/drivers/usb/gadget/at91_udc.c
+++ b/drivers/usb/gadget/at91_udc.c
@@ -1767,7 +1767,7 @@ static int __init at91udc_probe(struct platform_device *pdev)
}
/* newer chips have more FIFO memory than rm9200 */
- if (cpu_is_at91sam9260()) {
+ if (cpu_is_at91sam9260() || cpu_is_at91sam9g20()) {
udc->ep[0].maxpacket = 64;
udc->ep[3].maxpacket = 64;
udc->ep[4].maxpacket = 512;
--
1.7.3
next parent reply other threads:[~2011-05-13 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1305042888-19401-1-git-send-email-plagnioj@jcrosoft.com>
2011-05-13 15:03 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2011-05-13 16:20 ` Greg KH
2011-05-13 16:36 ` Nicolas Ferre
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=1305298982-5789-1-git-send-email-plagnioj@jcrosoft.com \
--to=plagnioj@jcrosoft.com \
--cc=gregkh@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sshtylyov@mvista.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®