From: Philippe CORNU <philippe.cornu@foss.st.com>
To: Yannick FERTRE <yannick.fertre@foss.st.com>,
Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: <dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 3/3] drm/stm: ltdc: add lvds pixel clock
Date: Fri, 28 Jun 2024 14:45:34 +0200 [thread overview]
Message-ID: <422a643f-1035-6be1-607c-85c43e2cf148@foss.st.com> (raw)
In-Reply-To: <7cdeaaab-ab8f-4b0c-89ec-cb61764a4abb@foss.st.com>
On 6/21/24 16:55, Yannick FERTRE wrote:
> Hi Raphaël,
>
> Thanks for your patch, it will not merged due to a new clock management.
>
> Philippe,
>
> this patch will be replaced by another which manages all clocks that the
> display controller
>
> will need (pixel clock, bus clock reference clock).
Hi Raphaël & Yannick,
I applied 1 & 2 on drm-misc-next.
Many thanks,
Philippe :-)
>
>
> Best regards
>
>
> Le 26/02/2024 à 11:48, Raphael Gallais-Pou a écrit :
>> The STM32MP25x display subsystem presents a mux which feeds the loopback
>> pixel clock of the current bridge in use into the LTDC. This mux is only
>> accessible through sysconfig registers which is not yet available in the
>> STM32MP25x common clock framework.
>>
>> While waiting for a complete update of the clock framework, this would
>> allow to use the LVDS.
>>
>> Signed-off-by: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
>> Signed-off-by: Yannick Fertre <yannick.fertre@foss.st.com>
>> ---
>> Changes in v2:
>> - Fixed my address
>> - Fixed smatch warning
>> ---
>> drivers/gpu/drm/stm/ltdc.c | 19 +++++++++++++++++++
>> drivers/gpu/drm/stm/ltdc.h | 1 +
>> 2 files changed, 20 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/stm/ltdc.c b/drivers/gpu/drm/stm/ltdc.c
>> index 5576fdae4962..23011a8913bd 100644
>> --- a/drivers/gpu/drm/stm/ltdc.c
>> +++ b/drivers/gpu/drm/stm/ltdc.c
>> @@ -838,6 +838,12 @@ ltdc_crtc_mode_valid(struct drm_crtc *crtc,
>> int target_max = target + CLK_TOLERANCE_HZ;
>> int result;
>> + if (ldev->lvds_clk) {
>> + result = clk_round_rate(ldev->lvds_clk, target);
>> + DRM_DEBUG_DRIVER("lvds pixclk rate target %d, available %d\n",
>> + target, result);
>> + }
>> +
>> result = clk_round_rate(ldev->pixel_clk, target);
>> DRM_DEBUG_DRIVER("clk rate target %d, available %d\n", target,
>> result);
>> @@ -1896,6 +1902,8 @@ void ltdc_suspend(struct drm_device *ddev)
>> DRM_DEBUG_DRIVER("\n");
>> clk_disable_unprepare(ldev->pixel_clk);
>> + if (ldev->lvds_clk)
>> + clk_disable_unprepare(ldev->lvds_clk);
>> }
>> int ltdc_resume(struct drm_device *ddev)
>> @@ -1910,6 +1918,13 @@ int ltdc_resume(struct drm_device *ddev)
>> DRM_ERROR("failed to enable pixel clock (%d)\n", ret);
>> return ret;
>> }
>> + if (ldev->lvds_clk) {
>> + if (clk_prepare_enable(ldev->lvds_clk)) {
>> + clk_disable_unprepare(ldev->pixel_clk);
>> + DRM_ERROR("Unable to prepare lvds clock\n");
>> + return -ENODEV;
>> + }
>> + }
>> return 0;
>> }
>> @@ -1981,6 +1996,10 @@ int ltdc_load(struct drm_device *ddev)
>> }
>> }
>> + ldev->lvds_clk = devm_clk_get(dev, "lvds");
>> + if (IS_ERR(ldev->lvds_clk))
>> + ldev->lvds_clk = NULL;
>> +
>> rstc = devm_reset_control_get_exclusive(dev, NULL);
>> mutex_init(&ldev->err_lock);
>> diff --git a/drivers/gpu/drm/stm/ltdc.h b/drivers/gpu/drm/stm/ltdc.h
>> index 9d488043ffdb..4a60ce5b610c 100644
>> --- a/drivers/gpu/drm/stm/ltdc.h
>> +++ b/drivers/gpu/drm/stm/ltdc.h
>> @@ -44,6 +44,7 @@ struct ltdc_device {
>> void __iomem *regs;
>> struct regmap *regmap;
>> struct clk *pixel_clk; /* lcd pixel clock */
>> + struct clk *lvds_clk; /* lvds pixel clock */
>> struct mutex err_lock; /* protecting error_status */
>> struct ltdc_caps caps;
>> u32 irq_status;
>>
prev parent reply other threads:[~2024-06-28 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 10:48 [PATCH v6 0/3] Introduce STM32 LVDS driver Raphael Gallais-Pou
2024-02-26 10:48 ` [PATCH v6 1/3] dt-bindings: display: add STM32 LVDS device Raphael Gallais-Pou
2024-03-18 15:22 ` Yannick FERTRE
2024-02-26 10:48 ` [PATCH v6 2/3] drm/stm: lvds: add new STM32 LVDS Display Interface Transmitter driver Raphael Gallais-Pou
2024-03-18 15:26 ` Yannick FERTRE
2024-02-26 10:48 ` [PATCH v6 3/3] drm/stm: ltdc: add lvds pixel clock Raphael Gallais-Pou
2024-06-21 14:55 ` Yannick FERTRE
2024-06-28 12:45 ` Philippe CORNU [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=422a643f-1035-6be1-607c-85c43e2cf148@foss.st.com \
--to=philippe.cornu@foss.st.com \
--cc=airlied@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=raphael.gallais-pou@foss.st.com \
--cc=robh+dt@kernel.org \
--cc=tzimmermann@suse.de \
--cc=yannick.fertre@foss.st.com \
/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).