From: Jani Nikula <jani.nikula@linux.intel.com>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
dri-devel@lists.freedesktop.org
Cc: "Alison Wang" <alison.wang@freescale.com>,
"Alexey Brodkin" <abrodkin@synopsys.com>,
"Jyri Sarha" <jsarha@ti.com>,
"Xinliang Liu" <z.liuxinliang@hisilicon.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Rongrong Zou" <zourongrong@gmail.com>,
"Daniel Vetter" <daniel.vetter@intel.com>,
"Maxime Ripard" <maxime.ripard@free-electrons.com>,
"Vincent Abriou" <vincent.abriou@st.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH] drm: Make the connector .detect() callback optional
Date: Wed, 30 Nov 2016 10:26:40 +0200 [thread overview]
Message-ID: <874m2p1igv.fsf@intel.com> (raw)
In-Reply-To: <1480452990-8331-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On Tue, 29 Nov 2016, Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> wrote:
> Many drivers (21 to be exact) create connectors that are always
> connected (for instance to an LVDS or DSI panel). Instead of forcing
> them to implement a dummy .detect() handler, make the callback optional
> and consider the connector as always connected in that case.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Acked-by: Jani Nikula <jani.nikula@intel.com>
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-11-30 8:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 20:56 [PATCH] drm: Make the connector .detect() callback optional Laurent Pinchart
2016-11-29 21:02 ` Maxime Ripard
2016-11-29 21:07 ` Sean Paul
2016-11-29 21:09 ` Laurent Pinchart
2016-12-01 18:15 ` Sean Paul
2016-11-29 21:23 ` Deucher, Alexander
2016-11-29 21:24 ` Jyri Sarha
2016-11-30 8:26 ` Jani Nikula [this message]
2016-11-30 9:37 ` Alexey Brodkin
2016-11-30 9:51 ` Philipp Zabel
2016-11-30 15:27 ` Vincent ABRIOU
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=874m2p1igv.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=abrodkin@synopsys.com \
--cc=alexander.deucher@amd.com \
--cc=alison.wang@freescale.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=maxime.ripard@free-electrons.com \
--cc=vincent.abriou@st.com \
--cc=z.liuxinliang@hisilicon.com \
--cc=zourongrong@gmail.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.