From: Quentin Schulz <quentin.schulz@cherry.de>
To: Heiko Stuebner <heiko@sntech.de>
Cc: andy.yan@rock-chips.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Heiko Stuebner <heiko.stuebner@cherry.de>
Subject: Re: [PATCH 1/2] drm/rockchip: lvds: move pclk preparation in with clk_get
Date: Fri, 28 Feb 2025 18:19:54 +0100 [thread overview]
Message-ID: <521cb717-68a4-43ce-84fa-580fcd8cd50b@cherry.de> (raw)
In-Reply-To: <20250228165755.405138-2-heiko@sntech.de>
Hi Heiko,
On 2/28/25 5:57 PM, Heiko Stuebner wrote:
> From: Heiko Stuebner <heiko.stuebner@cherry.de>
>
> The LVDS block needs a separate pclk only on some socs, so currently
> requests and prepares it in the soc-specific probe function, but common
> code is required to unprepare it in the error path or on driver remove.
>
> While this works because clk_unprepare just does nothing if clk is NULL,
> this mismatch of who is responsible still is not very nice.
> The clock-framework already has a helper for clk-get-and-prepare even
> with devres support in devm_clk_get_prepared().
>
> This will get and prepare the clock and also unprepare it on driver
> removal, saving the driver from having to handle it "manually".
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@cherry.de>
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Small nitpick below.
> ---
> drivers/gpu/drm/rockchip/rockchip_lvds.c | 17 ++---------------
> 1 file changed, 2 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/gpu/drm/rockchip/rockchip_lvds.c b/drivers/gpu/drm/rockchip/rockchip_lvds.c
> index 385cf6881504..c19b7b1f6cb5 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_lvds.c
> +++ b/drivers/gpu/drm/rockchip/rockchip_lvds.c
> @@ -448,13 +448,11 @@ struct drm_encoder_helper_funcs px30_lvds_encoder_helper_funcs = {
> static int rk3288_lvds_probe(struct platform_device *pdev,
> struct rockchip_lvds *lvds)
> {
> - int ret;
> -
> lvds->regs = devm_platform_ioremap_resource(pdev, 0);
> if (IS_ERR(lvds->regs))
> return PTR_ERR(lvds->regs);
>
> - lvds->pclk = devm_clk_get(lvds->dev, "pclk_lvds");
> + lvds->pclk = devm_clk_get_prepared(lvds->dev, "pclk_lvds");
> if (IS_ERR(lvds->pclk)) {
> DRM_DEV_ERROR(lvds->dev, "could not get pclk_lvds\n");
Should we say
Could not get or prepare pclk_lvds\n
instead?
Thanks!
Quentin
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-02-28 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 16:57 [PATCH 0/2] drm/rockchip: lvds: probe logging improvements Heiko Stuebner
2025-02-28 16:57 ` [PATCH 1/2] drm/rockchip: lvds: move pclk preparation in with clk_get Heiko Stuebner
2025-02-28 17:19 ` Quentin Schulz [this message]
2025-02-28 16:57 ` [PATCH 2/2] drm/rockchip: lvds: Hide scary error messages on probe deferral Heiko Stuebner
2025-02-28 17:42 ` Quentin Schulz
2025-02-28 17:45 ` Heiko Stübner
2025-02-28 17:55 ` Quentin Schulz
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=521cb717-68a4-43ce-84fa-580fcd8cd50b@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=andy.yan@rock-chips.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko.stuebner@cherry.de \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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