From: Frank Wunderlich <linux@fw-web.de>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: Frank Wunderlich <frank-w@public-files.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: [PATCH v8 0/2] Add Pmic to Bpi-R4
Date: Fri, 20 Dec 2024 17:38:34 +0100 [thread overview]
Message-ID: <20241220163838.114786-1-linux@fw-web.de> (raw)
From: Frank Wunderlich <frank-w@public-files.de>
After these 2 Patches are dropped from my dts-series [1] i verified these
with mtk and changed based on this.
The problem was that voltages from BUCK4 and LDO were not matching the
voltages from schematic.
These 2 are not software-controlled, but should show the right voltage
in regulator overview.
[1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=918585
Frank Wunderlich (2):
arm64: dts: mediatek: mt7988a-bpi-r4: Add MediaTek MT6682A/RT5190A
PMIC
arm64: dts: mediatek: mt7988a-bpi-r4: Add proc-supply for cpus
.../dts/mediatek/mt7988a-bananapi-bpi-r4.dts | 66 +++++++++++++++++++
arch/arm64/boot/dts/mediatek/mt7988a.dtsi | 8 +--
2 files changed, 70 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2024-12-20 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 16:38 Frank Wunderlich [this message]
2024-12-20 16:38 ` [PATCH v8 1/2] arm64: dts: mediatek: mt7988a-bpi-r4: Add MediaTek MT6682A/RT5190A PMIC Frank Wunderlich
2024-12-20 16:38 ` [PATCH v8 2/2] arm64: dts: mediatek: mt7988a-bpi-r4: Add proc-supply for cpus Frank Wunderlich
2024-12-20 16:44 ` Aw: [PATCH v8 0/2] Add Pmic to Bpi-R4 Frank Wunderlich
2025-01-02 12:46 ` 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=20241220163838.114786-1-linux@fw-web.de \
--to=linux@fw-web.de \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=krzk+dt@kernel.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).