Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1700041

Re: [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia N900

From Tomi Valkeinen <tomi.valkeinen@ti.com>
Newsgroups linux.kernel
Subject Re: [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia N900
Date 2017-07-31 15:30 +0200
Message-ID <u9iVH-6No-17@gated-at.bofh.it> (permalink)
References <tSoNP-2uY-3@gated-at.bofh.it> <tSwV4-7xc-21@gated-at.bofh.it> <tXMPw-2Ms-27@gated-at.bofh.it> <tXXUB-1XJ-5@gated-at.bofh.it> <tY3nk-5u2-25@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On 30/06/17 15:36, Daniel Vetter wrote:

> I don't think registering before everything is loaded make sense. On the
> big desktop driver chips we have all the bridge/encoder/panel drivers
> built into the driver. arm-soc loves to make everything a separate module,
> but in the end if you decided to not compile half of the driver you need,
> then it's not going to work.

I don't think that's quite the same. On the desktop you just have the
video card, and it's easy to enable that single component. On an
embedded device you have the SoC's display controller and then possibly
multiple external encoders/panels on the board. Those external
components have to be separate modules, they can't be part of the SoC
driver. The desktop video card matches only to the SoC's display controller.

> Imo the only thing we should support to be hotplugged in drm is stuff you
> can physically hotplug (like atm connectors). Everything else just
> complicates the code for no good reason at all.

"unplugging" components would not give much, I think, but allowing
adding new displays at runtime would be a very good thing.

It's not only about mistakenly having the driver disabled in the kernel
config, it could also be that some base driver failed to probe, which
then makes an encoder or a panel to defer probing as it can't get the
base resource. But HDMI or some other panel would work fine, but with
current architecture can't be used.

And if you really want to optimize, one a phone-type device you could
have the LCD driver built-in, but HDMI drivers as modules, and only load
the HDMI drivers if the user actually needs the HDMI.

 Tomi

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

Re: [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia  N900 Tomi Valkeinen <tomi.valkeinen@ti.com> - 2017-07-31 15:30 +0200
  Re: [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia  N900 Daniel Vetter <daniel@ffwll.ch> - 2017-08-02 12:20 +0200
    Re: [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia N900 Daniel Vetter <daniel@ffwll.ch> - 2017-08-02 14:10 +0200
    Re: [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia  N900 Tomi Valkeinen <tomi.valkeinen@ti.com> - 2017-08-02 14:10 +0200

csiph-web