From: "Andy Yan" <andyshrk@163.com>
To: "Dragan Simic" <dsimic@manjaro.org>
Cc: linux-rockchip@lists.infradead.org,
dri-devel@lists.freedesktop.org, heiko@sntech.de,
hjc@rock-chips.com, andy.yan@rock-chips.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re:[PATCH] drm/rockchip: cdn-dp: Remove redundant workarounds for firmware loading
Date: Thu, 4 Jul 2024 10:10:01 +0800 (CST) [thread overview]
Message-ID: <109c6f19.2559.1907b817a99.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <9b7a9e9b88ad8c7489ee1b4c70b8751eeb5cf6f9.1720049413.git.dsimic@manjaro.org>
Hi Dragan,
At 2024-07-04 07:32:02, "Dragan Simic" <dsimic@manjaro.org> wrote:
>After the additional firmware-related module information was introduced by
>the commit c0677e41a47f ("drm/rockchip: cdn-dp-core: add MODULE_FIRMWARE
>macro"), there's no longer need for the firmware-loading workarounds whose
>sole purpose was to prevent the missing firmware blob in an initial ramdisk
>from causing driver initialization to fail. Thus, delete the workarounds,
>which removes a sizable chunk of redundant code.
What would happen if there was no ramdisk? And the firmware is in rootfs ?
For example: A buildroot based tiny embedded system。
>
>Various utilities used by Linux distributions to generate initial ramdisks
>need to obey the firmware-related module information, so we can rely on the
>firmware blob being present in the generated initial ramdisks.
>
>Signed-off-by: Dragan Simic <dsimic@manjaro.org>
>---
> drivers/gpu/drm/rockchip/cdn-dp-core.c | 53 +++++---------------------
> 1 file changed, 10 insertions(+), 43 deletions(-)
>
>diff --git a/drivers/gpu/drm/rockchip/cdn-dp-core.c b/drivers/gpu/drm/rockchip/cdn-dp-core.c
>index bd7aa891b839..e1a7c6a1172b 100644
>--- a/drivers/gpu/drm/rockchip/cdn-dp-core.c
>+++ b/drivers/gpu/drm/rockchip/cdn-dp-core.c
>@@ -44,9 +44,9 @@ static inline struct cdn_dp_device *encoder_to_dp(struct drm_encoder *encoder)
> #define DPTX_HPD_DEL (2 << 12)
> #define DPTX_HPD_SEL_MASK (3 << 28)
>
>-#define CDN_FW_TIMEOUT_MS (64 * 1000)
> #define CDN_DPCD_TIMEOUT_MS 5000
> #define CDN_DP_FIRMWARE "rockchip/dptx.bin"
>+
> MODULE_FIRMWARE(CDN_DP_FIRMWARE);
>
> struct cdn_dp_data {
>@@ -909,61 +909,28 @@ static int cdn_dp_audio_codec_init(struct cdn_dp_device *dp,
> return PTR_ERR_OR_ZERO(dp->audio_pdev);
> }
>
>-static int cdn_dp_request_firmware(struct cdn_dp_device *dp)
>-{
>- int ret;
>- unsigned long timeout = jiffies + msecs_to_jiffies(CDN_FW_TIMEOUT_MS);
>- unsigned long sleep = 1000;
>-
>- WARN_ON(!mutex_is_locked(&dp->lock));
>-
>- if (dp->fw_loaded)
>- return 0;
>-
>- /* Drop the lock before getting the firmware to avoid blocking boot */
>- mutex_unlock(&dp->lock);
>-
>- while (time_before(jiffies, timeout)) {
>- ret = request_firmware(&dp->fw, CDN_DP_FIRMWARE, dp->dev);
>- if (ret == -ENOENT) {
>- msleep(sleep);
>- sleep *= 2;
>- continue;
>- } else if (ret) {
>- DRM_DEV_ERROR(dp->dev,
>- "failed to request firmware: %d\n", ret);
>- goto out;
>- }
>-
>- dp->fw_loaded = true;
>- ret = 0;
>- goto out;
>- }
>-
>- DRM_DEV_ERROR(dp->dev, "Timed out trying to load firmware\n");
>- ret = -ETIMEDOUT;
>-out:
>- mutex_lock(&dp->lock);
>- return ret;
>-}
>-
> static void cdn_dp_pd_event_work(struct work_struct *work)
> {
> struct cdn_dp_device *dp = container_of(work, struct cdn_dp_device,
> event_work);
> struct drm_connector *connector = &dp->connector;
> enum drm_connector_status old_status;
>-
> int ret;
>
> mutex_lock(&dp->lock);
>
> if (dp->suspended)
> goto out;
>
>- ret = cdn_dp_request_firmware(dp);
>- if (ret)
>- goto out;
>+ if (!dp->fw_loaded) {
>+ ret = request_firmware(&dp->fw, CDN_DP_FIRMWARE, dp->dev);
>+ if (ret) {
>+ DRM_DEV_ERROR(dp->dev, "Loading firmware failed: %d\n", ret);
>+ goto out;
>+ }
>+
>+ dp->fw_loaded = true;
>+ }
>
> dp->connected = true;
>
next prev parent reply other threads:[~2024-07-04 2:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 23:32 [PATCH] " Dragan Simic
2024-07-04 2:10 ` Andy Yan [this message]
2024-07-04 10:35 ` Dragan Simic
2024-07-08 7:46 ` Andy Yan
2024-07-08 9:51 ` Maxime Ripard
2024-07-09 8:17 ` Dragan Simic
2024-07-09 9:10 ` Andy Yan
2024-07-09 10:10 ` Dragan Simic
2024-07-09 10:46 ` Andy Yan
2024-07-09 16:26 ` Dragan Simic
2024-07-09 11:09 ` Maxime Ripard
2024-07-09 16:36 ` Dragan Simic
2024-07-10 7:13 ` Maxime Ripard
2024-07-10 14:22 ` Dragan Simic
2024-07-11 10:51 ` Maxime Ripard
2024-09-12 12:42 ` walker
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=109c6f19.2559.1907b817a99.Coremail.andyshrk@163.com \
--to=andyshrk@163.com \
--cc=airlied@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--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
all inboxes | Powered by JetHome®