From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>,
"Grant Likely" <grant.likely@secretlab.ca>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Linus Walleij" <linus.walleij@stericsson.com>,
"Denis Turischev" <denis@compulab.co.il>
Subject: Re: [PATCH] gpio: add support for ITE IT87xx Super I/O GPIO.
Date: Mon, 19 Mar 2012 09:39:50 -0700 [thread overview]
Message-ID: <1332175190.32717.151.camel@groeck-laptop> (raw)
In-Reply-To: <CACRpkdYTPc9b0ys-rMJ6VJSxVX9uubq6r1QFk4bQN5rMiqQPMQ@mail.gmail.com>
On Mon, 2012-03-19 at 10:05 -0400, Linus Walleij wrote:
> On Mon, Mar 19, 2012 at 2:56 PM, Guenter Roeck
> <guenter.roeck@ericsson.com> wrote:
> > On Mon, Mar 19, 2012 at 04:26:44AM -0400, Linus Walleij wrote:
>
> >> OK that is pinmuxing, if that is to be software-controlled the place to do
> >> it is in drivers/pinctrl. (Documentation/pinctrl.txt gives the backrgound.)
> (...)
> >>
> > Personally I would not dare touch those pins. If a pin is configured as UART pin
> > (or whatever), it is quite unlikely that it is exposed as GPIO pin. Worst case,
> > changing the configuration may result in broken hardware. Not sure what is supposed
> > to be gained by enabling the user to do that.
>
> Define "user", pinctrl does not have userspace interfaces if that's
> what you mean.
>
> If you mean "kernel programmer", these creatures seem to not respect what
> they should and shouldn't poke at ;-)
>
> The usecase is typically if the hardware is used in two different systems
> where the ROM/bootcode/etc does not set up muxing correctly, or are setup
> in a sub-optimal way (e.g. working but consuming too much power) and the
> kernel needs to get involved. Unless you have any scenario like that, no
> need to worry about it.
>
Ok, guess that makes sense.
Thanks,
Guenter
next prev parent reply other threads:[~2012-03-19 16:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 19:48 Diego Elio Pettenò
2012-03-17 3:01 ` Guenter Roeck
[not found] ` <20120317123151.AAF9A3E0952@localhost>
2012-03-17 18:53 ` Diego Elio Pettenò
2012-03-18 16:07 ` Guenter Roeck
2012-03-19 15:51 ` Diego Elio Pettenò
2012-03-18 23:14 ` Linus Walleij
2012-03-19 0:54 ` Guenter Roeck
2012-03-19 8:26 ` Linus Walleij
2012-03-19 13:56 ` Guenter Roeck
2012-03-19 14:05 ` Linus Walleij
2012-03-19 16:39 ` Guenter Roeck [this message]
2012-03-19 16:01 ` Diego Elio Pettenò
2012-03-19 16:43 ` Guenter Roeck
2012-03-19 16:54 ` Diego Elio Pettenò
2012-03-19 17:22 ` Guenter Roeck
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=1332175190.32717.151.camel@groeck-laptop \
--to=guenter.roeck@ericsson.com \
--cc=denis@compulab.co.il \
--cc=flameeyes@flameeyes.eu \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®