From: Marek Vasut <marex@denx.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Marek Vasut <marex@denx.de>, Conor Dooley <conor+dt@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
devicetree@vger.kernel.org, imx@lists.linux.dev
Subject: [PATCH 2/3] arm64: dts: imx8mm: Avoid iMX8MM errata ERR050080 on i.MX8MM Menlo board
Date: Tue, 21 May 2024 12:23:12 +0200 [thread overview]
Message-ID: <20240521102435.10019-2-marex@denx.de> (raw)
In-Reply-To: <20240521102435.10019-1-marex@denx.de>
i.MX8MM Mask Set Errata for Mask 0N87W, Rev. 1, 09/2021 document has the
following errata, which could affect the beeper and the LEDs. The beeper
has external pull down and it is likely gonna be off most of the time, so
disable pull resistors altogether. The LEDs do not have any external pull
resistors, so enable internal pull down, as they are also likely gonna be
off most of the time. The rest of the IO is not affected by the errata,
as it is not being driven against the pull resistor for the majority of
uptime.
"
ERR050080:
IO: Degradation of internal IO pullup/pulldown current capability for
IO's continuously driven in a 3.3V operating mode
Description:
There is a degradation of the internal IO pullup/pulldown capability
when the IO pads are continuously driven in the opposite logic level,
for example, when internal pullup is enabled with external logic
driving the pin low, and a 3.3V operating condition which limits
the pads pullup/pulldown ability.
All IO pin groups are impacted except for XTAL, DDR, PCI, USB, and
MIPI PHY IO’s.
Workaround:
Where the IO’s are used for 3.3V operation and the circuit requires
pullup or pulldown, use external resistors for the pullup/pulldown
and disable the internal pullup/pulldown via software.
"
Signed-off-by: Marek Vasut <marex@denx.de>
---
Cc: Conor Dooley <conor+dt@kernel.org>
Cc: Fabio Estevam <festevam@gmail.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>
Cc: Rob Herring <robh@kernel.org>
Cc: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Shawn Guo <shawnguo@kernel.org>
Cc: devicetree@vger.kernel.org
Cc: imx@lists.linux.dev
Cc: linux-arm-kernel@lists.infradead.org
---
arch/arm64/boot/dts/freescale/imx8mm-mx8menlo.dts | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/boot/dts/freescale/imx8mm-mx8menlo.dts b/arch/arm64/boot/dts/freescale/imx8mm-mx8menlo.dts
index 4c38979f7333f..ed83a019159ac 100644
--- a/arch/arm64/boot/dts/freescale/imx8mm-mx8menlo.dts
+++ b/arch/arm64/boot/dts/freescale/imx8mm-mx8menlo.dts
@@ -210,7 +210,7 @@ &iomuxc {
pinctrl_beeper: beepergrp {
fsl,pins = <
- MX8MM_IOMUXC_SPDIF_TX_GPIO5_IO3 0x1c4
+ MX8MM_IOMUXC_SPDIF_TX_GPIO5_IO3 0x4
>;
};
@@ -225,8 +225,8 @@ MX8MM_IOMUXC_ECSPI1_SS0_GPIO5_IO9 0x1c4
pinctrl_led: ledgrp {
fsl,pins = <
- MX8MM_IOMUXC_SAI1_TXD6_GPIO4_IO18 0x1c4
- MX8MM_IOMUXC_SAI1_TXFS_GPIO4_IO10 0x1c4
+ MX8MM_IOMUXC_SAI1_TXD6_GPIO4_IO18 0x184
+ MX8MM_IOMUXC_SAI1_TXFS_GPIO4_IO10 0x184
>;
};
--
2.43.0
next prev parent reply other threads:[~2024-05-21 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 10:23 [PATCH 1/3] arm64: dts: imx8mm: Describe carrier board 20 MHz Xtal on i.MX8MM Menlo board Marek Vasut
2024-05-21 10:23 ` Marek Vasut [this message]
2024-05-21 10:23 ` [PATCH 3/3] arm64: dts: imx8mm: Delete SoM hwmon node " Marek Vasut
2024-05-21 12:58 ` [PATCH 1/3] arm64: dts: imx8mm: Describe carrier board 20 MHz Xtal " Peng Fan
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=20240521102435.10019-2-marex@denx.de \
--to=marex@denx.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh@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