On Fri, 27 Mar 2015, Alex Deucher wrote:
> On Fri, Mar 27, 2015 at 8:08 AM, Jani Nikula wrote:
>> On Thu, 26 Mar 2015, Daniel Vetter wrote:
>>> On Thu, Mar 26, 2015 at 10:42:00AM +0200, Jani Nikula wrote:
If the user supplies EDID through firmware or debugfs override, the
driver callba
On Thu, 26 Mar 2015, Daniel Vetter wrote:
> On Thu, Mar 26, 2015 at 10:42:00AM +0200, Jani Nikula wrote:
>> If the user supplies EDID through firmware or debugfs override, the
>> driver callbacks are bypassed and the connector ELD does not get
>> updated, and audio fails. Set ELD for firmware and
On Fri, Mar 27, 2015 at 12:02 PM, Jani Nikula wrote:
> On Fri, 27 Mar 2015, Alex Deucher wrote:
>> On Fri, Mar 27, 2015 at 8:08 AM, Jani Nikula
>> wrote:
>>> On Thu, 26 Mar 2015, Daniel Vetter wrote:
On Thu, Mar 26, 2015 at 10:42:00AM +0200, Jani Nikula wrote:
> If the user supplies E
On Fri, Mar 27, 2015 at 8:08 AM, Jani Nikula wrote:
> On Thu, 26 Mar 2015, Daniel Vetter wrote:
>> On Thu, Mar 26, 2015 at 10:42:00AM +0200, Jani Nikula wrote:
>>> If the user supplies EDID through firmware or debugfs override, the
>>> driver callbacks are bypassed and the connector ELD does not
On Thu, Mar 26, 2015 at 10:42:00AM +0200, Jani Nikula wrote:
> If the user supplies EDID through firmware or debugfs override, the
> driver callbacks are bypassed and the connector ELD does not get
> updated, and audio fails. Set ELD for firmware and debugfs EDIDs too.
>
> There should be no harm