From: Mark yao <mark.yao@rock-chips.com>
To: David Airlie <airlied@linux.ie>, Heiko Stuebner <heiko@sntech.de>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Russell King <rmk+kernel@arm.linux.org.uk>,
Philipp Zabel <p.zabel@pengutronix.de>,
Andy Yan <andy.yan@rock-chips.com>,
Fabio Estevam <fabio.estevam@freescale.com>,
Thierry Reding <treding@nvidia.com>
Subject: Re: [RFC PATCH 8/9] drm: bridge/dw_hdmi: Covert to support atomic API
Date: Tue, 01 Dec 2015 16:07:02 +0800 [thread overview]
Message-ID: <565D5526.7030009@rock-chips.com> (raw)
In-Reply-To: <20151201072128.GF17050@phenom.ffwll.local>
On 2015年12月01日 15:21, Daniel Vetter wrote:
> On Tue, Dec 01, 2015 at 11:35:53AM +0800, Mark Yao wrote:
>> Fill atomic needed funcs with default atomic helper library.
>>
>> Rockchip use dw_hdmi, and drm/rockchip will covert to atomic api,
>> we need dw_hdmi support atomic funcs.
>>
>> Signed-off-by: Mark Yao <mark.yao@rock-chips.com>
> Aren't there drivers around which use dw_hdmi and which are still not yet
> atomic? This would break them. I think we neeed two connector_func tables
> and dw_hdmi needs to check for DRIVER_ATOMIC at runtime and pick the right
> version.
Right, another drm driver use dw_hdmi is imx, not yet atomic, this would
break it.
as you said, I would resend a patch to check DRIVER_ATOMIC at runtime.
Thanks
-Mark
>
> The larger problem here is that "who should register the drm_connector" is
> a bit an unsolved problem, since both the bridge and the driver should be
> able to customize/adjust the drm_connector at the end of a bridge chain.
> This here is just another example of this problem.
> -Daniel
>
>> ---
>> drivers/gpu/drm/bridge/dw_hdmi.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/bridge/dw_hdmi.c b/drivers/gpu/drm/bridge/dw_hdmi.c
>> index 56de9f1..587065a 100644
>> --- a/drivers/gpu/drm/bridge/dw_hdmi.c
>> +++ b/drivers/gpu/drm/bridge/dw_hdmi.c
>> @@ -22,6 +22,7 @@
>>
>> #include <drm/drm_of.h>
>> #include <drm/drmP.h>
>> +#include <drm/drm_atomic_helper.h>
>> #include <drm/drm_crtc_helper.h>
>> #include <drm/drm_edid.h>
>> #include <drm/drm_encoder_slave.h>
>> @@ -1515,11 +1516,14 @@ static void dw_hdmi_connector_force(struct drm_connector *connector)
>> }
>>
>> static struct drm_connector_funcs dw_hdmi_connector_funcs = {
>> - .dpms = drm_helper_connector_dpms,
>> + .dpms = drm_atomic_helper_connector_dpms,
>> .fill_modes = drm_helper_probe_single_connector_modes,
>> .detect = dw_hdmi_connector_detect,
>> .destroy = dw_hdmi_connector_destroy,
>> .force = dw_hdmi_connector_force,
>> + .reset = drm_atomic_helper_connector_reset,
>> + .atomic_duplicate_state = drm_atomic_helper_connector_duplicate_state,
>> + .atomic_destroy_state = drm_atomic_helper_connector_destroy_state,
>> };
>>
>> static struct drm_connector_helper_funcs dw_hdmi_connector_helper_funcs = {
>> --
>> 1.7.9.5
>>
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: mark.yao@rock-chips.com (Mark yao)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 8/9] drm: bridge/dw_hdmi: Covert to support atomic API
Date: Tue, 01 Dec 2015 16:07:02 +0800 [thread overview]
Message-ID: <565D5526.7030009@rock-chips.com> (raw)
In-Reply-To: <20151201072128.GF17050@phenom.ffwll.local>
On 2015?12?01? 15:21, Daniel Vetter wrote:
> On Tue, Dec 01, 2015 at 11:35:53AM +0800, Mark Yao wrote:
>> Fill atomic needed funcs with default atomic helper library.
>>
>> Rockchip use dw_hdmi, and drm/rockchip will covert to atomic api,
>> we need dw_hdmi support atomic funcs.
>>
>> Signed-off-by: Mark Yao <mark.yao@rock-chips.com>
> Aren't there drivers around which use dw_hdmi and which are still not yet
> atomic? This would break them. I think we neeed two connector_func tables
> and dw_hdmi needs to check for DRIVER_ATOMIC at runtime and pick the right
> version.
Right, another drm driver use dw_hdmi is imx, not yet atomic, this would
break it.
as you said, I would resend a patch to check DRIVER_ATOMIC at runtime.
Thanks
-Mark
>
> The larger problem here is that "who should register the drm_connector" is
> a bit an unsolved problem, since both the bridge and the driver should be
> able to customize/adjust the drm_connector at the end of a bridge chain.
> This here is just another example of this problem.
> -Daniel
>
>> ---
>> drivers/gpu/drm/bridge/dw_hdmi.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/bridge/dw_hdmi.c b/drivers/gpu/drm/bridge/dw_hdmi.c
>> index 56de9f1..587065a 100644
>> --- a/drivers/gpu/drm/bridge/dw_hdmi.c
>> +++ b/drivers/gpu/drm/bridge/dw_hdmi.c
>> @@ -22,6 +22,7 @@
>>
>> #include <drm/drm_of.h>
>> #include <drm/drmP.h>
>> +#include <drm/drm_atomic_helper.h>
>> #include <drm/drm_crtc_helper.h>
>> #include <drm/drm_edid.h>
>> #include <drm/drm_encoder_slave.h>
>> @@ -1515,11 +1516,14 @@ static void dw_hdmi_connector_force(struct drm_connector *connector)
>> }
>>
>> static struct drm_connector_funcs dw_hdmi_connector_funcs = {
>> - .dpms = drm_helper_connector_dpms,
>> + .dpms = drm_atomic_helper_connector_dpms,
>> .fill_modes = drm_helper_probe_single_connector_modes,
>> .detect = dw_hdmi_connector_detect,
>> .destroy = dw_hdmi_connector_destroy,
>> .force = dw_hdmi_connector_force,
>> + .reset = drm_atomic_helper_connector_reset,
>> + .atomic_duplicate_state = drm_atomic_helper_connector_duplicate_state,
>> + .atomic_destroy_state = drm_atomic_helper_connector_destroy_state,
>> };
>>
>> static struct drm_connector_helper_funcs dw_hdmi_connector_helper_funcs = {
>> --
>> 1.7.9.5
>>
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Mark yao <mark.yao@rock-chips.com>
To: David Airlie <airlied@linux.ie>, Heiko Stuebner <heiko@sntech.de>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Russell King <rmk+kernel@arm.linux.org.uk>,
Philipp Zabel <p.zabel@pengutronix.de>,
Andy Yan <andy.yan@rock-chips.com>,
Fabio Estevam <fabio.estevam@freescale.com>,
Thierry Reding <treding@nvidia.com>
Subject: Re: [RFC PATCH 8/9] drm: bridge/dw_hdmi: Covert to support atomic API
Date: Tue, 01 Dec 2015 16:07:02 +0800 [thread overview]
Message-ID: <565D5526.7030009@rock-chips.com> (raw)
In-Reply-To: <20151201072128.GF17050@phenom.ffwll.local>
On 2015年12月01日 15:21, Daniel Vetter wrote:
> On Tue, Dec 01, 2015 at 11:35:53AM +0800, Mark Yao wrote:
>> Fill atomic needed funcs with default atomic helper library.
>>
>> Rockchip use dw_hdmi, and drm/rockchip will covert to atomic api,
>> we need dw_hdmi support atomic funcs.
>>
>> Signed-off-by: Mark Yao <mark.yao@rock-chips.com>
> Aren't there drivers around which use dw_hdmi and which are still not yet
> atomic? This would break them. I think we neeed two connector_func tables
> and dw_hdmi needs to check for DRIVER_ATOMIC at runtime and pick the right
> version.
Right, another drm driver use dw_hdmi is imx, not yet atomic, this would
break it.
as you said, I would resend a patch to check DRIVER_ATOMIC at runtime.
Thanks
-Mark
>
> The larger problem here is that "who should register the drm_connector" is
> a bit an unsolved problem, since both the bridge and the driver should be
> able to customize/adjust the drm_connector at the end of a bridge chain.
> This here is just another example of this problem.
> -Daniel
>
>> ---
>> drivers/gpu/drm/bridge/dw_hdmi.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/bridge/dw_hdmi.c b/drivers/gpu/drm/bridge/dw_hdmi.c
>> index 56de9f1..587065a 100644
>> --- a/drivers/gpu/drm/bridge/dw_hdmi.c
>> +++ b/drivers/gpu/drm/bridge/dw_hdmi.c
>> @@ -22,6 +22,7 @@
>>
>> #include <drm/drm_of.h>
>> #include <drm/drmP.h>
>> +#include <drm/drm_atomic_helper.h>
>> #include <drm/drm_crtc_helper.h>
>> #include <drm/drm_edid.h>
>> #include <drm/drm_encoder_slave.h>
>> @@ -1515,11 +1516,14 @@ static void dw_hdmi_connector_force(struct drm_connector *connector)
>> }
>>
>> static struct drm_connector_funcs dw_hdmi_connector_funcs = {
>> - .dpms = drm_helper_connector_dpms,
>> + .dpms = drm_atomic_helper_connector_dpms,
>> .fill_modes = drm_helper_probe_single_connector_modes,
>> .detect = dw_hdmi_connector_detect,
>> .destroy = dw_hdmi_connector_destroy,
>> .force = dw_hdmi_connector_force,
>> + .reset = drm_atomic_helper_connector_reset,
>> + .atomic_duplicate_state = drm_atomic_helper_connector_duplicate_state,
>> + .atomic_destroy_state = drm_atomic_helper_connector_destroy_state,
>> };
>>
>> static struct drm_connector_helper_funcs dw_hdmi_connector_helper_funcs = {
>> --
>> 1.7.9.5
>>
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-12-01 8:07 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 3:26 [RFC PATCH 0/9] drm/rockchip: covert to support atomic API Mark Yao
2015-12-01 3:26 ` Mark Yao
2015-12-01 3:26 ` Mark Yao
2015-12-01 3:26 ` [RFC PATCH 1/9] drm/rockchip: vop: replace dpms with enable/disable Mark Yao
2015-12-01 3:26 ` Mark Yao
2015-12-01 3:26 ` Mark Yao
2015-12-01 3:26 ` [RFC PATCH 2/9] drm/rockchip: Use new vblank api drm_crtc_vblank_* Mark Yao
2015-12-01 3:26 ` Mark Yao
2015-12-01 3:26 ` Mark Yao
2015-12-01 7:56 ` Daniel Stone
2015-12-01 7:56 ` Daniel Stone
2015-12-01 7:56 ` Daniel Stone
2015-12-01 8:33 ` Mark yao
2015-12-01 8:33 ` Mark yao
2015-12-01 8:33 ` Mark yao
2015-12-01 9:01 ` Daniel Vetter
2015-12-01 9:01 ` Daniel Vetter
2015-12-01 9:43 ` Mark yao
2015-12-01 9:43 ` Mark yao
2015-12-01 9:43 ` Mark yao
2015-12-01 3:26 ` [RFC PATCH 3/9] drm/rockchip: Convert to support atomic API Mark Yao
2015-12-01 3:26 ` Mark Yao
2015-12-01 3:26 ` Mark Yao
2015-12-01 8:18 ` Daniel Stone
2015-12-01 8:18 ` Daniel Stone
2015-12-01 8:18 ` Daniel Stone
2015-12-01 9:21 ` Mark yao
2015-12-01 9:21 ` Mark yao
2015-12-01 9:21 ` Mark yao
2015-12-01 9:31 ` Mark yao
2015-12-01 9:31 ` Mark yao
2015-12-01 9:31 ` Mark yao
2015-12-02 14:18 ` Daniel Stone
2015-12-02 14:18 ` Daniel Stone
2015-12-02 14:22 ` Daniel Stone
2015-12-02 14:22 ` Daniel Stone
2015-12-02 14:22 ` Daniel Stone
2015-12-11 6:26 ` Mark yao
2015-12-11 6:26 ` Mark yao
2015-12-11 6:26 ` Mark yao
2015-12-01 3:26 ` [RFC PATCH 4/9] drm/rockchip: support atomic asynchronous commit Mark Yao
2015-12-01 3:26 ` Mark Yao
2015-12-01 3:26 ` Mark Yao
2015-12-01 3:28 ` [RFC PATCH 5/9] drm/rockchip: Optimization vop mode set Mark Yao
2015-12-01 3:28 ` Mark Yao
2015-12-01 3:28 ` Mark Yao
2015-12-01 3:30 ` [RFC PATCH 6/9] drm/rockchip: direct config connecter gate and out_mode Mark Yao
2015-12-01 3:30 ` Mark Yao
2015-12-01 3:30 ` Mark Yao
2015-12-01 3:32 ` [RFC PATCH 7/9] drm/rockchip: force enable vop when do mode setting Mark Yao
2015-12-01 3:32 ` Mark Yao
2015-12-02 16:55 ` Thierry Reding
2015-12-02 16:55 ` Thierry Reding
2015-12-02 16:55 ` Thierry Reding
2015-12-02 22:17 ` Daniel Vetter
2015-12-02 22:17 ` Daniel Vetter
2015-12-02 22:17 ` Daniel Vetter
2015-12-03 1:54 ` Mark yao
2015-12-03 1:54 ` Mark yao
2015-12-03 1:54 ` Mark yao
2015-12-01 3:35 ` [RFC PATCH 8/9] drm: bridge/dw_hdmi: Covert to support atomic API Mark Yao
2015-12-01 3:35 ` Mark Yao
2015-12-01 3:35 ` Mark Yao
2015-12-01 7:21 ` Daniel Vetter
2015-12-01 7:21 ` Daniel Vetter
2015-12-01 8:07 ` Mark yao [this message]
2015-12-01 8:07 ` Mark yao
2015-12-01 8:07 ` Mark yao
2015-12-01 8:17 ` [PATCH] drm: bridge/dw_hdmi: add atomic API support Mark Yao
2015-12-01 8:17 ` Mark Yao
2015-12-01 8:17 ` Mark Yao
2015-12-01 3:37 ` [RFC PATCH 9/9] drm/rockchip: dw_hdmi: use encoder enable function Mark Yao
2015-12-01 3:37 ` Mark Yao
2015-12-01 3:37 ` Mark Yao
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=565D5526.7030009@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=airlied@linux.ie \
--cc=andy.yan@rock-chips.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabio.estevam@freescale.com \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=treding@nvidia.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 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.