linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Brian Masney <bmasney@redhat.com>
To: Vinod Koul <vkoul@kernel.org>,
	Kishon Vijay Abraham I <kishon@kernel.org>,
	Chun-Kuang Hu <chunkuang.hu@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Chunfeng Yun <chunfeng.yun@mediatek.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Heiko Stuebner <heiko@sntech.de>
Cc: linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v2 0/9] phy: convert from clk round_rate() to determine_rate()
Date: Thu, 16 Oct 2025 12:21:47 -0400	[thread overview]
Message-ID: <aPEbm5qK8-hkV3w_@redhat.com> (raw)
In-Reply-To: <20250810-phy-clk-round-rate-v2-0-9162470bb9f2@redhat.com>

Hi Vinod,

On Sun, Aug 10, 2025 at 06:45:28PM -0400, Brian Masney wrote:
> The round_rate() clk ops is deprecated in the clk framework in favor
> of the determine_rate() clk ops, so let's go ahead and convert the
> drivers in the phy subsystem using the Coccinelle semantic patch
> posted below. I did a few minor cosmetic cleanups of the code in a
> few cases.

I'm hoping to get this series merged so that we can remove the round_rate()
clk op from the clk core. The clk maintainer (Stephen) mentioned this work
in his last pull to Linus.

https://lore.kernel.org/linux-clk/20251007051720.11386-1-sboyd@kernel.org/

Thanks,

Brian



      parent reply	other threads:[~2025-10-16 16:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-10 22:45 [PATCH v2 0/9] phy: convert from clk round_rate() to determine_rate() Brian Masney
2025-08-10 22:45 ` [PATCH v2 1/9] phy: freescale: phy-fsl-samsung-hdmi: convert from " Brian Masney
2025-08-10 22:45 ` [PATCH v2 2/9] phy: mediatek: phy-mtk-hdmi-mt2701: " Brian Masney
2025-08-20 16:29   ` Vinod Koul
2025-08-20 17:27     ` Brian Masney
2025-09-09 13:45       ` Brian Masney
2025-08-10 22:45 ` [PATCH v2 3/9] phy: mediatek: phy-mtk-hdmi-mt8173: " Brian Masney
2025-08-10 22:45 ` [PATCH v2 4/9] phy: mediatek: phy-mtk-hdmi-mt8195: " Brian Masney
2025-08-10 22:45 ` [PATCH v2 5/9] phy: mediatek: phy-mtk-mipi-dsi-mt8173: " Brian Masney
2025-08-10 22:45 ` [PATCH v2 6/9] phy: mediatek: phy-mtk-mipi-dsi-mt8183: " Brian Masney
2025-08-10 22:45 ` [PATCH v2 7/9] phy: rockchip: phy-rockchip-inno-hdmi: " Brian Masney
2025-10-20 14:06   ` Heiko Stuebner
2025-08-10 22:45 ` [PATCH v2 8/9] phy: rockchip: phy-rockchip-samsung-hdptx: " Brian Masney
2025-08-14 16:36   ` Cristian Ciocaltea
2025-10-20 14:06   ` Heiko Stuebner
2025-08-10 22:45 ` [PATCH v2 9/9] phy: ti: phy-j721e-wiz: " Brian Masney
2025-10-16 16:21 ` Brian Masney [this message]

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=aPEbm5qK8-hkV3w_@redhat.com \
    --to=bmasney@redhat.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chunfeng.yun@mediatek.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=heiko@sntech.de \
    --cc=kishon@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=p.zabel@pengutronix.de \
    --cc=vkoul@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).