From: "Heiko Stübner" <heiko@sntech.de>
To: Dragan Simic <dsimic@manjaro.org>
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,
quentin.schulz@cherry.de,
Heiko Stuebner <heiko.stuebner@cherry.de>
Subject: Re: [PATCH v3 1/3] drm/rockchip: lvds: move pclk preparation in with clk_get
Date: Tue, 04 Mar 2025 22:11:18 +0100 [thread overview]
Message-ID: <3048640.Lt9SDvczpP@diego> (raw)
In-Reply-To: <041c5f0e2371817a27577bd0989b9dca@manjaro.org>
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
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Dragan Simic <dsimic@manjaro.org>
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,
quentin.schulz@cherry.de,
Heiko Stuebner <heiko.stuebner@cherry.de>
Subject: Re: [PATCH v3 1/3] drm/rockchip: lvds: move pclk preparation in with clk_get
Date: Tue, 04 Mar 2025 22:11:18 +0100 [thread overview]
Message-ID: <3048640.Lt9SDvczpP@diego> (raw)
In-Reply-To: <041c5f0e2371817a27577bd0989b9dca@manjaro.org>
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
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-03-04 22:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 12:44 [PATCH v3 0/3] drm/rockchip: lvds: probe logging improvements Heiko Stuebner
2025-03-04 12:44 ` Heiko Stuebner
2025-03-04 12:44 ` [PATCH v3 1/3] drm/rockchip: lvds: move pclk preparation in with clk_get Heiko Stuebner
2025-03-04 12:44 ` Heiko Stuebner
2025-03-04 20:30 ` Dragan Simic
2025-03-04 20:30 ` Dragan Simic
2025-03-04 21:11 ` Heiko Stübner [this message]
2025-03-04 21:11 ` Heiko Stübner
2025-03-04 12:44 ` [PATCH v3 2/3] drm/rockchip: lvds: Hide scary error messages on probe deferral Heiko Stuebner
2025-03-04 12:44 ` Heiko Stuebner
2025-03-04 14:59 ` Quentin Schulz
2025-03-04 14:59 ` Quentin Schulz
2025-03-04 12:44 ` [PATCH v3 3/3] drm/rockchip: lvds: lower log severity for missing pinctrl settings Heiko Stuebner
2025-03-04 12:44 ` Heiko Stuebner
2025-03-04 15:00 ` Quentin Schulz
2025-03-04 15:00 ` Quentin Schulz
2025-03-04 21:12 ` [PATCH v3 0/3] drm/rockchip: lvds: probe logging improvements Heiko Stuebner
2025-03-04 21:12 ` Heiko Stuebner
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=3048640.Lt9SDvczpP@diego \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dsimic@manjaro.org \
--cc=heiko.stuebner@cherry.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=quentin.schulz@cherry.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.