From: Felipe Balbi <balbi@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Felipe Balbi <balbi@ti.com>, Tony Lindgren <tony@atomide.com>,
Paul Walmsley <paul@pwsan.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm: omap2+: hwmod: fix breakage introduced by d6504acd
Date: Mon, 7 Nov 2011 21:39:09 +0200 [thread overview]
Message-ID: <20111107193908.GA5059@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <20111107183208.GG15294@n2100.arm.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
Hi,
On Mon, Nov 07, 2011 at 06:32:08PM +0000, Russell King - ARM Linux wrote:
> On Mon, Nov 07, 2011 at 07:56:57PM +0200, Felipe Balbi wrote:
> > commit d6504acd (OMAP2+: hwmod: remove OMAP_CHIP*) has
> > mistakenly added MUSB as a hwmod available only on ES2.0
> > of OMAP3430.
> >
> > MUSB hwmod has always be available on all OMAP revisions
> > since OMAP2430.
>
> This doesn't seem to solve it:
then i can't help. From all I know the LDP is based on OMAP3430 so that
should work. If it doesn't, it's something deeper on hwmod, maybe ?
Paul, it's your call.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-11-07 19:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 17:56 [PATCH] arm: omap2+: hwmod: fix breakage introduced by d6504acd Felipe Balbi
2011-11-07 18:32 ` Russell King - ARM Linux
2011-11-07 19:39 ` Felipe Balbi [this message]
2011-11-07 21:27 ` Russell King - ARM Linux
2011-11-07 21:29 ` Paul Walmsley
2011-11-07 22:41 ` Russell King - ARM Linux
2011-11-07 22:51 ` Tony Lindgren
2011-11-07 22:55 ` Russell King - ARM Linux
2011-11-07 23:07 ` Tony Lindgren
2011-11-07 23:16 ` Russell King - ARM Linux
2011-11-07 23:27 ` Tony Lindgren
2011-11-07 21:30 ` Paul Walmsley
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=20111107193908.GA5059@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=paul@pwsan.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox