linux-kernel - Re: [PATCH 0/2] pinctrl: common handling of generic pinconfig props in dt

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: <CACRpkdaV0ipY4mYHt998D=NNKrpDaFhCA949V0-93NkOKcvHyA@mail.gmail.com>
Date:	Mon, 10 Jun 2013 14:52:13 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Heiko Stübner <heiko@...ech.de>
Cc:	Patrice Chotard <patrice.chotard.st@...il.com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] pinctrl: common handling of generic pinconfig props
 in dt

On Sun, Jun 9, 2013 at 1:59 AM, Heiko Stübner <heiko@...ech.de> wrote:

> following your suggestions for a common handling of things like pulls in dt,
> I've come up with the following solution - hopefully I've gotten the correct
> meaning of your explanaitions.
>
> It handles all the pinconfigs that either ignore the argument, or have very
> simple one, like PIN_CONFIG_OUTPUT does.

OK patches applied. It needs some rough fixes like NULL check
on kmalloc() but it'll do for a starter. Now I can tell everyone to
use this and refer to it.

> I've also attached my current rockchip pinctrl driver to show how it is using
> this currently.

OK I might just merge it. If you take the rest of the patches through
ARM SoC they will need to pull in my tree anyway if it's intended to
go in this merge window.

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/