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  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]
Date:   Thu, 23 Sep 2021 17:24:38 -0500
From:   Rob Herring <>
To:     Krzysztof Kozlowski <>,
        Guenter Roeck <>
Cc:     Jean Delvare <>, Jiri Kosina <>,
        Jonathan Cameron <>,,,
Subject: Re: [PATCH 3/6] dt-bindings: hwmon: ibm,cffps: move to trivial

On Tue, Sep 21, 2021 at 02:45:42PM +0200, Krzysztof Kozlowski wrote:
> On 21/09/2021 14:30, Guenter Roeck wrote:
> > On Tue, Sep 21, 2021 at 12:28:29PM +0200, Krzysztof Kozlowski wrote:
> >> The IBM Common Form Factor Power Supply Versions 1 and 2 bindings are
> >> trivial, so they can be integrated into trivial devices bindings.
> >>
> >> Signed-off-by: Krzysztof Kozlowski <>
> > 
> > I won't accept any of those "move to trivial devices" patches. In many cases
> > the bindings are simply incomplete. I can not and will not make that call,
> > and I always did and will leave it up to driver authors to decide if they
> > want to add a device to trivial devices or provide explicit bindings.
> > 
> > Please stop sending those patches.
> > 
> Back in the older times, there were no trivial-devices and checkpatch
> plus maintainers required documenting compatibles, so some of such
> simple bindings were created.

We've had trivial-devices since at least 2011, but it was under i2c 
until 2017. Many existed before we had clock, regulator, etc. bindings, 
so they may have been complete at the time.

> I understand however your point, fair enough. I'll stop sending such
> patches.

Just about every device has a power supply which would not fall in the 
current definition of trivial-devices, though maybe that could be 
extended. I do sometimes wonder if we should just get rid of 

On the flip side, I'd much rather have a schema for these than wait on 
someone to decide to convert them. That could mean a device.txt -> 
trivial-devices.yaml -> device.yaml trip, but that doesn't seem that 
terrible to me. Then we at least are running schema checks on the 
devices and know if actual users have more undocumented properties. 
We still have ~2000 free form binding docs to convert. I'm looking for 
whatever ways we can speed that up and this looks like one of them to 
me (both Krzysztof's great job doing all these conversions and utilizing 


Powered by blists - more mailing lists