devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hsin-Te Yuan <yuanhsinte@chromium.org>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	 Matthias Brugger <matthias.bgg@gmail.com>,
	 AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	 Hsin-Yi Wang <hsinyi@chromium.org>,
	 Enric Balletbo i Serra <eballetbo@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	 Hsin-Te Yuan <yuanhsinte@chromium.org>,
	 Daolong Zhu <jg_daolongzhu@mediatek.corp-partner.google.com>
Subject: [PATCH 4/4] arm64: dts: mt8183: Damu: add i2c2's i2c-scl-internal-delay-ns
Date: Wed, 09 Oct 2024 20:59:47 +0800	[thread overview]
Message-ID: <20241009-i2c-delay-v1-4-6cf59721c1d1@chromium.org> (raw)
In-Reply-To: <20241009-i2c-delay-v1-0-6cf59721c1d1@chromium.org>

From: Daolong Zhu <jg_daolongzhu@mediatek.corp-partner.google.com>

Add i2c2's i2c-scl-internal-delay-ns.

Fixes: cabc71b08eb5 ("arm64: dts: mt8183: Add kukui-jacuzzi-damu board")
Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Signed-off-by: Daolong Zhu <jg_daolongzhu@mediatek.corp-partner.google.com>
Signed-off-by: Hsin-Te Yuan <yuanhsinte@chromium.org>
---
 arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-damu.dts | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-damu.dts b/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-damu.dts
index 0b45aee2e29953b6117b462034a00dff2596b9ff..65860b33c01fe832f3a4b2e21d24ea6b4f0cba2b 100644
--- a/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-damu.dts
+++ b/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-damu.dts
@@ -30,3 +30,6 @@ &qca_wifi {
 	qcom,ath10k-calibration-variant = "GO_DAMU";
 };
 
+&i2c2 {
+	i2c-scl-internal-delay-ns = <20000>;
+};

-- 
2.47.0.rc0.187.ge670bccf7e-goog


  parent reply	other threads:[~2024-10-09 13:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 12:59 [PATCH 0/4] arm64: dts: mt8183: Add i2c-scl-internal-delay-ns Hsin-Te Yuan
2024-10-09 12:59 ` [PATCH 1/4] arm64: dts: mt8183: fennel: add i2c2's i2c-scl-internal-delay-ns Hsin-Te Yuan
2024-10-09 12:59 ` [PATCH 2/4] arm64: dts: mt8183: burnet: " Hsin-Te Yuan
2024-10-09 12:59 ` [PATCH 3/4] arm64: dts: mt8183: cozmo: " Hsin-Te Yuan
2024-10-09 12:59 ` Hsin-Te Yuan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-09  7:29 [PATCH 0/4] arm64: dts: mt8183: Add i2c-scl-internal-delay-ns Hsin-Te Yuan
2024-09-09  7:29 ` [PATCH 4/4] arm64: dts: mt8183: Damu: add i2c2's i2c-scl-internal-delay-ns Hsin-Te Yuan
2024-09-09 11:18   ` Matthias Brugger

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=20241009-i2c-delay-v1-4-6cf59721c1d1@chromium.org \
    --to=yuanhsinte@chromium.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eballetbo@kernel.org \
    --cc=hsinyi@chromium.org \
    --cc=jg_daolongzhu@mediatek.corp-partner.google.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh@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).