From: Gustavo Padovan <gustavo@padovan.org>
To: Inki Dae <inki.dae@samsung.com>
Cc: "linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH -v3 11/11] drm/exynos: atomic dpms support
Date: Mon, 6 Apr 2015 14:26:46 -0400 [thread overview]
Message-ID: <20150406182646.GA4980@joana> (raw)
In-Reply-To: <CAAQKjZMYXR7TxkGDKt=RTpE=ZpYyp7VveH_M6kEEB4EzcfCmcg@mail.gmail.com>
Hi Inki,
2015-04-05 Inki Dae <inki.dae@samsung.com>:
> Hi,
>
> 2015-04-04 3:09 GMT+09:00 Gustavo Padovan <gustavo@padovan.org>:
> > From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> >
> > Run dpms operations through the atomic intefaces. This basically removes
> > the .dpms() callback from econders and crtcs and use .disable() and
> > .enable() to turn the crtc on and off.
> >
> > v2: Address comments by Joonyoung:
> > - make hdmi code call ->disable() instead of ->dpms()
> > - do not use WARN_ON on crtc enable/disable
> >
> > Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> > ---
> > drivers/gpu/drm/exynos/exynos_dp_core.c | 2 +-
> > drivers/gpu/drm/exynos/exynos_drm_connector.c | 2 +-
> > drivers/gpu/drm/exynos/exynos_drm_crtc.c | 99 +++++++++++++++------------
> > drivers/gpu/drm/exynos/exynos_drm_dpi.c | 2 +-
> > drivers/gpu/drm/exynos/exynos_drm_drv.h | 4 +-
> > drivers/gpu/drm/exynos/exynos_drm_dsi.c | 2 +-
> > drivers/gpu/drm/exynos/exynos_drm_encoder.c | 27 ++------
> > drivers/gpu/drm/exynos/exynos_drm_vidi.c | 2 +-
> > drivers/gpu/drm/exynos/exynos_hdmi.c | 6 +-
> > 9 files changed, 70 insertions(+), 76 deletions(-)
> >
>
> ...snip...
>
> > diff --git a/drivers/gpu/drm/exynos/exynos_hdmi.c b/drivers/gpu/drm/exynos/exynos_hdmi.c
> > index 5b597bc..2ea7d01 100644
> > --- a/drivers/gpu/drm/exynos/exynos_hdmi.c
> > +++ b/drivers/gpu/drm/exynos/exynos_hdmi.c
> > @@ -1051,7 +1051,7 @@ static void hdmi_connector_destroy(struct drm_connector *connector)
> > }
> >
> > static struct drm_connector_funcs hdmi_connector_funcs = {
> > - .dpms = drm_helper_connector_dpms,
> > + .dpms = drm_atomic_helper_connector_dpms,
> > .fill_modes = drm_helper_probe_single_connector_modes,
> > .detect = hdmi_detect,
> > .destroy = hdmi_connector_destroy,
> > @@ -2127,8 +2127,8 @@ static void hdmi_dpms(struct exynos_drm_display *display, int mode)
> > */
> > if (crtc)
> > funcs = crtc->helper_private;
> > - if (funcs && funcs->dpms)
> > - (*funcs->dpms)(crtc, mode);
> > + if (funcs && funcs->disable)
> > + (*funcs->disable)(crtc, mode);
>
> This patch makes funcs->disable callback to be called instead of
> funcs->dpms callback. However, funcs->disable callback isn't required
> for second argument so the build is failed like below,
>
> drivers/gpu/drm/exynos/exynos_hdmi.c: In function 'hdmi_dpms':
> drivers/gpu/drm/exynos/exynos_hdmi.c:2131:4: error: too many arguments
> to function 'funcs->disable'
>
> Please, keep in mind that you should build it and at least have a
> basic test before posting.
Sure, I think this happened because I've been using exynos_defconfig to test
my kernels and HDMI is not there. Maybe should we add the EXYNOS_DRM_HDMI to
defconfig? What do you think?
Gustavo
next prev parent reply other threads:[~2015-04-06 18:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 18:09 [PATCH -v3 00/11] drm/exynos: Add atomic modesetting support Gustavo Padovan
2015-04-03 18:09 ` [PATCH -v3 01/11] drm/exynos: atomic phase 1: use drm_plane_helper_update() Gustavo Padovan
2015-04-03 18:09 ` [PATCH -v3 02/11] drm/exynos: atomic phase 1: use drm_plane_helper_disable() Gustavo Padovan
2015-04-03 18:09 ` [PATCH -v3 03/11] drm/exynos: atomic phase 1: add .mode_set_nofb() callback Gustavo Padovan
2015-04-03 18:09 ` [PATCH -v3 04/11] drm/exynos: atomic phase 2: wire up state reset(), duplicate() and destroy() Gustavo Padovan
2015-04-03 18:09 ` [PATCH -v3 05/11] drm/exynos: atomic phase 2: keep track of framebuffer pointer Gustavo Padovan
2015-04-03 18:09 ` [PATCH -v3 06/11] drm/exynos: atomic phase 3: atomic updates of planes Gustavo Padovan
2015-04-03 18:09 ` [PATCH -v3 07/11] drm/exynos: atomic phase 3: use atomic .set_config helper Gustavo Padovan
2015-04-03 18:09 ` [PATCH -v3 08/11] drm/exynos: atomic phase 3: convert page flips Gustavo Padovan
2015-04-03 18:09 ` [PATCH -v3 09/11] drm/exynos: remove exported functions from exynos_drm_plane Gustavo Padovan
2015-04-03 18:09 ` [PATCH -v3 10/11] drm/exynos: don't disable unused functions at init Gustavo Padovan
2015-04-03 18:09 ` [PATCH -v3 11/11] drm/exynos: atomic dpms support Gustavo Padovan
2015-04-05 14:42 ` Inki Dae
2015-04-06 18:26 ` Gustavo Padovan [this message]
2015-04-07 7:22 ` Joonyoung Shim
2015-04-07 19:56 ` [PATCH v4] " Gustavo Padovan
2015-04-10 18:57 ` [PATCH] drm/exynos: remove unnecessary calls to disable_plane() Gustavo Padovan
2015-04-13 6:32 ` Joonyoung Shim
2015-04-13 17:35 ` Gustavo Padovan
2015-04-06 10:46 ` [PATCH -v3 00/11] drm/exynos: Add atomic modesetting support Inki Dae
2015-04-06 15:44 ` Inki Dae
2015-04-07 7:06 ` Inki Dae
2015-04-07 11:14 ` Inki Dae
2015-04-07 17:24 ` Gustavo Padovan
2015-04-07 18:39 ` Gustavo Padovan
2015-04-07 19:14 ` Tobias Jakobi
2015-04-08 15:14 ` Inki Dae
2015-04-09 7:04 ` Joonyoung Shim
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=20150406182646.GA4980@joana \
--to=gustavo@padovan.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=inki.dae@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
/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).