All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Torgue <alexandre.torgue@st.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	Kevin Hilman <khilman@baylibre.com>, SoC Team <soc@kernel.org>,
	arm-soc <arm@kernel.org>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	Marcin Sloniewski <marcin.sloniewski@gmail.com>,
	Ahmad Fatoum <a.fatoum@pengutronix.de>,
	Marek Vasut <marex@denx.de>
Cc: Alexandre TORGUE <alexandre.torgue@st.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-stm32@st-md-mailman.stormreply.com"
	<linux-stm32@st-md-mailman.stormreply.com>
Subject: [GIT PULL] STM32 DT fixes for v5.10 #1
Date: Wed, 28 Oct 2020 16:28:33 +0100	[thread overview]
Message-ID: <4ac236b3-b980-f653-f644-53e586570724@st.com> (raw)

Hi Arnd, Olof and Kevin,

On v5.10-rc1 STM32 boards cannot boot. It is linked to a change in 
regulator framework which highlights that our supplies are not well 
described. This PR fixes it for STM32 boards that I have on my desk: ED1 
and DKx.

I assume that same patch has to be done for other STM32 boards, but as I 
don't have schematics I can't provide it. So a round2 has to be done for:
- stinger96
- MC-1
- Odyssey SOM
- DHCOR /DHCOM

Mani, Marek, Ahmad, Marcin can you please have a look on it and provide 
patches (then I'll provide round2). Thanks in advance.


Regards
Alex


The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:

   Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)

are available in the Git repository at:

   git://git.kernel.org/pub/scm/linux/kernel/git/atorgue/stm32.git 
tags/stm32-dt-for-v5.10-fixes-1

for you to fetch changes up to 728a7e225ad807b4b4de3be3fb653424199f8a76:

   ARM: dts: stm32: Describe Vin power supply on stm32mp157c-edx board 
(2020-10-28 15:08:24 +0100)

----------------------------------------------------------------
STM32 DT fixes for v5.10, round 1

Highlights:
-----------

  -On STM32MP157 DK & ED boards: Add Vin supply description to avoid
   random kernel crash due to vref_ddr regulator issue.

----------------------------------------------------------------
Pascal Paillet (2):
       ARM: dts: stm32: Describe Vin power supply on stm32mp15xx-dkx board
       ARM: dts: stm32: Describe Vin power supply on stm32mp157c-edx board

  arch/arm/boot/dts/stm32mp157c-ed1.dts  | 15 +++++++++++++++
  arch/arm/boot/dts/stm32mp15xx-dkx.dtsi | 17 +++++++++++++++++
  2 files changed, 32 insertions(+)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2020-10-28 15:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 15:28 Alexandre Torgue [this message]
2020-10-28 16:11 ` [GIT PULL] STM32 DT fixes for v5.10 #1 Arnd Bergmann
2020-10-28 17:38 ` Ahmad Fatoum
2020-10-30  9:04   ` Marek Vasut
2020-11-02 12:52     ` Ahmad Fatoum
2020-11-02 13:02       ` 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=4ac236b3-b980-f653-f644-53e586570724@st.com \
    --to=alexandre.torgue@st.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=marcin.sloniewski@gmail.com \
    --cc=marex@denx.de \
    --cc=olof@lixom.net \
    --cc=soc@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.