From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Olof Johansson <olof@lixom.net>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Ning Li <ning.li@intel.com>, Alan Cox <alan@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support
Date: Thu, 6 Nov 2014 08:07:13 +0200 [thread overview]
Message-ID: <20141106060713.GB1618@lahna.fi.intel.com> (raw)
In-Reply-To: <CAOesGMheJzkQ9jEmDx9+hpjk0Scbnv_JiK1yH+7eoxY4PYUS4A@mail.gmail.com>
On Wed, Nov 05, 2014 at 01:44:24PM -0800, Olof Johansson wrote:
> Pinctrl setup has traditionally always been done by firmware on x86,
> and some ARM platforms are again moving back to that state (since
> reconfiguring pinctrl in the kernel is in some cases not safe).
>
> What's the purpose of exposing this to the kernel on x86 now? I can
> see the need to expose GPIO, but not pinctrl? Having the pin control
> hidden away in firmware has been one of the benefits on x86, and
> you're now undoing it... :)
Well, the hardware is actually a pin controller so it can configure pins
in different way.
In addition to that we still do expect that the pins are configured by
the BIOS for the time being. The advantage of having pinctrl driver is
more like fixing things that the BIOS got wrong (like for example SPI
pins that were muxed as GPIOs), not to reconfigure everything.
Plus it has really nice debugfs interface :-)
prev parent reply other threads:[~2014-11-06 6:07 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 11:01 [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support Mika Westerberg
2014-11-03 11:01 ` [PATCH v2 1/2] gpio / ACPI: Add knowledge about pin controllers to acpi_get_gpiod() Mika Westerberg
2014-11-04 10:18 ` Linus Walleij
2014-11-03 11:01 ` [PATCH v2 2/2] pinctrl: Add Intel Cherryview/Braswell pin controller support Mika Westerberg
2014-11-04 10:23 ` Linus Walleij
2014-11-03 23:24 ` [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support Timur Tabi
2014-11-04 8:20 ` Mika Westerberg
2014-11-04 9:39 ` Mika Westerberg
2014-11-04 13:31 ` Rafael J. Wysocki
2014-11-04 13:48 ` Linus Walleij
2014-11-04 14:16 ` Rafael J. Wysocki
2014-11-04 14:12 ` Mika Westerberg
2014-11-04 16:37 ` Timur Tabi
2014-11-04 21:51 ` Timur Tabi
2014-11-04 22:47 ` Rafael J. Wysocki
2014-11-04 22:32 ` Timur Tabi
2014-11-04 22:39 ` Timur Tabi
2014-11-04 23:13 ` Rafael J. Wysocki
2014-11-04 22:56 ` Timur Tabi
2014-11-04 23:18 ` Timur Tabi
2014-11-05 21:04 ` Rafael J. Wysocki
2014-11-05 21:19 ` Rafael J. Wysocki
2014-11-04 23:00 ` Rafael J. Wysocki
2014-11-04 17:54 ` Timur Tabi
2014-11-04 19:04 ` Mika Westerberg
2014-11-06 19:30 ` Linus Walleij
2014-11-05 21:46 ` Grant Likely
2014-11-05 21:59 ` Timur Tabi
2014-11-05 22:15 ` Rafael J. Wysocki
2014-11-06 17:37 ` Grant Likely
2014-11-06 18:01 ` Timur Tabi
2014-11-07 23:12 ` Timur Tabi
2014-11-06 19:28 ` Linus Walleij
2014-11-05 21:44 ` Olof Johansson
2014-11-06 6:07 ` Mika Westerberg [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=20141106060713.GB1618@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=gnurou@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=ning.li@intel.com \
--cc=olof@lixom.net \
--cc=rjw@rjwysocki.net \
/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).