From: "Andy Yan" <andyshrk@163.com>
To: "Piotr Oniszczuk" <piotr.oniszczuk@gmail.com>
Cc: heiko@sntech.de, neil.armstrong@linaro.org,
sebastian.reichel@collabora.com, devicetree@vger.kernel.org,
hjc@rock-chips.com, mripard@kernel.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
yubing.zhang@rock-chips.com, dri-devel@lists.freedesktop.org,
"Andy Yan" <andy.yan@rock-chips.com>,
krzk+dt@kernel.org, robh@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re:Re: [PATCH 0/6] Add support for RK3588 DisplayPort Controller
Date: Thu, 6 Mar 2025 16:53:21 +0800 (CST) [thread overview]
Message-ID: <74c154b6.8c50.1956aa8c8d2.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <44213B17-FE14-4FB8-8319-1E31BBF6EAA0@gmail.com>
Hi,
在 2025-03-06 16:42:00,"Piotr Oniszczuk" <piotr.oniszczuk@gmail.com> 写道:
>
>
>> Wiadomość napisana przez Andy Yan <andyshrk@163.com> w dniu 6 mar 2025, o godz. 01:59:
>>
>>
>>
>>
>> Both of the two config options should be enabled.
>> andy@Pro480:~/WorkSpace/linux-next$ rg DW_DP .config
>> 4044:CONFIG_ROCKCHIP_DW_DP=y
>
>here i’m a bit lost….
>greping on full kernel sources (with applied https://patchwork.kernel.org/project/linux-rockchip/list/?series=936784) gives me no single appearance of ROCKCHIP_DW_DP…
>Do i miss something?
see PATCH 3/6:
diff --git a/drivers/gpu/drm/rockchip/Kconfig b/drivers/gpu/drm/rockchip/Kconfig
index 26c4410b2407..c8638baf9641 100644
--- a/drivers/gpu/drm/rockchip/Kconfig
+++ b/drivers/gpu/drm/rockchip/Kconfig
@@ -8,6 +8,7 @@ config DRM_ROCKCHIP
select DRM_PANEL
select VIDEOMODE_HELPERS
select DRM_ANALOGIX_DP if ROCKCHIP_ANALOGIX_DP
+ select DRM_DW_DP if ROCKCHIP_DW_DP
select DRM_DW_HDMI if ROCKCHIP_DW_HDMI
select DRM_DW_HDMI_QP if ROCKCHIP_DW_HDMI_QP
select DRM_DW_MIPI_DSI if ROCKCHIP_DW_MIPI_DSI
@@ -58,6 +59,12 @@ config ROCKCHIP_CDN_DP
RK3399 based SoC, you should select this
option.
+config ROCKCHIP_DW_DP
+ bool "Rockchip specific extensions for Synopsys DW DP"
+ help
+ Choose this option for Synopsys DesignWare Cores DisplayPort
+ transmit controller support on Rockchip SoC.
https://lore.kernel.org/linux-rockchip/047EECFC-7E55-44EC-896F-13FE04333E4D@gmail.com/T/#m178a325ea0ebc64187aae474d77c3f7a9e0bc93d
>
next prev parent reply other threads:[~2025-03-06 8:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 2:30 Re:Re: [PATCH 0/6] Add support for RK3588 DisplayPort Controller Andy Yan
2025-03-05 13:56 ` Piotr Oniszczuk
2025-03-06 0:59 ` Andy Yan
2025-03-06 8:42 ` Piotr Oniszczuk
2025-03-06 8:53 ` Andy Yan [this message]
2025-03-06 11:47 ` Piotr Oniszczuk
2025-03-06 12:15 ` Andy Yan
2025-03-06 14:08 ` Piotr Oniszczuk
2025-03-06 14:28 ` Piotr Oniszczuk
2025-03-07 0:48 ` Andy Yan
2025-03-09 20:53 ` Piotr Oniszczuk
2025-03-12 3:51 ` Andy Yan
2025-03-06 16:39 ` Dmitry Baryshkov
-- strict thread matches above, loose matches on Subject: below --
2025-02-23 11:30 Andy Yan
2025-02-28 20:30 ` Piotr Oniszczuk
2025-03-01 12:24 ` Andy Yan
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=74c154b6.8c50.1956aa8c8d2.Coremail.andyshrk@163.com \
--to=andyshrk@163.com \
--cc=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=piotr.oniszczuk@gmail.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=yubing.zhang@rock-chips.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