From: Rob Herring <robh@kernel.org>
To: Saravana Kannan <saravanak@google.com>
Cc: kernel-team@android.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Frank Rowand <frowand.list@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 2/2] of: property: Add device link support for pinctrl-0 through pinctrl-8
Date: Mon, 27 Jul 2020 15:07:34 -0600 [thread overview]
Message-ID: <20200727210734.GA873757@bogus> (raw)
In-Reply-To: <20200724234415.1651639-2-saravanak@google.com>
On Fri, 24 Jul 2020 16:44:15 -0700, Saravana Kannan wrote:
> Add support for pinctrl-0 through pinctrl-8 explicitly instead of trying
> to add support for pinctrl-%d properties.
>
> Of all the pinctrl-* properties in dts files (20322), only 47% (9531)
> are pinctrl-%d properties. Of all the pinctrl-%d properties, 99.5%
> (9486) are made up of pinctrl-[0-2]. 'pinctrl-8' is the current maximum
> found in dts files.
>
> Trying to parse all pinctrl-* properties and checking for pinctrl-%d is
> unnecessarily complicated. So, just add support for pinctrl-[0-8] for
> now. In the unlikely event we ever exceed pinctrl-8, we can come back
> and improve this.
>
> Signed-off-by: Saravana Kannan <saravanak@google.com>
> ---
> v1->v2:
> - Clarified in commit text that pinctrl-8 is the max found in the dts
> files.
>
> drivers/of/property.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
Applied, thanks!
next prev parent reply other threads:[~2020-07-27 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 23:44 [PATCH v2 1/2] of: property: Add device link support for multiple DT bindings Saravana Kannan
2020-07-24 23:44 ` [PATCH v2 2/2] of: property: Add device link support for pinctrl-0 through pinctrl-8 Saravana Kannan
2020-07-27 21:07 ` Rob Herring [this message]
2020-07-27 21:06 ` [PATCH v2 1/2] of: property: Add device link support for multiple DT bindings Rob Herring
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=20200727210734.GA873757@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.