[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <32481efc439b66da6d109e1484255aaf@manjaro.org>
Date: Mon, 17 Jun 2024 22:56:57 +0200
From: Dragan Simic <dsimic@...jaro.org>
To: Jonas Karlman <jonas@...boo.se>
Cc: Heiko Stübner <heiko@...ech.de>,
dri-devel@...ts.freedesktop.org, Michael Turquette
<mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>, Yakir Yang
<kuankuan.y@...il.com>, Jeffy Chen <jeffy.chen@...k-chips.com>,
linux-arm-kernel@...ts.infradead.org, linux-rockchip@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org
Subject: Re: [PATCH 02/13] clk: rockchip: Set parent rate for DCLK_VOP clock
on RK3228
On 2024-06-17 22:50, Jonas Karlman wrote:
> On 2024-06-17 22:30, Heiko Stübner wrote:
>> Am Samstag, 15. Juni 2024, 19:03:53 CEST schrieb Jonas Karlman:
>>> Similar to DCLK_LCDC on RK3328, the DCLK_VOP on RK3228 is typically
>>> parented by the hdmiphy clk and it is expected that the DCLK_VOP and
>>> hdmiphy clk rate are kept in sync.
>>>
>>> Use CLK_SET_RATE_PARENT and CLK_SET_RATE_NO_REPARENT flags, same as
>>> used
>>> on RK3328, to make full use of all possible supported display modes.
>>>
>>> Fixes: 0a9d4ac08ebc ("clk: rockchip: set the clock ids for RK3228
>>> VOP")
>>> Fixes: 307a2e9ac524 ("clk: rockchip: add clock controller for
>>> rk3228")
>>> Signed-off-by: Jonas Karlman <jonas@...boo.se>
>>
>> did your mailer have a hickup? Somehow I got patch2 (only this one)
>> 2 times
>
> Strange, not something I know about, each patch 1-13 are listed as 250
> Accepted (heiko@...ech.de) and patches arrived to the ML and patchwork:
>
> https://lore.kernel.org/all/20240615170417.3134517-1-jonas@kwiboo.se/
> https://patchwork.freedesktop.org/series/134926/
> https://patchwork.kernel.org/cover/13699322/
It might be that something is wrong with the MX host for sntech.de, I
got
one email rejected today with "invalid certificate" (or something like
that)
as the error message.
Powered by blists - more mailing lists