linux-kernel - Re: [RFC 1/3] pinctrl: add a driver for NVIDIA Tegra

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:	Sat, 10 Dec 2011 00:55:58 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Stephen Warren <swarren@...dia.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	ext Tony Lindgren <tony@...mide.com>
Subject: Re: [RFC 1/3] pinctrl: add a driver for NVIDIA Tegra

On Fri, Dec 9, 2011 at 6:28 PM, Stephen Warren <swarren@...dia.com> wrote:

> Hence, there's no point parsing it from device tree; we end up with exactly
> the same data in the driver, yet have spent a bunch of time parsing it out
> from device tree instead of just embedding it into the kernel binary.

For me there are two points:

- Avoiding clash with kernel maintainers who hate firmware-like tables and
  binary data filling up the kernel. Some certain other guy bearing my
  name comes to mind.

- Footprint: the majority of the stuff in your driver ends up in non-discardable
  memory, and will be kept around. Since we have this concept of a
  single zImage for a number of say ARMv7 systems, and since pin
  controllers can be pretty hard to load from modules, *all* of them
  may have to be compiled-in. If every driver for every board takes this
  approach I am afraid it will be end up with a measurable footprint.

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/