linux-kernel - Re: [PATCH 11/13] MIPS: Add Mobileye EyeQ6Lplus evaluation board dts

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: <2775216.vuYhMxLoTh@benoit.monin>
Date: Fri, 02 Jan 2026 16:27:34 +0100
From: Benoît Monin <benoit.monin@...tlin.com>
To: Mark Brown <broonie@...nel.org>, linux-spi@...r.kernel.org,
 Linus Walleij <linusw@...nel.org>
Cc: Krzysztof Kozlowski <krzk@...nel.org>,
 Vladimir Kondratiev <vladimir.kondratiev@...ileye.com>,
 Gregory CLEMENT <gregory.clement@...tlin.com>,
 Théo Lebrun <theo.lebrun@...tlin.com>,
 Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>,
 Michael Turquette <mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>,
 Philipp Zabel <p.zabel@...gutronix.de>,
 Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
 Tawfik Bayouk <tawfik.bayouk@...ileye.com>, linux-mips@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-clk@...r.kernel.org, linux-gpio@...r.kernel.org
Subject: Re: [PATCH 11/13] MIPS: Add Mobileye EyeQ6Lplus evaluation board dts

Hi Linus,

On Thursday, 1 January 2026 at 23:42:36 CET, Linus Walleij wrote:
> On Fri, Dec 19, 2025 at 4:57 PM Benoît Monin <benoit.monin@...tlin.com> wrote:
> 
> > In my particular case of a microcontroller acting as an SPI "relay" on the
> > evaluation board, what would be the best way to describe it? It connects
> > the two SPI controllers of the SoC, one is a host and one is a target, so
> > it behave as an SPI target on one side and as an SPI host on the other.
> >
> > The trivial devices bindings seems to be dedicated to devices, thus not for
> > SPI hosts. Do I need a dedicated binding or did I miss something I could
> > use for a trivial spidev slave?
> 
> That needs to be detailed and discussed with the SPI maintainer on the SPI
> devel list. (Added.)
> 
> Can you illustrate with a picture or so what is going on here?
> 
> Yours,
> Linus Walleij
> 
Here is what it looks like on the evaluation board of the EyeQ6Lplus:

    +------------------------+          +------------------------+
    | EyeQ6Lplus SoC         |          | Evaluation board MCU   |
    |                        |          |                        |
    |           +------------+          +------------+           |
    |           | SPI host   |          | SPI target |           |
    |           |            |          |            |           |
    |           |        CLK >----------> CLK        |           |
    |           |        SDO >----------> SDI        |           |
    |           |        SDI <----------< SDO        |·····      |
    |           |        CS0 >----------> CS         |    ·      |
    |           +------------+          +------------+    ·      |
    |                        |          |                 · (1)  |
    |           +------------+          +------------+    ·      |
    |           | SPI target |          | SPI host   |    ·      |
    |           |            |          |            |<····      |
    |           |        CLK <----------< CLK        |           |
    |           |        SDI <----------< SDO        |           |
    |           |        SDO >----------> SDI        |           |
    |           |        CS  <----------< CS0        |           |
    |           +------------+          +------------+           |
    |                        |          |                        |
    +------------------------+          +------------------------+

(1): The MCU, when the chip select is asserted on its SPI target, starts
     a transaction on its SPI host side. It then copies data received by
     the target side to the host side.

With the spidev entries in the device tree, it is used to test that SPI
of the SoC is working with `spidev_test`. So the MCU is part of the test
harness found on the evaluation board.

If the SPI signals of the SoC had been routed to a header, we could do the
same test with jumper wires, directly connecting the host and the target.

Best regards,
-- 
Benoît Monin, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com