From mboxrd@z Thu Jan 1 00:00:00 1970 From: fenglinw@codeaurora.org Subject: [PATCH V1 0/2] *** Update is_enabled flag to be consistent *** Date: Fri, 13 Oct 2017 14:15:02 +0800 Message-ID: <20171013061550.996-1-fenglinw@codeaurora.org> Return-path: Received: from smtp.codeaurora.org ([198.145.29.96]:42864 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751901AbdJMGQV (ORCPT ); Fri, 13 Oct 2017 02:16:21 -0400 Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org Cc: collinsd@codeaurora.org, aghayal@codeaurora.org, wruan@codeaurora.org, subbaram@codeaurora.org, kgunda@codeaurora.org, Fenglin Wu From: Fenglin Wu Currently, is_enabled flag is always set to true in pmic_gpio_populate() regardless of the hardware real time status. This is not correct and it gives the wrong information for the GPIOs which are disabled initially in hardware. Add two patches to fix this: One is set the is_enabled flag via reading the REG_EN_CTL register then its value can reflect the corrent initial hardware enable state; Another is set is_enable flag in pmic_gpio_set_mux() so that any disabled GPIO could be enabled right after setting pinmux. Fenglin Wu (2): pinctrl: qcom: spmi-gpio: Read REG_EN_CTL to get initial enable state pinctrl: qcom: spmi-gpio: Set is_enabled flag in set_mux() drivers/pinctrl/qcom/pinctrl-spmi-gpio.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) -- Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.