From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] udoo: fix watchdog setting
Date: Thu, 07 Nov 2013 09:19:08 +0100 [thread overview]
Message-ID: <527B4CFC.4020900@denx.de> (raw)
In-Reply-To: <1383770684.3741.28.camel@localhost>
Hi Giuseppe,
On 06/11/2013 21:44, Giuseppe Pagano wrote:
> To have watchdog quiet during kernel boot it is necessary to
> change gpio wdt trigger direction.
>
Sorry, this is not a good explanation. You force a GPIO to drop a
feture, instead of disabling the feature itself. And maybe some other
people want to have this feature enabled.
Which is the timeout for the watchdog ? Why is it hitting too soon ?
Fix should be not done simply removing the effect, but checking the cause.
>
> Signed-off-by: Giuseppe Pagano <giuseppe.pagano@seco.com>
> Cc: sbabic at denx.de
>
> ---
>
> diff -uNr a/board/udoo/udoo.c b/board/udoo/udoo.c
> --- a/board/udoo/udoo.c 2013-11-06 18:47:26.000000000 +0100
> +++ b/board/udoo/udoo.c 2013-11-06 18:54:46.000000000 +0100
> @@ -168,6 +168,7 @@
> imx_iomux_v3_setup_multiple_pads(wdog_pads,
> ARRAY_SIZE(wdog_pads));
> gpio_direction_output(WDT_TRG, 0);
> gpio_direction_output(WDT_EN, 1);
> + gpio_direction_input(WDT_TRG);
I do not think this a right way to disable a watchdog.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2013-11-07 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 20:44 [U-Boot] [PATCH 4/4] udoo: fix watchdog setting Giuseppe Pagano
2013-11-07 8:19 ` Stefano Babic [this message]
2013-11-07 11:49 ` Giuseppe Pagano
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=527B4CFC.4020900@denx.de \
--to=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
/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