linux-kernel - Re: [PATCH v3 char-misc-next] misc: microchip: pci1xxxx: Add OTP/EEPROM driver for the pci1xxxx switch

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20230207134526.2465045-1-michael@walle.cc>
Date:   Tue,  7 Feb 2023 14:45:26 +0100
From:   Michael Walle <michael@...le.cc>
To:     gregkh@...uxfoundation.org
Cc:     Kumaravel.Thiagarajan@...rochip.com,
        Tharunkumar.Pasumarthi@...rochip.com, UNGLinuxDriver@...rochip.com,
        arnd@...db.de, linux-gpio@...r.kernel.org,
        linux-kernel@...r.kernel.org, lkp@...el.com,
        Michael Walle <michael@...le.cc>
Subject: Re: [PATCH v3 char-misc-next] misc: microchip: pci1xxxx: Add OTP/EEPROM driver for the pci1xxxx switch

>> Our objective with that part of code is to wait for OTP_STATUS_BUSY_BIT 
>> to be cleared in the hardware, but make sure that we wait for a maximum 
>> of OTP_RW_TIMEOUT_MILLISECONDS ms in the driver and not beyond that. 
>
> How exact much do you mean by "not beyond that"?

Yeah that sounds strange. What is the reason to not wait "beyond that"?

Reading that paragraph above, it looks like you should have a look at
linux/iopoll.h.

-michael