From: Stefan Agner <stefan@agner.ch>
To: narmstrong@baylibre.com, linux-amlogic@lists.infradead.org,
linux-media@vger.kernel.org
Subject: HDMI CEC on ODROID-N2+
Date: Thu, 13 Jan 2022 15:36:38 +0100 [thread overview]
Message-ID: <d2ef8936c54567c9c2652b3c53a82f68@agner.ch> (raw)
Hi Neil,
I am trying to use HDMI CEC on ODROID-N2+ using Linux 5.10.91. However,
I was unsuccessful: As far as I can tell cec-client uses the right
device (I disabled CONFIG_DRM_DW_HDMI_CEC since my kernel is still
missing your patch "drm/meson: dw-hdmi: disable DW-HDMI CEC
sub-driver"). But communication won't work, and dmesg prints timeout
messages:
[ 68.831253] cec-meson_g12a_ao_cec: message ff 84 20 00 06 timed out
[ 71.134987] cec-meson_g12a_ao_cec: message ff 87 00 15 82 timed out
[ 73.438826] cec-meson_g12a_ao_cec: message f0 timed out
[ 75.742677] cec-meson_g12a_ao_cec: message f0 timed out
[ 78.046555] cec-meson_g12a_ao_cec: message f0 timed out
[ 80.350446] cec-meson_g12a_ao_cec: message f0 timed out
[ 82.654358] cec-meson_g12a_ao_cec: message 11 timed out
[ 84.958285] cec-meson_g12a_ao_cec: message 11 timed out
[ 87.262194] cec-meson_g12a_ao_cec: message 11 timed out
[ 89.566130] cec-meson_g12a_ao_cec: message 11 timed out
I did a quick test with CoreELEC which uses the 4.9 downstream kernel,
CEC seems to work there. So it does not seem to be my hardware setup.
A quick test with the latest Linux 5.16 shows the same errors.
Do you happen to have an idea? Do you know if HDMI CEC using upstream
kernels worked at one point on that particular platform?
--
Stefan
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2022-01-13 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 14:36 Stefan Agner [this message]
2022-01-13 15:52 ` Neil Armstrong
2022-01-15 10:02 ` (EXT) " Alexander Stein
2022-01-15 10:52 ` Stefan Agner
2022-01-15 13:28 ` Stefan Agner
2022-01-16 10:14 ` Alexander Stein
2022-01-16 10:50 ` Stefan Agner
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=d2ef8936c54567c9c2652b3c53a82f68@agner.ch \
--to=stefan@agner.ch \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=narmstrong@baylibre.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
all inboxes | Powered by JetHome®