From: Shawn Guo <shawnguo@kernel.org>
To: "Guido Günther" <agx@sigxcpu.org>
Cc: Rob Herring <robh+dt@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>,
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: Re: [PATCH v2 0/2] arm64: dts: imx8mq-librem5-devkit: Use 0.9V for VDD_GPU
Date: Thu, 23 Apr 2020 09:18:47 +0800 [thread overview]
Message-ID: <20200423011846.GG8571@dragon> (raw)
In-Reply-To: <cover.1587480093.git.agx@sigxcpu.org>
On Tue, Apr 21, 2020 at 04:44:12PM +0200, Guido Günther wrote:
> 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
This one should also be prefixed like arm64: dts: imx8mq-librem5-devkit:
I fixed it up and applied both.
Shawn
>
> arch/arm64/boot/dts/freescale/imx8mq-librem5-devkit.dts | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --
> 2.26.1
>
prev parent reply other threads:[~2020-04-23 1:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 14:44 [PATCH v2 0/2] arm64: dts: imx8mq-librem5-devkit: Use 0.9V for VDD_GPU Guido Günther
2020-04-21 14:44 ` [PATCH v2 1/2] " 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 ` Shawn Guo [this message]
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=20200423011846.GG8571@dragon \
--to=shawnguo@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=abel.vesa@nxp.com \
--cc=agx@sigxcpu.org \
--cc=angus@akkea.ca \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martink@posteo.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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).