* Merlijn Wajer <merlijn@xxxxxxxxxx> [171026 06:28]: > On 26/10/17 00:07, Tony Lindgren wrote: > > * Merlijn Wajer <merlijn@xxxxxxxxxx> [171025 14:54]: > >> Hi, > >> > >> I have been trying to get HDMI to work on the Motorola Droid4, as I saw > >> that it should be supported. When I enable DRM_OMAP, OMAP4_DSS_HDMI and > >> DRM_OMAP_CONNECTOR_HDMI, I don't get any output on HDMI (Full config > >> here [1], for Linux 4.14-rc4). I see this in dmesg (repeatedly) [2]: > >> > >> [ 21.360321] of_get_named_gpiod_flags: parsed 'hpd-gpios' property of > >> node '/connector[0]' - status (0) > >> [ 21.370147] connector-hdmi connector: failed to find video source > >> > >> My hunch is that perhaps something is missing in the device tree, but > >> after looking for time in the omapdrm code I cannot figure it out. Am I > >> perhaps missing some configuration options? > >> > >> I also do not seem to have any /dev/dri entries, although I did expect > >> to see them. > > > > Hmm I've been using it a lot over past six months with lapdock with > > typically updating to Linux next about once a week or every few weeks. > > I'm just using pending LCD and backlight patches, and omap2plus_defconfig > > with following patch. Maybe see if you're missing something from that > > patch? > > > > Also Tomi pointed out earlier that n900 needed the analog tv module > > loaded for LCD output.. I wonder if you need also the pending LCD > > patches applied? > > I presume you mean these 14 patches, where this is the first one: > https://patchwork.kernel.org/patch/9860917/ > > I have applied these 14 patches on top of 4.14-rc4 without errors. I've > also added the config options that you suggested. With new modules, > kernel and devtree I don't get that many 'connector-hdmi' errors, > suggesting that this error may be solved, but I still don't seem to get > any output on HDMI. > > There seems to be another/new error relating to some missing te-gpios > (or te-gpio) in the device tree, that the n950 device tree does have, > but the droid4 device tree does not have? I think these are harmless. I don't think there is such a GPIO on droid 4, or if there is we don't know the GPIO number. > The LCD doesn't seem to show anything either. Here is the kernel output > [1], and my current config [2]. Oh OK, you also need the pending TI LMU backlight patches: https://patchwork.kernel.org/patch/9845089/ https://patchwork.kernel.org/patch/9845087/ Sebastian's blog has a status matrix that should have links to the most recent pending patches: http://elektranox.org/droid4/ > /dev/dri/* is also still missing - it is still my assumption that this > should show up if all goes well - is this correct? Yeah you should get the unaccelerated dri available: $ find /dev/dri/ /dev/dri/ /dev/dri/card0 /dev/dri/by-path /dev/dri/by-path/platform-omapdrm.0-card /dev/dri/by-path/platform-omapdrm.0-render /dev/dri/renderD128 Not sure if and why we have some ordering problem with DSS if one of the dts configured displays is not loaded. Also note that Linux next has the omap4 CEC driver merged that might provide some fun too once you get things working. Regards, Tony > [1] http://sprunge.us/DZXf > [2] http://sprunge.us/WhJL -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
