On Wed, May 14, 2014 at 08:05:11AM +0200, David Herrmann wrote:
> Hi
>
> On Wed, May 14, 2014 at 2:03 AM, Dave Airlie wrote:
> > Since any objects you get with find are only valid under mode_config.mutex,
> > yes some drivers mess this up, but they should be fixed.
>
> Didn't know that we have
>
> So we leak all dynamically created objects? There's no
> kfree(intel_connector) here and we cannot add it because
> drm_mode_object_find() is not ref-counted. So we keep the connector in
> the mode_group and wait until the final drm_mode_config_cleanup()? But
> drm_connector_cleanup() already
Hi
On Wed, May 14, 2014 at 2:03 AM, Dave Airlie wrote:
> Since any objects you get with find are only valid under mode_config.mutex,
> yes some drivers mess this up, but they should be fixed.
Didn't know that we have such a rule. Then it's fine, of course. The
page-flip code is what worried me,
Hi Dave
On Mon, May 12, 2014 at 8:46 AM, Dave Airlie wrote:
> From: Dave Airlie
>
> This adds DP 1.2 MST support on Haswell systems.
>
> Notes:
> a) this reworks irq handling for DP MST ports, so that we can
> avoid the mode config locking in the current hpd handlers, as
> we need to process
From: Dave Airlie
This adds DP 1.2 MST support on Haswell systems.
Notes:
a) this reworks irq handling for DP MST ports, so that we can
avoid the mode config locking in the current hpd handlers, as
we need to process up/down msgs at a better time.
b) it introduces a new MST