From: Marek Vasut <marex@denx.de>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: Alexandre Torgue <alexandre.torgue@st.com>,
Patrice Chotard <patrice.chotard@st.com>,
Patrick Delaunay <patrick.delaunay@st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V4 00/22] ARM: dts: stm32: Repair AV96 board
Date: Sun, 5 Apr 2020 22:01:54 +0200 [thread overview]
Message-ID: <0faa0102-4504-d17b-fb7a-d710100cce2f@denx.de> (raw)
In-Reply-To: <20200405183729.GA9410@Mani-XPS-13-9360>
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-04-05 20:02 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 13:22 [PATCH V4 00/22] ARM: dts: stm32: Repair AV96 board Marek Vasut
2020-04-01 13:22 ` [PATCH V4 01/22] ARM: dts: stm32: Add alternate pinmux for ethernet RGMII Marek Vasut
2020-04-01 13:22 ` [PATCH V4 02/22] ARM: dts: stm32: Repair ethernet operation on AV96 Marek Vasut
2020-04-01 13:22 ` [PATCH V4 03/22] ARM: dts: stm32: Add missing ethernet PHY reset " Marek Vasut
2020-04-06 6:10 ` Manivannan Sadhasivam
2020-04-01 13:22 ` [PATCH V4 04/22] ARM: dts: stm32: Add missing ethernet PHY skews " Marek Vasut
2020-04-01 13:22 ` [PATCH V4 05/22] ARM: dts: stm32: Add alternate pinmux for SDMMC1 direction pins Marek Vasut
2020-04-01 13:22 ` [PATCH V4 06/22] ARM: dts: stm32: Repair SDMMC1 operation on AV96 Marek Vasut
2020-04-06 6:24 ` Manivannan Sadhasivam
2020-04-01 13:22 ` [PATCH V4 07/22] ARM: dts: stm32: Repair PMIC configuration " Marek Vasut
2020-04-01 13:22 ` [PATCH V4 08/22] ARM: dts: stm32: Repair PMIC interrupt " Marek Vasut
2020-04-01 13:22 ` [PATCH V4 09/22] ARM: dts: stm32: Add alternate pinmux for SDMMC2 pins 4-7 Marek Vasut
2020-04-01 13:22 ` [PATCH V4 10/22] ARM: dts: stm32: Add eMMC attached to SDMMC2 on AV96 Marek Vasut
2020-04-06 6:47 ` Manivannan Sadhasivam
2020-04-01 13:22 ` [PATCH V4 11/22] ARM: dts: stm32: Add QSPI NOR " Marek Vasut
2020-04-06 6:49 ` Manivannan Sadhasivam
2020-04-01 13:22 ` [PATCH V4 12/22] ARM: dts: stm32: Add configuration EEPROM " Marek Vasut
2020-04-01 13:22 ` [PATCH V4 13/22] ARM: dts: stm32: Add alternate pinmux for SDMMC3 pins Marek Vasut
2020-04-01 13:22 ` [PATCH V4 14/22] ARM: dts: stm32: Enable WiFi on AV96 Marek Vasut
2020-04-01 13:22 ` [PATCH V4 15/22] ARM: dts: stm32: Add alternate pinmux for USART2 pins Marek Vasut
2020-04-01 13:22 ` [PATCH V4 16/22] ARM: dts: stm32: Enable Bluetooth on AV96 Marek Vasut
2020-04-01 13:22 ` [PATCH V4 17/22] ARM: dts: stm32: Add alternate pinmux for LTDC pins Marek Vasut
2020-04-01 13:22 ` [PATCH V4 18/22] ARM: dts: stm32: Add bindings for HDMI video on AV96 Marek Vasut
2020-04-06 7:05 ` Manivannan Sadhasivam
2020-04-01 13:22 ` [PATCH V4 19/22] ARM: dts: stm32: Add alternate pinmux for SAI2 pins Marek Vasut
2020-04-01 13:22 ` [PATCH V4 20/22] ARM: dts: stm32: Add bindings for audio on AV96 Marek Vasut
2020-04-01 13:22 ` [PATCH V4 21/22] ARM: dts: stm32: Add bindings for USB " Marek Vasut
2020-04-06 7:22 ` Manivannan Sadhasivam
2020-04-06 11:08 ` Marek Vasut
2020-04-07 18:37 ` Marek Vasut
2020-04-10 9:08 ` Manivannan Sadhasivam
2020-04-10 9:16 ` Marek Vasut
2020-04-10 11:34 ` Manivannan Sadhasivam
2020-04-10 18:02 ` Marek Vasut
2020-04-11 4:12 ` Manivannan Sadhasivam
2020-04-12 1:54 ` Marek Vasut
2020-04-01 13:22 ` [PATCH V4 22/22] ARM: dts: stm32: Rename LEDs to match silkscreen " Marek Vasut
2020-04-06 7:24 ` Manivannan Sadhasivam
2020-04-05 14:43 ` [PATCH V4 00/22] ARM: dts: stm32: Repair AV96 board Manivannan Sadhasivam
2020-04-05 14:55 ` Marek Vasut
2020-04-05 18:37 ` Manivannan Sadhasivam
2020-04-05 20:01 ` Marek Vasut [this message]
2020-04-06 6:04 ` Manivannan Sadhasivam
2020-04-06 7:27 ` Manivannan Sadhasivam
2020-04-07 15:32 ` Marek Vasut
2020-04-10 9:00 ` Manivannan Sadhasivam
2020-04-10 9:55 ` Marek Vasut
2020-04-10 11:28 ` Manivannan Sadhasivam
2020-04-10 18:03 ` Marek Vasut
2020-04-21 10:30 ` Marek Vasut
2020-04-21 16:04 ` Alexandre Torgue
2020-04-21 17:07 ` Marek Vasut
2020-04-22 7:27 ` Alexandre Torgue
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0faa0102-4504-d17b-fb7a-d710100cce2f@denx.de \
--to=marex@denx.de \
--cc=alexandre.torgue@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=patrice.chotard@st.com \
--cc=patrick.delaunay@st.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).