linux-kernel - Re: [PATCH v4 1/5] dt-bindings: misc: Add mikrobus-connector

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]

Date: Tue, 19 Mar 2024 10:38:30 +0100
From: "Michael Walle" <mwalle@...nel.org>
To: "Ayush Singh" <ayushdevel1325@...il.com>, "Krzysztof Kozlowski"
 <krzysztof.kozlowski@...aro.org>, "open list"
 <linux-kernel@...r.kernel.org>
Cc: <jkridner@...gleboard.org>, <robertcnelson@...gleboard.org>,
 <lorforlinux@...gleboard.org>, "Rob Herring" <robh@...nel.org>, "Krzysztof
 Kozlowski" <krzysztof.kozlowski+dt@...aro.org>, "Conor Dooley"
 <conor+dt@...nel.org>, "Nishanth Menon" <nm@...com>, "Vignesh Raghavendra"
 <vigneshr@...com>, "Tero Kristo" <kristo@...nel.org>, "Derek Kiernan"
 <derek.kiernan@....com>, "Dragan Cvetic" <dragan.cvetic@....com>, "Arnd
 Bergmann" <arnd@...db.de>, "Greg Kroah-Hartman"
 <gregkh@...uxfoundation.org>, "Vaishnav M A" <vaishnav.a@...com>, "Mark
 Brown" <broonie@...nel.org>, "Johan Hovold" <johan@...nel.org>, "Alex
 Elder" <elder@...nel.org>, "open list:OPEN FIRMWARE AND FLATTENED DEVICE
 TREE BINDINGS" <devicetree@...r.kernel.org>, "moderated list:ARM/TEXAS
 INSTRUMENTS K3 ARCHITECTURE" <linux-arm-kernel@...ts.infradead.org>, "open
 list:SPI SUBSYSTEM" <linux-spi@...r.kernel.org>, "moderated list:GREYBUS
 SUBSYSTEM" <greybus-dev@...ts.linaro.org>, "Vaishnav M A"
 <vaishnav@...gleboard.org>
Subject: Re: [PATCH v4 1/5] dt-bindings: misc: Add mikrobus-connector

Hi,

> Regardless, this patch actually does not contain any code for EEPROM 
> support I have just mentioned it to give more context on why mikroBUS 
> manifest is the focus of this patch instead of DT overlay or something 
> else.

Right, and I think this is the crux here. Why can't you use DT
overlays? The manifest files, seem to be yet another hardware
description (method) and we already have DT. Can't we have some kind
of userspace helper that could translate them to DT overlays? That
way, you could also handle the EEPROM vs non-EEPROM case, or have
some other kind of method to load a DT overlay.

Admittedly, I've never worked with in-kernel overlays, but AFAIK
they work with some subsystems.

-michael

Download attachment "signature.asc" of type "application/pgp-signature" (253 bytes)