linux-kernel - Re: [PATCH V3 2/2] gpio: add STA2X11 GPIO block

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:	Fri, 13 Apr 2012 13:44:02 +0200
From:	Alessandro Rubini <rubini@...dd.com>
To:	linus.walleij@...aro.org
Cc:	linux-kernel@...r.kernel.org, giancarlo.asnaghi@...com,
	alan@...ux.intel.com, sameo@...ux.intel.com,
	grant.likely@...retlab.ca, linus.walleij@...ricsson.com
Subject: Re: [PATCH V3 2/2] gpio: add STA2X11 GPIO block

> I would still prefer to use the pinctrl subsystem for this from day
> 1 instead of adding more custom stuff for later refactoring...

I see your point. I attacked pinctrl some time ago, but it is overly
complex for this simple stuff. We have static configuration that is
enacted at boot, and that's it.  Using pinctrl would mean much more
code (and more bugs, as a side effect) for no real advantage.  I
appreciate the flexibility of pinctrl, and I see it's really good to
have a way to describe complex SoC hardware, but it just isn't always
needed.

Besides, it's still marked as experimental, which on one side is not
reassuring about its stability, and on the other means my whole
chipset should depend on experimental as a consequence.

thanks
/alessandro
--
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/