[Linux-stm32] [PATCH V4 00/22] ARM: dts: stm32: Repair AV96 board

[Marek Vasut]

On 4/5/20 8:37 PM, Manivannan Sadhasivam wrote:
> On Sun, Apr 05, 2020 at 04:55:54PM +0200, Marek Vasut wrote:
>> On 4/5/20 4:43 PM, Manivannan Sadhasivam wrote:
>>> Hi Marek,
>>
>> Hi,
>>
>>> On Wed, Apr 01, 2020 at 03:22:15PM +0200, Marek Vasut wrote:
>>>> The AV96 board device tree is completely broken and does not match the
>>>> hardware. This series fixes it up.
>>>>
>>>
>>> Can you please share a git tree with all these patches? These are not
>>> applying cleanly on top of mainline/master or linux-next/master.
>>
>> Alex asked for them to be rebased on
>> git://git.kernel.org/pub/scm/linux/kernel/git/atorgue/stm32.git
>> branch
>> stm32-next
>>
> 
> Thanks, I'm able to build with your patches. Btw, I just found that the
> current mainline versions of u-boot and Linux kernel are certainly broken
> on old Avenger96 (588-100) as well.

Considering the difference between the prototype board and the 588-200
production board, that's quite possible. Are you willing to test things
on the 588-100 board ? If so, then we can try and support the 588-100 too.

> u-boot doesn't boot while linux kernel has MMC2 and Ethernet broken as you
> reported. However, checking out the commit which added Avenger96 board support
> in both projects works fine.

At least
35a54d41d9d4 ("ARM: dts: stm32mp1: sync device tree with v5.2-rc4")
in U-Boot broke the old board.

But that should all be fixed for the upcoming U-Boot release in master
already (for 588-200).

The rest is a lot of incorrect pinmux in both, fixed in U-Boot already,
fixed by this set for Linux.

> So this clearly tells that there is a regression which caused the board support
> to be broken with mainline u-boot and kernel. I didn't try to find the offending
> commit(s) as the support for STM32MP1 got matured in both the projects. But
> we can go ahead with your patches.
> 
> I will review the remaining patches tomorrow