Messages in this thread | | | Date | Thu, 06 Nov 2014 12:01:15 -0600 | From | Timur Tabi <> | Subject | Re: [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support |
| |
On 11/06/2014 11:37 AM, Grant Likely wrote: > 2) Where direct control over the pinctrl hardware is required by the > OS, build it into the GPIO driver functionality (which from what I > understand is exactly what Mika has done).
So you're saying that if the GPIO driver is asked to read/write data to GPIO #35, then the driver should first make sure that the pin #35 is configured for GPIO? What if that pin is configured for I2C instead, and now some random driver, is asking to read from GPIO #35, has now broken I2C?
-- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
| |