Thread (30 messages) 30 messages, 5 authors, 2014-11-03
STALE4272d
Revisions (8)
  1. v1 [diff vs current]
  2. v1 [diff vs current]
  3. v1 [diff vs current]
  4. v1 [diff vs current]
  5. v1 current
  6. v1 [diff vs current]
  7. v2 [diff vs current]
  8. v3 [diff vs current]

[PATCH 0/4] Make Armada 375 use the reference clock when possible

From: Ezequiel Garcia <hidden>
Date: 2014-10-23 12:36:35
Also in: linux-watchdog

On 10/22/2014 11:08 AM, Andrew Lunn wrote:
quoted
You don't clearly state whether your patch series keep compatibility
with the 375 Z1 or not. And in fact, it doesn't keep compatibility with
Z1.
Hi Thomas

That answers my question. Thanks
quoted
I'm fine with that, but then it means we should officially declare
the Z1 support in mainline as dead, and get rid of the workarounds that
applied only to 375 Z1.
A big ACK.

How bad is it if you run these patches on a Z1? Is it worth adding a
revision check and calling BUG()?
So, I just tried this on a Z1. Here's the result:

sleep 3 -> sleeps for 6 seconds

Configuring the watchdog for 3 seconds and:

echo "barf" > /dev/watchdog -> resets after 6 seconds

So using the 25 MHz reference clock is broken on Z1, but the point at
least boots; it will "just" keep track of time wrongly.
-- 
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help