Comment # 12 on bug 1204315 from Ivan Ivanov

(In reply to Takashi Iwai from comment #11)

> Could you check what conflicts in those memory area by looking at
> /proc/iomem?

/proc/iomem don't show anything.

Error starts in devm_aperture_acquire(), where simpledrm tries to
add new resource to the list of apertures, but finds that there is
already one which cover same memory region. And it looks like the
aperture was added by ... simpledrm module.

simple-framebuffer simple-framebuffer.0: Conflicting range [mem
0x3e402000-0x3ebeb000 flags 0x200] with simple-framebuffer:
3e402000.framebuffer range: [mem 0x3e402000-0x3ebfa000 flags 0x200]

I am not sure that is difference between simple-framebuffer.0 and
3e402000.framebuffer devices. Above shows that when simple-framebuffer.0 device
try to register 0x3e402000-0x3ebfa000 aperture it finds that the same was
already registred for 3e402000.framebuffer devices.