From: mporter@ti.com (Matt Porter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: AM33XX: clock data: fix mcasp entries
Date: Wed, 10 Oct 2012 10:36:53 -0400 [thread overview]
Message-ID: <20121010143653.GD13724@beef> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EB3B5BD@DBDE01.ent.ti.com>
On Wed, Oct 10, 2012 at 02:33:54PM +0000, Vaibhav Hiremath wrote:
> On Wed, Oct 10, 2012 at 20:00:49, Porter, Matt wrote:
> > 6ea74cb ARM: OMAP2+: hwmod: get rid of all omap_clk_get_by_name usage
> > exposes a bug in the AM33XX clock data for mcasp. After moving to
> > clk_get() usage, the _init() of all registered hwmods fails on mcasp0
> > due to incorrect clock data causing clk_get() to fail. This causes all
> > successive hwmods to fail to _init() leaving them in a bad state.
> >
> > This patch updates the mcasp clock entries so clk_get() will succeed.
> > It is tested on BeagleBone and is needed for 3.7-rc1 to fix AM33xx
> > boot.
> >
>
> Matt,
>
> I have already submitted patch for this and it is accepted and merged in
> Tony's pull request.
>
> https://patchwork.kernel.org/patch/1499271/
Heh, ok. My search skills failed badly when I ran into this.
Thanks :)
-Matt
next prev parent reply other threads:[~2012-10-10 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 14:30 [PATCH] ARM: OMAP2+: AM33XX: clock data: fix mcasp entries Matt Porter
2012-10-10 14:33 ` Hiremath, Vaibhav
2012-10-10 14:36 ` Matt Porter [this message]
2012-10-29 15:45 ` Hebbar, Gururaja
2012-10-30 0:33 ` Joel A Fernandes
2012-10-30 0:35 ` Joel A Fernandes
2012-10-30 20:28 ` Joel A Fernandes
2012-10-31 5:39 ` Hebbar, Gururaja
2012-11-03 19:32 ` Joel A Fernandes
2012-11-05 8:13 ` Mark Brown
2012-11-05 16:52 ` Joel A Fernandes
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=20121010143653.GD13724@beef \
--to=mporter@ti.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;
as well as URLs for NNTP newsgroup(s).