linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: omap5/dra7xx: Fix counter frequency drift for AM572x errata i856.
Date: Wed, 17 Dec 2014 10:49:11 -0500	[thread overview]
Message-ID: <20141217154911.GU24110@csclub.uwaterloo.ca> (raw)
In-Reply-To: <5491A501.100@ti.com>

On Wed, Dec 17, 2014 at 05:45:05PM +0200, Tero Kristo wrote:
> Yea clock mux can be used. However, we don't have support for DRA7
> control module clocks in the DT yet. I have posted patches with
> support towards this a couple of weeks back, but they need some
> revising.
> 
> Thus, we maybe need to apply the timer patches as is for now, and
> fix the clock tree a bit later.

Certainly the patches so far fix the system time issue.  I don't think
anything else in the clock tree using this clock is that picky about
the clock being of by 0.05% (when using 20MHz SYSCLK1, which I believe
all boards so far do, other than the one board on my desk with a 19.2MHz
clock because we wanted to see what happened).  Certainly if someone
does build a baord using either 19.2 or 27MHz as supported in the
documentation, then it becomes more relevant potentially.

But I certainly don't consider fixing the clock tree urgent.  I think
we can start shipping products with the clock tree in the current state
(but we couldn't with the system time being that bad, which the patches
so far fix).

-- 
Len Sorensen

  reply	other threads:[~2014-12-17 15:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12 22:08 [PATCH 0/2] ARM: omap5/dra7xx counter frequency fixes Lennart Sorensen
2014-12-12 22:08 ` [PATCH 1/2] ARM: omap5/dra7xx: Fix frequency typos Lennart Sorensen
2014-12-16 11:38   ` Lokesh Vutla
2014-12-16 14:06   ` Nishanth Menon
2014-12-16 16:39     ` Lennart Sorensen
2014-12-12 22:08 ` [PATCH 2/2] ARM: omap5/dra7xx: Fix counter frequency drift for AM572x errata i856 Lennart Sorensen
2014-12-14  4:45   ` Lennart Sorensen
2014-12-16 11:35     ` Lokesh Vutla
2014-12-16 14:58       ` Nishanth Menon
2014-12-16 16:36         ` Lennart Sorensen
2014-12-16 18:59           ` Nishanth Menon
2014-12-16 19:27             ` Lennart Sorensen
2014-12-16 19:33               ` Nishanth Menon
2014-12-17 13:21         ` Tero Kristo
2014-12-17 14:55           ` Lennart Sorensen
2014-12-17 15:22             ` Nishanth Menon
2014-12-17 15:27               ` Lennart Sorensen
2014-12-17 15:45                 ` Tero Kristo
2014-12-17 15:49                   ` Lennart Sorensen [this message]
2014-12-17 15:53                   ` Nishanth Menon
2014-12-17 15:56                     ` Tero Kristo
2014-12-16 16:16       ` Lennart Sorensen
2014-12-16 19:56         ` Nishanth Menon
2014-12-16 19:58           ` Lennart Sorensen

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=20141217154911.GU24110@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --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).