From: Martin Kepplinger <martin.kepplinger@puri.sm>
To: robh@kernel.org, shawnguo@kernel.org, kernel@pengutronix.de,
festevam@gmail.com
Cc: kernel@puri.sm, linux-imx@nxp.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Martin Kepplinger <martin.kepplinger@puri.sm>
Subject: [PATCH 5/5] arm64: dts: imx8mq-librem5-r2: set nearlevel to 120
Date: Mon, 8 Feb 2021 14:15:27 +0100 [thread overview]
Message-ID: <20210208131527.24463-6-martin.kepplinger@puri.sm> (raw)
In-Reply-To: <20210208131527.24463-1-martin.kepplinger@puri.sm>
On Birch I can never reach 220 and hence the display would never
turn off. Tests suggest 120 to be a good threshold value for all Birch
devices.
Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm>
---
arch/arm64/boot/dts/freescale/imx8mq-librem5-r2.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/freescale/imx8mq-librem5-r2.dts b/arch/arm64/boot/dts/freescale/imx8mq-librem5-r2.dts
index d77fc5df3f06..73bd431cbd6a 100644
--- a/arch/arm64/boot/dts/freescale/imx8mq-librem5-r2.dts
+++ b/arch/arm64/boot/dts/freescale/imx8mq-librem5-r2.dts
@@ -25,5 +25,5 @@
};
&proximity {
- proximity-near-level = <220>;
+ proximity-near-level = <120>;
};
--
2.20.1
prev parent reply other threads:[~2021-02-08 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 13:15 [PATCH 0/5] arm64: dts: librem5 phone and devkit dts and config updates Martin Kepplinger
2021-02-08 13:15 ` [PATCH 1/5] arm64: dts: imx8mq-librem5-devkit: Drop buck3 startup-ramp-delay Martin Kepplinger
2021-02-08 13:15 ` [PATCH 2/5] arm64: dts: librem5: Drop assigned-clocks from SAI2 Martin Kepplinger
2021-02-08 13:15 ` [PATCH 3/5] arm64: defconfig: Enable devfreq support for i.MX8MQ Martin Kepplinger
2021-02-08 14:05 ` Krzysztof Kozlowski
2021-02-08 13:15 ` [PATCH 4/5] arm64: dts: librem5: protect some partitions of the nor-flash Martin Kepplinger
2021-02-08 14:09 ` Krzysztof Kozlowski
2021-02-08 13:15 ` Martin Kepplinger [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=20210208131527.24463-6-martin.kepplinger@puri.sm \
--to=martin.kepplinger@puri.sm \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kernel@puri.sm \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).