[0/2] omap5 uevm: convert to device model

Message ID	20200602202343.6495-1-t-kristo@ti.com
Headers	show List-Id: U-Boot discussion <u-boot.lists.denx.de> From: t-kristo at ti.com (Tero Kristo) Date: Tue, 2 Jun 2020 23:23:41 +0300 Subject: [PATCH 0/2] omap5 uevm: convert to device model Message-ID: <20200602202343.6495-1-t-kristo@ti.com>
Series	omap5 uevm: convert to device model \| expand [0/2] omap5 uevm: convert to device model [1/2] omap5: Copy device tree from linux 5.7.y [2/2] omap5: uevm: convert to device model

Message ID

20200602202343.6495-1-t-kristo@ti.com

Headers

List-Id: U-Boot discussion <u-boot.lists.denx.de>
From: t-kristo at ti.com (Tero Kristo)
Date: Tue, 2 Jun 2020 23:23:41 +0300
Subject: [PATCH 0/2] omap5 uevm: convert to device model
Message-ID: <20200602202343.6495-1-t-kristo@ti.com>

Series

omap5 uevm: convert to device model | expand

Message

Tero Kristo June 2, 2020, 8:23 p.m. UTC

Hi,

Following the omap4 panda conversion series, this converts the
omap5-uevm board to device model. Some semi nasty hacks were needed in
the omap5-u-boot.dtsi files as this is common to both dra7xx and omap5,
due to overloading of dra7xx architecture on top of omap5. Fixing that
requires some more patching, so I just did a simple #ifdef within the
u-boot specific dtsi file for now.

-Tero


--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki