[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <CSCPKPC8OB80.1TTBCM3YDVJQ5@void.crly.cz>
Date: Wed, 03 May 2023 16:22:32 +0200
From: "Roman Beranek" <me@...y.cz>
To: "Frank Oltmanns" <frank@...manns.dev>,
"Maxime Ripard" <mripard@...nel.org>,
"Jernej Skrabec" <jernej.skrabec@...il.com>
Cc: "Chen-Yu Tsai" <wens@...e.org>, "David Airlie" <airlied@...il.com>,
"Daniel Vetter" <daniel@...ll.ch>,
"Samuel Holland" <samuel@...lland.org>,
"Ondrej Jirman" <megi@....cz>, <dri-devel@...ts.freedesktop.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-sunxi@...ts.linux.dev>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/7] drm: sun4i: set proper TCON0 DCLK rate in DSI
mode
Hello everyone,
I apologize for my absence from the discussion during past week, I got
hit with tonsillitis.
On Mon May 1, 2023 at 3:40 PM CEST, Frank Oltmanns wrote:
> Looking at ccu_nkm_determine_rate(), we've found our culprit because it
> does not try parent clock rates other than the current one. The same
> applies to all other ccu_nkm_* functions.
Yes, that's why I dropped CLK_SET_RATE_PARENT from pll-mipi in v3.
> b. Add functionality to ccu_nkm_* to also update the parent clock rate.
>
> I'm actually interested in tackling b, but I can't make any promises as
> to if and when I'll be able to solve it. I'm not certain about any side
> effects this might have.
It sounds like an interesting exercise. But what if HDMI is then added
to the mix?
Best regards
Roman
Powered by blists - more mailing lists