linux-kernel - Re: [PATCH 0/2] add support for partial pin space

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: <CACRpkdaS7843scS5jwVajMzrUy3c7bSUHMW7n+=fkk6XTEKfDA@mail.gmail.com>
Date:	Tue, 3 Jan 2012 08:57:26 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Chanho Park <chanho61.park@...sung.com>
Cc:	swarren@...dia.com, Baohua.Song@....com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] add support for partial pin space

On Tue, Jan 3, 2012 at 8:47 AM, Chanho Park <chanho61.park@...sung.com> wrote:

> A pin space of current pinctrl driver always start with zero-based pin
> number. And pins are enumerated from 0 to a max pin number. If there are
> two pins (one is 0, another is 1000), we always enumerate from 0 to 1000
> for just only two pins. This patch enables to start non-zero based pin
> number and to enumerate actually owned pins.
>
> For example, there is a system which has huge(500 or 1000) pins. If muxing
> or controlling pins are small, we just define such small pins instead of
> whole pins.

Seems like you're fixing my code to do what was originally intended :-)

The maxpin member was something I introduced for sparse ranges
which would auto-register "dummy pins" for those not included in the
enumeration.

That doesn't quite work, so was left behind.

I'll try applying the patches and see what happens.

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/