linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-sh@vger.kernel.org
Subject: Re: [PATCH v3] drm: Renesas R-Car Display Unit DRM driver
Date: Thu, 06 Jun 2013 13:21:35 +0000	[thread overview]
Message-ID: <CADnq5_NJMmk-11vVXm4mXt19OQRyNje74GsaLg31ML72JPMvyQ@mail.gmail.com> (raw)
In-Reply-To: <CAKMK7uHB_x_qjFi40UbZs++3Z8cY8qnX2z2gw+_jGdHmEYEK=w@mail.gmail.com>

On Thu, Jun 6, 2013 at 9:12 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Jun 5, 2013 at 3:10 PM, Alex Deucher <alexdeucher@gmail.com> wrote:
>> To me at least, it doesn't make sense that an encoder can clone
>> itself.  If an encoder is already in use, trying to clone itself would
>> only lead to confusion and possible bugs (make sure some code path
>> doesn't try and reprogram the encoder again, etc.).
>
> For me the possible_clones mask is just the set of encoders which can
> together share a crtc (presuming that crtc is indeed in all of the
> possible_crtcs mask of each encoder). From that pov it makes imo sense
> that a given encoder itself can always be with itself on the same crtc
> ;-)
>
> Otoh setcrtc doesn't care one bit about encoders (the crtc helpers do
> internally use them, but it's not interface). And the possible_clones
> stuff is by far not enough to describe all hw restrictions. So tbh I
> don't care which way we go (or whether we indeed keep on using this
> much at all).

Same.  I can go either way.

Alex

> -Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2013-06-06 13:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04  2:53 [PATCH v3] drm: Renesas R-Car Display Unit DRM driver Laurent Pinchart
2013-06-04 14:12 ` Daniel Vetter
2013-06-04 18:03   ` Laurent Pinchart
2013-06-04 18:36     ` Daniel Vetter
2013-06-05  1:51       ` Laurent Pinchart
2013-06-05  8:55         ` Daniel Vetter
2013-06-07  7:44           ` Laurent Pinchart
2013-06-07  8:50             ` Daniel Vetter
2013-06-14  0:54               ` Laurent Pinchart
2013-06-14 14:03                 ` Daniel Vetter
2013-06-18 23:45                   ` Laurent Pinchart
2013-06-20 14:06                     ` Daniel Vetter
2013-06-05 11:57         ` Ville Syrjälä
2013-06-05 13:10         ` Alex Deucher
2013-06-06 13:12           ` Daniel Vetter
2013-06-06 13:21             ` Alex Deucher [this message]
2013-06-07  7:23               ` Laurent Pinchart
2013-06-07  8:51                 ` 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=CADnq5_NJMmk-11vVXm4mXt19OQRyNje74GsaLg31ML72JPMvyQ@mail.gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-sh@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).