On Thu, Oct 23, 2025 at 10:20:41AM +0200, Geert Uytterhoeven wrote: > Hi Laurent, > > On Tue, 21 Oct 2025 at 20:45, Laurent Pinchart > <[email protected]> wrote: > > On Tue, Oct 21, 2025 at 07:26:49PM +0100, Lad, Prabhakar wrote: > > > On Tue, Oct 21, 2025 at 11:26 AM Geert Uytterhoeven wrote: > > > > On Wed, 15 Oct 2025 at 21:26, Prabhakar <[email protected]> > > > > wrote: > > > > > This patch series adds DU/DSI clocks and provides support for the > > > > > MIPI DSI interface on the RZ/V2H(P) SoC. > > > > > > > > > > v10->v11: > > > > > - Split CPG_PLL_CLK1_K/M/PDIV macro change into separate patch > > > > > - Updated rzv2h_cpg_plldsi_div_determine_rate() > > > > > while iterating over the divider table > > > > > - Added Acked-by tag from Tomi for patch 2/7 and 3/7 > > > > > - Added Reviewed-by tag from Geert for patch 2/7 and 3/7 > > > > > > > > I think this series is ready for merging. > > > > > > \o/ > > > > > > > > Lad Prabhakar (7): > > > > > clk: renesas: rzv2h-cpg: Add instance field to struct pll > > > > > clk: renesas: rzv2h-cpg: Use GENMASK for PLL fields > > > > > clk: renesas: rzv2h-cpg: Add support for DSI clocks > > > > > clk: renesas: r9a09g057: Add clock and reset entries for DSI and > > > > > LCDC > > > > > dt-bindings: display: bridge: renesas,dsi: Document RZ/V2H(P) and > > > > > RZ/V2N > > > > > drm: renesas: rz-du: mipi_dsi: Add LPCLK clock support > > > > > drm: renesas: rz-du: mipi_dsi: Add support for RZ/V2H(P) SoC > > > > > > > > As this touches both clk and drm, let's discuss the merge strategy. > > > > My proposal: > > > > 1. I queue patches 1-3 in an immutable branch with a signed tag, > > > > to be used as a base for the remaining patches, > > > > 2. I queue patch 4 on top of 1 in renesas-clk for v6.19, > > > > 3. The DRM people queue patches 5-7 on top of 1. > > > > > > > > Does that sound fine for you? > > > Sounds good to me. > > > > > > Biju/Tomi, are you OK with the above? > > > > The plan seems good to me. Note that you won't be able to push this > > yourself to drm-misc as committers are limited to pushing linear > > branches. We need an ack from the drm-misc maintainers, and one of them > > Do you mean new commits must be in a single branch, or drm-misc > itself must be linear? In case of the former, 5-7 can be applied on top of > my immutable branch, without involving a merge?
drm-misc must be linear, committers must rebase patches on the drm-misc-next branch before pushing. > > will need to merge the branch (either branch 1. as prepared by Geert, on > > top of which you can them push patches 5-7 yourself, or a branch you'll > > prepare on top of 1. with patches 5-7). > > Note that another change to include/linux/clk/renesas.h, > and thus a dependency of drm on clk, is coming in > "[PATCH v3 0/2] Remove hard coded values for MIPI-DSI" > https://lore.kernel.org/[email protected] > > Would it be worthwhile to wait on/speed up review of the latter? Nobody will complain about reviews being sped up :-) -- Regards, Laurent Pinchart
