linux-kernel - Re: [PATCH v2 03/12] dt-bindings: connector: Add the GOcontroll Moduline module slot bindings

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:
 <PA4PR04MB7630DA5DF63C18530B86AB59C5DF2@PA4PR04MB7630.eurprd04.prod.outlook.com>
Date: Mon, 17 Mar 2025 10:42:14 +0000
From: Maud Spierings | GOcontroll <maudspierings@...ontroll.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
CC: Rob Herring <robh@...nel.org>, Neil Armstrong <neil.armstrong@...aro.org>,
	Jessica Zhang <quic_jesszhan@...cinc.com>, Maarten Lankhorst
	<maarten.lankhorst@...ux.intel.com>, Maxime Ripard <mripard@...nel.org>,
	Thomas Zimmermann <tzimmermann@...e.de>, David Airlie <airlied@...il.com>,
	Simona Vetter <simona@...ll.ch>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>, Thierry Reding
	<thierry.reding@...il.com>, Sam Ravnborg <sam@...nborg.org>, Liu Ying
	<victor.liu@....com>, Shawn Guo <shawnguo@...nel.org>, Sascha Hauer
	<s.hauer@...gutronix.de>, Pengutronix Kernel Team <kernel@...gutronix.de>,
	Fabio Estevam <festevam@...il.com>, Mark Brown <broonie@...nel.org>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"imx@...ts.linux.dev" <imx@...ts.linux.dev>,
	"linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "linux-spi@...r.kernel.org"
	<linux-spi@...r.kernel.org>
Subject: Re: [PATCH v2 03/12] dt-bindings: connector: Add the GOcontroll
 Moduline module slot bindings

From: Krzysztof Kozlowski <krzk@...nel.org>
Sent: Monday, March 17, 2025 11:34 AM
 
>On Sat, Mar 15, 2025 at 07:32:28AM +0000, Maud Spierings | GOcontroll wrote:
>> >> +required:
>> >> +  - compatible
>> >> +  - reg
>> >> +  - reset-gpios
>> >> +  - interrupts
>> >> +  - sync-gpios
>> >> +  - i2c-bus
>> >> +  - slot-number
>> >> +
>> >> +additionalProperties: false
>> >> +
>> >> +examples:
>> >> +  - |
>> >> +    #include <dt-bindings/gpio/gpio.h>
>> >> +    #include <dt-bindings/interrupt-controller/irq.h>
>> >> +
>> >> +    spi {
>> >> +        #address-cells = <1>;
>> >> +        #size-cells = <0>;
>> >> +
>> >> +        connector@0 {
>> >
>> >I find this being a SPI device a bit strange. Is there a defined SPI
>> >device that every slot is going to have? Or the connector has SPI
>> >interface and *anything* could be attached on it?
>>
>> So a module slot is like a pcie slot, it can be occupied or not, and when
>
>But which buses...

I don't think I am fully understanding what you are asking of me. The
module will always be an spi device, that is the main communication bus.

Kind regards,
Maud