From: "Guido Günther" <agx@sigxcpu•org>
To: "Rob Herring" <robh+dt@kernel•org>,
"Shawn Guo" <shawnguo@kernel•org>,
"Sascha Hauer" <s.hauer@pengutronix•de>,
"Pengutronix Kernel Team" <kernel@pengutronix•de>,
"Fabio Estevam" <festevam@gmail•com>,
"NXP Linux Team" <linux-imx@nxp•com>,
"Angus Ainslie (Purism)" <angus@akkea•ca>,
"Martin Kepplinger" <martink@posteo•de>,
"Guido Günther" <agx@sigxcpu•org>,
"Abel Vesa" <abel.vesa@nxp•com>,
"Anson Huang" <Anson.Huang@nxp•com>,
devicetree@vger•kernel.org, linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org
Subject: [PATCH v2 0/2] arm64: dts: imx8mq-librem5-devkit: Use 0.9V for VDD_GPU
Date: Tue, 21 Apr 2020 16:44:12 +0200 [thread overview]
Message-ID: <cover.1587480093.git.agx@sigxcpu.org> (raw)
According to the imx8mq data sheet running VDD_GPU at 0.9V is enough
when not overclocking to 1GHz (which we currently don't do).
changes from v2:
- rebase aginst Shawn's tree
- fix a warning for the typec connector
Guido Günther (2):
arm64: dts: imx8mq-librem5-devkit: Use 0.9V for VDD_GPU
arm64: dts: Don't use underscore in node name
arch/arm64/boot/dts/freescale/imx8mq-librem5-devkit.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.26.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-04-21 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 14:44 Guido Günther [this message]
2020-04-21 14:44 ` [PATCH v2 1/2] arm64: dts: imx8mq-librem5-devkit: Use 0.9V for VDD_GPU Guido Günther
2020-04-21 14:44 ` [PATCH v2 2/2] arm64: dts: Don't use underscore in node name Guido Günther
2020-04-23 1:18 ` [PATCH v2 0/2] arm64: dts: imx8mq-librem5-devkit: Use 0.9V for VDD_GPU Shawn Guo
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=cover.1587480093.git.agx@sigxcpu.org \
--to=agx@sigxcpu$(echo .)org \
--cc=Anson.Huang@nxp$(echo .)com \
--cc=abel.vesa@nxp$(echo .)com \
--cc=angus@akkea$(echo .)ca \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=festevam@gmail$(echo .)com \
--cc=kernel@pengutronix$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-imx@nxp$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=martink@posteo$(echo .)de \
--cc=robh+dt@kernel$(echo .)org \
--cc=s.hauer@pengutronix$(echo .)de \
--cc=shawnguo@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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