<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/watchdog, branch linux-2.6.34.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.34.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.34.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2012-05-17T15:20:59Z</updated>
<entry>
<title>watchdog: mtx1-wdt: request gpio before using it</title>
<updated>2012-05-17T15:20:59Z</updated>
<author>
<name>Florian Fainelli</name>
</author>
<published>2011-06-15T17:15:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=af99bfc79386bb0fec583ee393e27e4344d3b27f'/>
<id>urn:sha1:af99bfc79386bb0fec583ee393e27e4344d3b27f</id>
<content type='text'>
commit 9b19d40aa3ebaf1078779da10555da2ab8512422 upstream.

Otherwise, the gpiolib autorequest feature will produce a WARN_ON():

WARNING: at drivers/gpio/gpiolib.c:101 0x8020ec6c()
autorequest GPIO-215
[...]

Signed-off-by: Florian Fainelli &lt;florian@openwrt.org&gt;
Signed-off-by: Wim Van Sebroeck &lt;wim@iguana.be&gt;
[PG: use combo gpio_request+gpio_direction_output vs. gpio_request_one
 to avoid build failure, as per v2.6.32.47 commit 35b6863ce555c ]
Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;
</content>
</entry>
<entry>
<title>ARM: 6126/1: ARM mpcore_wdt: fix build failure and other fixes</title>
<updated>2010-05-12T10:18:14Z</updated>
<author>
<name>Srinidhi Kasagar</name>
</author>
<published>2010-05-12T04:53:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=98af057092f8f0dabe63c5df08adc2bbfbddb1d2'/>
<id>urn:sha1:98af057092f8f0dabe63c5df08adc2bbfbddb1d2</id>
<content type='text'>
This fixes the build failures seen when building mpcore_wdt and it
also removes the nonexistent ARM_MPCORE_PLATFORM dependency, instead
make it dependent on HAVE_ARM_TWD.

Also this fixes spinlock usage appropriately.

Signed-off-by: srinidhi kasagar &lt;srinidhi.kasagar@stericsson.com&gt;
Acked-by: Linus Walleij &lt;linus.walleij@stericsson.com&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>watchdog: ep93xx_wdt.c fix default timout value in MODULE_PARM_DESC string.</title>
<updated>2010-05-03T08:58:56Z</updated>
<author>
<name>Wim Van Sebroeck</name>
</author>
<published>2010-05-03T08:58:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d557f651b3617b46ed18d5bac48a851df1dbf684'/>
<id>urn:sha1:d557f651b3617b46ed18d5bac48a851df1dbf684</id>
<content type='text'>
The WATCHDOG_TIMEOUT macro does not exist. The default timeout value is WDT_TIMEOUT.
Fix the MODULE_PARM_DESC so that the code can compile again.

reported-by: Randy Dunlap &lt;randy.dunlap@oracle.com&gt;
Signed-off-by: Wim Van Sebroeck &lt;wim@iguana.be&gt;
</content>
</entry>
<entry>
<title>watchdog: booke_wdt: fix build - unconstify watchdog_info</title>
<updated>2010-04-27T07:58:47Z</updated>
<author>
<name>Anton Vorontsov</name>
</author>
<published>2010-04-26T22:59:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d8d8b63b6dc413696ade040e52173c068df11702'/>
<id>urn:sha1:d8d8b63b6dc413696ade040e52173c068df11702</id>
<content type='text'>
commit 42747d712de56cf2087b702d2ad90af114c53138 ("[WATCHDOG] watchdog_info
constify") introduced the following build failure:

   CC      booke_wdt.o
 booke_wdt.c: In function 'booke_wdt_init':
 booke_wdt.c:220: error: assignment of read-only variable 'ident'

Fix this by removing 'const' qualifier from watchdog_info struct.

Signed-off-by: Anton Vorontsov &lt;avorontsov@mvista.com&gt;
Signed-off-by: Wim Van Sebroeck &lt;wim@iguana.be&gt;
Cc: Kumar Gala &lt;galak@kernel.crashing.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

</content>
</entry>
<entry>
<title>watchdog: sbc_fitpc2_wdt: fixed "scheduling while atomic" bug.</title>
<updated>2010-04-26T18:22:30Z</updated>
<author>
<name>Denis Turischev</name>
</author>
<published>2010-04-22T16:54:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=322af98c56c70b3ec6f637fb07d41a9591a6ff9a'/>
<id>urn:sha1:322af98c56c70b3ec6f637fb07d41a9591a6ff9a</id>
<content type='text'>
spinlock need to be replaced by mutex because of sleep functions
inside wdt_send_data.

Signed-off-by: Denis Turischev &lt;denis@compulab.co.il&gt;
Signed-off-by: Wim Van Sebroeck &lt;wim@iguana.be&gt;

</content>
</entry>
<entry>
<title>watchdog: sbc_fitpc2_wdt: fixed I/O operations order</title>
<updated>2010-04-26T18:17:34Z</updated>
<author>
<name>Denis Turischev</name>
</author>
<published>2010-04-22T16:50:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fcf1dd7e68ceb6420478c8d89d35b4745d0b2f42'/>
<id>urn:sha1:fcf1dd7e68ceb6420478c8d89d35b4745d0b2f42</id>
<content type='text'>
There are fitpc2 compatible boards that hang with existent i/o
operations order. Solution is to switch between writing to data
and command ports.

Signed-off-by: Denis Turischev &lt;denis@compulab.co.il&gt;
Signed-off-by: Wim Van Sebroeck &lt;wim@iguana.be&gt;

</content>
</entry>
<entry>
<title>Watchdog: sb_wdog.c: Fix sibyte watchdog initialization</title>
<updated>2010-04-26T18:14:03Z</updated>
<author>
<name>Guenter Roeck</name>
</author>
<published>2010-04-19T15:37:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=86913315de5ed13debd1566dfea15c4179b1f0c0'/>
<id>urn:sha1:86913315de5ed13debd1566dfea15c4179b1f0c0</id>
<content type='text'>
Watchdog configuration register and timer count register were interchanged,
causing wrong values to be written into both registers.
This caused watchdog triggered resets even if the watchdog was reset in time.

Signed-off-by: Guenter Roeck &lt;guenter.roeck@ericsson.com&gt;
Acked-by: Ralf Baechle &lt;ralf@linux-mips.org&gt;
Signed-off-by: Wim Van Sebroeck &lt;wim@iguana.be&gt;

</content>
</entry>
<entry>
<title>[WATCHDOG] max63xx driver depends on ioremap()</title>
<updated>2010-04-16T12:26:32Z</updated>
<author>
<name>Geert Uytterhoeven</name>
</author>
<published>2010-04-07T17:57:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=aebaec975f30c4db40bb418fe9117bb6b4655b1b'/>
<id>urn:sha1:aebaec975f30c4db40bb418fe9117bb6b4655b1b</id>
<content type='text'>
Correct fix for the "ioremap() causes build failure on S390" should have been
a dependancy on HAS_IOMEM. So we add this dependancy also (and leave the driver
in the ARM section for now).

Signed-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;
Signed-off-by: Wim Van Sebroeck &lt;wim@iguana.be&gt;

</content>
</entry>
<entry>
<title>[WATCHDOG] max63xx: be careful when disabling the watchdog</title>
<updated>2010-04-16T12:26:27Z</updated>
<author>
<name>Marc Zyngier</name>
</author>
<published>2010-04-09T16:43:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b1183e064a3f95d27351b2d2c811b50bf4d770a4'/>
<id>urn:sha1:b1183e064a3f95d27351b2d2c811b50bf4d770a4</id>
<content type='text'>
When shutting down the watchdog timer, special care must be taken
not to overwrite other bits in the register, as it may be shared
with other peripherals.

For example, on the Arcom Vulcan, the register is shared between
the watchdog and the PCI reset line...

Signed-off-by: Marc Zyngier &lt;maz@misterjones.org&gt;
Signed-off-by: Wim Van Sebroeck &lt;wim@iguana.be&gt;

</content>
</entry>
<entry>
<title>[WATCHDOG] fixed book E watchdog period register mask.</title>
<updated>2010-04-16T12:23:04Z</updated>
<author>
<name>Luuk Paulussen</name>
</author>
<published>2010-04-15T03:59:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0fb06571bbb5c72b4663c20f721323260ea802bf'/>
<id>urn:sha1:0fb06571bbb5c72b4663c20f721323260ea802bf</id>
<content type='text'>
A previous fix changed the WDTP function to use the period directly,
rather than subtracting from 63.  However the mask generation was
not changed, so the mask was coming out as 0.  This patch fixes it.

Signed-off-by: Luuk Paulussen &lt;luuk.paulussen@alliedtelesis.co.nz&gt;
Signed-off-by: Wim Van Sebroeck &lt;wim@iguana.be&gt;

</content>
</entry>
</feed>
