On Mon, May 15, 2017 at 03:33:12PM +0300, Ville Syrjälä wrote: > On Mon, May 15, 2017 at 02:04:43PM +0200, Daniel Vetter wrote: > > On Sat, May 13, 2017 at 11:52:01AM +0100, Chris Wilson wrote: > > > As we can have multiple tx in the queue, with individual waiters, make > > > sure that all are woken when any state changes (so that we are sure the > > > right owner of the txmsg is woken). > > > > > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > > > > I think in practice we need probe vs. the userspace dp aux interface (or > > multiple userspace apps beating on this), and on multiple different mst > > sinks, but better safe than sorry. > > Someone has to figure out what I did wrong in my remote DPCD aux_dev > attempt before we can actually do that: > > [1] git://github.com/vsyrjala/linux.git dp_mst_port_aux_dev Oh, I didn't realize we don't register the full dp aux for remotes. But we do register the i2c for remotes, and that's good enough to blow up. i2c dev nodes is also more likely to be used by userspace for real (through the ddc tool). -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
