Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

Am Donnerstag, den 23.06.2016, 12:08 +0800 schrieb Nicolas Boichat: [...] > >> >> I think it'd be a bit weird to have the DDC bus phandle on the DP > >> >> connector, as we're not reading the EDID on the DP side of the bridge, > >> >> but on the HDMI side (and the bridge can do all sort of things

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

Am Donnerstag, den 23.06.2016, 12:08 +0800 schrieb Nicolas Boichat: [...] > >> >> I think it'd be a bit weird to have the DDC bus phandle on the DP > >> >> connector, as we're not reading the EDID on the DP side of the bridge, > >> >> but on the HDMI side (and the bridge can do all sort of things

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

Hi Philipp, On Wed, Jun 22, 2016 at 4:51 PM, Philipp Zabel wrote: > Hi Nicolas, > > Am Mittwoch, den 22.06.2016, 14:32 +0800 schrieb Nicolas Boichat: >> >> Actually, experimenting a bit more with the code, I realized that the >> >> connector is always attached to the

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

Hi Philipp, On Wed, Jun 22, 2016 at 4:51 PM, Philipp Zabel wrote: > Hi Nicolas, > > Am Mittwoch, den 22.06.2016, 14:32 +0800 schrieb Nicolas Boichat: >> >> Actually, experimenting a bit more with the code, I realized that the >> >> connector is always attached to the encoder, not the bridge, so

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

Hi Nicolas, Am Mittwoch, den 22.06.2016, 14:32 +0800 schrieb Nicolas Boichat: > >> Actually, experimenting a bit more with the code, I realized that the > >> connector is always attached to the encoder, not the bridge, so the 2 > >> layouts above are actually identical (from the userspace point

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

Hi Nicolas, Am Mittwoch, den 22.06.2016, 14:32 +0800 schrieb Nicolas Boichat: > >> Actually, experimenting a bit more with the code, I realized that the > >> connector is always attached to the encoder, not the bridge, so the 2 > >> layouts above are actually identical (from the userspace point

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

+Philipp On Wed, Jun 22, 2016 at 11:54 AM, Archit Taneja wrote: > > > On 6/22/2016 8:14 AM, Nicolas Boichat wrote: >> >> Hi Archit, >> >> Thanks for your reply. >> >> On Tue, Jun 21, 2016 at 11:39 PM, Archit Taneja >> wrote: >>> >>> Hi, >>> >>> On

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

+Philipp On Wed, Jun 22, 2016 at 11:54 AM, Archit Taneja wrote: > > > On 6/22/2016 8:14 AM, Nicolas Boichat wrote: >> >> Hi Archit, >> >> Thanks for your reply. >> >> On Tue, Jun 21, 2016 at 11:39 PM, Archit Taneja >> wrote: >>> >>> Hi, >>> >>> On 6/20/2016 12:44 PM, Nicolas Boichat wrote:

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

On 6/22/2016 8:14 AM, Nicolas Boichat wrote: Hi Archit, Thanks for your reply. On Tue, Jun 21, 2016 at 11:39 PM, Archit Taneja wrote: Hi, On 6/20/2016 12:44 PM, Nicolas Boichat wrote: ANX7688 is a HDMI to DP converter (as well as USB-C port controller), that has

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

On 6/22/2016 8:14 AM, Nicolas Boichat wrote: Hi Archit, Thanks for your reply. On Tue, Jun 21, 2016 at 11:39 PM, Archit Taneja wrote: Hi, On 6/20/2016 12:44 PM, Nicolas Boichat wrote: ANX7688 is a HDMI to DP converter (as well as USB-C port controller), that has an internal

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

Hi Archit, Thanks for your reply. On Tue, Jun 21, 2016 at 11:39 PM, Archit Taneja wrote: > Hi, > > On 6/20/2016 12:44 PM, Nicolas Boichat wrote: >> >> ANX7688 is a HDMI to DP converter (as well as USB-C port controller), >> that has an internal microcontroller. >> >> The

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

Hi Archit, Thanks for your reply. On Tue, Jun 21, 2016 at 11:39 PM, Archit Taneja wrote: > Hi, > > On 6/20/2016 12:44 PM, Nicolas Boichat wrote: >> >> ANX7688 is a HDMI to DP converter (as well as USB-C port controller), >> that has an internal microcontroller. >> >> The only reason a Linux

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

Hi, On 6/20/2016 12:44 PM, Nicolas Boichat wrote: ANX7688 is a HDMI to DP converter (as well as USB-C port controller), that has an internal microcontroller. The only reason a Linux kernel driver is necessary is to reject resolutions that require more bandwidth than what is available on the DP

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

Hi, On 6/20/2016 12:44 PM, Nicolas Boichat wrote: ANX7688 is a HDMI to DP converter (as well as USB-C port controller), that has an internal microcontroller. The only reason a Linux kernel driver is necessary is to reject resolutions that require more bandwidth than what is available on the DP

[RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

ANX7688 is a HDMI to DP converter (as well as USB-C port controller), that has an internal microcontroller. The only reason a Linux kernel driver is necessary is to reject resolutions that require more bandwidth than what is available on the DP side. DP bandwidth and lane count are reported by

[RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

ANX7688 is a HDMI to DP converter (as well as USB-C port controller), that has an internal microcontroller. The only reason a Linux kernel driver is necessary is to reject resolutions that require more bandwidth than what is available on the DP side. DP bandwidth and lane count are reported by