From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Niyas Sait <niyas.sait@linaro.org>
Cc: linux-gpio@vger.kernel.org, mika.westerberg@linux.intel.com,
rafael@kernel.org, linus.walleij@linaro.org
Subject: Re: [PATCH RFC v2 0/3] pinctrl: add ACPI support to pin controller
Date: Wed, 16 Nov 2022 11:56:47 +0200 [thread overview]
Message-ID: <Y3Sz32+4uuynGeAy@smile.fi.intel.com> (raw)
In-Reply-To: <c9eb64c4-4cb3-b25c-df04-97da24a595fd@linaro.org>
On Wed, Nov 16, 2022 at 09:50:05AM +0000, Niyas Sait wrote:
> On 15/11/2022 18:47, Andy Shevchenko wrote:
> > On top of that, how other hardware can utilize what you are doing without
> > adding redundancy to the ACPI?
>
> Sorry I missed this question.
>
> I am not sure if there is any redundancy to ACPI spec.
>
> ACPI pin resources gives you most of the bits you need to describe the pin
> dependencies and configuration required for the device.
>
> For my particular implementation (not part of this proposal), I had to pass
> extra data to the driver to describe the GPIO number to Pin mapping and conf
> and mux registers. But that can be potentially fully handled in the driver.
> Sorry for the repetition.
The GPIO to pin mapping is done by GPIO ranges. This can be made up in the
driver or, IIRC, in DT (so in ACPI) by already registered properties).
Not sure, why you don't use them.
> Let me know if I missed your question :-)
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-11-16 9:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 17:54 [PATCH RFC v2 0/3] pinctrl: add ACPI support to pin controller Niyas Sait
2022-11-15 17:54 ` [PATCH RFC v2 1/3] pinctrl: add support for ACPI PinGroup resource Niyas Sait
2022-11-16 9:41 ` Mika Westerberg
2022-11-17 13:28 ` Niyas Sait
2022-11-17 15:08 ` Mika Westerberg
2022-11-15 17:54 ` [PATCH RFC v2 2/3] pinconf-generic: clarify pull up and pull down config values Niyas Sait
2022-11-17 9:30 ` Linus Walleij
2022-11-17 10:37 ` Andy Shevchenko
2022-11-17 10:39 ` Andy Shevchenko
2022-11-17 11:53 ` Niyas Sait
2022-11-17 12:36 ` Andy Shevchenko
2022-11-15 17:54 ` [PATCH RFC v2 3/3] pinctrl: add support for ACPI pin function and config resources Niyas Sait
2022-11-16 9:57 ` Mika Westerberg
2022-11-15 18:12 ` [PATCH RFC v2 0/3] pinctrl: add ACPI support to pin controller Andy Shevchenko
2022-11-15 18:29 ` Niyas Sait
2022-11-15 18:47 ` Andy Shevchenko
2022-11-15 19:15 ` Niyas Sait
2022-11-16 10:16 ` Andy Shevchenko
2022-11-16 10:27 ` Niyas Sait
2022-11-16 9:50 ` Niyas Sait
2022-11-16 9:56 ` Andy Shevchenko [this message]
2022-11-16 10:40 ` Niyas Sait
2022-11-16 13:27 ` Andy Shevchenko
2022-11-16 13:38 ` Andy Shevchenko
2022-11-16 10:17 ` 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=Y3Sz32+4uuynGeAy@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=niyas.sait@linaro.org \
--cc=rafael@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;
as well as URLs for NNTP newsgroup(s).