From: Niyas Sait <niyas.sait@linaro.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-gpio@vger.kernel.org, mika.westerberg@linux.intel.com,
rafael@kernel.org, linus.walleij@linaro.org
Subject: Re: [PATCH RFC 0/3] pinctrl: add ACPI support to pin controller
Date: Fri, 11 Nov 2022 07:15:46 +0000 [thread overview]
Message-ID: <b3f26f6b-757d-a3b0-fb54-ea54f3588fc0@linaro.org> (raw)
In-Reply-To: <Y21dtJySQX29VDIh@smile.fi.intel.com>
> Meanwhile, can we see the DSDT excerpt(s) that shows how you use these
> resources there?
I've used the following prototype for I.MX8MP
https://gitlab.com/nsait-linaro/acpi-patches/-/blob/master/0001-add-acpi-pinctrl-support-for-i2c-controllers.patch
> Also note, we need some clarification to be done in the ACPI specification
> regarding the numbering schema, used in those resources. TL;DR: for Gpio*()
> the number space is GPIO, for Pin*() is pin control (real pin numbering,
> since not all of them can be GPIOs and GPIO can have its own additional
> layer of numbering mapping).
Yes that would be helpful!
I've done some prototyping and have used the _DSD to pass the GPIO to
Pin mapping to the GPIO controller. See following patches
https://gitlab.com/nsait-linaro/acpi-patches/-/blob/master/0001-add-GPIO-controllers-to-ACPI-table.patch#L89
https://gitlab.com/nsait-linaro/acpi-patches/-/blob/master/0001-add-acpi-gpio-controller-support-to-IMX-platform.patch
next prev parent reply other threads:[~2022-11-11 7:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 19:12 [PATCH RFC 0/3] pinctrl: add ACPI support to pin controller Niyas Sait
2022-11-10 19:12 ` [PATCH RFC 1/3] pinctrl: add support for acpi PinGroup resource Niyas Sait
2022-11-11 12:12 ` Mika Westerberg
2022-11-15 18:10 ` Niyas Sait
2022-11-10 19:12 ` [PATCH RFC 2/3] pinconf-generic: add pull up and pull down config with resistance Niyas Sait
2022-11-10 20:17 ` Andy Shevchenko
2022-11-11 7:23 ` Niyas Sait
2022-11-11 9:17 ` Linus Walleij
2022-11-11 9:22 ` Niyas Sait
2022-11-10 19:12 ` [PATCH RFC 3/3] pinctrl: add support for acpi pin function and config resources Niyas Sait
2022-11-11 12:24 ` Mika Westerberg
2022-11-15 18:14 ` Niyas Sait
2022-11-10 20:14 ` [PATCH RFC 0/3] pinctrl: add ACPI support to pin controller Andy Shevchenko
2022-11-10 20:23 ` Andy Shevchenko
2022-11-11 7:15 ` Niyas Sait [this message]
2022-11-11 7:17 ` Niyas Sait
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=b3f26f6b-757d-a3b0-fb54-ea54f3588fc0@linaro.org \
--to=niyas.sait@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--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).