Messages in this thread | | | Date | Wed, 4 Feb 2015 10:01:49 +0100 | Subject | Re: [PATCH] pinctrl: cherryview: Configure HiZ pins to be input when requested as GPIOs | From | Linus Walleij <> |
| |
On Thu, Jan 29, 2015 at 11:44 AM, Mika Westerberg <mika.westerberg@linux.intel.com> wrote:
> If the pin is in HiZ mode when it is requested as GPIO its value cannot be > read (it always returns 0). In order to cope with the Linux GPIO subsystem > where we do not have such state at all, turn the pin to be input instead. > > Reported-by: Jerome Blin <jerome.blin@intel.com> > Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Patch applied.
Since putting a pin into GPIO mode start poking around in essentially pin control registers, we may need to revisit the issue of the pin control subsystem not denying simultaneous use of a pin for a device muxing and GPIO. Maybe the "strict" setting forcing a pin to be either one or the other on a per-driver basis would enforce a better policy on this driver (and some others).
Yours, Linus Walleij
| |