From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [GIT PULL] musb regression fixes for v3.7-rc4
Date: Mon, 12 Nov 2012 16:22:17 +0000 [thread overview]
Message-ID: <201211121622.17616.arnd@arndb.de> (raw)
In-Reply-To: <20121109223939.GZ6801@atomide.com>
On Friday 09 November 2012, Tony Lindgren wrote:
> This series fixes an annoying regression to make MUSB working
> on omap4 again. Although it's getting rather late for these
> changes for the -rc cycle, it is important as many devices
> are using MUSB for charging and connectivity.
>
> With the USB PHY changes, MUSB started using the newly added
> drivers/usb/phy/omap-usb2.c driver introduced by commit
> 657b306a (usb: phy: add a new driver for omap usb2 phy)
> that is using the newly introduced drivers/bus/omap-ocp2scp.c
> introduced by commit 26a84b3e (drivers: bus: add a new driver
> for omap-ocp2scp).
>
> These changes allowed dropping a lot of PHY related code from
> arch/arm/mach-omap2/omap_phy_internal.c and have it live in
> the device driver like it should with commit c9e4412a (arm: omap:
> phy: remove unused functions from omap-phy-internal.c).
>
> However, MUSB on omap4 broke with these changes for legacy
> platform data boot, and now only works with device tree for
> omap4. Unfortunately we are still few critical bindings away
> from being able to make omap4 usbale with device tree.
>
> Fix the regression properly by adding platform data support
> to the ocp2scp driver so we can avoid adding back the driver
> code to arch/arm/mach-omap2.
>
Applied to fixes branch, will send this soon.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] musb regression fixes for v3.7-rc4
Date: Mon, 12 Nov 2012 16:22:17 +0000 [thread overview]
Message-ID: <201211121622.17616.arnd@arndb.de> (raw)
In-Reply-To: <20121109223939.GZ6801@atomide.com>
On Friday 09 November 2012, Tony Lindgren wrote:
> This series fixes an annoying regression to make MUSB working
> on omap4 again. Although it's getting rather late for these
> changes for the -rc cycle, it is important as many devices
> are using MUSB for charging and connectivity.
>
> With the USB PHY changes, MUSB started using the newly added
> drivers/usb/phy/omap-usb2.c driver introduced by commit
> 657b306a (usb: phy: add a new driver for omap usb2 phy)
> that is using the newly introduced drivers/bus/omap-ocp2scp.c
> introduced by commit 26a84b3e (drivers: bus: add a new driver
> for omap-ocp2scp).
>
> These changes allowed dropping a lot of PHY related code from
> arch/arm/mach-omap2/omap_phy_internal.c and have it live in
> the device driver like it should with commit c9e4412a (arm: omap:
> phy: remove unused functions from omap-phy-internal.c).
>
> However, MUSB on omap4 broke with these changes for legacy
> platform data boot, and now only works with device tree for
> omap4. Unfortunately we are still few critical bindings away
> from being able to make omap4 usbale with device tree.
>
> Fix the regression properly by adding platform data support
> to the ocp2scp driver so we can avoid adding back the driver
> code to arch/arm/mach-omap2.
>
Applied to fixes branch, will send this soon.
Arnd
next prev parent reply other threads:[~2012-11-12 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 22:39 [GIT PULL] musb regression fixes for v3.7-rc4 Tony Lindgren
2012-11-09 22:39 ` Tony Lindgren
2012-11-12 16:22 ` Arnd Bergmann [this message]
2012-11-12 16:22 ` Arnd Bergmann
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=201211121622.17616.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--cc=tony@atomide.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 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.