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,
fugang.duan@linaro.org
Subject: Re: [PATCH v3 1/2] pinctrl: add support for ACPI pin function and config resources
Date: Wed, 30 Nov 2022 21:36:19 +0000 [thread overview]
Message-ID: <50f04f83-93e5-3516-3e6a-a09bd995ec8d@linaro.org> (raw)
In-Reply-To: <Y4fGx3yWnbejOsVy@smile.fi.intel.com>
On 30/11/2022 21:10, Andy Shevchenko wrote:
> ...
>
>> struct list_head dt_maps;
>> + struct list_head acpi_maps;
> Why these can't be unified?
>
> From the pin control point of view the data it needs should be ~equal
> independently on the resource provider (ACPI, DT, etc.).
Yes I think they can be unified and some DT specific functions can be
generalized as well. It is going to be a slightly bigger change and will
touch most of drivers. I will add changes to next revision.
--
Niyas
next prev parent reply other threads:[~2022-11-30 21:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 16:40 [PATCH v3 0/2] pinctrl: add ACPI support to pin controller Niyas Sait
2022-11-30 16:40 ` [PATCH v3 1/2] pinctrl: add support for ACPI pin function and config resources Niyas Sait
2022-11-30 21:02 ` Andy Shevchenko
2022-11-30 21:33 ` Niyas Sait
2022-11-30 23:30 ` Andy Shevchenko
2022-12-01 9:27 ` Niyas Sait
2022-12-01 23:04 ` Andy Shevchenko
2022-12-05 7:20 ` Niyas Sait
2022-12-05 12:47 ` Andy Shevchenko
2022-12-20 10:53 ` Niyas Sait
2023-01-03 16:49 ` Niyas Sait
2023-01-09 14:09 ` Andy Shevchenko
2023-01-09 21:33 ` Niyas Sait
2022-11-30 21:10 ` Andy Shevchenko
2022-11-30 21:36 ` Niyas Sait [this message]
2022-11-30 16:40 ` [PATCH v3 2/2] pinctrl: add support for ACPI pin groups 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=50f04f83-93e5-3516-3e6a-a09bd995ec8d@linaro.org \
--to=niyas.sait@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fugang.duan@linaro.org \
--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).