Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ahaslam@baylibre.com (Axel Haslam)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] fix ohci phy name
Date: Wed,  2 Nov 2016 13:44:32 +0100	[thread overview]
Message-ID: <20161102124435.31777-1-ahaslam@baylibre.com> (raw)

The usb ohci clock match is not working because the usb clock
is registered as "ohci" instead of "ohci.0"

But since there is only a single ohci instance, lets pass -1 to
the platform data id parameter and avoid the extra ".0" matching.

while we are fixing this, rename the driver to "ohci-da8xx" to be
consistent with davinci musb and other usb drivers.

Axel Haslam (3):
  ARM: davinci: da8xx: Fix ohci driver name
  phy: da8xx-usb: rename the ohci device to ohci-da8xx
  usb: ohci-da8xx: rename driver to ohci-da8xx

 arch/arm/mach-davinci/da830.c     | 2 +-
 arch/arm/mach-davinci/da850.c     | 2 +-
 arch/arm/mach-davinci/da8xx-dt.c  | 2 +-
 arch/arm/mach-davinci/usb-da8xx.c | 4 ++--
 drivers/phy/phy-da8xx-usb.c       | 5 +++--
 drivers/usb/host/ohci-da8xx.c     | 2 +-
 6 files changed, 9 insertions(+), 8 deletions(-)

-- 
2.10.1

             reply	other threads:[~2016-11-02 12:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02 12:44 Axel Haslam [this message]
2016-11-02 12:44 ` [PATCH 1/3] ARM: davinci: da8xx: Fix ohci driver name Axel Haslam
2016-11-02 21:38   ` David Lechner
2016-11-02 12:44 ` [PATCH 2/3] phy: da8xx-usb: rename the ohci device to ohci-da8xx Axel Haslam
2016-11-02 21:41   ` David Lechner
2016-11-03 16:50   ` Kishon Vijay Abraham I
2016-11-04  5:34     ` Sekhar Nori
2016-11-04 21:04       ` Kishon Vijay Abraham I
2016-11-02 12:44 ` [PATCH 3/3] usb: ohci-da8xx: rename driver " Axel Haslam
2016-11-02 21:44   ` David Lechner
2016-11-03 11:56   ` Sekhar Nori
2016-11-03 12:19     ` Axel Haslam
2016-11-03  8:24 ` [PATCH 0/3] fix ohci phy name Axel Haslam
2016-11-03 12:00   ` Sekhar Nori
2016-11-03 13:58     ` Axel Haslam

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=20161102124435.31777-1-ahaslam@baylibre.com \
    --to=ahaslam@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.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