[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131120125121.GB2674@sirena.org.uk>
Date: Wed, 20 Nov 2013 12:51:21 +0000
From: Mark Brown <broonie@...nel.org>
To: Stephen Warren <swarren@...dotorg.org>
Cc: Kyungmin Park <kmpark@...radead.org>,
Doug Anderson <dianders@...omium.org>,
devicetree@...r.kernel.org,
linux-samsung-soc <linux-samsung-soc@...r.kernel.org>,
Heiko Stübner <heiko@...ech.de>,
Tomasz Figa <t.figa@...sung.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Kukjin Kim <kgene.kim@...sung.com>,
Thomas Abraham <thomas.abraham@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: [PATCH] pinctrl: samsung: Allow pin value to be initialized
using pinfunc.
On Tue, Nov 19, 2013 at 05:07:04PM -0700, Stephen Warren wrote:
> On 11/19/2013 05:02 PM, Kyungmin Park wrote:
> > Some pins are not connected (NC). At that cases, there's no drivers to
> > handle it. To reduce power leakage, it sets proper configuration with
> > values instead of reset values.
> Hmm. Shouldn't board firmware configure that kind of thing?
> (Of course, some firmware is starting to use DT to configure itself, so
> that just shifts the DT discussion, but anyway).
Even if it's not sometimes the firmware is intended to be thin with
configuration punted to the OS.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists