[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbK6bmYQbUcwxBRoq6L3YJ9yq5fQuF7zEbrStbiCrYEQQ@mail.gmail.com>
Date: Thu, 20 Oct 2011 15:44:16 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Shawn Guo <shawn.guo@...escale.com>
Cc: Stephen Warren <swarren@...dia.com>,
Linus Walleij <linus.walleij@...ricsson.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Barry Song <21cnbao@...il.com>,
Linaro Dev <linaro-dev@...ts.linaro.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
David Brown <davidb@...eaurora.org>,
Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [PATCH 2/2] pinctrl: add a generic control interface
On Thu, Oct 20, 2011 at 4:45 AM, Shawn Guo <shawn.guo@...escale.com> wrote:
> We should not require device driver to call these APIs directly. There
> are so many pinctrl subsystem internal details left to its users.
As explained I already have drivers that need to do this. OK they
are out-of-tree, but they do exist.
For U5500 we have a SIM card driver which sets pull down resistance
and load capacitance in response to information retrieved from the
card at runtime. This is not static or internal to pinctrl at all. How should
I solve this if pin configuration is not exposed?
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists