All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCH v1 2/3] drivers: pinctrl-single: add support to parse gpio properties
Date: Wed, 29 Apr 2020 12:04:38 -0600	[thread overview]
Message-ID: <CAPnjgZ35z3wF68y+pJKMOOE2=y=8vEm-_2LzDrs_YGCaYLLBrA@mail.gmail.com> (raw)
In-Reply-To: <20200429163446.15390-3-rayagonda.kokatanur@broadcom.com>

Hi Rayagonda,

+Stephen Warren

On Wed, 29 Apr 2020 at 10:35, Rayagonda Kokatanur
<rayagonda.kokatanur@broadcom.com> wrote:
>
> Parse different gpio properties from dt as part of probe
> function. This detail will be used to enable pinctrl pad
> later when gpio lines are requested.
>
> Signed-off-by: Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>
> ---
>  drivers/pinctrl/pinctrl-single.c | 62 +++++++++++++++++++++++++++++++-
>  1 file changed, 61 insertions(+), 1 deletion(-)

Can you please add the binding and a test? Also I think this feature
should be behind a Kconfig flag to avoid code-size increase.

Regards,
Simon

  reply	other threads:[~2020-04-29 18:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29 16:34 [PATCH v1 0/3] extend pinctrl-single driver with APIs Rayagonda Kokatanur
2020-04-29 16:34 ` [PATCH v1 1/3] drivers: pinctrl-single: handle different register width Rayagonda Kokatanur
2020-04-29 18:04   ` Simon Glass
2020-04-30 10:06     ` Rayagonda Kokatanur
2020-05-08  1:36       ` Simon Glass
2020-05-24 10:46         ` Rayagonda Kokatanur
2020-05-25  2:15           ` Simon Glass
2020-05-26 18:57             ` Rayagonda Kokatanur
2020-04-29 16:34 ` [PATCH v1 2/3] drivers: pinctrl-single: add support to parse gpio properties Rayagonda Kokatanur
2020-04-29 18:04   ` Simon Glass [this message]
2020-04-30 11:10     ` Rayagonda Kokatanur
2020-05-08  1:36       ` Simon Glass
2020-04-29 16:34 ` [PATCH v1 3/3] drivers: pinctrl-single: add request api Rayagonda Kokatanur
2020-04-29 18:04   ` Simon Glass
2020-04-30 11:03     ` Rayagonda Kokatanur
2020-05-08  1:36       ` Simon Glass

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='CAPnjgZ35z3wF68y+pJKMOOE2=y=8vEm-_2LzDrs_YGCaYLLBrA@mail.gmail.com' \
    --to=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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.