public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	<arm@kernel.org>,
	soc@kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
	linux-arm-kernel@lists.infradead.org,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: [GIT PULL] ARM: mvebu: dt64 for v5.8 (#1)
Date: Wed, 20 May 2020 18:31:34 +0200	[thread overview]
Message-ID: <878shmeffd.fsf@FE-laptop> (raw)

Hi,

Here is the first pull request for dt64 for mvebu for v5.8.

Gregory

The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:

  Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)

are available in the Git repository at:

  git://git.infradead.org/linux-mvebu.git tags/mvebu-dt64-5.8-1

for you to fetch changes up to c2671acbbbd822ef077cc168991e0a7dbe2172c9:

  arm64: dts: armada-3720-turris-mox: fix SFP binding (2020-05-17 18:57:48 +0200)

----------------------------------------------------------------
mvebu dt64 for 5.8 (part 1)

Armada 3720 based SoC:

+ Fix PCIe support allowing to use Compex wifi cards

+ Turris MOX board:
  - fix SFP binding
  - forbid SDR104 on SDIO to pass electromagnetic interference certifications

+ uDPU board: add i2c recovery support

Armada 8040 based SoC: SolidRun 8040: update phy interface

----------------------------------------------------------------
Baruch Siach (1):
      arm64: dts: marvell: drop i2c timeout-ms property

Marek Behún (4):
      arm64: dts: marvell: armada-37xx: Set pcie_reset_pin to gpio function
      arm64: dts: marvell: armada-37xx: Move PCIe comphy handle property
      arm64: dts: armada-3720-turris-mox: forbid SDR104 on SDIO for FCC purposes
      arm64: dts: armada-3720-turris-mox: fix SFP binding

Pali Rohár (1):
      arm64: dts: marvell: armada-37xx: Move PCIe max-link-speed property

Russell King (2):
      arm64: dts: update SolidRun Armada 8040 phy interface types
      arm64: dts: add uDPU i2c bus recovery

 arch/arm64/boot/dts/marvell/armada-3720-db.dts     |  3 +++
 .../boot/dts/marvell/armada-3720-espressobin.dtsi  |  2 +-
 .../boot/dts/marvell/armada-3720-turris-mox.dts    | 10 +++-------
 arch/arm64/boot/dts/marvell/armada-3720-uDPU.dts   | 22 ++++++++++++++++++++--
 arch/arm64/boot/dts/marvell/armada-37xx.dtsi       |  4 +++-
 .../dts/marvell/armada-8040-clearfog-gt-8k.dts     |  2 +-
 .../dts/marvell/armada-8040-mcbin-singleshot.dts   |  4 ++--
 arch/arm64/boot/dts/marvell/armada-8040-mcbin.dts  |  4 ++--
 arch/arm64/boot/dts/marvell/armada-ap80x.dtsi      |  1 -
 9 files changed, 35 insertions(+), 17 deletions(-
-- 
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com

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

                 reply	other threads:[~2020-05-20 16:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=878shmeffd.fsf@FE-laptop \
    --to=gregory.clement@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=olof@lixom.net \
    --cc=sebastian.hesselbarth@gmail.com \
    --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