linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:17:07 +0000	[thread overview]
Message-ID: <e54b421c-20f3-9f2e-c087-20ea6fefb2a7@linaro.org> (raw)
In-Reply-To: <Y21btYwNRMD4xXXL@smile.fi.intel.com>

> I'm not sure it will go to the v6/2-rc1 due to tough time range
> (we are almost at -rc5), I hope you are not in such hurry.

Thanks. That's fine.

On 10/11/2022 20:14, Andy Shevchenko wrote:
> On Thu, Nov 10, 2022 at 07:12:55PM +0000, Niyas Sait wrote:
>> This is a proposal for adding ACPI support to pin controller.
>>
>> The patch supports following resources introduced in ACPI from v6.2
>>
>> - PinFunction
>> - PinConfig
>> - PinGroupFunction
>> - PinGroupConfig
>> - PinGroup
>>
>> The patch has been tested on NXP I.MX8MP Plus platform with ACPI.
> 
> Thank you very much for this work!
> 
> I will take time to review it, presumably next week.
> 
> I'm not sure it will go to the v6/2-rc1 due to tough time range
> (we are almost at -rc5), I hope you are not in such hurry.
> 
>> Niyas Sait (3):
>>    pinctrl: add support for acpi PinGroup resource
>>    pinconf-generic: add pull up and pull down config with resistance
>>    pinctrl: add support for acpi pin function and config resources
>>
>>   drivers/pinctrl/Makefile                |   1 +
>>   drivers/pinctrl/core.c                  |  19 +-
>>   drivers/pinctrl/core.h                  |   3 +
>>   drivers/pinctrl/pinctrl-acpi.c          | 450 ++++++++++++++++++++++++
>>   drivers/pinctrl/pinctrl-acpi.h          |  50 +++
>>   include/linux/pinctrl/pinconf-generic.h |   6 +
>>   include/linux/pinctrl/pinctrl.h         |  15 +
>>   7 files changed, 540 insertions(+), 4 deletions(-)
>>   create mode 100644 drivers/pinctrl/pinctrl-acpi.c
>>   create mode 100644 drivers/pinctrl/pinctrl-acpi.h
>>
>> -- 
>> 2.25.1
>>
> 

      parent reply	other threads:[~2022-11-11  7:17 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
2022-11-11  7:17   ` Niyas Sait [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=e54b421c-20f3-9f2e-c087-20ea6fefb2a7@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).