lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141217154911.GU24110@csclub.uwaterloo.ca>
Date:	Wed, 17 Dec 2014 10:49:11 -0500
From:	"Lennart Sorensen" <lsorense@...lub.uwaterloo.ca>
To:	Tero Kristo <t-kristo@...com>
Cc:	Nishanth Menon <nm@...com>, Lokesh Vutla <lokeshvutla@...com>,
	linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, Sekhar Nori <nsekhar@...com>
Subject: Re: [PATCH 2/2] ARM: omap5/dra7xx: Fix counter frequency drift for
 AM572x errata i856.

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ