From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/4] drm/i915: Make encoder cloning more flexible
Date: Mon, 10 Mar 2014 21:17:38 +0200 [thread overview]
Message-ID: <20140310191738.GU3852@intel.com> (raw)
In-Reply-To: <CABVU7+v47M4VKg4u9ChXXd+qZ7GuZSkjsE93taoSio5d_sR0QA@mail.gmail.com>
On Mon, Mar 10, 2014 at 03:27:09PM -0300, Rodrigo Vivi wrote:
> On Mon, Mar 3, 2014 at 11:15 AM, <ville.syrjala@linux.intel.com> wrote:
> > diff --git a/drivers/gpu/drm/i915/intel_tv.c b/drivers/gpu/drm/i915/intel_tv.c
> > index b64fc1c..5be4ab2 100644
> > --- a/drivers/gpu/drm/i915/intel_tv.c
> > +++ b/drivers/gpu/drm/i915/intel_tv.c
> > @@ -1639,9 +1639,8 @@ intel_tv_init(struct drm_device *dev)
> > intel_connector_attach_encoder(intel_connector, intel_encoder);
> > intel_encoder->type = INTEL_OUTPUT_TVOUT;
> > intel_encoder->crtc_mask = (1 << 0) | (1 << 1);
> > - intel_encoder->cloneable = false;
> > + intel_encoder->cloneable = 0;
> > intel_encoder->base.possible_crtcs = ((1 << 0) | (1 << 1));
> > - intel_encoder->base.possible_clones = (1 << INTEL_OUTPUT_TVOUT);
>
> why did you remove this?
> or shouldn't it be a separated patch at least?
It has no business being here. We compute possible_clones dynamically
so this will get overwritten. I forgot to mention it in the commits
msg. It could be a separate patch, but since it does nothing just
killing it as part of this patch seems fine.
>
> The rest of the approach looks ok for me, so with this explained or
> fixed feel free to use
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@gmail.com>
>
> > intel_tv->type = DRM_MODE_CONNECTOR_Unknown;
> >
> > /* BIOS margin values */
> > --
> > 1.8.3.2
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
>
>
> --
> Rodrigo Vivi
> Blog: http://blog.vivi.eng.br
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-03-10 19:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 14:15 [PATCH 0/4] drm/915: Relax output cloning restrictions ville.syrjala
2014-03-03 14:15 ` [PATCH 1/4] drm/i915: Make encoder cloning more flexible ville.syrjala
2014-03-05 18:20 ` Daniel Vetter
2014-03-05 18:47 ` Ville Syrjälä
2014-03-10 18:27 ` Rodrigo Vivi
2014-03-10 19:17 ` Ville Syrjälä [this message]
2014-03-03 14:15 ` [PATCH 2/4] drm/i915: Don't use HDMI 12bpc when cloning with other encoder types ville.syrjala
2014-03-10 18:31 ` Rodrigo Vivi
2014-03-03 14:15 ` [PATCH 3/4] drm/i915: Allow HDMI+VGA cloning ville.syrjala
2014-03-10 18:41 ` Rodrigo Vivi
2014-03-03 14:15 ` [PATCH 4/4] drm/i915: Allow HDMI+HDMI cloning on g4x ville.syrjala
2014-03-05 18:21 ` Daniel Vetter
2014-03-05 18:41 ` Ville Syrjälä
2014-03-10 18:50 ` Rodrigo Vivi
2014-03-10 20:49 ` 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=20140310191738.GU3852@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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.