linux-kernel - Re: [PATCH 11/19] ARM: ux500: Add all known I2C sub-device nodes to the HREF 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]

Date:	Mon, 10 Sep 2012 04:34:15 -0700
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	STEricsson_nomadik_linux@...t.st.com, linus.walleij@...ricsson.com,
	arnd@...db.de
Subject: Re: [PATCH 11/19] ARM: ux500: Add all known I2C sub-device nodes to
 the HREF DT

On Fri, Sep 7, 2012 at 1:14 PM, Lee Jones <lee.jones@...aro.org> wrote:

> Here we add the skeleton nodes for each of the known I2C sub-devices
> currently registered on ST-Ericsson's HREF Development Platform. We
> will fill these nodes in turn as the drivers are enabled for Device
> Tree.
>
> Signed-off-by: Lee Jones <lee.jones@...aro.org>

Can't we have it the other way around (discussing patch ordering
with Arnd simultaneously), so you first add the DT support to the
subdevices, then add the more complete nodes to the device tree?

And if you put in a device tree like this, will these devices
not collide with the ones that are currently supplied from
the boardfiles? I'm a bit confused here, maybe I'm not smart
enough to understand this...

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/