linux-kernel - Re: [PATCH v6 2/2] dt-bindings: rtc: add max313xx RTCs

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]

Message-ID: <392dbedc-6b5b-48f6-a7f2-94a2aa6bbc33@roeck-us.net>
Date: Wed, 7 Feb 2024 07:00:53 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: "Miclaus, Antoniu" <Antoniu.Miclaus@...log.com>,
 Alexandre Belloni <alexandre.belloni@...tlin.com>,
 Chris Packham <Chris.Packham@...iedtelesis.co.nz>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
 "robh+dt@...nel.org" <robh+dt@...nel.org>,
 "krzysztof.kozlowski+dt@...aro.org" <krzysztof.kozlowski+dt@...aro.org>,
 "conor+dt@...nel.org" <conor+dt@...nel.org>,
 "jdelvare@...e.com" <jdelvare@...e.com>,
 "noname.nuno@...il.com" <noname.nuno@...il.com>,
 "linux-rtc@...r.kernel.org" <linux-rtc@...r.kernel.org>,
 "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 "linux-hwmon@...r.kernel.org" <linux-hwmon@...r.kernel.org>,
 Ibrahim Tilki <Ibrahim.Tilki@...log.com>,
 "Arslanbenzer, Zeynep" <Zeynep.Arslanbenzer@...log.com>
Subject: Re: [PATCH v6 2/2] dt-bindings: rtc: add max313xx RTCs

On 2/7/24 01:54, Miclaus, Antoniu wrote:
[ ... ]
>>
>> The max31335 is not available
>>
>   
> Indeed, the max31355 datasheet is not available yet. This is also stated in the
> cover letter of the patch series for max31335.
> 
> It was an urgent request from a customer to have it mainline as soon as possible.
> 
> If there are questions about the part functionality, I can definitely help.
> 

It seems to be quite common for automotive chips, though, that they are held
tightly under wrap, making it all but impossible to properly review their drivers.
I have observed several times now that information not available to reviewers
resulted in bad or buggy drivers. This isn't about willingness to help, it is
about the ability to understand chip capabilities and requirements.

Guenter