On Thu, Jan 29, 2015 at 11:44 AM, Mika Westerberg <mika.westerb...@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.b...@intel.com> > Signed-off-by: Mika Westerberg <mika.westerb...@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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
