linux-kernel - Re: [Question] How to implement GPIO driver for sparse hw numbers?

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:	Wed, 15 Jul 2015 00:04:32 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Question] How to implement GPIO driver for sparse hw numbers?

On Fri, Jun 19, 2015 at 5:27 AM, Masahiro Yamada
<yamada.masahiro@...ionext.com> wrote:

> In my understanding, the GPIO driver framework requires that
> the hw numbers should be contiguous within each GPIO chip.

Yes but noone says that .request() to the driver has to succeed
on every GPIO so just cover all GPIOs from 0 to 307 with
your GPIO chip and then implement your "holes" in the GPIO
range from 0 to 307 by letting .request() fail.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/