From: Tony Lindgren <tony@atomide.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: "Bedia, Vaibhav" <vaibhav.bedia@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: OMAP2+: Fix selection of clockevent timer when using device-tree
Date: Fri, 1 Feb 2013 14:44:54 -0800 [thread overview]
Message-ID: <20130201224453.GF22517@atomide.com> (raw)
In-Reply-To: <51095D85.6080204@ti.com>
* Jon Hunter <jon-hunter@ti.com> [130130 09:54]:
>
> On 01/30/2013 01:18 AM, Bedia, Vaibhav wrote:
> > On Wed, Jan 30, 2013 at 01:53:11, Hunter, Jon wrote:
> >> Commit 9725f44 (ARM: OMAP: Add DT support for timer driver) added
> >> device-tree support for selecting a clockevent timer by property.
> >> However, the code is currently ignoring the property passed and
> >> selecting the first available timer found. Hence, for the OMAP3 beagle
> >> board timer-12 is not being selected as expected. Fix this problem
> >> by ensuring the timer property is passed to omap_get_timer_dt().
> >
> > I thought that was intentional ;) and had this change in the clkevt-clksrc
> > interchange patch for AM33xx.
>
> No definitely was not. Thanks, I had missed that detail in the patch you
> sent!
>
> > Anyways, this change works for me so...
> >
> > Tested-by: Vaibhav Bedia <vaibhav.bedia@ti.com>
>
> Thanks!
Thanks applying into omap-for-v3.9/fixes-non-critical.
Tony
prev parent reply other threads:[~2013-02-01 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 20:23 [PATCH] ARM: OMAP2+: Fix selection of clockevent timer when using device-tree Jon Hunter
2013-01-30 5:54 ` Santosh Shilimkar
2013-01-30 7:18 ` Bedia, Vaibhav
2013-01-30 17:51 ` Jon Hunter
2013-02-01 22:44 ` Tony Lindgren [this message]
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=20130201224453.GF22517@atomide.com \
--to=tony@atomide.com \
--cc=jon-hunter@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=vaibhav.bedia@ti.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;
as well as URLs for NNTP newsgroup(s).