From: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
To: Peter Geis <pgwipeout@gmail.com>
Cc: "Andrzej Hajda" <andrzej.hajda@intel.com>,
"Neil Armstrong" <narmstrong@baylibre.com>,
"Robert Foss" <robert.foss@linaro.org>,
"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
"Jonas Karlman" <jonas@kwiboo.se>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Pierre-Hugues Husson" <phh@phh.me>,
"Archit Taneja" <architt@codeaurora.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Robin Murphy" <robin.murphy@arm.com>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"Heiko Stübner" <heiko@sntech.de>,
dri-devel@lists.freedesktop.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/bridge: synopsys/dw-hdmi: set cec clock rate
Date: Sun, 13 Mar 2022 17:14:49 +0100 [thread overview]
Message-ID: <E86F11A4-011B-43ED-90D2-BB6BA9353A3F@gmail.com> (raw)
In-Reply-To: <CAMdYzYq06QSmFAwCuTmBYy4LfQAQDxzx2PGc8HOB1iEjxXHGyg@mail.gmail.com>
> Wiadomość napisana przez Peter Geis <pgwipeout@gmail.com> w dniu 13.03.2022, o godz. 13:56:
>
>>
>
> I was worried about that, thanks for testing it.
> Can you send me the cec_clk rate before and after this patch?
>
Here it is:
working:
enable prepare protect duty hardware
clock count count count rate accuracy phase cycle enable
-------------------------------------------------------------------------------------------------------
clk_hdmi_cec 1 2 0 32743 0 0 50000 Y
non-working:
enable prepare protect duty hardware
clock count count count rate accuracy phase cycle enable
-------------------------------------------------------------------------------------------------------
clk_hdmi_cec 1 2 0 32768 0 0 50000 Y
dmesg
[ 52.745988] cec-dw_hdmi: message 44 timed out
[ 54.879307] cec-dw_hdmi: message 44 timed out
[ 57.012654] cec-dw_hdmi: message 88 timed out
[ 59.145973] cec-dw_hdmi: message 88 timed out
player:
2022-03-13 11:04:40.938355 E CECAdapter: CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=22
2022-03-13 11:04:40.938366 E CECAdapter: CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=22
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2022-03-13 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 20:24 [PATCH] drm/bridge: synopsys/dw-hdmi: set cec clock rate Peter Geis
2022-01-26 20:32 ` Fabio Estevam
2022-01-27 9:33 ` Sascha Hauer
2022-01-28 19:03 ` Peter Geis
2022-03-13 10:12 ` Piotr Oniszczuk
2022-03-13 12:56 ` Peter Geis
2022-03-13 16:14 ` Piotr Oniszczuk [this message]
2022-03-14 11:31 ` Robin Murphy
2022-03-14 16:34 ` Robin Murphy
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=E86F11A4-011B-43ED-90D2-BB6BA9353A3F@gmail.com \
--to=piotr.oniszczuk@gmail.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=andrzej.hajda@intel.com \
--cc=architt@codeaurora.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=narmstrong@baylibre.com \
--cc=pgwipeout@gmail.com \
--cc=phh@phh.me \
--cc=robert.foss@linaro.org \
--cc=robin.murphy@arm.com \
--cc=s.hauer@pengutronix.de \
/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