Re: small brainstorm for the problem I have

[Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>]

+Cc: Mika, Hans (if you have any input on this, I will appreciate)

On Tue, Feb 11, 2025 at 01:14:44PM +0100, Bartosz Golaszewski wrote:
> On Mon, Feb 10, 2025 at 10:31 AM Andy Shevchenko
> <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote:
> >
> > I have a device that uses SPI bitbang (which is physically represented by bunch
> > of GPIOs). I want to have a driver of that device to use SPI GPIO driver, but...
> >
> > 1) SPI GPIO has an established DT schema and hardcoded GPIO line names in the
> > driver.
> >
> > 2) The firmware for the device uses already some names for the GPIO lines that
> > not compatible with SPI GPIO schema.
> >
> > So, what would be the best approach here?
> >
> > I was thinking about the following:
> > 1) Use GPIO aggregator to fake the chip that will provide necessary names.
> >
> > 2) Hack the GPIO library to add a quirk for this specific device to translate
> > the line names.
> >
> > 3) ...your variant...
> >
> 
> I would go with #1 of course - as it has the least impact on the
> kernel - but setting the names is not yet available upstream. I'm
> Cc'ing Koichiro Den who's working on adding support for it.

I now realized that under "names" I actually meant "connection IDs"
(con_id in the code).

-- 
With Best Regards,
Andy Shevchenko