[U-Boot] [PATCH 0/14] dm: omap: Provide access to driver model for am335x, and move boards

Simon Glass sjg at chromium.org
Thu Oct 23 21:18:28 CEST 2014


Hi Tom,

On 20 October 2014 09:13, Tom Rini <trini at ti.com> wrote:
> On Tue, Oct 14, 2014 at 09:26:51AM +0200, Simon Glass wrote:
>> Hi,
>>
>> On 22 September 2014 17:48, Simon Glass <sjg at chromium.org> wrote:
>> > This series adjusts the serial and GPIO drivers, used by Beaglebone for
>> > example, to work with driver model. Since there are still boards using
>> > these drivers but not driver model, this adds new functionality rather
>> > than replacing what exists.
>> >
>> > Several patches tweak and fix the existing driver model serial and GPIO
>> > implementation.
>> >
>> > There are two Beaglebone Black configurations:
>> >
>> > - Device tree control with verified boot
>> > - No device tree control
>> >
>> > The first uses device tree to select the serial console and provide
>> > information needed by the serial driver (similar to how things work on
>> > Tegra). The second uses platform data provided by a common board file.
>> >
>> > Both are converted, so this is a good example of how to support both device
>> > tree and platform data if needed.
>>
>> Are there any comments on this series please?
>
> As part of settling back into the groove, I need to fire these up on my
> am335x boards and go from there.

Thanks for the comments. I plan to apply the v2 series to dm/master soon.

Regards,
Simon


More information about the U-Boot mailing list