[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vc9Ra4_rRhtScDrNqV0SJPNf-MDF_yksbKoYnTDuYeAxg@mail.gmail.com>
Date: Thu, 15 Jun 2023 11:52:03 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
Alexander Stein <alexander.stein@...tq-group.com>,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
Bartosz Golaszewski <brgl@...ev.pl>,
Andy Shevchenko <andy@...nel.org>,
Geert Uytterhoeven <geert+renesas@...der.be>
Subject: Re: [PATCH v2 3/4] gpio: aggregator: Set up a parser of delay line parameters
On Thu, Jun 15, 2023 at 9:37 AM Linus Walleij <linus.walleij@...aro.org> wrote:
> On Thu, Jun 15, 2023 at 1:14 AM Andy Shevchenko
> <andriy.shevchenko@...ux.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 a signal delay line. Set up a parser to support it.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
>
> I guess this is one of those instances where we actually need some OF-specific
> code for parsing the special case, and other HW descriptions will need
> other special code. It's fine for non-trivial stuff I think.
Actually if you look into IIO, the xlate there is fwnode specific
nowadays and theoretically the specifics of OF can be parsed in ACPI
as well. I would like to get rid of OF_GPIO completely, but let's
see...
> Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
Thank you!
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists