Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: arm-soc <arm@kernel.org>, SoC Team <soc@kernel.org>
Cc: Ryder Lee <ryder.lee@mediatek.com>,
	Hsin-Yi Wang <hsinyi@chromium.org>,
	Michael Kao <michael.kao@mediatek.com>,
	Ulrich Hecht <ulrich.hecht+renesas@gmail.com>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-mediatek@lists.infradead.org>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	Chunfeng Yun <chunfeng.yun@mediatek.com>,
	Ikjoon Jang <ikjn@chromium.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] arm64: mediatek: updates for v5.8
Date: Sat, 16 May 2020 22:04:09 +0200	[thread overview]
Message-ID: <2794a8db-c14f-ac34-9e28-9f3700db6c4c@gmail.com> (raw)

Hi Olof,
Hi Arnd,

Please have a look on the device tree changes for 64-bit platforms. The
highlight for me is the support for the support for the MT8173 based Chromebooks
(like the Acer R13). This has been around for quite some time, but in the end we
took up the work between several people to get it all ready for upstream.

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-dts64

for you to fetch changes up to f0e5405b9ebf084c34c41f5d38a0013bee166f4d:

  arm64: dts: mt8173: Add capacity-dmips-mhz attributes (2020-05-16 18:36:40 +0200)

----------------------------------------------------------------
MT2712:
- replace deprecated compatible for the usb PHY

MT6797:
- switch to SPDX identifier
- add and enable I2C device for x20 development board
- add I2C compatible to the binding description

MT7622:
- add Wi-Fi device and enable it for the Bananpi-R64

MT8173:
- add CPU capacities based on Dhryston benchmark
- fix DT build warnings
- set throtteling range to limitless
- add Elm and Hana devices on which several chromebooks are based
- add Global Command Queue entries to the users

MT8183:
- split cpuidle states in two as the clusters have different target residencies

----------------------------------------------------------------
Chunfeng Yun (1):
      arm64: dts: mt2712: use non-empty ranges for usb-phy

Hsin-Yi Wang (6):
      arm64: dts: mt8173: Add gce setting in mmsys and display node
      dt-bindings: arm64: dts: mediatek: Add mt8173 elm and hana
      arm64: dts: mt8173: add uart aliases
      arm64: dts: mt8173: fix unit name warnings
      arm64: dts: mediatek: add mt8173 elm and hana board
      arm64: dts: mt8173: fix mdp aliases property name

Ikjoon Jang (1):
      arm64: dts: mt8183: adjust cpuidle target residency

Manivannan Sadhasivam (4):
      dt-bindings: i2c: Document I2C controller binding for MT6797 SoC
      arm64: dts: mediatek: Add I2C support for MT6797 SoC
      arm64: dts: mediatek: Enable I2C support for 96Boards X20 Development board
      arm64: dts: mediatek: Switch to SPDX license identifier for MT6797 SoC

Michael Kao (1):
      arm64: dts: mt8173: fix cooling device range

Ryder Lee (1):
      arm64: dts: mt7622: add built-in Wi-Fi device nodes

Ulrich Hecht (1):
      arm64: dts: mt8173: Add capacity-dmips-mhz attributes

 .../devicetree/bindings/arm/mediatek.yaml          |   22 +
 .../devicetree/bindings/i2c/i2c-mt65xx.txt         |    1 +
 arch/arm64/boot/dts/mediatek/Makefile              |    3 +
 arch/arm64/boot/dts/mediatek/mt2712e.dtsi          |   42 +-
 arch/arm64/boot/dts/mediatek/mt6797-x20-dev.dts    |   49 +
 arch/arm64/boot/dts/mediatek/mt6797.dtsi           |  229 +++-
 .../boot/dts/mediatek/mt7622-bananapi-bpi-r64.dts  |    4 +
 arch/arm64/boot/dts/mediatek/mt7622-rfb1.dts       |    4 +
 arch/arm64/boot/dts/mediatek/mt7622.dtsi           |   11 +
 .../boot/dts/mediatek/mt8173-elm-hana-rev7.dts     |   27 +
 arch/arm64/boot/dts/mediatek/mt8173-elm-hana.dts   |   14 +
 arch/arm64/boot/dts/mediatek/mt8173-elm-hana.dtsi  |   70 ++
 arch/arm64/boot/dts/mediatek/mt8173-elm.dts        |   14 +
 arch/arm64/boot/dts/mediatek/mt8173-elm.dtsi       | 1173 ++++++++++++++++++++
 arch/arm64/boot/dts/mediatek/mt8173.dtsi           |   78 +-
 arch/arm64/boot/dts/mediatek/mt8183.dtsi           |   26 +-
 16 files changed, 1705 insertions(+), 62 deletions(-)
 create mode 100644 arch/arm64/boot/dts/mediatek/mt8173-elm-hana-rev7.dts
 create mode 100644 arch/arm64/boot/dts/mediatek/mt8173-elm-hana.dts
 create mode 100644 arch/arm64/boot/dts/mediatek/mt8173-elm-hana.dtsi
 create mode 100644 arch/arm64/boot/dts/mediatek/mt8173-elm.dts
 create mode 100644 arch/arm64/boot/dts/mediatek/mt8173-elm.dtsi

_______________________________________________
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 20:04 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=2794a8db-c14f-ac34-9e28-9f3700db6c4c@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=arm@kernel.org \
    --cc=chunfeng.yun@mediatek.com \
    --cc=hsinyi@chromium.org \
    --cc=ikjn@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=michael.kao@mediatek.com \
    --cc=ryder.lee@mediatek.com \
    --cc=soc@kernel.org \
    --cc=ulrich.hecht+renesas@gmail.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