linux-kernel - Re: [PATCH 1/1] pinctrl: handle dummy state in core

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: <CACRpkdZw6iv=PjvvU4s5L8yV6813gCD7t8Vk-S66v-nXPaf+=Q@mail.gmail.com>
Date:	Wed, 18 Apr 2012 15:52:23 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Sascha Hauer <s.hauer@...gutronix.de>
Cc:	Dong Aisheng <aisheng.dong@...escale.com>,
	"linus.walleij@...ricsson.com" <linus.walleij@...ricsson.com>,
	Dong Aisheng-B29396 <B29396@...escale.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Stephen Warren <swarren@...dotorg.org>
Subject: Re: [PATCH 1/1] pinctrl: handle dummy state in core

On Wed, Apr 18, 2012 at 2:28 PM, Sascha Hauer <s.hauer@...gutronix.de> wrote:

> Currently Dong Aisheng is working on i.MX6, we have i.MX31, i.MX35,
> i.MX51 and i.MX53 enabled in the same defconfig. Waiting for all
> machines turn over at once to pinctrl is illusionary. We have to make
> drivers work with and without pinctrl. We have a bunch of bad choices:
>
> - create a dummy pinctrl for all boards which do not have real pinmux
>  support

Viable compromise.

> - ignore pinctrl_request errors in drivers.

Ugh. Not good.

> - generate and return a dummy pinctrl in the core if no real pinctrl is
>  found.
>
> (replace pinctrl with regulators or clocks, it's the same situation, and
> it's not only i.MX specific)

Since we have dummy regulators, we should not break the design
pattern creating more confusion.

Stephen can you live with dummy pinctrl handles emitted by the
core, if explictly enabled by a Kconfig option?

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/