On Mon, 2014-02-10 at 18:37 +0100, Daniel Vetter wrote:
> On Mon, Feb 10, 2014 at 12:15:27PM +0200, Imre Deak wrote:
> > On Mon, 2014-02-10 at 10:23 +0100, Daniel Vetter wrote:
> > > On Sat, Feb 08, 2014 at 02:52:11AM +0200, Imre Deak wrote:
> > > > Atm we set the parent of the dp i2c device to be
On Mon, Feb 10, 2014 at 12:15:27PM +0200, Imre Deak wrote:
> On Mon, 2014-02-10 at 10:23 +0100, Daniel Vetter wrote:
> > On Sat, Feb 08, 2014 at 02:52:11AM +0200, Imre Deak wrote:
> > > Atm we set the parent of the dp i2c device to be the correspondig
> > > connector device. During driver cleanup w
On Mon, 2014-02-10 at 10:23 +0100, Daniel Vetter wrote:
> On Sat, Feb 08, 2014 at 02:52:11AM +0200, Imre Deak wrote:
> > Atm we set the parent of the dp i2c device to be the correspondig
> > connector device. During driver cleanup we first remove the connector
> > device through intel_modeset_clean
On Sat, Feb 08, 2014 at 02:52:11AM +0200, Imre Deak wrote:
> Atm we set the parent of the dp i2c device to be the correspondig
> connector device. During driver cleanup we first remove the connector
> device through intel_modeset_cleanup()->drm_sysfs_connector_remove() and
> only after that the i2c
Atm we set the parent of the dp i2c device to be the correspondig
connector device. During driver cleanup we first remove the connector
device through intel_modeset_cleanup()->drm_sysfs_connector_remove() and
only after that the i2c device through the encoder's destroy callback.
This order is not s
