linux-kernel - [PATCH V1 0/2] *** Update is_enabled flag to be consistent ***

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20171013061550.996-1-fenglinw@codeaurora.org>
Date:   Fri, 13 Oct 2017 14:15:02 +0800
From:   fenglinw@...eaurora.org
To:     linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:     collinsd@...eaurora.org, aghayal@...eaurora.org,
        wruan@...eaurora.org, subbaram@...eaurora.org,
        kgunda@...eaurora.org, Fenglin Wu <fenglinw@...eaurora.org>
Subject: [PATCH V1 0/2] *** Update is_enabled flag to be consistent ***

From: Fenglin Wu <fenglinw@...eaurora.org>

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.