From: Tony Lindgren <tony@atomide.com>
To: "DebBarma, Tarun Kanti" <tarun.kanti@ti.com>
Cc: Kevin Hilman <khilman@ti.com>,
linux-omap@vger.kernel.org, paul@pwsan.com,
santosh.shilimkar@ti.com, b-cousson@ti.com
Subject: Re: [PATCH 2/2] ARM: omap: dmtimer: set non-posted mode if iclk less than 4*fck
Date: Wed, 20 Jun 2012 06:13:47 -0700 [thread overview]
Message-ID: <20120620131346.GI12766@atomide.com> (raw)
In-Reply-To: <CAC83ZvKv_kwvYLG3RfN-ttKXU8pg+yqRGa9S83BAJj6=yeVP2g@mail.gmail.com>
* DebBarma, Tarun Kanti <tarun.kanti@ti.com> [120606 04:15]:
> On Wed, May 30, 2012 at 2:51 AM, Kevin Hilman <khilman@ti.com> wrote:
> > Tarun Kanti DebBarma <tarun.kanti@ti.com> writes:
> >
> >> Timers in PER domain periodically report old time from TCRR in
> >> posted mode if ick < 4*fck. Therefore, set timer to non-posted
> >> whenever ick < 4*fck for all timers.
> >
> > Is there an erratum assocaited with this?
> Yes, but it has not yet got into the document. Right now what we have
> is a hardware defect.
> >
> > Does this problem affect every SoC?
> Not quite sure about OMAP2 but it affects OMAP3+.
This seems not too urgent and OK to queue into fixes-non-critical?
Tony
next prev parent reply other threads:[~2012-06-20 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 13:53 [PATCH 0/2] ARM: omap: dmtimer: fix incorrect TCRR value in posted mode Tarun Kanti DebBarma
2012-05-11 13:53 ` [PATCH 1/2] ARM: omap: hwmod: Add an 'ick' clkdev alias Tarun Kanti DebBarma
2012-05-11 13:53 ` [PATCH 2/2] ARM: omap: dmtimer: set non-posted mode if iclk less than 4*fck Tarun Kanti DebBarma
2012-05-29 21:21 ` Kevin Hilman
2012-06-06 11:11 ` DebBarma, Tarun Kanti
2012-06-20 13:13 ` Tony Lindgren [this message]
2012-06-20 13:17 ` Shilimkar, Santosh
2012-06-20 14:15 ` Tony Lindgren
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=20120620131346.GI12766@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@ti.com \
--cc=tarun.kanti@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