On 02/05/2014 12:18 PM, Mark Brown wrote:
On Wed, Feb 05, 2014 at 10:19:22AM +0100, Lars-Peter Clausen wrote:
[..]
Bonus points for making this a generic helper function that takes a
runtime and a EDID and then applies the EDID constraints on the
runtime.
...as previously requested. I know there was some discusion of broader
moves to factor this stuff out but it'd still be good to keep it
separated out even prior to a final non-EDID based solution so it's
easier to refactor.
I think it will always be EDID (or ELD) based. As I understood it the
re-factoring Takashi was talking about is related to how this data is passed
from the graphics driver to the audio driver. The way things work right now
in HDA land is that the graphics driver reads the EDID from the monitor,
converts it to ELD and writes it to a special memory region in the graphics
controller. This generates an interrupt in the audio driver and the audio
driver reads the ELD from the hardware and sets up the constraints based on
that. And I think that the plan is to change this to pass the EDID directly
from the graphics driver to the audio driver without taking the detour
through the hardware. This is what we'll need for embedded systems anyway. A
system that allows to associate a sound driver with a specific HDMI port and
status updates for that port, e.g. new EDID or cable connected/disconnected
are passed from the graphics driver handling that port to the audio driver.
- Lars
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel
