[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZS9OVv8osoc5E1KOcqfFnvECnKJzM1kXZ9qNKQMZgB=w@mail.gmail.com>
Date: Thu, 19 Jan 2012 17:58:46 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Thomas Abraham <thomas.abraham@...aro.org>
Cc: Linus Walleij <linus.walleij@...ricsson.com>,
linux-kernel@...r.kernel.org, Stephen Warren <swarren@...dia.com>,
Grant Likely <grant.likely@...retlab.ca>,
Barry Song <21cnbao@...il.com>,
Shawn Guo <shawn.guo@...escale.com>,
Dong Aisheng <dong.aisheng@...aro.org>,
Rajendra Nayak <rajendra.nayak@...aro.org>,
Haojian Zhuang <haojian.zhuang@...vell.com>
Subject: Re: [PATCH v6] pinctrl: add a pin config interface
On Wed, Jan 18, 2012 at 8:16 AM, Thomas Abraham
<thomas.abraham@...aro.org> wrote:
> In case of runtime pinmuxing, the pin configuration would also be
> required to be setup in some cases. pin_config_set() is suitable to be
> called from the platform code. In case of runtime pinmuxing in driver
> code, is there any way to set the pin config also at runtime in driver
> code?
Yes that is already possible today with the pin_config_set() and
pin_config_group_set() calls already merged for 3.3.
However there is no relation between the struct device and these
config settings so I feel that this is a bit hack-ish, but it was
atleast something we could agree upon.
Thanks,
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