devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen-Yu Tsai <wenst@chromium.org>
To: Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>
Cc: Chen-Yu Tsai <wenst@chromium.org>,
	devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] arm64: dts: mediatek: Add MT8186 Voltorb Chromebooks
Date: Thu, 20 Jun 2024 17:47:35 +0800	[thread overview]
Message-ID: <20240620094746.2404753-1-wenst@chromium.org> (raw)

Hi folks,

This series adds support for the MT8186 Voltorb Chromebooks. This is yet
another product based on the Corsola reference design. This particular
version features a higher end spec-ed SoC, necessitating a beefier
regulator for the big core cluster.

Patch 1 adds an entry for a new regulator IC. How this differs from
the previous iteration is not totally clear.

Patch 2 adds an entry for the Voltorb devices.

Patch 3 adds the device trees for the new devices.


Please have a look. I expect either all three patches to go through the
MediaTek tree; or the first can go through the regulator tree, and the
other two through the MediaTek tree.


Thanks
ChenYu


Chen-Yu Tsai (3):
  dt-bindings: regulator: mt6315: Document MT6319 PMIC
  dt-bindings: arm: mediatek: Add MT8186 Voltorb Chromebooks
  arm64: dts: mediatek: Add MT8186 Voltorb Chromebooks

 .../devicetree/bindings/arm/mediatek.yaml     |   7 ++
 .../bindings/regulator/mt6315-regulator.yaml  |   6 +-
 arch/arm64/boot/dts/mediatek/Makefile         |   2 +
 .../mt8186-corsola-voltorb-sku589824.dts      |  13 +++
 .../mt8186-corsola-voltorb-sku589825.dts      |  25 +++++
 .../dts/mediatek/mt8186-corsola-voltorb.dtsi  | 103 ++++++++++++++++++
 6 files changed, 155 insertions(+), 1 deletion(-)
 create mode 100644 arch/arm64/boot/dts/mediatek/mt8186-corsola-voltorb-sku589824.dts
 create mode 100644 arch/arm64/boot/dts/mediatek/mt8186-corsola-voltorb-sku589825.dts
 create mode 100644 arch/arm64/boot/dts/mediatek/mt8186-corsola-voltorb.dtsi

-- 
2.45.2.741.gdbec12cfda-goog


             reply	other threads:[~2024-06-20  9:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20  9:47 Chen-Yu Tsai [this message]
2024-06-20  9:47 ` [PATCH 1/3] dt-bindings: regulator: mt6315: Document MT6319 PMIC Chen-Yu Tsai
2024-06-20 16:12   ` Conor Dooley
2024-06-20  9:47 ` [PATCH 2/3] dt-bindings: arm: mediatek: Add MT8186 Voltorb Chromebooks Chen-Yu Tsai
2024-06-20 16:13   ` Conor Dooley
2024-06-24  7:45     ` Chen-Yu Tsai
2024-06-20  9:47 ` [PATCH 3/3] arm64: dts: " Chen-Yu Tsai
2024-06-21  0:49 ` (subset) [PATCH 0/3] " Mark Brown
2024-06-24 10:51 ` AngeloGioacchino Del Regno

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=20240620094746.2404753-1-wenst@chromium.org \
    --to=wenst@chromium.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hsin-hsiung.wang@mediatek.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh@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;
as well as URLs for NNTP newsgroup(s).