On Fri, Aug 19, 2016 at 06:03:06PM +, Pandiyan, Dhinakaran wrote:
> On Fri, 2016-08-19 at 10:02 +0200, Daniel Vetter wrote:
> > On Mon, Aug 15, 2016 at 05:00:53PM -0700, Dhinakaran Pandiyan wrote:
> > > There are places in the driver where we just need the 'port' associated
> > > with an
On Fri, 2016-08-19 at 10:02 +0200, Daniel Vetter wrote:
> On Mon, Aug 15, 2016 at 05:00:53PM -0700, Dhinakaran Pandiyan wrote:
> > There are places in the driver where we just need the 'port' associated
> > with an encoder and not 'struct intel_digital_port' that contains it.
> > This basically is
On Thu, 2016-08-18 at 21:39 -0700, Rodrigo Vivi wrote:
> On Mon, Aug 15, 2016 at 05:00:53PM -0700, Dhinakaran Pandiyan wrote:
> > There are places in the driver where we just need the 'port' associated
> > with an encoder and not 'struct intel_digital_port' that contains it.
> > This basically is
On Mon, Aug 15, 2016 at 05:00:53PM -0700, Dhinakaran Pandiyan wrote:
> There are places in the driver where we just need the 'port' associated
> with an encoder and not 'struct intel_digital_port' that contains it.
> This basically is a generic implementation of intel_ddi_get_encoder_port()
>
On Mon, Aug 15, 2016 at 05:00:53PM -0700, Dhinakaran Pandiyan wrote:
> There are places in the driver where we just need the 'port' associated
> with an encoder and not 'struct intel_digital_port' that contains it.
> This basically is a generic implementation of intel_ddi_get_encoder_port()
>
There are places in the driver where we just need the 'port' associated
with an encoder and not 'struct intel_digital_port' that contains it.
This basically is a generic implementation of intel_ddi_get_encoder_port()
handling both DDI and Non-DDI encoders. The handling of the analog encoder
is
