From: Aradhya Bhatia <a-bhatia1@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Conor Dooley <conor+dt@kernel.org>,
Devicetree List <devicetree@vger.kernel.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Rahul T R <r-ravikumar@ti.com>, Devarsh Thakkar <devarsht@ti.com>,
Jai Luthra <j-luthra@ti.com>,
Jayesh Choudhary <j-choudhary@ti.com>
Subject: Re: [PATCH v3 1/8] arm64: dts: ti: k3-am62x-sk-common: Update main-i2c1 frequency
Date: Thu, 3 Aug 2023 12:04:27 +0530 [thread overview]
Message-ID: <eea30962-0ec6-b967-7764-e57c9d6c75fa@ti.com> (raw)
In-Reply-To: <20230730163052.w5y5a25xgpxzuhzs@serving>
Hi Nishanth,
On 30-Jul-23 22:00, Nishanth Menon wrote:
> On 23:04-20230728, Aradhya Bhatia wrote:
>> The Display Data Channel (DDC) transactions between an HDMI transmitter
>> (SIL9022A in this case) and an HDMI monitor, occur at a maximum of
>> 100KHz. That's the maximum supported frequency within DDC standards.
>>
>> While the SIL9022A can transact with the core at 400KHz, it needs to
>> drop the frequency to 100KHz when communicating with the monitor,
>> otherwise, the i2c controller times out and shows warning like this.
>>
>> [ 985.773431] omap_i2c 20010000.i2c: controller timed out
>>
>> That feature, however, has not been enabled in the SIL9022 driver.
>>
>> Since, dropping the frequency doesn't affect any other devices on the
>> bus, drop the main-i2c1 frequency from 400KHz to 100KHz.
>>
>> Signed-off-by: Aradhya Bhatia <a-bhatia1@ti.com>
>> ---
>> arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi b/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi
>> index 34c8ffc553ec..540ed8a0d7fb 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi
>> @@ -300,7 +300,7 @@ &main_i2c1 {
>> status = "okay";
>> pinctrl-names = "default";
>> pinctrl-0 = <&main_i2c1_pins_default>;
>> - clock-frequency = <400000>;
>> + clock-frequency = <100000>;
>>
>> tlv320aic3106: audio-codec@1b {
>> #sound-dai-cells = <0>;
>> --
>> 2.40.1
>>
>
> I know we had issues with level shifters on the dev platform previously,
> but do we need this patch anymore with the production boards?
>
> if so, use Fixes and I can pick for next.
>
This doesn't have anything to do with the level shifter issue we have
had previously. The DDC communication between the monitor and the HDMI
bridge requires that the bus frequency be 100KHz. Some monitors still
end up supporting higher frequencies on higher quality HDMI cables,
but to support a larger variety, we need to ensure that it doesn't
exceed 100KHz. Hence, this is just as much applicable on the production
boards.
Since the capability of the SIL9022 to drop down the transaction
frequency to 100KHz has not been enabled in the driver, I am changing
the bus frequency for the whole i2c-1 bus.
And this patch is not required if display is not being used, so I don't
think we need to back-port to older versions via "Fixes" tag... unless I
am missing a deeper point you were trying to make?
If so, let me know, and I will post a new version with the said tag.
Regards
Aradhya
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-03 6:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 17:34 [PATCH v3 0/8] arm64: ti: k3-am62: Add display support Aradhya Bhatia
2023-07-28 17:34 ` [PATCH v3 1/8] arm64: dts: ti: k3-am62x-sk-common: Update main-i2c1 frequency Aradhya Bhatia
2023-07-30 16:30 ` Nishanth Menon
2023-08-03 6:34 ` Aradhya Bhatia [this message]
2023-07-28 17:34 ` [PATCH v3 2/8] arm64: dts: ti: k3-am62-main: Add node for DSS Aradhya Bhatia
2023-08-03 14:14 ` Francesco Dolcini
2023-07-28 17:34 ` [PATCH v3 3/8] arm64: dts: ti: k3-am62x-sk-common: Add DSS pinmux info Aradhya Bhatia
2023-07-30 16:31 ` Nishanth Menon
2023-07-28 17:34 ` [PATCH v3 4/8] arm64: dts: ti: k3-am62x-sk-common: Add HDMI support Aradhya Bhatia
2023-07-28 17:34 ` [PATCH v3 5/8] arm64: dts: ti: am62x-sk: Add overlay for HDMI audio Aradhya Bhatia
2023-07-28 17:34 ` [PATCH v3 6/8] arm64: dts: ti: k3-am625-beagleplay: Add DSS pinmux info Aradhya Bhatia
2023-07-30 16:33 ` Nishanth Menon
2023-08-03 6:37 ` Aradhya Bhatia
2023-07-28 17:34 ` [PATCH v3 7/8] arm64: dts: ti: k3-am625-beagleplay: Add HDMI support Aradhya Bhatia
2023-07-28 17:34 ` [PATCH v3 8/8] arm64: defconfig: Enable ITE_IT66121 HDMI transmitter Aradhya Bhatia
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=eea30962-0ec6-b967-7764-e57c9d6c75fa@ti.com \
--to=a-bhatia1@ti.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j-choudhary@ti.com \
--cc=j-luthra@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=r-ravikumar@ti.com \
--cc=robh+dt@kernel.org \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=vigneshr@ti.com \
/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