Hi Linus,
Please pull the watchdog fixes for the v4.16 release cycle.
This series contains:
* f71808e_wdt: Fix magic close handling
* sbsa: 32-bit read fix for WCV
* hpwdt: Remove legacy NMI sourcing
The output from git request-pull:
--
e license text and module licence match
watchdog: add SPDX identifiers for watchdog subsystem
Milton Miller (2):
watchdog: aspeed: Fix translation of reset mode to ctrl register
watchdog: aspeed: Allow configuring for alternate boot
Wim Van Sebroeck (4):
Merge branc
: rave-sp: add NVMEM dependency
Matteo Croce (1):
watchdog: i6300esb: fix build failure
Radu Rendec (1):
watchdog: xen_wdt: fix potential build failure
Wim Van Sebroeck (1):
watchdog: sp5100_tco.c: fix potential build failure
drivers/watchdog/Kconfig | 4
1 file changed
The following changes since commit 4dd3c2e5a4225e3df85afc6033e62ce8b09f0ed2:
Merge tag 'nfsd-4.15' of git://linux-nfs.org/~bfields/linux (2017-11-18
11:22:04 -0800)
are available in the git repository at:
git://www.linux-watchdog.org/linux-watchdog.git
for you to fetch changes up to 14807
On Sat, Sep 03, 2005 at 02:42:36AM -0400, Daniel Phillips wrote:
> On Friday 02 September 2005 20:16, Mark Fasheh wrote:
> > As far as userspace dlm apis go, dlmfs already abstracts away a large part
> > of the dlm interaction...
>
> Dumb question, why can't you use sysfs for this instead of rolli
On Fri, Sep 02, 2005 at 11:17:08PM +0200, Andi Kleen wrote:
> Andrew Morton <[EMAIL PROTECTED]> writes:
>
> >
> > Again, that's not a technical reason. It's _a_ reason, sure. But what are
> > the technical reasons for merging gfs[2], ocfs2, both or neither?
clusterfilesystems are very common,
yCodeRelDate4 04052004
wCountryCode 0x4803
Device Status: 0x0000
(Bus Powered)
Regards Wim.
On Wed, Sep 21, 2016 at 02:21:17PM +0200, Oliver Neukum wrote:
> On Tue, 2016-09-20 at 17:45 +0200, Wim Osterholt wrote:
>
> Anyway, which of its configurations is used?
> Please look up the bConfigurationValue for your device
> in sysfs.
And what might that be?
'locate sys
which reads 'Conexant' and
bConfigurationValue which reads '1'
Regards, Wim.
> PIRQ_PENALTY_PCI_USING;
> +
>
>
>
> > Bjorn
I tried this on kernel 4.7.0-rc4, but that didn't help. It still tried to
grab irq7.
Regards, Wim.
- w...@djo.tudelft.nl -
nction and then send
> the output?
>
> pr_info("%s:%d irq = %d penalty = %d\n", __func__, __LINE__, irq,
> penalty);
>
This produced some 60 lines extra. Too much to include here.
The entire dmesg file is here:
http://webserver.djo.tudelft
must be done in a safe 4.7.4 or a crashable 4.8.
(if I get that far to retrieve dmesg to a file).
Anyway, echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control
results in 'No such file or directory' because there is no 'dynamic_debug'.
The kernel option DYNAMIC_DEBUG was not set.
A new kernel is compiling now..
Groeten, Wim.
trl_msg - rq 0x20,
val 0x0, len 0x7, result 7
4.8-rc7 is compiling now..
Regards, Wim.
ll output of dmesg after that.
That is not possible under a 4.8 kernel.
'Fixing recursive fault but reboot is needed!' and frozen it is.
Regards, Wim.
thread_data+0xf/0x13 SS:ESP 0068:dec31f44
[ 410.763961] CR2: ffec
[ 410.763964] ---[ end trace 6872abde65b2c9e2 ]---
[ 410.763965] Fixing recursive fault but reboot is needed!
Regards, Wim.
t I didn't all write down, but it says
null pointer dereference at 0246
...
failed while handling devices/pci:00/:00:1d.3/usb7/7-1/7-1:1d etc.
...
udevd .. is taking too long..
Could someone please explain and repair the magic that is happening here?
Thanks in advance, Wim Osterholt.
- w...@djo.tudelft.nl -
[13125] failed while
handling '/devices/pci:00/:00:1d.3/usb7/7-1/7-1:1.0'
Sep 6 19:15:44 localhost shutdown[13136]: shutting down for system reboot
Regards, Wim.
for anything the last 20 years or so.
I don't have the device at hand here, so new logs will be available
tomorrow.
Regards, Wim.
SS:ESP 0068:dc741ce8
[ 46.391243] CR2: 0246
[ 46.802809] ---[ end trace 3cd7f784cc67fa66 ]---
[ 46.811156] udevd[884]: worker [1868] terminated by signal 9 (Killed)
[ 46.811164] udevd[884]: worker [1868] failed while handling
'/devices/pci:00/0000:00:1d.2/usb4/4-1/4-1:1.1'
Regards, Wim.
y
Hello Julius,
I agree with you. Using an existing standard is better than inventing a new one
in this case. I think using the coreboot logging is a good idea as there is
indeed a lot of support already available and it is lightweight and simple.
Best Regards,
Wim Vervoorn
Eltan B.V
Tom, you used the wrong GPL license header. Please fix that to be v2 not v3.
The
+# SPDX-License-Identifier: GPL-2.0
is correct but the adi-test.c one is not.
On 04/20/2018 10:34 AM, Tom Hromatka wrote:
Add a selftest for the sparc64 privileged ADI driver. These
tests verify the read(), prea
da 5b 5d e9 f5 fd ff ff 55 89 e5 3e 8d 74 26 00 8b 80 84 02 00 00 5d <8b> 40
ec c3 55 89 e5 52 3e 8d 74 26 00 b9 04 00 00 00 8b 90 84
[ 161.398316] EIP: [] kthread_data+0xf/0x13 SS:ESP 0068:df4dbf44
[ 161.398318] CR2: ffec
[ 161.398320] ---[ end trace da016e6d3520a332 ]---
[ 161.398321] Fixing recursive fault but reboot is needed!
Regards, Wim.
27;t understand how it could crash.
The oops does normally not immediately lead to a crash. Only with debugging
on it will halt immediately and the log will tell you that a reboot will
be necessairy.
Wim.
No idea of what you mean here.
> would you? What's the output of
>
> cat /sys/bus/usb/drivers/cdc_acm/new_id
Just empty.
Wim.
On Thu, Dec 29, 2016 at 05:53:58PM +0100, Wim Osterholt wrote:
L.S.,
>
> after appearance of kernel-4.10-rc1 two days ago I was pleasantly surprised
> to find a question about lirc_serial in 'make oldconfig':
>
> Homebrew Serial Port Receiver (IR_SERIAL) [N/m/?] (N
On Sat, Jan 07, 2017 at 05:11:38PM +0100, Wim Osterholt wrote:
> On Thu, Dec 29, 2016 at 05:53:58PM +0100, Wim Osterholt wrote:
>
> L.S.,
> >
> > after appearance of kernel-4.10-rc1 two days ago...
>
> A quickly following release of 4.10-rc2 made sure that lirc_dev
On Wed, Jun 22, 2016 at 11:54:39PM -0400, ok...@codeaurora.org wrote:
> On 2016-06-21 18:13, Wim Osterholt wrote:
> >>
> >>pr_info("%s:%d irq = %d penalty = %d\n", __func__, __LINE__, irq,
> >>penalty);
> >>
> >
> >
ll Inspiron 4100.
The same problem arises at a Dell Inspiron 510m.
I've not seen it on a workstation Dell XW4300.
Groeten, Wim.
- w...@djo.tudelft.nl -
out -b new v4.5 (assuming that the first 'wrong' kernel would be best)
git revert 09954bad448(that did something, which I assume te be good)
copied the .config file from 4.5 I had lying around and ran make.
Surprising or not, the thusly compiled kernel ran fine and I could handle
floppies like before!
(open(/dev/fd0,O_ACCMODE) succeeds.)
Regards, Wim.
- w...@djo.tudelft.nl -
or some such.
Problem is that fdutils is probably unmaintained for ten years or so.
Regards, Wim.
- w...@djo.tudelft.nl -
On Wed, Jun 15, 2016 at 04:13:53PM +0200, Jiri Kosina wrote:
>
> Wim, could you please test whether the patch below, applied on top of
> vanilla kernel (i.e. drop the revert), everything you are using still
> works as expected?
>
Applied on kernel-4.7-rc3 it looks like it
On my first message I stated:
It looks to me that the code in floppy.c is quite old; no changes here.
So the bug is elsewhere in the kernel.
That was because the changelog at the beginning of floppy.c ended in 2003.
Wouln't it be wise to keep these items updated?
Groeten, Wim.
--
space for ioctl-only open().
>
> Reintroduce back the original behavior wrt !(FMODE_READ|FMODE_WRITE)
> modes, while still keeping the original O_NDELAY bug fixed.
>
> Cc: sta...@vger.kernel.org # v4.5+
> Reported-by: Wim Osterholt
> Tested-by: Wim Osterholt
> Signed-off-by: Jir
On Wed, Nov 16, 2016 at 01:34:30PM +0100, Oliver Neukum wrote:
>
> This is very odd. We need to know where it crashes. Please try the
> insane debug patch I posted.
A bit of patience please. Yesterday I hadn't the modem at hand.
Groeten, Wim.
On Wed, Nov 16, 2016 at 04:07:57PM +0100, Wim Osterholt wrote:
> A bit of patience please. Yesterday I hadn't the modem at hand.
Whell, I lost track of what happens where with which config file..
Confusion about the bug not appearing an too many configs with SMP set
where I'm sure
On Thu, Nov 17, 2016 at 02:57:33AM +0100, Wim Osterholt wrote:
> Now a retry of 4.9-rc5. I take the config of 4.8.8 and accept
> the default for the new options.
> SMP set. No call trace appears.
> For completeness I should also try with SMP unset. That is for tomorrow
> then.
On Thu, Nov 17, 2016 at 10:14:34AM +0100, Wim Osterholt wrote:
> > For completeness I should also try with SMP unset. That is for tomorrow
> > then.
>
> With CONFIG_SMP unset nothing goes wrong here either.
> It looks like it has been fixed in 4.9-rc5, but I should also d
or C_S unset)
Tests on other machines with (slightly) different configs all seem to
confirm that the problems are gone when CONFIG_SMP is set.
Regards, Wim.
at shutdown
time). It's not even an oops but a warning. In the end it happens to just
work.
Regards, Wim.
(For lirc-0.9.0 you'll need a missing patch for the vanished f_dentry stuff
in the kernel source.)
Regards, Wim.
On Mon, Nov 21, 2016 at 02:19:32PM +0100, Oliver Neukum wrote:
> On Thu, 2016-11-17 at 17:11 +0100, Wim Osterholt wrote:
>
> > Nov 17 15:07:51 localhost kernel: Check point 10
> > Nov 17 15:07:51 localhost kernel: BUG: unable to handle kernel NULL pointer
> > dereferenc
On Mon, Nov 21, 2016 at 04:58:25PM +0100, Wim Osterholt wrote:
>
> I didn't find traces of kernel-4.9-rc5 being ran on any of my laptops, so I
> can't have seen a crash on rc5. It seems rc5 and rc6 is safe now.
Neither 4.8.10, nor 4.8.9 show the bug.
It must be a bug ousid
+ACPI
http://webserver.djo.tudelft.nl/dmesg473+ACPI
http://webserver.djo.tudelft.nl/dmesg473noACPI
(with excuses for the silly hostname which is out of our control)
Regards, Wim.
- w...@djo.tudelft.nl -
On Tue, Oct 18, 2016 at 02:18:43PM +0200, Oliver Neukum wrote:
> On Mon, 2016-10-17 at 17:20 +0200, Wim Osterholt wrote:
> > On Mon, Oct 17, 2016 at 04:10:45PM +0200, Oliver Neukum wrote:
> > > Hi,
> > >
> > > I got one of those devices. However, I don&#
no changes here.
So the bug is elsewhere in the kernel.
Could someone please explain and repair the magic that is happening here?
Thanks in advance, Wim Osterholt.
- w...@djo.tudelft.nl -
main(int argc, char *argv[])
> {
> if (open("foo", 3) == -1)
> perror("foo");
> return 0;
> }
No errors get printed for kernel 4.4 to 4.7 .
Regards, Wim.
- w...@djo.tudelft.nl -
ISA_IRQS)
> - penalty += acpi_isa_irq_penalty[irq];
> + return acpi_isa_irq_penalty[irq];
>
> /*
> * Penalize IRQ used by ACPI SCI. If ACPI SCI pin attributes conflict
Regards, Wim.
- w...@djo.tudelft.nl -
On Sat, Jun 25, 2016 at 04:51:03AM -0400, ok...@codeaurora.org wrote:
> On 2016-06-24 21:39, Wim Osterholt wrote:
>
> Please apply the patches on top of clean 4.7-rc4 tree and apply them in
> order with
>
> git am 0001...
> git am 0002...
It doesn't work that way.
B
t
> you something to test before posting the official version.
The 510m just finished compiling and now it works fine too.
Thanks.
Regards, Wim.
- w...@djo.tudelft.nl -
s quite similar to the one from kernel-4.6 .
Tested-by: Wim Osterholt.
.nl/.config-4.8.1
Many options are inherited by 'make oldconfig' from version to version,
without me knowing what it all means. So maybe it's just a weird combination
of options then?
Regards, Wim.
make any
difference, except for that it says 'a reboot is necessairy' en then it
freezes. Still no symbols.
Google didn't tell me anything useful, nor did you.
This took me days already.
I told you all you need: plug in a modem that needs cdc_acm.
Wim.
- w...@djo.tudelft.nl -
On Thu, Sep 08, 2016 at 03:05:15PM +0200, Oliver Neukum wrote:
>
> your stack trace is broken. Did you fail to install the System.map file?
>
> Regards
> Oliver
A laptop, more broken than the rest, does not output anything after
inserting. Later on it crashes. No system.map f
if (quirks & NO_CAP_LINE)
1348acm->ctrl_caps &= ~USB_CDC_CAP_LINE;
1349acm->ctrlsize = ctrlsize;
1350acm->readsize = readsize;
(gdb) quit
A new kernel is compiling now.
Regards, Wim.
0249
[ 3745.49] ---[ end trace e6bc96526d51607e ]---
[ 3745.006322] udevd[945]: worker [24530] terminated by signal 9 (Killed)
[ 3745.008927] udevd[945]: worker [24530] failed while handling
'/devices/pci0000:00/:00:1d.3/usb6/6-1/6-1:1.0'
Regards, Wim.
ohci_pci ohci_hcd uhci_hcd wmi floppy parport_pc soundcore
ehci_pci parport acpi_cpufreq ehci_hcd button processor
[ 551.177957] CPU: 0 PID: 725 Comm: kworker/0:2 Tainted: G O
4.8.0-rc8 #1
Regards, Wim.
On Wed, Sep 28, 2016 at 07:38:41PM -0400, Sinan Kaya wrote:
>
> Can you try these patches on your machines please?
I applied the included patches on vanilla 4.8-rc8 and my machine booted
fine. (I saw a remark about SCSI interrupts, but I have no SCSI.)
Regards, Wim.
ctrlsize = usb_endpoint_maxp(epctrl);
1329WARN_ON(!epread);
1330readsize = usb_endpoint_maxp(epread) *
1331(quirks == SINGLE_RX_URB ? 1 : 2);
1332acm->combined_interfaces = combined_interfaces;
1333WARN_ON(!epwrite);
1334acm->writesize = usb_endpoint_maxp(epwrite) * 20;
1335acm->control = control_interface;
1336acm->data = data_interface;
(gdb)
quit
Regards, Wim.
Hi Aaro,
> Introduce Retu watchdog driver.
>
> Cc: linux-watch...@vger.kernel.org
> Acked-by: Felipe Balbi
> Acked-by: Tony Lindgren
> Signed-off-by: Aaro Koskinen
> Cc: Wim Van Sebroeck
Added tolinux-watchdog-next.
Kind regards,
Wim.
--
To unsubscribe from thi
Hi Guenter,
> Signed-off-by: Guenter Roeck
> ---
> drivers/watchdog/Kconfig |1 +
> drivers/watchdog/booke_wdt.c | 185
> +++---
> 2 files changed, 66 insertions(+), 120 deletions(-)
>
Added to linux-watchdog-next.
Kind
chdog: introduce retu_wdt driver")
> from the watchdog tree.
>
> I fixed it up (see below) and can carry the fix as necessary (no action
> is required).
Thanks!
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Hi Fabio, Samuel,
> This patch adds support for the ux500_wdt watchdog that is found in
> ST-Ericsson Ux500 platform. The driver is based on PRCMU APIs.
>
> Acked-by: Linus Walleij
> Acked-by: Lee Jones
> Signed-off-by: Fabio Baltieri
Acked-by: Wim Van Sebroeck
Kind re
r
> watchdog register base address.
>
> This patch fixes this bug.
>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=43176
> Signed-off-by: Takahisa Tanaka
Added to linux-watchdog-next.
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "u
o module perform a read-merge-write operation
> on all the chipset (sp5100, sb7x0, sb8x0 or later).
>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=43176
> Signed-off-by: Takahisa Tanaka
Added to linux-watchdog-next.
Kind regards,
Wim.
--
To unsubscribe from this list: send
9f4b): undefined reference to
> `watchdog_register_device'
>
> Signed-off-by: Randy Dunlap
> Cc: David Dajun Chen
> Cc: Wim Van Sebroeck
> Cc: linux-watch...@vger.kernel.org
> ---
> drivers/watchdog/Kconfig |1 +
> 1 file changed, 1 insertion(+)
>
> Fou
(.data+0x28): Section mismatch in
> reference from the variable at91wdt_driver to the (unknown reference)
> .init.rodata:(unknown)
> The variable at91wdt_driver references
> the (unknown reference) __initconst (unknown)
>
> Signed-off-by: Arnd Bergmann
> Cc: Wim Van Sebroeck
lt="
> __MODULE_STRING(WATCHDOG_NOWAYOUT) ")");
>
> MODULE_LICENSE("GPL");
> +MODULE_ALIAS("platform:orion_wdt");
> MODULE_ALIAS_MISCDEV(WATCHDOG_MINOR);
> --
> 1.7.1
>
Added to linux-watchdog-next.
Kind regard
NOWAYOUT;
The rest is OK by me. So if bowayout get's fixed then you have my acked-by.
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
gt; 10 74 4a 48 c7 c7 80 6d f5 81 e8 ae ab 22 00 48 89 c3
> 48 85
> [0.067063] RIP [] perf_init_event+0x32/0x100
> [0.067067] RSP
> [0.067069] CR2:
> [0.067077] ---[ end trace 3cbbfd94f0f8f035 ]---
touch_nmi_watchdog is defined in kernel/watchdog.c
Hi Sedat,
> while digging into a Linux-Next issue [0] I wanted to browse the
> watchdog GitWeb, but it seems not to be available for me!
Correct. I disabled it because the server has not enough memory...
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "unsubs
>> 16;
>
> /* Calculate the timeout in seconds */
> if (prescale)
> @@ -273,6 +298,7 @@
> .compatible = "fsl,mpc823-wdt",
> .data = &(struct mpc8xxx_wdt_type) {
> .prescaler = 0x800,
> + .hw_enabled = true,
> },
> },
> {},
The rest of the code is OK and when above comments are corrected,
I will add the patch to improve the userspace experience.
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
;
> Signed-off-by: Alessandro Rubini
> Acked-by: Giancarlo Asnaghi
> Signed-off-by: Davide Ciminaghi
> Acked-by: Wim Van Sebroeck
> Acked-by: Linus Walleij
> Acked-by: Viresh Kumar
> Signed-off-by: H. Peter Anvin
Added to linux-watchdog-next.
Kind regards,
Wim.
--
To un
Hi Pali,
> Like other watchdog drivers, this patch adds new option nowayout
> which overwrite WATCHDOG_NOWAYOUT.
Added to linux-watchdog-next.
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...
Hi Kumar,
> Update the code to use devm_* API so that driver
> core will manage resources.
>
> Signed-off-by: Kumar, Anil
Added to linux-watchdog-next.
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
delay.h header file was included twice.
Signed-off-by: Sachin Kamat
Signed-off-by: Wim Van Sebroeck
commit 4b1c2f41c2dda158bb7a3dded70775a76b581995
Author: Randy Dunlap
Date: Mon Jul 23 10:46:11 2012 -0700
watchdog: fix watchdog-test.c build warning
Fix compiler
And the fix is in Linus his tree also now.
Kind regards,
Wim.
> On 08/29/2012 06:39 AM, yan wrote:
>
> > This patch fixs the following compiler warning:
> >
>
>
> Hi,
> This is already fixed in the watchdog git tree.
>
> Thanks.
>
> > Do
Hi Oskar,
> This watchdog device provides pretimeout facilities:
> Set some timeout value and get informed about imminent
> watchdog activity thru interrupt.
>
> Allow user to wait for this interrupt thru poll(2),
> and to clear it thru read(2).
>
> Signed-off-by: Oskar
ke it easy later to switch to common clk based implementation
> >> of clk driver from DaVinci specific driver.
> >>
> >> Signed-off-by: Murali Karicheri
Could you resent the original e-mail because I didn't seem to have received
it...
And I can't even find it
Hi Denys,
> Probably someone can help me with this? Or it is hardware bug of chipset?
> I will try to look more docs, maybe i will be able to find whats wrong there.
I'll have a look at it next week.
Greetings,
Wim.
--
To unsubscribe from this list: send the line "unsubscribe
+
> > 3 files changed, 238 insertions(+), 0 deletions(-)
> > create mode 100644 drivers/watchdog/da9055_wdt.c
I'll review it tomorrow- or wednesday-evening. My first impression is that it
looks OK.
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "un
gt; ---
> drivers/watchdog/softdog.c |1 -
> 1 file changed, 1 deletion(-)
Patch added to linux-watchdog-next.
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
Hi Stephen,
> On Thu, 11 Jul 2013 22:34:24 +0200 Wim Van Sebroeck wrote:
> >
> > Please pull from 'master' branch of
> > git://www.linux-watchdog.org/linux-watchdog.git
>
> This was all rebased in the last day from what has been in linux-next for
>
rted git but apparently it didn't do anything anymore.
I just restarted it and saw a pull coming in again. So it is fixed now.
Thanks for pointing it out.
Wim.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel
return ret;\) }
... when != res
+ res = platform_get_resource(pdev, IORESOURCE_MEM, n);
e = devm_ioremap_resource(e1, res);
//
Signed-off-by: Julia Lawall
Reviewed-by: Guenter Roeck
Signed-off-by: Wim Van Sebroeck
commit 8ecc7d2b2207ed9642e3d0140bfaa8c93a6ea47f
Aut
main) iLO device. All auxilary iLO devices will have a
subsystem device ID set to 0x1979 in order for hpwdt to differentiate
between
the two types.
Signed-off-by: Thomas Mingarelli
Tested-by: Lisa Mitchell
Signed-off-by: Wim Van Sebroeck
For completeness, I added the o
plan to keep the set of patches together in one tree?
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
pci_mem_addr + 0x72;
>
> + /* Make sure that timer is disabled until /dev/watchdog is opened */
> + hpwdt_stop();
> +
> /* Make sure that we have a valid soft_margin */
> if (hpwdt_change_timer(soft_margin))
> hpwdt_change_timer(DEFAULT_MARGIN);
03:37 2012 +0200
watchdog: twl4030_wdt: add DT support
Add DT support for twl4030_wdt. This is needed to get twl4030_wdt to
probe when booting with DT.
Signed-off-by: Aaro Koskinen
Signed-off-by: Wim Van Sebroeck
commit 412b3729dd0234771c67452b8999191f1e8d8630
Au
>
> > From the watchdog-kernel-api documentation:
> > * parent: set this to the parent device (or NULL) before calling
> > watchdog_register_device.
> >
> Hi Wim,
>
> We live and learn ... thanks a lot for the hint!
If it's about learning: the old way w
Hi Johannes,
> On Mon, May 27, 2013 at 08:25:54PM +0200, Wim Van Sebroeck wrote:
> [...]
> > > + watchdog_set_drvdata(&a21_wdt, drv);
> >
> > I am missing the initialisation of the watchdog's timeout value here...
>
> This watchdog only knows two time
>
> > From the watchdog-kernel-api documentation:
> > * parent: set this to the parent device (or NULL) before calling
> > watchdog_register_device.
> >
> Hi Wim,
>
> unfortunately that only works if the driver is instantiated as platform
> drive
Hi Guenter,
> On Tue, May 28, 2013 at 10:10:53AM +0200, Johannes Thumshirn wrote:
> > On Mon, May 27, 2013 at 08:25:54PM +0200, Wim Van Sebroeck wrote:
> > [...]
> > > > + watchdog_set_drvdata(&a21_wdt, drv);
> > >
> > > I am missing the in
Hi Johannes,
> Ok I'll do. Should I repost this as a change of this patch or the "add driver"
> patch?
the add driver patch.
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger
plication doing it anyway is
> > buggy
> > > > and should be fixed.
> > >
> > > I fully understand your points and 100% agree with you
> > > 1. the application is broken and should be fixed
> > > 2. also the kernel shouldn't fix any probl
wdt) should indeed be fixed because they poke in the hardware
directly and can't be really detected.
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
inux-watchdog-next.
I am still thinking about wether or not we shouldn't add a timer to this
watchdog device driver. But that's something we can change later on.
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mes
-off-by: Johannes Thumshirn
I will not add this patch and put it in my waiting queue.
Reason: we should first do the sysfs stuff for the wwatchdog_core (since
active and nowayout are parameters that will be in the sysfs watchdog core).
Kind regards,
Wim.
--
To unsubscribe from this list: send the
> 1 file changed, 11 insertions(+), 20 deletions(-)
Both patches added to linux-watchdog-next.
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel
ess than or equal to 1 second(basically small values).
>
> As suggested by Wim Van Sebroeck & Guenter Roeck we should
> add this functionality of individual watchdog drivers in the core
> watchdog core.
Have you considered the effect this change has on all watchdog drivers
that do
Hi Lubomir,
> This adds a driver for watchdog timer hardware present on Broadcom BCM2835
> SoC,
> used in Raspberry Pi and Roku 2 devices.
>
> Signed-off-by: Lubomir Rintel
> Tested-by: Stephen Warren
> Cc: Stephen Warren
> Cc: Wim Van Sebroeck
> Cc: Guenter
1 - 100 of 476 matches
Mail list logo
