linux-kernel - [PATCH 0/2] pinctrl: qcom: glymur: Fix gpio pin functions and clean-up match table

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20250919-pinctrl-qcom-glymur-fixes-v1-0-426ea410aa94@linaro.org>
Date: Fri, 19 Sep 2025 15:17:10 +0300
From: Abel Vesa <abel.vesa@...aro.org>
To: Bjorn Andersson <andersson@...nel.org>, 
 Linus Walleij <linus.walleij@...aro.org>, 
 Pankaj Patil <pankaj.patil@....qualcomm.com>, 
 Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Cc: linux-arm-msm@...r.kernel.org, linux-gpio@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Abel Vesa <abel.vesa@...aro.org>
Subject: [PATCH 0/2] pinctrl: qcom: glymur: Fix gpio pin functions and
 clean-up match table

This glymur pinctrl driver is not currently being used by any platforms
upstream, but once the entire platform support will be merged, there
will be some issues with the gpios as they will be wrongly requested by
the pin muxing config in DT, if the gpio pin function is not marked via
the generic macro as GPIO category function. Fix this issue now by
marking the gpio function properly.

While at it, drop the useless compatible specific match data from the
table.

Signed-off-by: Abel Vesa <abel.vesa@...aro.org>
---
Abel Vesa (2):
      pinctrl: qcom: glymur: Drop unnecessary platform data from match table
      pinctrl: qcom: glymur: Fix the gpio and egpio pin functions

 drivers/pinctrl/qcom/pinctrl-glymur.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
---
base-commit: 8f7f8b1b3f4c613dd886f53f768f82816b41eaa3
change-id: 20250919-pinctrl-qcom-glymur-fixes-7ea30c8202f1

Best regards,
-- 
Abel Vesa <abel.vesa@...aro.org>