linux-kernel - RE: [RFC PATCH] watchdog: da9062: Correct the timeout values [Klartext]

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <DB9PR10MB46529728D2574AE35CB84D3680349@DB9PR10MB4652.EURPRD10.PROD.OUTLOOK.COM>
Date:   Tue, 15 Feb 2022 09:16:10 +0000
From:   Adam Thomson <Adam.Thomson.Opensource@...semi.com>
To:     Christoph Niedermaier <cniedermaier@...electronics.com>,
        Guenter Roeck <linux@...ck-us.net>,
        Adam Thomson <Adam.Thomson.Opensource@...semi.com>,
        Andrej Picej <andrej.picej@...ik.com>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>
CC:     Support Opensource <Support.Opensource@...semi.com>,
        Wim Van Sebroeck <wim@...ux-watchdog.org>,
        "linux-watchdog@...r.kernel.org" <linux-watchdog@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [RFC PATCH] watchdog: da9062: Correct the timeout values
 [Klartext]

On 14 February 2022 18:03, Christoph Niedermaier wrote:

> I come to the conclusion that under normal condition (room temperature) the
> timeout values could be improved, but due to the used internal ring oscillator
> on the DA9061 chip under extreme conditions like automotive (125 degrees) the
> values come close to the DA9062 timeout values, if an external oscillator
> is used. In order not to trigger too early in extreme situations, the values
> must be left as they are. But I told Dialog to add a note in the data sheet
> explaining the deviation when the internal oscillator is used (DA9061).
> 
> Thanks for helping me and best regards
> Christoph

Thanks for the update. I'll also push internally for the Datasheet update
so this is clearer in the future, to avoid any misunderstandings.