On Fri, Jan 03, 2014 at 05:26:14PM +0100, David Herrmann wrote:
> Hi
>
> On Fri, Jan 3, 2014 at 5:13 PM, Russell King - ARM Linux
> wrote:
> > I'm not so sure - since the only place this mask gets used is with
> > the "possible_crtcs" field. It's got nothing to do with the
> > "possible_clones"
Hi
On Fri, Jan 3, 2014 at 5:13 PM, Russell King - ARM Linux
wrote:
> On Fri, Jan 03, 2014 at 05:05:46PM +0100, David Herrmann wrote:
>> Hi
>>
>> On Thu, Jan 2, 2014 at 10:27 PM, Russell King
>> wrote:
>> > The encoder possible_crtcs mask identifies which CRTCs can be bound to
>> > a particular e
Hi
On Thu, Jan 2, 2014 at 10:27 PM, Russell King
wrote:
> The encoder possible_crtcs mask identifies which CRTCs can be bound to
> a particular encoder. Each bit from bit 0 defines an index in the list
> of CRTCs held in the DRM mode_config crtc_list. Rather than having
> drivers trying to trac
On Fri, Jan 03, 2014 at 05:05:46PM +0100, David Herrmann wrote:
> Hi
>
> On Thu, Jan 2, 2014 at 10:27 PM, Russell King
> wrote:
> > The encoder possible_crtcs mask identifies which CRTCs can be bound to
> > a particular encoder. Each bit from bit 0 defines an index in the list
> > of CRTCs held
The encoder possible_crtcs mask identifies which CRTCs can be bound to
a particular encoder. Each bit from bit 0 defines an index in the list
of CRTCs held in the DRM mode_config crtc_list. Rather than having
drivers trying to track the position of their CRTCs in the list, expose
the code which a
