Re: pinctrl_config APIs, and other pinmux questions

2011-10-20 Thread Linus Walleij
On Tue, Oct 18, 2011 at 8:02 PM, Stephen Warren wrote: > [Me] >> 1) The need to configure per-pin "stuff" like biasing, driving, >>   load capacitance ... whatever I sent of a proposal for this so we get somewhere... >> 2) The need to handle state transitions of pinmux settings. Still uncertain

Re: pinctrl_config APIs, and other pinmux questions

2011-10-18 Thread Shawn Guo
On Mon, Oct 17, 2011 at 08:51:11AM -0700, Stephen Warren wrote: > Shawn Guo wrote at Friday, October 14, 2011 9:12 PM: > > On Fri, Oct 14, 2011 at 08:53:33AM -0700, Stephen Warren wrote: > ... > > > Having the driver expose a list of all possible combinations of pin > > > configurations seems impra

RE: pinctrl_config APIs, and other pinmux questions

2011-10-18 Thread Stephen Warren
Linus Walleij wrote at Monday, October 17, 2011 9:03 AM: > Thanks for a long letter, took som time to read, but as usual it > contains good stuff! > > I think you're talking about two things here: > > 1) The need to configure per-pin "stuff" like biasing, driving, > load capacitance ... whateve

RE: pinctrl_config APIs, and other pinmux questions

2011-10-17 Thread Stephen Warren
Shawn Guo wrote at Friday, October 14, 2011 9:12 PM: > On Fri, Oct 14, 2011 at 08:53:33AM -0700, Stephen Warren wrote: ... > > Having the driver expose a list of all possible combinations of pin > > configurations seems impractical, for the same reason as I objected to > > the original proposal for

Re: pinctrl_config APIs, and other pinmux questions

2011-10-17 Thread Linus Walleij
On Fri, Oct 14, 2011 at 4:59 PM, Shawn Guo wrote: > [Stephen] >> I've started to look at porting the Tegra pinmux driver to your pinctrl >> subsystem. In order to replace the existing pinmux driver, I need a way >> to support configuring options such as tri-state, pull-up/down, drive- >> strength,

Re: pinctrl_config APIs, and other pinmux questions

2011-10-17 Thread Linus Walleij
Thanks for a long letter, took som time to read, but as usual it contains good stuff! I think you're talking about two things here: 1) The need to configure per-pin "stuff" like biasing, driving, load capacitance ... whatever 2) The need to handle state transitions of pinmux settings. I prefe

Re: pinctrl_config APIs, and other pinmux questions

2011-10-14 Thread Shawn Guo
On Fri, Oct 14, 2011 at 08:53:33AM -0700, Stephen Warren wrote: > Shawn Guo wrote at Friday, October 14, 2011 8:59 AM: > > It might be a good place for me to catch up the pinctrl subsystem > > discussion, as far as imx migration concerned. > > > > I have not read the backlog of all the previous di

RE: pinctrl_config APIs, and other pinmux questions

2011-10-14 Thread Stephen Warren
Shawn Guo wrote at Friday, October 14, 2011 8:59 AM: > It might be a good place for me to catch up the pinctrl subsystem > discussion, as far as imx migration concerned. > > I have not read the backlog of all the previous discussion, so please > excuse me if something I put here have been discusse

Re: pinctrl_config APIs, and other pinmux questions

2011-10-14 Thread Shawn Guo
It might be a good place for me to catch up the pinctrl subsystem discussion, as far as imx migration concerned. I have not read the backlog of all the previous discussion, so please excuse me if something I put here have been discussed. On Thu, Oct 13, 2011 at 01:59:55PM -0700, Stephen Warren wr