All of lore.kernel.org
 help / color / mirror / Atom feed
From: jiri.prchal@aksignal.cz (Jiří Prchal)
To: linux-arm-kernel@lists.infradead.org
Subject: at91sam9: watchdog: period
Date: Mon, 18 May 2015 08:25:16 +0200	[thread overview]
Message-ID: <555985CC.1000707@aksignal.cz> (raw)
In-Reply-To: <5556006D.30306@atmel.com>



On 15.5.2015 16:19, Nicolas Ferre wrote:
>> I have the same hardware setup and the watchdog timeout is 15
>> seconds for me. For my kernel, I am using the Atmel fork at
>> github.com/linux4sam/linux-at91, master branch at commit
>> 5d5b332821753d616e65da6237f0a3330e59b98f.
>
> FYI, I've just moved the master branch of our github to the newer
> 3.18-based branch: linux-3.18-at91.
>
> Bye,

Since this files at91sam9_wdt.c and at91sam9_wdt.h are without changes between git 3.18 and 4.0.3 I think the problem is 
somewhere else. Later I can try whole git 3.18 kernel, now I don't have time for it.

Bye

  reply	other threads:[~2015-05-18  6:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  7:16 at91sam9: watchdog: period Jiří Prchal
2015-05-15 13:59 ` Bryan Evenson
2015-05-15 14:19   ` Nicolas Ferre
2015-05-18  6:25     ` Jiří Prchal [this message]
2015-05-15 15:25 ` Boris Brezillon
2015-05-18  6:27   ` Jiří Prchal
2015-05-18  7:27     ` Boris Brezillon
2015-05-18  8:17       ` Jiří Prchal
2015-05-19  3:07         ` Yang, Wenyou
2015-05-19  7:14           ` Boris Brezillon
2015-05-19  9:01             ` Jiří Prchal
2015-05-19  9:14               ` Boris Brezillon
2015-05-19  9:52                 ` Jiří Prchal
2015-05-19 10:04                   ` Boris Brezillon
2015-05-20 12:39                     ` Jiří Prchal
2015-05-21 12:41                     ` Jiří Prchal
2015-05-27  7:11                       ` Jiří Prchal
2015-05-19  7:12     ` Boris Brezillon
2015-05-19  9:00       ` Jiří Prchal
2015-10-06 13:07 ` Jiří Prchal
2015-10-06 18:03 ` Sylvain Rochet
2015-10-07  7:16   ` Jiří Prchal
2015-10-07  9:22   ` Sylvain Rochet

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=555985CC.1000707@aksignal.cz \
    --to=jiri.prchal@aksignal.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.