From: mindentropy <mindentropy@gmail.com>
To: festevam@gmail.com
Cc: mindentropy@gmail.com, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] Modified imx7d-sdb.dts file so that VLDO4 provides 2.8V for MIPI CSI/DSI
Date: Wed, 28 Jun 2017 23:15:18 +0530 [thread overview]
Message-ID: <20170628174518.5950-1-mindentropy@gmail.com> (raw)
From: Gautam Bhat <mindentropy@gmail.com>
* According to mx7sabresd schematics the MIPI CSI/DSI voltage rails
should be 2.8V but the voltage provided is a maximum of 3.3V and
minimum of 1.8V. Providing such a higher voltage might damage the
peripherals and violates the schematic settings.
Signed-off-by: Gautam Bhat <mindentropy@gmail.com>
---
arch/arm/boot/dts/imx7d-sdb.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/imx7d-sdb.dts b/arch/arm/boot/dts/imx7d-sdb.dts
index 5be01a1bf840..1da1f97ec342 100644
--- a/arch/arm/boot/dts/imx7d-sdb.dts
+++ b/arch/arm/boot/dts/imx7d-sdb.dts
@@ -262,8 +262,8 @@
};
vgen6_reg: vldo4 {
- regulator-min-microvolt = <1800000>;
- regulator-max-microvolt = <3300000>;
+ regulator-min-microvolt = <2800000>;
+ regulator-max-microvolt = <2800000>;
regulator-always-on;
};
};
--
2.11.0
next reply other threads:[~2017-06-28 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 17:45 mindentropy [this message]
2017-06-28 20:19 ` [PATCH] Modified imx7d-sdb.dts file so that VLDO4 provides 2.8V for MIPI CSI/DSI Fabio Estevam
2017-07-01 7:39 ` [PATCH v2] ARM: dts: imx7d-sdb: Set VLDO4 outpt to " mindentropy
2017-07-01 12:41 ` Fabio Estevam
2017-07-12 7:18 ` 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=20170628174518.5950-1-mindentropy@gmail.com \
--to=mindentropy@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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).