[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3048640.Lt9SDvczpP@diego>
Date: Tue, 04 Mar 2025 22:11:18 +0100
From: Heiko Stübner <heiko@...ech.de>
To: Dragan Simic <dsimic@...jaro.org>
Cc: andy.yan@...k-chips.com, maarten.lankhorst@...ux.intel.com,
mripard@...nel.org, tzimmermann@...e.de, dri-devel@...ts.freedesktop.org,
linux-arm-kernel@...ts.infradead.org, linux-rockchip@...ts.infradead.org,
linux-kernel@...r.kernel.org, quentin.schulz@...rry.de,
Heiko Stuebner <heiko.stuebner@...rry.de>
Subject:
Re: [PATCH v3 1/3] drm/rockchip: lvds: move pclk preparation in with clk_get
Am Dienstag, 4. März 2025, 21:30:22 MEZ schrieb Dragan Simic:
> Hello Heiko,
>
> On 2025-03-04 13:44, Heiko Stuebner wrote:
> > diff --git a/drivers/gpu/drm/rockchip/rockchip_lvds.c
> > b/drivers/gpu/drm/rockchip/rockchip_lvds.c
> > index 385cf6881504..ecfae8d5da89 100644
> > --- a/drivers/gpu/drm/rockchip/rockchip_lvds.c
> > +++ b/drivers/gpu/drm/rockchip/rockchip_lvds.c
> > @@ -448,15 +448,13 @@ 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");
> > + DRM_DEV_ERROR(lvds->dev, "could not get or prepare pclk_lvds\n");
>
> I'm wondering why this patch isn't replacing deprecated DRM
> logging macros with their preferred successors in a couple of
> places, just like what the patch 2/3 from this series does?
because this patch is about reorganizing the clock handling :-)
Changing the logging functions is a different topic and so has no place
in _this_ patch.
And of course drm-logging is a separate beast to tame altogether.
drm_err vs. dev_err; lvds->dev vs. drm_dev (there was an argument over
what belongs where recently) .
And I had neither the capacity nor time to delve into all that, so limited
myself to stuff I understood :-)
Heiko
Powered by blists - more mailing lists