linux-kernel - Re: [PATCH v2 1/1] gpio-f7188x: fix base values conflicts with other gpio pins

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

Date:   Tue, 30 May 2023 13:40:06 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     simon.guinot@...uanux.org
Cc:     xingtong_wu@....com, brgl@...ev.pl, linux-gpio@...r.kernel.org,
        linux-kernel@...r.kernel.org, henning.schild@...mens.com,
        xingtong.wu@...mens.com
Subject: Re: [PATCH v2 1/1] gpio-f7188x: fix base values conflicts with other
 gpio pins

On Mon, May 29, 2023 at 3:56 PM <simon.guinot@...uanux.org> wrote:

> This way the assignation would be dynamic and the pin numbers found in
> controller datasheet would be meaningful as well.

I always had in my mind that this is what you should use the
.dbg_show() callback in struct gpio_chip for.

It is for debugging, not ABI and cross-referencing datasheets is definitely
debugging, so use that and look in /proc/sys/kernel/debug/gpio
for the data you want for cross-referencing.

Yours,
Linus Walleij