linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shobhit Kumar <shobhit.kumar@intel.com>,
	Ilia Mirkin <imirkin@alum.mit.edu>,
	Dave Airlie <airlied@linux.ie>
Subject: linux-next: manual merge of the drm-intel tree with the drm tree
Date: Thu, 29 Aug 2013 14:09:06 +1000	[thread overview]
Message-ID: <20130829140906.2c4b5dea4453266265018c0b@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 3002 bytes --]

Hi all,

Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/drm_crtc.c between commit b21e3afe2357 ("drm: use ida to
allocate connector ids") from the drm tree and commit 88cd8b8b1503 ("drm:
add MIPI DSI encoder and connector types") from the drm-intel tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).
 
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc drivers/gpu/drm/drm_crtc.c
index 54b4169,190827d..0000000
--- a/drivers/gpu/drm/drm_crtc.c
+++ b/drivers/gpu/drm/drm_crtc.c
@@@ -186,22 -193,23 +186,23 @@@ struct drm_conn_prop_enum_list 
   * Connector and encoder types.
   */
  static struct drm_conn_prop_enum_list drm_connector_enum_list[] =
 -{	{ DRM_MODE_CONNECTOR_Unknown, "Unknown", 0 },
 -	{ DRM_MODE_CONNECTOR_VGA, "VGA", 0 },
 -	{ DRM_MODE_CONNECTOR_DVII, "DVI-I", 0 },
 -	{ DRM_MODE_CONNECTOR_DVID, "DVI-D", 0 },
 -	{ DRM_MODE_CONNECTOR_DVIA, "DVI-A", 0 },
 -	{ DRM_MODE_CONNECTOR_Composite, "Composite", 0 },
 -	{ DRM_MODE_CONNECTOR_SVIDEO, "SVIDEO", 0 },
 -	{ DRM_MODE_CONNECTOR_LVDS, "LVDS", 0 },
 -	{ DRM_MODE_CONNECTOR_Component, "Component", 0 },
 -	{ DRM_MODE_CONNECTOR_9PinDIN, "DIN", 0 },
 -	{ DRM_MODE_CONNECTOR_DisplayPort, "DP", 0 },
 -	{ DRM_MODE_CONNECTOR_HDMIA, "HDMI-A", 0 },
 -	{ DRM_MODE_CONNECTOR_HDMIB, "HDMI-B", 0 },
 -	{ DRM_MODE_CONNECTOR_TV, "TV", 0 },
 -	{ DRM_MODE_CONNECTOR_eDP, "eDP", 0 },
 -	{ DRM_MODE_CONNECTOR_VIRTUAL, "Virtual", 0},
 +{	{ DRM_MODE_CONNECTOR_Unknown, "Unknown" },
 +	{ DRM_MODE_CONNECTOR_VGA, "VGA" },
 +	{ DRM_MODE_CONNECTOR_DVII, "DVI-I" },
 +	{ DRM_MODE_CONNECTOR_DVID, "DVI-D" },
 +	{ DRM_MODE_CONNECTOR_DVIA, "DVI-A" },
 +	{ DRM_MODE_CONNECTOR_Composite, "Composite" },
 +	{ DRM_MODE_CONNECTOR_SVIDEO, "SVIDEO" },
 +	{ DRM_MODE_CONNECTOR_LVDS, "LVDS" },
 +	{ DRM_MODE_CONNECTOR_Component, "Component" },
 +	{ DRM_MODE_CONNECTOR_9PinDIN, "DIN" },
 +	{ DRM_MODE_CONNECTOR_DisplayPort, "DP" },
 +	{ DRM_MODE_CONNECTOR_HDMIA, "HDMI-A" },
 +	{ DRM_MODE_CONNECTOR_HDMIB, "HDMI-B" },
 +	{ DRM_MODE_CONNECTOR_TV, "TV" },
 +	{ DRM_MODE_CONNECTOR_eDP, "eDP" },
 +	{ DRM_MODE_CONNECTOR_VIRTUAL, "Virtual" },
+ 	{ DRM_MODE_CONNECTOR_DSI, "DSI" },
  };
  
  static const struct drm_prop_enum_list drm_encoder_enum_list[] =
@@@ -211,24 -219,9 +212,25 @@@
  	{ DRM_MODE_ENCODER_LVDS, "LVDS" },
  	{ DRM_MODE_ENCODER_TVDAC, "TV" },
  	{ DRM_MODE_ENCODER_VIRTUAL, "Virtual" },
+ 	{ DRM_MODE_ENCODER_DSI, "DSI" },
  };
  
 +void drm_connector_ida_init(void)
 +{
 +	int i;
 +
 +	for (i = 0; i < ARRAY_SIZE(drm_connector_enum_list); i++)
 +		ida_init(&drm_connector_enum_list[i].ida);
 +}
 +
 +void drm_connector_ida_destroy(void)
 +{
 +	int i;
 +
 +	for (i = 0; i < ARRAY_SIZE(drm_connector_enum_list); i++)
 +		ida_destroy(&drm_connector_enum_list[i].ida);
 +}
 +
  const char *drm_get_encoder_name(const struct drm_encoder *encoder)
  {
  	static char buf[32];

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2013-08-29  4:09 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29  4:09 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-03  0:09 linux-next: manual merge of the drm-intel tree with the drm tree Stephen Rothwell
2023-10-05 14:41 ` Jani Nikula
2023-05-30  1:59 Stephen Rothwell
2023-05-30  1:57 Stephen Rothwell
2023-05-30  2:10 ` Stephen Rothwell
2023-01-24 23:42 Stephen Rothwell
2022-09-13  2:19 Stephen Rothwell
2022-09-12  1:46 Stephen Rothwell
2022-02-11  2:06 Stephen Rothwell
2022-02-09  0:55 Stephen Rothwell
2021-08-12  1:28 Stephen Rothwell
2021-04-01  2:13 Stephen Rothwell
2021-03-17  3:08 Stephen Rothwell
2021-03-18  1:52 ` Stephen Rothwell
2021-04-29 22:23   ` Stephen Rothwell
2021-05-14  1:53     ` Stephen Rothwell
2021-05-14 12:14       ` Thomas Zimmermann
2021-01-25  0:46 Stephen Rothwell
2020-07-14  2:59 Stephen Rothwell
2019-08-22  3:15 Stephen Rothwell
2019-02-06  0:42 Stephen Rothwell
2019-01-17  1:59 Stephen Rothwell
2017-05-19  2:04 Stephen Rothwell
2016-09-07  3:59 Stephen Rothwell
2014-07-23  3:18 Stephen Rothwell
2014-07-23  3:06 Stephen Rothwell
2014-07-23  5:09 ` Daniel Vetter
2014-04-03  1:00 Stephen Rothwell
2014-01-22  3:09 Stephen Rothwell
2014-01-22  3:04 Stephen Rothwell
2014-01-22 10:06 ` Daniel Vetter
2014-01-23  1:21   ` Olof Johansson
2014-01-23 21:10     ` Olof Johansson
2013-11-07  2:37 Stephen Rothwell
2013-06-18  3:04 Stephen Rothwell
2013-05-01  4:37 Stephen Rothwell
2013-05-01  8:08 ` Daniel Vetter

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=20130829140906.2c4b5dea4453266265018c0b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imirkin@alum.mit.edu \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=shobhit.kumar@intel.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;
as well as URLs for NNTP newsgroup(s).