From: Matthias Brugger <matthias.bgg@gmail.com>
To: arm-soc <arm@kernel.org>, SoC Team <soc@kernel.org>
Cc: "moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] ARM: mediatek: arm 32-bit updates for v5.8
Date: Sat, 16 May 2020 21:55:26 +0200 [thread overview]
Message-ID: <ec17cf62-5463-9537-6618-2db9b2b5036e@gmail.com> (raw)
Hi Arnd and Olof,
Please have a look at the following pull request which includes arm32 changes.
Regards,
Matthias
---
The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:
Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/
tags/v5.7-next-dts32
for you to fetch changes up to 189881af810d452b592ee958db43eb4c57df9803:
arm: dts: mt2701: Add usb2 device nodes (2020-05-16 21:03:06 +0200)
----------------------------------------------------------------
MT2701:
- add MUSB device to the SoC and the EVB
MT7623:
- add Mali-450 device node and bindings
- add phy to gmac2
----------------------------------------------------------------
Min Guo (1):
arm: dts: mt2701: Add usb2 device nodes
Ryder Lee (1):
arm: dts: mt7623: add Mali-450 device node
Sean Wang (2):
arm: dts: mt7623: add phy-mode property for gmac2
dt-bindings: gpu: mali-utgard: add mediatek, mt7623-mali compatible
.../devicetree/bindings/gpu/arm,mali-utgard.yaml | 2 ++
arch/arm/boot/dts/mt2701-evb.dts | 21 ++++++++++++++
arch/arm/boot/dts/mt2701.dtsi | 33 ++++++++++++++++++++++
arch/arm/boot/dts/mt7623.dtsi | 25 ++++++++++++++++
arch/arm/boot/dts/mt7623n-rfb-emmc.dts | 1 +
5 files changed, 82 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-05-16 19:55 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=ec17cf62-5463-9537-6618-2db9b2b5036e@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--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