From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 372842FFDE3 for ; Mon, 11 May 2026 16:18:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778516335; cv=none; b=RKRyYrUmszydCTvL5I/a9vZxFic2ngtju6uxIBu4gUv32HXu2ph6CymP0xsEna/499SIA9HKItZz348K0NPJjg30udyL4afw4/KfDrd7MIvQI+wje37lHhOo680hV62hd5wpKl8OVyGGmkj5rBznkY/3S+X7SWOjU8LWX4CNviM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778516335; c=relaxed/simple; bh=U42E3LWzv0TbWP6oMpvlSaV2MRzXzGekhXV6lEcRbbw=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=D9Aa/xsY4PRiT+0iJpk9UoPvTjtKSxzDYymR4gCyge+dHefmjNRjOyIF/aNRGEwQ77T1VbkXg0QNQNw6T6/h29YfXuE4Hz92cScOIqY6SN+10fyGNCKCGmEKr+QFTyWoO6HSYTQJC71LGShNw/IZjcDuqecKgmXx9N3BlCa9ruI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=bp5Iggbt; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="bp5Iggbt" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4F270C2BCB0; Mon, 11 May 2026 16:18:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1778516334; bh=U42E3LWzv0TbWP6oMpvlSaV2MRzXzGekhXV6lEcRbbw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=bp5IggbtfeBSdhgblUSlx5B9HKMPMNBePGqseTxadNe/RW825h2Z3OeVKgEDn3tcd xR3p4DuwGz3q9YXyxWYPblbXKoiI/tl6KzE3P2pfCLBgMHVySY/JLfAe77NL7aVBJZ Gp6TKLJ0a/MSOsI9UmCKZJxU020GgO6lwRQs3sLdLbdgfXGNyewkbUCc91qq4YOKDu xvMiYzOipBjq2iJvWHbxoWmxAFedqQd4iXjrt6KNElYEJ2qH5z+Bk0UQHqR4IxMIrx 9MQmVrHtTuLRxBojQCIvevJ6espW6NozkWG+87beE1gvTi9gls3oCzx98M5NWzqzuz t/g6f7FJAkwVg== Date: Mon, 11 May 2026 21:48:51 +0530 From: Vinod Koul To: Cristian Ciocaltea Cc: Neil Armstrong , Heiko Stuebner , Algea Cao , Dmitry Baryshkov , kernel@collabora.com, linux-phy@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/6] phy: rockchip: samsung-hdptx: Clock fixes and API transition cleanups Message-ID: References: <20260227-hdptx-clk-fixes-v1-0-f998f2762d0f@collabora.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On 10-05-26, 11:55, Cristian Ciocaltea wrote: > Hi Vinod, > > On 5/10/26 10:36 AM, Vinod Koul wrote: > > On 27-02-26, 22:48, Cristian Ciocaltea wrote: > >> This series provides a set of bug fixes and cleanups for the Rockchip > >> Samsung HDPTX PHY driver. > >> > >> The first part of the series (i.e. PATCH 1 & 2) addresses clock rate > >> calculation and synchronization issues. Specifically, it fixes edge > >> cases where the PHY PLL is pre-programmed by an external component (like > >> a bootloader) or when changing the color depth (bpc) while keeping the > >> modeline constant. Because the Common Clock Framework .set_rate() > >> callback might not be invoked if the pixel clock remains unchanged, this > >> previously led to out-of-sync states between CCF and the actual HDMI PHY > >> configuration. > >> > >> The second part focuses on code cleanups and modernizing the register > >> access. Now that dw_hdmi_qp driver has fully switched to using > >> phy_configure(), we can drop the deprecated TMDS rate setup workarounds > >> and the restrict_rate_change flag logic. Finally, it refactors the > >> driver to consistently use standard bitfield macros. > > > > Sorry looks like I have missed to review this one. > > Can you please rebase on phy/fixes and send... > > I've just verified and it applies cleanly on top of phy/fixes. > Do you still need a resend? Yes please, it didnt apply for me -- ~Vinod