Linux SOC development
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.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>
Cc: Marek Vasut <marex@denx.de>,
	Ahmad Fatoum <a.fatoum@pengutronix.de>,
	Alexandre TORGUE <alexandre.torgue@foss.st.com>,
	"linux-stm32@st-md-mailman.stormreply.com"
	<linux-stm32@st-md-mailman.stormreply.com>,
	Jagan Teki <jagan@amarulasolutions.com>,
	dillon min <dillon.minfei@gmail.com>
Subject: [GIT PULL] STM32 DT changes for v5.14 #1
Date: Thu, 10 Jun 2021 18:01:14 +0200	[thread overview]
Message-ID: <e4bfb255-63fb-74a8-d591-eb09821c93ee@foss.st.com> (raw)

Hi ARM SoC maintainers,

Please consider this first round of STM32 DT updates for v5.14. This PR 
provides mainly DT yaml verification fixes.

regards
Alex

The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:

   Linux 5.13-rc1 (2021-05-09 14:17:44 -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.14-1

for you to fetch changes up to 4bf4abe19089245b7b12f35e5cafb5477b3e2c48:

   ARM: dts: stm32: fix stpmic node for stm32mp1 boards (2021-06-10 
16:08:18 +0200)

----------------------------------------------------------------
STM32 DT updates for v5.14, round 1

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

MCU part:
  - Fixes for Yaml verifications

MPU part:
  - Configure qspi's mdma transfer to block for stm32mp151

  - ST boards:
   - Fixes for yaml verifications

  - DH boards:
   - Fixes for yaml verifications
   - Rework of LAN8710i on DHCOM SoM to fit with requested reset sequence.

  - Odyssey boards:
   - fix Sd card detectection (gpio line updated)
   - fix eMMC VQMMC suuply (use vdd instead of v3v3)

----------------------------------------------------------------
Alexandre Torgue (9):
       ARM: dts: stm32: fix gpio-keys node on STM32 MCU boards
       ARM: dts: stm32: fix RCC node name on stm32f429 MCU
       ARM: dts: stm32: fix timer nodes on STM32 MCU to prevent warnings
       ARM: dts: stm32: update pinctrl node name on STM32 MCU to prevent 
warnings
       ARM: dts: stm32: fix i2c node name on stm32f746 to prevent warnings
       ARM: dts: stm32: move stmmac axi config in ethernet node on stm32mp15
       dt-bindings: net: document ptp_ref clk in dwmac
       ARM: dts: stm32: fix ltdc pinctrl on microdev2.0-of7
       ARM: dts: stm32: fix stpmic node for stm32mp1 boards

Grzegorz Szymaszek (3):
       ARM: dts: stm32: fix stm32mp157c-odyssey card detect pin
       ARM: dts: stm32: add a new DCMI pins group on stm32mp15
       ARM: dts: stm32: fix the Odyssey SoM eMMC VQMMC supply

Marek Vasut (6):
       ARM: dts: stm32: Rework LAN8710Ai PHY reset on DHCOM SoM
       ARM: dts: stm32: Remove extra size-cells on dhcom-pdk2
       ARM: dts: stm32: Fix touchscreen node on dhcom-pdk2
       ARM: dts: stm32: Drop unused linux,wakeup from touchscreen node 
on DHCOM SoM
       ARM: dts: stm32: Rename eth@N to ethernet@N on DHCOM SoM
       ARM: dts: stm32: Rename spi-flash/mx66l51235l@N to flash@N on 
DHCOM SoM

Patrice Chotard (1):
       ARM: dts: stm32: Configure qspi's mdma transfer to block for 
stm32mp151

  .../devicetree/bindings/net/stm32-dwmac.yaml       |  6 +-
  arch/arm/boot/dts/stm32429i-eval.dts               |  8 +--
  arch/arm/boot/dts/stm32746g-eval.dts               |  6 +-
  arch/arm/boot/dts/stm32f4-pinctrl.dtsi             |  2 +-
  arch/arm/boot/dts/stm32f429-disco.dts              |  6 +-
  arch/arm/boot/dts/stm32f429-pinctrl.dtsi           | 72 
++++++++++-----------
  arch/arm/boot/dts/stm32f429.dtsi                   | 10 +--
  arch/arm/boot/dts/stm32f469-disco.dts              |  6 +-
  arch/arm/boot/dts/stm32f469-pinctrl.dtsi           | 74 
++++++++++------------
  arch/arm/boot/dts/stm32f7-pinctrl.dtsi             |  2 +-
  arch/arm/boot/dts/stm32f746.dtsi                   | 12 +---
  arch/arm/boot/dts/stm32f769-disco.dts              |  6 +-
  arch/arm/boot/dts/stm32h743.dtsi                   |  4 --
  arch/arm/boot/dts/stm32mp15-pinctrl.dtsi           | 33 ++++++++++
  arch/arm/boot/dts/stm32mp151.dtsi                  | 16 ++---
  ...m32mp157a-microgea-stm32mp1-microdev2.0-of7.dts |  2 +-
  arch/arm/boot/dts/stm32mp157a-stinger96.dtsi       |  7 +-
  arch/arm/boot/dts/stm32mp157c-odyssey-som.dtsi     |  7 +-
  arch/arm/boot/dts/stm32mp157c-odyssey.dts          |  2 +-
  arch/arm/boot/dts/stm32mp15xx-dhcom-pdk2.dtsi      |  7 +-
  arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi       | 17 +++--
  arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi       |  2 +-
  arch/arm/boot/dts/stm32mp15xx-osd32.dtsi           |  7 +-
  23 files changed, 151 insertions(+), 163 deletions(-)

             reply	other threads:[~2021-06-10 16:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 16:01 Alexandre TORGUE [this message]
2021-06-12 16:10 ` [GIT PULL] STM32 DT changes for v5.14 #1 patchwork-bot+linux-soc

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=e4bfb255-63fb-74a8-d591-eb09821c93ee@foss.st.com \
    --to=alexandre.torgue@foss.st.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=dillon.minfei@gmail.com \
    --cc=jagan@amarulasolutions.com \
    --cc=khilman@baylibre.com \
    --cc=linux-stm32@st-md-mailman.stormreply.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox