linux-kernel - Re: [PATCH 1/2] rtc: k3: wait until the unlock field is not zero

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Tue, 23 Aug 2022 22:26:27 +0200
From:   Alexandre Belloni <alexandre.belloni@...tlin.com>
To:     a.zummo@...ertech.it, bb@...com
Cc:     linux-kernel@...r.kernel.org, linux-rtc@...r.kernel.org, nm@...com
Subject: Re: [PATCH 1/2] rtc: k3: wait until the unlock field is not zero

On Tue, 16 Aug 2022 12:33:11 -0500, Bryan Brattlof wrote:
> After writing the magic words to the KICK0 and KICK1 registers, we must
> wait for a 1 in the unlock field of the general control register to
> signify when the rtc device is in an unlocked state.
> 
> 

Applied, thanks!

[1/2] rtc: k3: wait until the unlock field is not zero
      commit: f2c5671a64d2a79341e8ee45d5933f6a76960189
[2/2] rtc: k3: detect SoC to determine erratum fix
      commit: 1e2585b49d849196f359bbf86677943fe2d80afe

Best regards,

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com