Messages in this thread | | | Date | Mon, 10 Oct 2011 14:27:37 +0200 | Subject | Re: [PATCH 1/2] drivers: create a pin control subsystem v9 | From | Linus Walleij <> |
| |
On Mon, Oct 10, 2011 at 2:30 PM, Shawn Guo <shawn.guo@freescale.com> wrote:
>> +The example 8x8 PGA package above will have pin numbers 0 thru 63 assigned to >> +its physical pins. It will name the pins { A1, A2, A3 ... H6, H7, H8 } using >> +pinctrl_register_pins_[sparse|dense]() and a suitable data set as shown > > It should just be pinctrl_register_pins()?
Yep, fixed it.
>> +System pinmux hogging >> +===================== >> + >> +A system pinmux map entry, i.e. a pinmux setting that does not have a device >> +associated with it, can be hogged by the core when the pin controller is >> +registered. This means that the core will attempt to call regulator_get() and >> +regulator_enable() on it immediately after the pin control device has been >> +registered. > > s/regulator_get/pinmux_get, and s/regulator_enable/pinmux_enable
Fixed this too, sorry for being so hung up on the regulator subsystem, must be that I really like it...
Thanks, Linus Walleij
| |