linux-kernel - RFC: phase out static using gpio numbers in platform drivers

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>] [day] [month] [year] [list]

Message-ID: <40af948c-3407-2100-777c-3bfb30f22708@metux.net>
Date:   Wed, 31 Jul 2019 17:29:18 +0200
From:   "Enrico Weigelt, metux IT consult" <lkml@...ux.net>
To:     "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: RFC: phase out static using gpio numbers in platform drivers

Hello folks,

I've seen a lot of drivers (eg. many arch specific board init code)
are still using raw gpio numbers, which AFAIK are deprecated.

Shall we start phasing them out and rewrite the corresponding drivers
to use match tables ?

--mtx

-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@...ux.net -- +49-151-27565287