From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: linux-gpio@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: small brainstorm for the problem I have
Date: Mon, 10 Feb 2025 11:31:00 +0200 [thread overview]
Message-ID: <Z6nHVEB85AQE-rQE@smile.fi.intel.com> (raw)
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...
--
With Best Regards,
Andy Shevchenko
next reply other threads:[~2025-02-10 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 9:31 Andy Shevchenko [this message]
2025-02-11 12:14 ` small brainstorm for the problem I have Bartosz Golaszewski
2025-02-11 12:21 ` Andy Shevchenko
2025-02-12 22:55 ` Linus Walleij
2025-02-13 7:58 ` Andy Shevchenko
2025-02-13 11:24 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z6nHVEB85AQE-rQE@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox