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 V2 00/22] ARM: dts: stm32: Repair AV96 board
Date: Tue, 31 Mar 2020 15:44:52 +0200 [thread overview]
Message-ID: <7dc86fa9-504c-cbc3-9a24-29644d66f9e3@denx.de> (raw)
In-Reply-To: <20200331040736.GA14274@Mani-XPS-13-9360>
On 3/31/20 6:07 AM, Manivannan Sadhasivam wrote:
> Hi Marek,
Hi,
> Thanks for the series.
>
> On Tue, Mar 31, 2020 at 02:56:39AM +0200, Marek Vasut wrote:
>> The AV96 board device tree is completely broken and does not match the
>> hardware. This series fixes it up.
>>
>
> Completely broken?
The board didn't even boot.
> The patch submitted previously was an initial one and there
> were many interfaces not enabled. I agree that there are few _obvious_ things
> like SDMMC1/Ethernet pinmux, LED naming were wrong. This was due to the fact the
> board was on early bringup stage and I couldn't test Ethernet due to my setup
> issue at that time (yeah I know it is bad). Also, I don't get access to DHCOR
> schematics as well for things like PMIC. Do you have access to it?
Yes, I do have access.
> If possible can you share a link to that if available publicly?
The SoM schematic is not available in public, no, sorry.
> I will test this series and also the uboot one on my board and give my
> Tested-by tag soon.
>
> Anyway, I think the patchset subject could be something like,
> "Improve AV96 support" :)
I think if something doesn't work, "Repair" is the right word for it.
_______________________________________________
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-03-31 16:23 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 0:56 [PATCH V2 00/22] ARM: dts: stm32: Repair AV96 board Marek Vasut
2020-03-31 0:56 ` [PATCH V2 01/22] ARM: dts: stm32: Add alternate pinmux for ethernet RGMII Marek Vasut
2020-03-31 4:13 ` Manivannan Sadhasivam
2020-03-31 0:56 ` [PATCH V2 02/22] ARM: dts: stm32: Repair ethernet operation on AV96 Marek Vasut
2020-03-31 4:13 ` Manivannan Sadhasivam
2020-03-31 0:56 ` [PATCH V2 03/22] ARM: dts: stm32: Add missing ethernet PHY reset " Marek Vasut
2020-03-31 4:21 ` Manivannan Sadhasivam
2020-03-31 0:56 ` [PATCH V2 04/22] ARM: dts: stm32: Add missing ethernet PHY skews " Marek Vasut
2020-03-31 4:22 ` Manivannan Sadhasivam
2020-03-31 0:56 ` [PATCH V2 05/22] ARM: dts: stm32: Add alternate pinmux for SDMMC1 direction pins Marek Vasut
2020-03-31 4:28 ` Manivannan Sadhasivam
2020-03-31 0:56 ` [PATCH V2 06/22] ARM: dts: stm32: Repair SDMMC1 operation on AV96 Marek Vasut
2020-03-31 4:33 ` Manivannan Sadhasivam
2020-03-31 13:36 ` Marek Vasut
2020-03-31 14:02 ` Manivannan Sadhasivam
2020-03-31 15:45 ` Marek Vasut
2020-03-31 0:56 ` [PATCH V2 07/22] ARM: dts: stm32: Add alternate pinmux for SDMMC2 pins 4-7 Marek Vasut
2020-03-31 4:36 ` Manivannan Sadhasivam
2020-03-31 0:56 ` [PATCH V2 08/22] ARM: dts: stm32: Add eMMC attached to SDMMC2 on AV96 Marek Vasut
2020-03-31 4:43 ` Manivannan Sadhasivam
2020-03-31 15:46 ` Marek Vasut
2020-03-31 0:56 ` [PATCH V2 09/22] ARM: dts: stm32: Repair PMIC configuration " Marek Vasut
2020-03-31 0:56 ` [PATCH V2 10/22] ARM: dts: stm32: Repair PMIC interrupt " Marek Vasut
2020-03-31 0:56 ` [PATCH V2 11/22] ARM: dts: stm32: Add QSPI NOR " Marek Vasut
2020-03-31 0:56 ` [PATCH V2 12/22] ARM: dts: stm32: Add configuration EEPROM " Marek Vasut
2020-03-31 6:34 ` Manivannan Sadhasivam
2020-03-31 0:56 ` [PATCH V2 13/22] ARM: dts: stm32: Enable GPU " Marek Vasut
2020-03-31 6:36 ` Manivannan Sadhasivam
2020-03-31 0:56 ` [PATCH V2 14/22] ARM: dts: stm32: Add alternate pinmux for SDMMC3 pins Marek Vasut
2020-03-31 6:40 ` Manivannan Sadhasivam
2020-03-31 0:56 ` [PATCH V2 15/22] ARM: dts: stm32: Enable WiFi on AV96 Marek Vasut
2020-03-31 6:43 ` Manivannan Sadhasivam
2020-03-31 0:56 ` [PATCH V2 16/22] ARM: dts: stm32: Add alternate pinmux for USART2 pins Marek Vasut
2020-03-31 6:46 ` Manivannan Sadhasivam
2020-03-31 0:56 ` [PATCH V2 17/22] ARM: dts: stm32: Enable Bluetooth on AV96 Marek Vasut
2020-03-31 6:47 ` Manivannan Sadhasivam
2020-03-31 0:56 ` [PATCH V2 18/22] ARM: dts: stm32: Add alternate pinmux for LTDC pins Marek Vasut
2020-03-31 0:56 ` [PATCH V2 19/22] ARM: dts: stm32: Add bindings for HDMI video on AV96 Marek Vasut
2020-03-31 0:56 ` [PATCH V2 20/22] ARM: dts: stm32: Add bindings for audio " Marek Vasut
2020-03-31 0:57 ` [PATCH V2 21/22] ARM: dts: stm32: Add bindings for USB " Marek Vasut
2020-03-31 0:57 ` [PATCH V2 22/22] ARM: dts: stm32: Rename LEDs to match silkscreen " Marek Vasut
2020-03-31 4:09 ` Manivannan Sadhasivam
2020-03-31 4:07 ` [PATCH V2 00/22] ARM: dts: stm32: Repair AV96 board Manivannan Sadhasivam
2020-03-31 13:44 ` Marek Vasut [this message]
2020-03-31 14:09 ` Manivannan Sadhasivam
2020-03-31 15:51 ` Marek Vasut
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=7dc86fa9-504c-cbc3-9a24-29644d66f9e3@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