[PATCH v2 00/16] Sync NXP LS1028A-RDB device trees between U-Boot and Linux

[Priyanka Jain]

>-----Original Message-----
>From: Vladimir Oltean <vladimir.oltean at nxp.com>
>Sent: Tuesday, December 14, 2021 8:09 PM
>To: Priyanka Jain <priyanka.jain at nxp.com>; u-boot at lists.denx.de
>Cc: Michael Walle <michael at walle.cc>; Tom Rini <trini at konsulko.com>; Leo Li
><leoyang.li at nxp.com>; Heiko Schocher <hs at denx.de>; Simon Glass
><sjg at chromium.org>; Ramon Fried <rfried.dev at gmail.com>
>Subject: Re: [PATCH v2 00/16] Sync NXP LS1028A-RDB device trees between U-
>Boot and Linux
>
>Hi Priyanka,
>
>On Tue, Dec 07, 2021 at 10:20:07PM +0200, Vladimir Oltean wrote:
>> The changes were intended to be minimal, but unfortunately I
>> discovered some other stuff as well:
>> - we need to make some changes to the compatible strings of RTC devices
>>   and I2C muxes. This has ramifications to other NXP boards which were
>>   also updated.
>> - I broke Ethernet on LS1028A boards through a patch that is currently
>>   in Ramon's tree.
>>
>> Therefore this patch set is a bit larger than would be otherwise
>> expected.
>>
>> The Linux device tree changes have just been posted by me here and are
>> currently in flight, but they are rather small so I don't expect too
>> much pushback on them:
>> https://lore.kernel.org/linux-arm-kernel/20211202141528.2450169-5-vlad
>> imir.oltean at nxp.com/T/#m6f63c92e75fa79a01144b2c2c6dc4776e7971395
>>
>> I've also triggered an Azure CI build with these changes:
>> https://github.com/u-boot/u-boot/pull/102
>> and it appears that 2 tests fail due to external causes:
>> 1.
>> https://dev.azure.com/u-boot/u-boot/_build/results?buildId=3283&view=l
>> ogs&jobId=5fafc5b9-a417-5c75-4c48-15c7f941e4ee&j=5fafc5b9-a417-5c75-4c
>> 48-15c7f941e4ee&t=c864b9c4-48aa-5e04-3916-54070f85e156
>> 2.
>> https://dev.azure.com/u-boot/u-boot/_build/results?buildId=3283&view=l
>> ogs&j=5fafc5b9-a417-5c75-4c48-15c7f941e4ee&t=c864b9c4-48aa-5e04-3916-
>5
>> 4070f85e156&l=27
>>
>> Unable to find image
>> 'trini/u-boot-gitlab-ci-runner:focal-20211006-14Nov2021' locally
>> docker: Error response from daemon: Head "https://registry-
>1.docker.io/v2/trini/u-boot-gitlab-ci-runner/manifests/focal-20211006-
>14Nov2021": received unexpected HTTP status: 502 Bad Gateway.
>>
>> The other tests seem to pass.
>
>The Linux side of device tree patches were merged today, and I see you've
>reviewed the U-Boot side of changes too. Could you please pick them up?

Yes, I will pick the series as part of next pull-request for 2022.04

Regards
Priyanka