From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alessandro Rubini Date: Mon, 15 Jun 2009 15:01:20 +0200 Subject: [U-Boot] [PATCH 2/2] at91sam9263ek: active watchdog support via at91sam9263ek_wdt_config In-Reply-To: <20090615124422.GQ22102@game.jcrosoft.org> References: <20090615124422.GQ22102@game.jcrosoft.org> <1233505762-23290-1-git-send-email-plagnioj@jcrosoft.com> <1233505762-23290-2-git-send-email-plagnioj@jcrosoft.com> <20090308231923.C8F86832E8B8@gemini.denx.de> <20090613123700.GD3814@game.jcrosoft.org> Message-ID: <20090615130120.GA2747@mail.gnudd.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de >> But you have to delete hw_watchdog_init(). >> If you set there MR then linux won't be able to do it. >> The patch needs only the WATCHDOG_RESET() and nothing more. I agree. > you need to update linux, the watchdog can be enable in u-boot > but as it can only be disable once if u-boot or any other bootloader init > we can not disable it > so in this case linux will just have to buy time to the watchdog On the sam926x processors It can only be confitured once. So Giulio is right: u-boot shouldn't configure it, just kick it any now and then. When a client asked to used the watchdog on the 9260 I chose not to disable it in at91boot nor in u-boot. Then Linux (i.e., the final user) could do whatever was fit: either disable it, enable it with a faster timeout or leave it alone (at 13s or whatever the default is) until some application sets a policy. I don't like this hardware choice of "configure once only": never-disable makes sense, but never-enable doesn't, in my opinion. But based on that the right thing for u-boot is not configuring it a all, or we loose flexibility in later stages. /alessandro