Re: [PATCH v4 5/5] drm: simpledrm: honour remove_conflicting_framebuffers()

2016-08-23 Thread Noralf Trønnes
Den 23.08.2016 20:01, skrev Daniel Vetter: On Tue, Aug 23, 2016 at 7:52 PM, Noralf Trønnes wrote: +static int sdrm_fbdev_event_notify(struct notifier_block *self, + unsigned long action, void *data) +{ + struct sdrm_device *sdrm; +

Re: [PATCH v4 5/5] drm: simpledrm: honour remove_conflicting_framebuffers()

2016-08-23 Thread Noralf Trønnes
Den 23.08.2016 20:01, skrev Daniel Vetter: On Tue, Aug 23, 2016 at 7:52 PM, Noralf Trønnes wrote: +static int sdrm_fbdev_event_notify(struct notifier_block *self, + unsigned long action, void *data) +{ + struct sdrm_device *sdrm; + struct fb_event

Re: [PATCH v4 5/5] drm: simpledrm: honour remove_conflicting_framebuffers()

2016-08-23 Thread Daniel Vetter
On Tue, Aug 23, 2016 at 7:52 PM, Noralf Trønnes wrote: >>> +static int sdrm_fbdev_event_notify(struct notifier_block *self, >>> + unsigned long action, void *data) >>> +{ >>> + struct sdrm_device *sdrm; >>> + struct fb_event *event

Re: [PATCH v4 5/5] drm: simpledrm: honour remove_conflicting_framebuffers()

2016-08-23 Thread Daniel Vetter
On Tue, Aug 23, 2016 at 7:52 PM, Noralf Trønnes wrote: >>> +static int sdrm_fbdev_event_notify(struct notifier_block *self, >>> + unsigned long action, void *data) >>> +{ >>> + struct sdrm_device *sdrm; >>> + struct fb_event *event = data; >>> +

Re: [PATCH v4 5/5] drm: simpledrm: honour remove_conflicting_framebuffers()

2016-08-23 Thread Noralf Trønnes
Den 23.08.2016 14:41, skrev Daniel Vetter: On Mon, Aug 22, 2016 at 10:25:25PM +0200, Noralf Trønnes wrote: There is currently no non-fbdev mechanism in place to kick out simpledrm when the real hw-driver is probed. As a stop gap until that is in place, honour remove_conflicting_framebuffers()

Re: [PATCH v4 5/5] drm: simpledrm: honour remove_conflicting_framebuffers()

2016-08-23 Thread Noralf Trønnes
Den 23.08.2016 14:41, skrev Daniel Vetter: On Mon, Aug 22, 2016 at 10:25:25PM +0200, Noralf Trønnes wrote: There is currently no non-fbdev mechanism in place to kick out simpledrm when the real hw-driver is probed. As a stop gap until that is in place, honour remove_conflicting_framebuffers()

Re: [PATCH v4 5/5] drm: simpledrm: honour remove_conflicting_framebuffers()

2016-08-23 Thread Daniel Vetter
On Mon, Aug 22, 2016 at 10:25:25PM +0200, Noralf Trønnes wrote: > There is currently no non-fbdev mechanism in place to kick out > simpledrm when the real hw-driver is probed. As a stop gap until > that is in place, honour remove_conflicting_framebuffers() and > delete the simple-framebuffer

Re: [PATCH v4 5/5] drm: simpledrm: honour remove_conflicting_framebuffers()

2016-08-23 Thread Daniel Vetter
On Mon, Aug 22, 2016 at 10:25:25PM +0200, Noralf Trønnes wrote: > There is currently no non-fbdev mechanism in place to kick out > simpledrm when the real hw-driver is probed. As a stop gap until > that is in place, honour remove_conflicting_framebuffers() and > delete the simple-framebuffer

[PATCH v4 5/5] drm: simpledrm: honour remove_conflicting_framebuffers()

2016-08-22 Thread Noralf Trønnes
There is currently no non-fbdev mechanism in place to kick out simpledrm when the real hw-driver is probed. As a stop gap until that is in place, honour remove_conflicting_framebuffers() and delete the simple-framebuffer platform device when it's called. Signed-off-by: Noralf Trønnes

[PATCH v4 5/5] drm: simpledrm: honour remove_conflicting_framebuffers()

2016-08-22 Thread Noralf Trønnes
There is currently no non-fbdev mechanism in place to kick out simpledrm when the real hw-driver is probed. As a stop gap until that is in place, honour remove_conflicting_framebuffers() and delete the simple-framebuffer platform device when it's called. Signed-off-by: Noralf Trønnes ---