lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 17 Dec 2020 19:23:14 +0100 From: Rasmus Villemoes <rasmus.villemoes@...vas.dk> To: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>, Rob Herring <robh+dt@...nel.org> Cc: "open list:REAL TIME CLOCK (RTC) SUBSYSTEM" <linux-rtc@...r.kernel.org>, Alexandre Belloni <alexandre.belloni@...tlin.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Qiang Zhao <qiang.zhao@....com>, Bruno Thomsen <bruno.thomsen@...il.com> Subject: Re: [PATCH v2 1/3] dt-bindings: rtc: add reset-source property On 17/12/2020 19.12, Uwe Kleine-König wrote: > On Thu, Dec 17, 2020 at 10:51:08AM -0600, Rob Herring wrote: >> On Fri, Dec 11, 2020 at 5:10 PM Rasmus Villemoes >> <rasmus.villemoes@...vas.dk> wrote: >> I'm wondering how you solve which wdog to ping when there are multiple >> without relying on numbering. I guess 'reset-source' will solve that >> even if that's not your current fix. So I guess I'm fine with this. > > I guess you'd need some udev magic that ensures that the right watchdog > always gets the same number. The thing is, my board only has one watchdog, and my userspace opens /dev/watchdog (aka /dev/watchdog0). But when a driver suddenly exposes another watchdog device [which happens to be non-functional], and that just happens (probe order, link order, whatever) to be the first one defined, things break. Yes, in the general case one would need some udev rules to create appropriate symlinks. But when there's only one actual device, and I know that, using /dev/watchdog or /dev/watchdog0 is fine. I'll resend cc'ing the dt mailing list, and taking into account the stuff already in -next. Thanks, Rasmus
Powered by blists - more mailing lists