linux-kernel - Re: [PATCH 1/4] gpio: pxa: convert to one gpiochip

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]

Message-ID: <CACRpkdbNRck0S_6P4+HX-4bSkLvsnbOokig4oGgB+vVt6M2sdg@mail.gmail.com>
Date:	Thu, 10 Dec 2015 16:04:22 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Robert Jarzmik <robert.jarzmik@...e.fr>
Cc:	Alexandre Courbot <gnurou@...il.com>,
	Haojian Zhuang <haojian.zhuang@...il.com>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Daniel Mack <zonque@...il.com>
Subject: Re: [PATCH 1/4] gpio: pxa: convert to one gpiochip

On Sat, Nov 28, 2015 at 10:37 PM, Robert Jarzmik <robert.jarzmik@...e.fr> wrote:

> The pxa gpio IP is provided by one chip, which holds multiple banks.
>
> Another reason the driver should register only one gpiochip instead of
> multiple gpiochips (ie. 1 per each bank) is that for pincontrol and
> devicetree integration (think gpio-ranges), it's impossible to have the
> contiguous pin range 0..127 mapped to gpios 0..127.
>
> This patch, amongst other thinks, paves the path to loosen the bond with
> the global structure variable pxa_gpio_chip.
>
> Signed-off-by: Robert Jarzmik <robert.jarzmik@...e.fr>

Patch applied.

Since noone else seems to care, would you consider sending a patch
to MAINTAINERS listing yourself as maintainer of this GPIO driver?

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/