From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] gpio: add pin biasing and drive mode to gpiolib
Date: Wed, 20 Apr 2011 17:17:55 +0200 [thread overview]
Message-ID: <BANLkTinv_-6dJJXAWc=NFTceXGA9sabanA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=Oc+y+31KugbEy66Mp96=bf_G8Mg@mail.gmail.com>
2011/4/20 Haojian Zhuang <haojian.zhuang@gmail.com>:
> I have an another question on board initialization. The configuration on pins
> are including drive strength, pull and multiple function.
>
> Since this patch can configure drive strength, pull. Will it be preferred to use
> in board initialization?
I am reusing it (inside the example driver) for drive strength and bias.
Multiple function again is pin/padmuxing.
Even if some people are only muxing pins that can also be used as GPIO,
this is not always the case. We can shunt out the same pins to be used as
I2C or SPI for example, that means this cannot be handled in a GPIO
driver since it has nothing to do with GPIO pins at all.
Thus we need an orthogonal pin/padmux mechanism.
Yours,
Linus Walleij
next prev parent reply other threads:[~2011-04-20 15:17 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 21:37 [PATCH 1/2] gpio: add pin biasing and drive mode to gpiolib Linus Walleij
2011-04-17 21:48 ` Alan Cox
2011-04-17 21:58 ` Linus Walleij
2011-04-17 22:03 ` Alan Cox
2011-04-18 0:09 ` Kyungmin Park
2011-04-18 7:17 ` Kurt Van Dijck
2011-04-18 8:04 ` Ben Nizette
2011-04-18 8:19 ` Alan Cox
2011-04-18 8:50 ` Ben Nizette
2011-04-18 11:59 ` Mark Brown
2011-04-18 22:16 ` Ben Nizette
2011-04-18 22:31 ` Mark Brown
2011-04-19 4:50 ` Ben Nizette
2011-04-20 12:11 ` Linus Walleij
2011-04-18 12:26 ` Alan Cox
2011-04-18 22:26 ` Ben Nizette
2011-04-19 8:38 ` Alan Cox
2011-04-19 8:51 ` Kyungmin Park
2011-04-20 12:32 ` Linus Walleij
2011-04-20 12:38 ` Kyungmin Park
2011-04-20 14:54 ` Alan Cox
2011-04-20 14:26 ` Haojian Zhuang
2011-04-20 14:40 ` Kyungmin Park
2011-04-20 15:04 ` Haojian Zhuang
2011-04-20 15:17 ` Linus Walleij [this message]
2011-04-20 15:32 ` Alan Cox
2011-04-20 15:45 ` Linus Walleij
2011-04-27 21:55 ` Russell King - ARM Linux
2011-04-27 22:16 ` H Hartley Sweeten
2011-04-20 15:13 ` Linus Walleij
2011-04-20 15:29 ` Alan Cox
2011-04-20 15:39 ` Linus Walleij
2011-04-20 15:43 ` Alan Cox
2011-04-27 21:58 ` Russell King - ARM Linux
2011-04-20 0:09 ` Ben Nizette
2011-04-20 9:45 ` Alan Cox
2011-04-20 12:38 ` Linus Walleij
2011-04-20 14:55 ` Alan Cox
2011-04-20 12:21 ` Linus Walleij
2011-04-20 23:32 ` Ben Nizette
2011-04-21 6:48 ` Linus Walleij
2011-04-23 8:25 ` Ben Nizette
2011-04-21 0:29 ` Ben Nizette
2011-04-20 12:19 ` Linus Walleij
2011-04-20 12:22 ` Alan Cox
2011-04-20 12:04 ` Linus Walleij
2011-04-20 23:24 ` Ben Nizette
2011-04-21 15:39 ` Stijn Devriendt
2011-04-22 11:36 ` Linus Walleij
2011-04-22 11:56 ` Alan Cox
2011-04-23 8:35 ` Ben Nizette
2011-04-25 18:52 ` Rohit Vaswani
2011-04-26 7:48 ` Linus Walleij
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='BANLkTinv_-6dJJXAWc=NFTceXGA9sabanA@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).