From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andy@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v2 0/4] gpio: aggregator: Incorporate gpio-delay functionality
Date: Thu, 15 Jun 2023 02:14:42 +0300 [thread overview]
Message-ID: <20230614231446.3687-1-andriy.shevchenko@linux.intel.com> (raw)
The newly appeared gpio-delay module enables external signal delay lines
that may be connected to the GPIOs. But at the same time it copies the
GPIO forwarder functionality. Besides that the approach does not scale.
If we would have another external component, we would need yet another
driver. That's why I think, and seems others support me, better to
enable such a functionality inside GPIO aggregator driver.
Patch 1 is a cleanup that may be applied independently on the decision
about the rest.
Please, test and comment!
In v2:
- split as a series
- covered CONFIG_OF_GPIO=n case
- removed the gpio-delay
- moved gpio-delay Kconfig help to the comment in the code
Not in v2:
- updated DT description to note about long timeouts in atomic mode
- sysfs hiding for gpio-delay functionality
- used msleep(): the documentation is _against_ this
Andy Shevchenko (4):
gpio: aggregator: Remove CONFIG_OF and of_match_ptr() protections
gpio: aggregator: Support delay for setting up individual GPIOs
gpio: aggregator: Set up a parser of delay line parameters
gpio: delay: Remove duplicative functionality
drivers/gpio/Kconfig | 9 --
drivers/gpio/Makefile | 1 -
drivers/gpio/gpio-aggregator.c | 109 ++++++++++++++++++++--
drivers/gpio/gpio-delay.c | 164 ---------------------------------
4 files changed, 103 insertions(+), 180 deletions(-)
delete mode 100644 drivers/gpio/gpio-delay.c
--
2.40.0.1.gaa8946217a0b
next reply other threads:[~2023-06-14 23:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 23:14 Andy Shevchenko [this message]
2023-06-14 23:14 ` [PATCH v2 1/4] gpio: aggregator: Remove CONFIG_OF and of_match_ptr() protections Andy Shevchenko
2023-06-15 6:34 ` Linus Walleij
2023-06-15 7:28 ` Geert Uytterhoeven
2023-06-14 23:14 ` [PATCH v2 2/4] gpio: aggregator: Support delay for setting up individual GPIOs Andy Shevchenko
2023-06-15 6:35 ` Linus Walleij
2023-06-15 7:42 ` Geert Uytterhoeven
2023-06-14 23:14 ` [PATCH v2 3/4] gpio: aggregator: Set up a parser of delay line parameters Andy Shevchenko
2023-06-15 6:37 ` Linus Walleij
2023-06-15 8:52 ` Andy Shevchenko
2023-06-15 7:48 ` Geert Uytterhoeven
2023-06-15 9:07 ` Andy Shevchenko
2023-06-14 23:14 ` [PATCH v2 4/4] gpio: delay: Remove duplicative functionality Andy Shevchenko
2023-06-15 6:38 ` Linus Walleij
2023-06-15 7:49 ` Geert Uytterhoeven
2023-06-15 9:10 ` [PATCH v2 0/4] gpio: aggregator: Incorporate gpio-delay functionality Andy Shevchenko
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=20230614231446.3687-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=andy@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®