From: Vignesh Raghavendra <vigneshr@ti.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Bjorn Andersson <quic_bjorande@quicinc.com>,
Arnd Bergmann <arnd@arndb.de>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH -next 0/2] arm64: dts: ti: Fixes for Beagleplay SD
Date: Thu, 30 Mar 2023 16:29:19 +0530 [thread overview]
Message-ID: <20230330105921.3639185-1-vigneshr@ti.com> (raw)
Couple of fixups on top of ti-next branch:
The SD supply on Beagle is really coming from PMIC LDO1 even though its
controllable via GPIO, hence fix the DT accordingly, this also means
PMIC regulator drivers need to be built-in to allow SD card rootfs
Nishanth,
Better to squash into respetive commits if possible
Vignesh Raghavendra (2):
arm64: configs: defconfig: Make TPS65219 regulator built-in
arm64: dts: ti: k3-am625-beagleplay: Fixup SD card supply regulator
arch/arm64/boot/dts/ti/k3-am625-beagleplay.dts | 2 +-
arch/arm64/configs/defconfig | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
--
2.40.0
next reply other threads:[~2023-03-30 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 10:59 Vignesh Raghavendra [this message]
2023-03-30 10:59 ` [PATCH 1/2] arm64: configs: defconfig: Make TPS65219 regulator built-in Vignesh Raghavendra
2023-03-30 10:59 ` [PATCH 2/2] arm64: dts: ti: k3-am625-beagleplay: Fixup SD card supply regulator Vignesh Raghavendra
2023-03-30 14:59 ` [PATCH -next 0/2] arm64: dts: ti: Fixes for Beagleplay SD Nishanth Menon
2023-03-30 22:05 ` Nishanth Menon
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=20230330105921.3639185-1-vigneshr@ti.com \
--to=vigneshr@ti.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=quic_bjorande@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=will@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
all inboxes | Powered by JetHome®