linux-kernel - Re: [PATCH 00/19] First HREF Device Tree enablement patch-set

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: <201209101349.08857.arnd@arndb.de>
Date:	Mon, 10 Sep 2012 13:49:08 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Lee Jones <lee.jones@...aro.org>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	STEricsson_nomadik_linux@...t.st.com, linus.walleij@...ricsson.com
Subject: Re: [PATCH 00/19] First HREF Device Tree enablement patch-set

On Monday 10 September 2012, Linus Walleij wrote:
> > When the driver offers
> > two ways of probing a device, this lets us change from one way to
> > the other without going through a phase where we use neither of them
> > or (worse) both at the same time.
> 
> Maybe unrelated, but as usual it works as long as there are no
> DMA channels or callback functions :-/
> 
> The MMC, PL022 patches in this patch set: both need
> AUXDATA and DT data simultaneously due to DMA channels
> and callbacks passed in as AUXDATA.

Yes, that's another discussion. When this happens, we obviously
keep the platform data (or add a new version of it), but I'd still
use one patch to add the node to the device tree and simultaneously
add the auxdata and remove the static device registration.

	Arnd
--
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/