From: max.oss.09@gmail.com
To: Max Krummenacher <max.krummenacher@toradex.com>
Cc: 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,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] arm64: dts: freescale: imx8m{m|p}: don't limit i2c2 max. clock
Date: Mon, 27 May 2024 18:03:44 +0200 [thread overview]
Message-ID: <20240527160359.1965512-1-max.oss.09@gmail.com> (raw)
From: Max Krummenacher <max.krummenacher@toradex.com>
This sets the I2C clock frequency to something people expect it to
be by default.
For I2C DDC we do want to lower the I2C clock to have more reliable
communication. However that should be done where the I2C bus is
assigned to a HDMI DDC, not as the default.
Max Krummenacher (2):
arm64: dts: freescale: imx8mm-verdin: don't limit i2c2 max. clock
arm64: dts: freescale: imx8mp-verdin: don't limit i2c2 max. clock
arch/arm64/boot/dts/freescale/imx8mm-verdin.dtsi | 2 +-
arch/arm64/boot/dts/freescale/imx8mp-verdin.dtsi | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
--
2.42.0
next reply other threads:[~2024-05-27 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 16:03 max.oss.09 [this message]
2024-05-27 16:03 ` [PATCH v1 1/2] arm64: dts: freescale: imx8mm-verdin: don't limit i2c2 max. clock max.oss.09
2024-05-27 16:03 ` [PATCH v1 2/2] arm64: dts: freescale: imx8mp-verdin: " max.oss.09
2024-06-16 2:32 ` [PATCH v1 0/2] arm64: dts: freescale: imx8m{m|p}: " 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=20240527160359.1965512-1-max.oss.09@gmail.com \
--to=max.oss.09@gmail.com \
--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=linux-kernel@vger.kernel.org \
--cc=max.krummenacher@toradex.com \
--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;
as well as URLs for NNTP newsgroup(s).