Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp4785132iob; Mon, 9 May 2022 01:19:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx3PmCxdsJYA4YYx0ZurWen4dsjpNvjaOVt7wc4qVk2ntFMvmzPL6RCcCcxzb5cRDdomTFy X-Received: by 2002:a17:903:20d3:b0:15b:151c:cadb with SMTP id i19-20020a17090320d300b0015b151ccadbmr15422084plb.154.1652084398249; Mon, 09 May 2022 01:19:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652084398; cv=none; d=google.com; s=arc-20160816; b=dq+MeQ9G7QmCDR6CpdI+kNewP11lOsYFXDh/NaCWaRloAfabse3ofvbTRfMG+FhjW/ Rx+a2Jzmdx3k0zVm26JGVJuaWfaNjmV4sk1ITJUr7Uy1J6JiG48kDub1NQHfrrPu60ct XZ6UsvCI2zqYnmbPtUvJUK/A51RJbbRUaK3f4+r0sizidYAyclPnW4ocL6vne5nsqq5g m9THykAWUfq8NMxPhjrb2Un4ioJnpmM8CqWQKgK+uf9aae3Etta9VpNvwnBgkWB5rK/Z /N/jj4mbheCXRYv7LEnA3qfy/mDha10Mrf3h98//tDPyXEG9PDXfnq5ZiVD1DM71FSju a3Hg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=7PpGp+IxjY/mFC2wCH1dJ/EU5sBQTGAt350jNpBo3oU=; b=miQ0nVaijERknvCfzReNkujlv6OVhh5lRDIWmRI38Y4Emws1e8FgNYEQQcatNhEjUe K7jbx6EmA+n8xJHDcmS5hjZmPMC9qZPre9dM2QYxJXFX5+6T82GTAz9wSNFl6BzonbCV WtrlKbFAqKbJ5kxILoeqNNrmsgUQtyaJSjHjtymhoteqB9kB6yNFafDHgPKYGIqOtYDY 4PeEbn7xKQGsmeKG6+10CtcUwOB5PEiUayDkB0PX3JoTpttWQEif/MbSPCMHM07CH1ae om1/FBZlOqCM0nfxGzgf+HU8CNaSzYGwrJzEzsuvEmbW2t3UUsTzZ1k+XrRTtguHgBvj WkMQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=h2aKHfeb; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id 204-20020a6217d5000000b0050d304dbf4dsi12543406pfx.210.2022.05.09.01.19.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 May 2022 01:19:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=h2aKHfeb; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 685E41E0283; Mon, 9 May 2022 01:08:00 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1379932AbiEENrM (ORCPT + 99 others); Thu, 5 May 2022 09:47:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59166 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1379855AbiEENrF (ORCPT ); Thu, 5 May 2022 09:47:05 -0400 Received: from fllv0015.ext.ti.com (fllv0015.ext.ti.com [198.47.19.141]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E9FE257999; Thu, 5 May 2022 06:43:24 -0700 (PDT) Received: from fllv0035.itg.ti.com ([10.64.41.0]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id 245DhA3u030876; Thu, 5 May 2022 08:43:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1651758190; bh=7PpGp+IxjY/mFC2wCH1dJ/EU5sBQTGAt350jNpBo3oU=; h=From:To:CC:Subject:Date:In-Reply-To:References; b=h2aKHfebjZGw0M5mTyx/EmM6CIDH2KRf6D6PMo2jfhRwr7+GFLgmlQLJ+Ql2vOuUn mCIg/J0s3GM/9h31tAb4eqOENIxWoUkV+9j+APvQN8qPl0cV5eKhJhn7x/BNoxyJUq 0l6ewkMnQF4+Kbpq0brtGnlQK8mzkRA2VfIknR+4= Received: from DFLE114.ent.ti.com (dfle114.ent.ti.com [10.64.6.35]) by fllv0035.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 245DhA6J053453 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 5 May 2022 08:43:10 -0500 Received: from DFLE101.ent.ti.com (10.64.6.22) by DFLE114.ent.ti.com (10.64.6.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.14; Thu, 5 May 2022 08:43:10 -0500 Received: from fllv0039.itg.ti.com (10.64.41.19) by DFLE101.ent.ti.com (10.64.6.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.14 via Frontend Transport; Thu, 5 May 2022 08:43:09 -0500 Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0039.itg.ti.com (8.15.2/8.15.2) with ESMTP id 245Dh939104707; Thu, 5 May 2022 08:43:09 -0500 From: Aradhya Bhatia To: Vignesh Raghavendra CC: Nishanth Menon , Rob Herring , Linux ARM Kernel List , Devicetree List , Linux Kernel List , Aradhya Bhatia , Rahul T R Subject: [PATCH v2 3/4] arm64: dts: ti: k3-am625-sk: Update main-i2c1 frequency Date: Thu, 5 May 2022 19:13:02 +0530 Message-ID: <20220505134303.23208-4-a-bhatia1@ti.com> X-Mailer: git-send-email 2.36.0 In-Reply-To: <20220505134303.23208-1-a-bhatia1@ti.com> References: <20220505134303.23208-1-a-bhatia1@ti.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Update the main-i2c1 frequency from 400KHz to 100KHz. There are 2 devices on the i2c-1 bus. An IO-Expander and an HDMI TX. Both of these are capable of servicing i2c upto a max frequency of 400KHz. However, below warning log shows up while running any userspace application that uses the HDMI display when the main-i2c1 frequency is set at 400KHz. [ 985.773431] omap_i2c 20010000.i2c: controller timed out With some further tests using 2 frequencies, 100 KHz and 400KHz across different HDMI cable & monitor setups, it was observed that, - i2c frequency of 400KHz works fine with standard good quality HDMI cables with branded displays. It will show the controller timeout warnings only when a sub-standard / generic HDMI cable is being used. - Using 100KHz for i2c frequency, stops the warning from showing up for the generic HDMI cables as well. Since, the IO-Expander is the only other component on that i2c bus and we are not performing any intensive operations on it, it would be safe to set the i2c frequency at 100KHz in order to support a broader variety of HDMI cables. Signed-off-by: Aradhya Bhatia Reviewed-by: Rahul T R --- arch/arm64/boot/dts/ti/k3-am625-sk.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/ti/k3-am625-sk.dts b/arch/arm64/boot/dts/ti/k3-am625-sk.dts index ab3d90d358ee..96414c5dacf7 100644 --- a/arch/arm64/boot/dts/ti/k3-am625-sk.dts +++ b/arch/arm64/boot/dts/ti/k3-am625-sk.dts @@ -357,7 +357,7 @@ &main_i2c0 { &main_i2c1 { pinctrl-names = "default"; pinctrl-0 = <&main_i2c1_pins_default>; - clock-frequency = <400000>; + clock-frequency = <100000>; exp1: gpio@22 { compatible = "ti,tca6424"; -- 2.36.0