[PATCH] arm: dts: stm32mp15: alignment with v5.11-rc2

[Marek Vasut]

On 1/13/21 10:48 AM, Patrick DELAUNAY wrote:
> Hi Marek,

Hi,

> On 1/11/21 1:15 PM, Marek Vasut wrote:
>> On 1/11/21 12:33 PM, Patrick Delaunay wrote:
>>> Device tree alignment with Linux kernel v5.11-rc2
>>> - fix DCMI DMA features on stm32mp15 family
>>> - Add alternate pinmux for FMC EBI bus
>>> - Harmonize EHCI/OHCI DT nodes name on stm32mp15
>>> - update sdmmc IP version for STM32MP15
>>> - Add LP timer irqs on stm32mp151
>>> - Add LP timer wakeup-source on stm32mp151
>>> - enable HASH by default on stm32mp15
>>> - enable CRC1 by default on stm32mp15
>>> - enable CRYP by default on stm32mp15
>>> - set bus-type in DCMI endpoint for stm32mp157c-ev1 board
>>> - reorder spi4 within stm32mp15-pinctrl
>>> - add STUSB1600 Type-C using I2C4 on stm32mp15xx-dkx
>>> - fix mdma1 clients channel priority level on stm32mp151
>>> - fix dmamux reg property on stm32mp151
>>> - adjust USB OTG gadget fifo sizes in stm32mp151
>>> - update stm32mp151 for remote proc synchronization support
>>> - support child mfd cells for the stm32mp1 TAMP syscon
>>
>> Are you completely sure the dhcom based boards generate the same DT 
>> after the sync ?
>>
>> I would rather prefer sync with Linux 5.10 (LTS), or is that not an 
>> option due to some extra DT patches ?
>>
>> Either way, if you have an upstream queue for this DT sync somewhere, 
>> please give me a link, I plan to sync the dhcom boards after 2021.01 
>> is out, so I would build on top of that.
> 
> I am sure the DT is not the same, sorry.
> 
> At least for the SOC part (new nodes, updates value).
> 
> I compare the dhcom device tree (dts file form dtb) and I don't found 
> modifications except the phandle changes and the expected modifications.
> 
> But it is not a exhaustive check.

There is dtdiff, you can run it on the generated SPL and U-Boot DTBs 
before and after your changes. That should be a thorough check.

> For ST boards, the U-Boot device trees are aligned with  Linux 5.9 since 
> the commit 62f95af92a3fc21a72f5f3198f0d065cbd773f03 ("ARM: dts: 
> stm32mp1: DT alignment with Linux kernel v5.9-rc4")
> 
> I skip the Linux 5.10 (LTS) as it comes after v2020.10 merge windows and 
> the 5.11 device tree are already updated (pull request from Alexandre 
> Torgue = 
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/atorgue/stm32)
> 
> But if you prefer I can split it in 2 steps
> 
> 1/ Device tree alignment with Linux kernel v5.10 (LTS)
> 
> 2/ Device tree alignment with Linux kernel v5.11-rc2
> 
> Today the patch is present in next branch of stm custodians 
> (https://gitlab.denx.de/u-boot/custodians/u-boot-stm/-/tree/next)
> 
> And I am preparing a pull request for the master branch.

Keep it as-is, I just wanted to know why you didn't pick the LTS option, 
now it's clear, thanks.