linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jernej Skrabec <jernej.skrabec@gmail.com>
To: mripard@kernel.org, wens@csie.org
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
	Jernej Skrabec <jernej.skrabec@gmail.com>
Subject: [PATCH 0/2] dts: Add CEC clock to DW HDMI
Date: Sat, 20 Nov 2021 08:34:46 +0100	[thread overview]
Message-ID: <20211120073448.32480-1-jernej.skrabec@gmail.com> (raw)

Experimentation proved that CEC controller in H3-like DW-HDMI core
depends on 32 kHz clock output from RTC. If board has external 32768 Hz
crystal, HDMI CEC always work. However, if external crystal is missing
and 32 kHz clock is generated by internal oscillator, CEC communication
may or may not work, depending on accuracy. Changing internal oscillator
prescaler can make CEC work.

This was totally missed when implementing HDMI support, because user
manual has no CEC information besides the fact that it exists.

Please take a look.

Best regards,
Jernej

Jernej Skrabec (2):
  arm64: dts: allwinner: a64: Add CEC clock to HDMI
  ARM: dts: sunxi: Add CEC clock to DW-HDMI

 arch/arm/boot/dts/sun8i-r40.dtsi              | 4 ++--
 arch/arm/boot/dts/sunxi-h3-h5.dtsi            | 4 ++--
 arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)

-- 
2.34.0


             reply	other threads:[~2021-11-20  7:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-20  7:34 Jernej Skrabec [this message]
2021-11-20  7:34 ` [PATCH 1/2] arm64: dts: allwinner: a64: Add CEC clock to HDMI Jernej Skrabec
2021-11-20  7:34 ` [PATCH 2/2] ARM: dts: sunxi: Add CEC clock to DW-HDMI Jernej Skrabec
2021-11-22  9:07 ` [PATCH 0/2] dts: Add CEC clock to DW HDMI Maxime Ripard

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=20211120073448.32480-1-jernej.skrabec@gmail.com \
    --to=jernej.skrabec@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=mripard@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=wens@csie.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).