Re: [RFC PATCH 0/3] i2c: Introduce i2c bus extensions

Ayush Singh
2025-07-03T11:26:26Z

On 6/13/25 13:00, Herve Codina wrote:

> Hi Ayush,
>
> On Thu, 12 Jun 2025 13:22:45 +0530
> Ayush Singh <ayush@beagleboard.org> wrote:
>
>> I have tested this patch series for use with pocketbeagle 2 connector
>> driver [0]. To get a better idea how it looks in real devicetree, see
>> the base tree [1] and the overlay [2]. Since it also used gpio and pwm
>> nexus nodes, along with providing pinmux for pins, it can provide a
>> better picture of how the different pieces (export-symbols, nexus nodes,
>> etc) look when combined.
> Nice. Happy to see that I am no more alone with a system using these
> features.
>
>>
>> I also have a question for Herve. Do you already have any working
>> patches for similar extension for SPI and UART in some private tree?
> No, I didn't do anything related to SPI nor UART.
>
> On my system, no SPI nor UART are wired to my connector and so, I haven't
> got any needs to implement extension busses for SPI an UART (serial dev bus)
> nor any support for nexus nodes for other kind of components.
>
> Best regards,
> Hervé

I have added SPI bus extension to my kernel tree [0]. Now, the techlab
cape (other than mikrobus port) works using export-symbols + i2c and spi
bus extension + eeprom auto detection.

Here is a list of everything currently working on the tree:

1. EEPROM based auto-detection.

2. SPI

3. I2C

4. PWM

5. GPIO

Missing:

1. UART (Don't have a cape that has something using the UART yet. Maybe
need to experiment with MikroBUS).

Not quite sure what else to do to move things forward.

Best Regards,

Ayush Singh

[0]: https://github.com/Ayush1325/linux/tree/beagle-cape-v1