From: Jay Aurabind <jay.aurabind@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: GPIO controller driver pull up/down without pinctrl
Date: Fri, 11 Oct 2019 12:54:02 +0530 [thread overview]
Message-ID: <CAOsEZoitZmA848a4W2rkFZNjCWoN5aj291zcUi9P-+xMprCFRw@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdb7irxRVCB2htGhomnO-EpPSPRd9VqmHktwBo=+2Zx4tg@mail.gmail.com>
On Fri, 11 Oct 2019 at 12:39, Linus Walleij <linus.walleij@linaro.org> wrote:
>
> On Fri, Oct 11, 2019 at 8:26 AM Jay Aurabind <jay.aurabind@gmail.com> wrote:
>
> > Quoting "Documentation/devicetree/bindings/gpio/gpio.txt":
> >
> > Optional standard bitfield specifiers for the last cell:
> >
> > [snip]
> >
> > This setting only applies to hardware with a simple on/off
> > control for pull-up configuration. If the hardware has more
> > elaborate pull-up configuration, it should be represented
> > using a pin control binding.
> >
> > So if I do not want a separate pinctrl driver, how can I do the
> > necessary pull up/down setup in the gpio controller driver? I could
> > not find any drivers using the simple interface. Is this facility
> > available?
>
> See:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpio/gpio-pca953x.c
> Callbacks pca953x_gpio_set_config() and what it calls further from there.
>
Thank you very much for the quick response!
--
Thanks and Regards,
Jay
prev parent reply other threads:[~2019-10-11 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 6:26 GPIO controller driver pull up/down without pinctrl Jay Aurabind
2019-10-11 7:02 ` Linus Walleij
2019-10-11 7:24 ` Jay Aurabind [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=CAOsEZoitZmA848a4W2rkFZNjCWoN5aj291zcUi9P-+xMprCFRw@mail.gmail.com \
--to=jay.aurabind@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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 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).