linux-kernel - Re: [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-prev] [day] [month] [year] [list]

Message-ID: <CACRpkdY3Hz1QgK9jDVE6LT5DeNKbvz+-aa3Q9=njkESHmyeksw@mail.gmail.com>
Date: Mon, 13 Oct 2025 12:15:42 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Abel Vesa <abel.vesa@...aro.org>
Cc: Bjorn Andersson <andersson@...nel.org>, Pankaj Patil <pankaj.patil@....qualcomm.com>, 
	Konrad Dybcio <konrad.dybcio@....qualcomm.com>, linux-arm-msm@...r.kernel.org, 
	linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] pinctrl: qcom: glymur: Fix gpio pin functions and
 clean-up match table

On Fri, Sep 19, 2025 at 2:17 PM Abel Vesa <abel.vesa@...aro.org> wrote:

> 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>

Patches applied for next since they are not regressions.

Yours,
Linus Walleij