On Mon, May 5, 2014 at 7:14 PM, Dylan Reid <dgreid@xxxxxxxxxx> wrote: > On Mon, May 5, 2014 at 1:32 PM, Thierry Reding <thierry.reding@xxxxxxxxx> wrote: >> On Mon, May 05, 2014 at 12:07:51PM -0700, Dylan Reid wrote: >>> Hi Thierry, >>> >>> Did you have to make any user-space changes to test the HDMI output on >>> Venice2? I've got your recent patch series and see the hdmi device >>> being probed but I haven't figured out how to get X to use it. I'm >>> using the sample rootfs that was posted for the Jetson board. >> >> I've used custom userspace, but I would expect regular X to work with >> the patches as well. The sample rootfs probably comes with only the >> NVIDIA Tegra X driver installed. Have you tried installing the >> xf86-video-modesetting driver? That should automatically use the HDMI >> output if it's connected to a monitor. If not you should still be able >> to manually configure the outputs using xrandr. > > Thanks, I haven't gotten to the point where I can see a screen in > xrandr yet, I'll try to find some time to dig a little deeper this > week. > >> >>> My goal is to be able to test the hdmi audio changes on this as well >>> as our downstream kernel. >> >> Note that while there's some code to support HDMI audio, nobody's ever >> tested this upstream and it's likely not to work. So I think there may >> be more work required to get that running. I can help out with that, >> it's been on my list of things to do for a while. > > Understood, although what is upstream looks pretty similar to what is > in our tree so I'm optimistic =) Sorry I didn't get around to testing this until today. Luckily it worked, but I had to make two changes: 1) Make the hdmi entry in the tegra124 dt compatible with tegra114-hdmi. 2) Have driver/gpu/drm/tegra/hdmi.c enable hdmi-supply when enabling the pll supply, without this DDC doesn't work. Easy fixes, I'll post patches for these this weekend. -Dylan > >> >> Thierry -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html