On 8/29/2017 9:51 AM, Shawn Guo wrote:
On Tue, Aug 29, 2017 at 09:03:02AM +0800, Fenglin Wu wrote:
I agree the GPIO's ownership is configurable and it always configured at
the very beginning of the device boot up which is not visible by linux
kernel drivers/image. Normally, this configuration
On 8/29/2017 9:51 AM, Shawn Guo wrote:
On Tue, Aug 29, 2017 at 09:03:02AM +0800, Fenglin Wu wrote:
I agree the GPIO's ownership is configurable and it always configured at
the very beginning of the device boot up which is not visible by linux
kernel drivers/image. Normally, this configuration
On Tue, Aug 29, 2017 at 09:03:02AM +0800, Fenglin Wu wrote:
> I agree the GPIO's ownership is configurable and it always configured at
> the very beginning of the device boot up which is not visible by linux
> kernel drivers/image. Normally, this configuration is fixed in one
> platform and it's
On Tue, Aug 29, 2017 at 09:03:02AM +0800, Fenglin Wu wrote:
> I agree the GPIO's ownership is configurable and it always configured at
> the very beginning of the device boot up which is not visible by linux
> kernel drivers/image. Normally, this configuration is fixed in one
> platform and it's
On 8/28/2017 10:54 PM, Shawn Guo wrote:
On Wed, Jul 19, 2017 at 03:17:07PM +0800, fengl...@codeaurora.org wrote:
From: Fenglin Wu
Add support for qcom,gpios-disallowed property which is used to exclude
PMIC GPIOs not owned by the APSS processor from the pinctrl
On 8/28/2017 10:54 PM, Shawn Guo wrote:
On Wed, Jul 19, 2017 at 03:17:07PM +0800, fengl...@codeaurora.org wrote:
From: Fenglin Wu
Add support for qcom,gpios-disallowed property which is used to exclude
PMIC GPIOs not owned by the APSS processor from the pinctrl device.
If I understand it
On Wed, Jul 19, 2017 at 03:17:07PM +0800, fengl...@codeaurora.org wrote:
> From: Fenglin Wu
>
> Add support for qcom,gpios-disallowed property which is used to exclude
> PMIC GPIOs not owned by the APSS processor from the pinctrl device.
If I understand it correctly,
On Wed, Jul 19, 2017 at 03:17:07PM +0800, fengl...@codeaurora.org wrote:
> From: Fenglin Wu
>
> Add support for qcom,gpios-disallowed property which is used to exclude
> PMIC GPIOs not owned by the APSS processor from the pinctrl device.
If I understand it correctly, whether PMIC GPIOs is owned
On 7/25/2017 3:09 AM, Rob Herring wrote:
+ Definition: Array of the GPIO hardware numbers corresponding to GPIOs
+ which the APSS processor is not allowed to configure.
+ The hardware numbers are indexed from 1.
+ The interrupt
On 7/25/2017 3:09 AM, Rob Herring wrote:
+ Definition: Array of the GPIO hardware numbers corresponding to GPIOs
+ which the APSS processor is not allowed to configure.
+ The hardware numbers are indexed from 1.
+ The interrupt
On Wed, Jul 19, 2017 at 03:17:07PM +0800, fengl...@codeaurora.org wrote:
> From: Fenglin Wu
>
> Add support for qcom,gpios-disallowed property which is used to exclude
> PMIC GPIOs not owned by the APSS processor from the pinctrl device.
>
> Signed-off-by: Fenglin Wu
On Wed, Jul 19, 2017 at 03:17:07PM +0800, fengl...@codeaurora.org wrote:
> From: Fenglin Wu
>
> Add support for qcom,gpios-disallowed property which is used to exclude
> PMIC GPIOs not owned by the APSS processor from the pinctrl device.
>
> Signed-off-by: Fenglin Wu
> ---
>
From: Fenglin Wu
Add support for qcom,gpios-disallowed property which is used to exclude
PMIC GPIOs not owned by the APSS processor from the pinctrl device.
Signed-off-by: Fenglin Wu
---
.../devicetree/bindings/pinctrl/qcom,pmic-gpio.txt | 12
From: Fenglin Wu
Add support for qcom,gpios-disallowed property which is used to exclude
PMIC GPIOs not owned by the APSS processor from the pinctrl device.
Signed-off-by: Fenglin Wu
---
.../devicetree/bindings/pinctrl/qcom,pmic-gpio.txt | 12 ++
drivers/pinctrl/qcom/pinctrl-spmi-gpio.c
14 matches
Mail list logo