From: Frieder Schrempf <frieder@fris.de>
To: devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>
Cc: Frieder Schrempf <frieder.schrempf@kontron.de>,
Fabio Estevam <festevam@gmail.com>,
Heiko Thiery <heiko.thiery@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: [PATCH 3/6] arm64: dts: imx8mm-kontron: Remove low DDRC operating point
Date: Wed, 13 Jul 2022 09:41:14 +0200 [thread overview]
Message-ID: <20220713074118.14733-4-frieder@fris.de> (raw)
In-Reply-To: <20220713074118.14733-1-frieder@fris.de>
From: Frieder Schrempf <frieder.schrempf@kontron.de>
For some reason there is a problem with finding a DDR configuration
that works on all operating points and all LPDDR4 types used on the
SoM. Therefore the bootloader currently doesn't configure the lowest
of the three operating points. Let's also skip this in the kernel
devicetree to make sure it isn't used.
Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de>
---
arch/arm64/boot/dts/freescale/imx8mm-kontron-n801x-som.dtsi | 4 ----
1 file changed, 4 deletions(-)
diff --git a/arch/arm64/boot/dts/freescale/imx8mm-kontron-n801x-som.dtsi b/arch/arm64/boot/dts/freescale/imx8mm-kontron-n801x-som.dtsi
index 77c074b491a6..2d0661cce89b 100644
--- a/arch/arm64/boot/dts/freescale/imx8mm-kontron-n801x-som.dtsi
+++ b/arch/arm64/boot/dts/freescale/imx8mm-kontron-n801x-som.dtsi
@@ -46,10 +46,6 @@ &ddrc {
ddrc_opp_table: opp-table {
compatible = "operating-points-v2";
- opp-25M {
- opp-hz = /bits/ 64 <25000000>;
- };
-
opp-100M {
opp-hz = /bits/ 64 <100000000>;
};
--
2.37.0
next prev parent reply other threads:[~2022-07-13 7:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 7:41 [PATCH 0/6] arm64: dts: imx8mm-kontron: Improvements and OSM board support Frieder Schrempf
2022-07-13 7:41 ` [PATCH 1/6] arm64: dts: imx8mm-kontron: Adjust board and SoM model strings Frieder Schrempf
2022-07-14 15:53 ` Fabio Estevam
2022-07-14 16:04 ` Frieder Schrempf
2022-07-13 7:41 ` [PATCH 2/6] arm64: dts: imx8mm-kontron: Use the VSELECT signal to switch SD card IO voltage Frieder Schrempf
2022-07-14 14:53 ` Heiko Thiery
2022-07-13 7:41 ` Frieder Schrempf [this message]
2022-07-13 7:41 ` [PATCH 4/6] arm64: dts: imx8mm-kontron: Use upper case PMIC regulator names Frieder Schrempf
2022-07-13 7:52 ` Heiko Thiery
2022-07-13 8:15 ` Frieder Schrempf
2022-07-13 8:25 ` Frieder Schrempf
2022-07-13 7:41 ` [PATCH 5/6] arm64: dts: Add support for Kontron SL/BL i.MX8MM OSM-S Frieder Schrempf
2022-07-13 8:36 ` Marco Felsch
2022-07-13 8:44 ` Frieder Schrempf
2022-07-13 8:46 ` Marco Felsch
2022-07-13 7:41 ` [PATCH 6/6] dt-bindings: arm: fsl: Add Kontron BL i.MX8MM OSM-S board Frieder Schrempf
2022-07-13 7:55 ` Krzysztof Kozlowski
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=20220713074118.14733-4-frieder@fris.de \
--to=frieder@fris.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=heiko.thiery@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--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).