linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Afzal Mohammed <afzal@ti.com>
To: Felipe Balbi <balbi@ti.com>
Cc: linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
	Afzal Mohammed <afzal@ti.com>
Subject: [PATCH 0/2] usb: musb: dsps: fixes for -rc
Date: Wed, 31 Oct 2012 19:54:21 +0530	[thread overview]
Message-ID: <cover.1351691448.git.afzal@ti.com> (raw)

Hi Balbi,

This series contains a couple of fixes for musb dsps wrapper.

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 in during
previous merge window.

Second one corrects binding document; changes were made in driver as
per review comments, but documentation was not updated.

Please consider this series for inclusion in the next -rc cycle.

To support usb on beagle bone, further changes to handle control
module registers for phy has to be made, they will be posted as
a seperate series.


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


             reply	other threads:[~2012-10-31 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 14:24 Afzal Mohammed [this message]
2012-10-31 14:24 ` [PATCH 1/2] Revert "usb: musb: dsps: remove explicit NOP device creation" Afzal Mohammed
2012-10-31 14:24 ` [PATCH 2/2] usb: musb: dsps: document dt bindings properly Afzal Mohammed
     [not found] ` <cover.1351691448.git.afzal-l0cyMroinI0@public.gmane.org>
2012-11-02 11:33   ` [PATCH 0/2] usb: musb: dsps: fixes for -rc Afzal Mohammed

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.1351691448.git.afzal@ti.com \
    --to=afzal@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 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).