[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <537215D3.70306@ti.com>
Date: Tue, 13 May 2014 08:53:39 -0400
From: Tom Rini <trini@...com>
To: Robert Nelson <robertcnelson@...il.com>,
Tony Lindgren <tony@...mide.com>
CC: Matt Ranostay <mranostay@...il.com>, <robh+dt@...nel.org>,
<mark.rutland@....com>, Russell King <linux@....linux.org.uk>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
devicetree <devicetree@...r.kernel.org>,
linux kernel <linux-kernel@...r.kernel.org>,
Pantelis Antoniou <pantelis.antoniou@...il.com>,
Matt Porter <matt.porter@...aro.org>
Subject: Re: [PATCH v2] ARM: dts: am335x-bone-common: Add i2c2 definition
On 05/12/2014 04:57 PM, Robert Nelson wrote:
>>> Either case if fine with me. As who knows when the dtc "overlay" will
>>> every truly make it mainline, as the capemgr was the only real kernel
>>> user of the i2c/at24 eeprom information.
>>
>> Sounds like we should keep it disabled though so u-boot can be used
>> to toggle it while waiting for the capemgr. That's because the board
>> has a header for pins, so it's not exactly limited to just the capes.
>>
>> Anybody working on enabling/disabling cape dtb configurations in u-boot?
>
> Well,
>
> Would Tom even approve of that in mainline u-boot? He didn't want my
> "invert" the gpio to enable the usb hub on the older beagle xm A/B..
>
> http://lists.denx.de/pipermail/u-boot/2014-January/172154.html
>
> http://lists.denx.de/pipermail/u-boot/2014-January/172274.html
I would think that using the 'fdt' command in U-Boot to add all
properties of every cape found on a running system would drive someone
to madness quite quickly. Moving all of Pantelis' work for dynamic
device trees from the kernel to N bootloaders (U-Boot, barebox, UEFI,
etc) sounds like a step in the wrong direction.
--
Tom
--
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/
Powered by blists - more mailing lists