From: Afzal Mohammed <afzal@ti.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Benoit Cousson <b-cousson@ti.com>,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org
Subject: [PATCH/RESEND 0/2] usb: musb: am335x support part-2
Date: Tue, 6 Nov 2012 20:44:59 +0530 [thread overview]
Message-ID: <cover.1352213124.git.afzal@ti.com> (raw)
Hi Balbi,
This is a resend of remaining changes to get am335x usb working. These
were sent on 31 Oct with subject, "usb: musb: dsps: fixes for -rc.
First one restores capability to support at least one instance of musb.
Without it, even a single instance can't be supported as change which
is reverted by it was made along with multi phy changes and nop
transciever dt support, both other changes didn't make it to mainline.
Second one corrects binding document; changes were made in driver as
per review comments, but documentation was not updated.
This is made on top of your "musb" branch. To get USB0 functional on
am335x based boards like beagle bone, first one is required.
Regards
Afzal
Afzal Mohammed (2):
Revert "usb: musb: dsps: remove explicit NOP device creation"
usb: musb: dsps: document dt bindings properly
Documentation/devicetree/bindings/usb/am33xx-usb.txt | 8 ++++----
drivers/usb/musb/musb_dsps.c | 3 ++-
2 files changed, 6 insertions(+), 5 deletions(-)
--
1.7.12
next reply other threads:[~2012-11-06 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 15:14 Afzal Mohammed [this message]
[not found] ` <cover.1352213124.git.afzal-l0cyMroinI0@public.gmane.org>
2012-11-06 15:17 ` [PATCH/RESEND 1/2] Revert "usb: musb: dsps: remove explicit NOP device creation" Afzal Mohammed
2012-11-06 15:17 ` [PATCH/RESEND 2/2] usb: musb: dsps: document dt bindings properly Afzal Mohammed
2012-11-08 18:17 ` [PATCH/RESEND 0/2] usb: musb: am335x support part-2 Felipe Balbi
2012-11-09 5:06 ` Mohammed, Afzal
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=cover.1352213124.git.afzal@ti.com \
--to=afzal@ti.com \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.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 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.