From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Alexander Stein <linux@ew.tq-group.com>
Subject: Re: [rfc, rft, PATCH v1 1/1] gpio: aggregator: Introduce delay support for individual output pins
Date: Mon, 12 Jun 2023 20:34:39 +0300 [thread overview]
Message-ID: <ZIdXL2Net/5ttmXB@smile.fi.intel.com> (raw)
In-Reply-To: <CACRpkdbaf3UzW+x6emER5J5KJUQoJmdipwY_RQp0Ovj2N6RnsA@mail.gmail.com>
On Fri, Jun 09, 2023 at 09:50:37AM +0200, Linus Walleij wrote:
> On Thu, Jun 8, 2023 at 6:22 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
>
> > The aggregator mode can also handle properties of the platform, that
> > do not belong to the GPIO controller itself. One of such a property
> > is signal delay line. Intdoduce support of it.
> (...)
> > I don't like the idea of gpio-delay or similar. We have already GPIO
> > aggregator that incorporates the GPIO proxy / forwarder functionality.
>
> You are right. This is the right solution going forward IMO.
Thank you for the support.
Take into consideration 1 kinda neutral and 2 for votes, I'll going to split
and improve the patch (series).
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-06-12 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 16:21 [rfc, rft, PATCH v1 1/1] gpio: aggregator: Introduce delay support for individual output pins Andy Shevchenko
2023-06-08 19:32 ` kernel test robot
2023-06-08 19:43 ` kernel test robot
2023-06-09 6:40 ` Alexander Stein
2023-06-12 17:30 ` Andy Shevchenko
2023-06-09 7:11 ` Geert Uytterhoeven
2023-06-12 17:32 ` Andy Shevchenko
2023-06-09 7:50 ` Linus Walleij
2023-06-12 17:34 ` Andy Shevchenko [this message]
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=ZIdXL2Net/5ttmXB@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--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 \
--cc=linux@ew.tq-group.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.