No HDMI output on AC100

No HDMI output on AC100

[Thomas Meyer]

Hi,

Kernel version: 3.10.0-0.rc4.git0.1.fc20.armv7hl

This is the latest Fedora ARM kernel. Config is available here:
http://pkgs.fedoraproject.org/cgit/kernel.git/tree/config-armv7

Package is here:
http://arm.koji.fedoraproject.org/koji/packageinfo?packageID=3547

After connecting my LC display to the hdmi output, it tells me that the "singal is out of range"

This is what I see in the kernel log:

$ dmesg |grep hdmi
[   33.403417] tegra-hdmi 54280000.hdmi: failed to get VDD regulator
[   33.403441] platform 54280000.hdmi: Driver tegra-hdmi requests probe deferral
[   33.429833] +3.3vs_ldo7,avdd_hdmi: 3300 mV 
[   33.430023] +3.3vs_ldo7,avdd_hdmi: supplied by +3.7vs_sm2,vin_ldo*
[   33.431246] +1.8vs_ldo8,avdd_hdmi_pll: 1800 mV 
[   33.431434] +1.8vs_ldo8,avdd_hdmi_pll: supplied by +3.7vs_sm2,vin_ldo*
[  979.737773] tegra-hdmi 54280000.hdmi: cannot set audio to 44100 at 65000000 pclk

any ideas?

with kind regards
thomas

Re: No HDMI output on AC100

[Marc Dietrich]

Hi Thomas,

On Saturday 08 June 2013 10:33:55 Thomas Meyer wrote:
> Hi,
> 
> Kernel version: 3.10.0-0.rc4.git0.1.fc20.armv7hl
> 
> This is the latest Fedora ARM kernel. Config is available here:
> http://pkgs.fedoraproject.org/cgit/kernel.git/tree/config-armv7
> 
> Package is here:
> http://arm.koji.fedoraproject.org/koji/packageinfo?packageID=3547
> 
> After connecting my LC display to the hdmi output, it tells me that the
> "singal is out of range"
> 
> This is what I see in the kernel log:
> 
> $ dmesg |grep hdmi
> [   33.403417] tegra-hdmi 54280000.hdmi: failed to get VDD regulator
> [   33.403441] platform 54280000.hdmi: Driver tegra-hdmi requests probe
> deferral [   33.429833] +3.3vs_ldo7,avdd_hdmi: 3300 mV
> [   33.430023] +3.3vs_ldo7,avdd_hdmi: supplied by +3.7vs_sm2,vin_ldo*
> [   33.431246] +1.8vs_ldo8,avdd_hdmi_pll: 1800 mV
> [   33.431434] +1.8vs_ldo8,avdd_hdmi_pll: supplied by +3.7vs_sm2,vin_ldo*
> [  979.737773] tegra-hdmi 54280000.hdmi: cannot set audio to 44100 at
> 65000000 pclk
> 
> any ideas?

is the regulator (tps6586x) build-in? The make everything a module path isn't 
well tested I guess. 

Marc

Re: No HDMI output on AC100

[Thomas Meyer]

> On Saturday 08 June 2013 10:33:55 Thomas Meyer wrote:
>> Kernel version: 3.10.0-0.rc4.git0.1.fc20.armv7hl
>> 
>> This is the latest Fedora ARM kernel. Config is available here:
>> http://pkgs.fedoraproject.org/cgit/kernel.git/tree/config-armv7
>> 
>> This is what I see in the kernel log:
>> 
>> $ dmesg |grep hdmi
>> [   33.403417] tegra-hdmi 54280000.hdmi: failed to get VDD regulator
>> [   33.403441] platform 54280000.hdmi: Driver tegra-hdmi requests probe
>> 
>> any ideas?
> 
> is the regulator (tps6586x) build-in?

No, it's a module.

> The make everything a module path isn't 
> well tested I guess. 

Oh... So how to fix this?!

> 
> Marc

Re: No HDMI output on AC100

[Marc Dietrich]

On Saturday 08 June 2013 16:21:59 Thomas Meyer wrote:
> > On Saturday 08 June 2013 10:33:55 Thomas Meyer wrote:
> >> Kernel version: 3.10.0-0.rc4.git0.1.fc20.armv7hl
> >> 
> >> This is the latest Fedora ARM kernel. Config is available here:
> >> http://pkgs.fedoraproject.org/cgit/kernel.git/tree/config-armv7
> >> 
> >> This is what I see in the kernel log:
> >> 
> >> $ dmesg |grep hdmi
> >> [   33.403417] tegra-hdmi 54280000.hdmi: failed to get VDD regulator
> >> [   33.403441] platform 54280000.hdmi: Driver tegra-hdmi requests probe
> >> 
> >> any ideas?
> > 
> > is the regulator (tps6586x) build-in?
> 
> No, it's a module.
> 
> > The make everything a module path isn't
> > well tested I guess.
> 
> Oh... So how to fix this?!

mmh, either

a) try to load the module in initrd before everything else (but after i2c)
b) ask the fedora people to make it build-in
c) ask Thierry (added to cc) if this could be a tegra drm problem

Marc

Re: No HDMI output on AC100

[Lucas Stach]

[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]

Am Samstag, den 08.06.2013, 16:21 +0200 schrieb Thomas Meyer:
> > On Saturday 08 June 2013 10:33:55 Thomas Meyer wrote:
> >> Kernel version: 3.10.0-0.rc4.git0.1.fc20.armv7hl
> >> 
> >> This is the latest Fedora ARM kernel. Config is available here:
> >> http://pkgs.fedoraproject.org/cgit/kernel.git/tree/config-armv7
> >> 
> >> This is what I see in the kernel log:
> >> 
> >> $ dmesg |grep hdmi
> >> [   33.403417] tegra-hdmi 54280000.hdmi: failed to get VDD regulator
> >> [   33.403441] platform 54280000.hdmi: Driver tegra-hdmi requests probe
> >> 
> >> any ideas?
> > 
> > is the regulator (tps6586x) build-in?
> 
> No, it's a module.
> 
> > The make everything a module path isn't 
> > well tested I guess. 
> 
It's not the problem here. The driver requests to be probed again and
comes up once the regulator is there.

Though the pixel clock looks odd for a HD HDMI monitor. Try looking at
the Xorg log to see what mode of your monitor get's chosen and why it
fails.

Regards,
Lucas

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5715 bytes --]

Re: No HDMI output on AC100

[Marc Dietrich]

On Saturday 08 June 2013 18:05:52 Lucas Stach wrote:
> Am Samstag, den 08.06.2013, 16:21 +0200 schrieb Thomas Meyer:
> > > On Saturday 08 June 2013 10:33:55 Thomas Meyer wrote:
> > >> Kernel version: 3.10.0-0.rc4.git0.1.fc20.armv7hl
> > >> 
> > >> This is the latest Fedora ARM kernel. Config is available here:
> > >> http://pkgs.fedoraproject.org/cgit/kernel.git/tree/config-armv7
> > >> 
> > >> This is what I see in the kernel log:
> > >> 
> > >> $ dmesg |grep hdmi
> > >> [   33.403417] tegra-hdmi 54280000.hdmi: failed to get VDD regulator
> > >> [   33.403441] platform 54280000.hdmi: Driver tegra-hdmi requests probe
> > >> 
> > >> any ideas?
> > > 
> > > is the regulator (tps6586x) build-in?
> > 
> > No, it's a module.
> > 
> > > The make everything a module path isn't
> > > well tested I guess.
> 
> It's not the problem here. The driver requests to be probed again and
> comes up once the regulator is there.
> 
> Though the pixel clock looks odd for a HD HDMI monitor. Try looking at
> the Xorg log to see what mode of your monitor get's chosen and why it
> fails.

I just checked myself. Found that tps6586x-regulator module can't be 
autoloaded, so I connected my TV, booted and modprobed the module by hand.
All works more or less fine, so probe deferral is no problem.

Thomas, did you add cma=64M to you kernel command line? HDMI needs some 
memory.

Marc

Re: No HDMI output on AC100

[Stephen Warren]

On 06/08/2013 02:07 PM, Marc Dietrich wrote:
> On Saturday 08 June 2013 18:05:52 Lucas Stach wrote:
>> Am Samstag, den 08.06.2013, 16:21 +0200 schrieb Thomas Meyer:
>>>> On Saturday 08 June 2013 10:33:55 Thomas Meyer wrote:
>>>>> Kernel version: 3.10.0-0.rc4.git0.1.fc20.armv7hl
>>>>>
>>>>> This is the latest Fedora ARM kernel. Config is available here:
>>>>> http://pkgs.fedoraproject.org/cgit/kernel.git/tree/config-armv7
>>>>>
>>>>> This is what I see in the kernel log:
>>>>>
>>>>> $ dmesg |grep hdmi
>>>>> [   33.403417] tegra-hdmi 54280000.hdmi: failed to get VDD regulator
>>>>> [   33.403441] platform 54280000.hdmi: Driver tegra-hdmi requests probe
>>>>>
>>>>> any ideas?
>>>>
>>>> is the regulator (tps6586x) build-in?
>>>
>>> No, it's a module.
>>>
>>>> The make everything a module path isn't
>>>> well tested I guess.
>>
>> It's not the problem here. The driver requests to be probed again and
>> comes up once the regulator is there.
>>
>> Though the pixel clock looks odd for a HD HDMI monitor. Try looking at
>> the Xorg log to see what mode of your monitor get's chosen and why it
>> fails.
> 
> I just checked myself. Found that tps6586x-regulator module can't be 
> autoloaded, so I connected my TV, booted and modprobed the module by hand.
> All works more or less fine, so probe deferral is no problem.

It could well just be that the tps6586x driver is missing the module
correct MODULE_ALIAS that makes the module auto-load when the relevant
entry is in the DT. The top-level MFD driver does have a
MODULE_DEVICE_TABLE which should set this up automatically, so perhaps
it's because there's nothing causing the regulator MFD component to load
when the top-level MFD component loads?

Re: No HDMI output on AC100

[Thomas Meyer]

Am Samstag, den 08.06.2013, 22:07 +0200 schrieb Marc Dietrich:
> On Saturday 08 June 2013 18:05:52 Lucas Stach wrote:
> > Am Samstag, den 08.06.2013, 16:21 +0200 schrieb Thomas Meyer:
> > > > On Saturday 08 June 2013 10:33:55 Thomas Meyer wrote:
> > > >> Kernel version: 3.10.0-0.rc4.git0.1.fc20.armv7hl
> > > >> 
> > > >> This is the latest Fedora ARM kernel. Config is available here:
> > > >> http://pkgs.fedoraproject.org/cgit/kernel.git/tree/config-armv7
> > > >> 
> > > >> This is what I see in the kernel log:
> > > >> 
> > > >> $ dmesg |grep hdmi
> > > >> [   33.403417] tegra-hdmi 54280000.hdmi: failed to get VDD regulator
> > > >> [   33.403441] platform 54280000.hdmi: Driver tegra-hdmi requests probe
> > > >> 
> > > >> any ideas?
> > > > 
> > > > is the regulator (tps6586x) build-in?
> > > 
> > > No, it's a module.
> > > 
> > > > The make everything a module path isn't
> > > > well tested I guess.
> > 
> > It's not the problem here. The driver requests to be probed again and
> > comes up once the regulator is there.
> > 
> > Though the pixel clock looks odd for a HD HDMI monitor. Try looking at
> > the Xorg log to see what mode of your monitor get's chosen and why it
> > fails.
> 
> I just checked myself. Found that tps6586x-regulator module can't be 
> autoloaded, so I connected my TV, booted and modprobed the module by hand.
> All works more or less fine, so probe deferral is no problem.

I did also notice, that the module needs to loaded manually, so I put it
in /etc/modules-load.d/regulator.conf to let systemd load it on every
start.

> 
> Thomas, did you add cma=64M to you kernel command line? HDMI needs some 
> memory.

yes, I tried with cma=64M and without the cma option, but no success.

> 
> Marc
> 

Re: No HDMI output on AC100

[Thomas Meyer]

Am Samstag, den 08.06.2013, 18:05 +0200 schrieb Lucas Stach:
> Am Samstag, den 08.06.2013, 16:21 +0200 schrieb Thomas Meyer:
> > > On Saturday 08 June 2013 10:33:55 Thomas Meyer wrote:
> > >> Kernel version: 3.10.0-0.rc4.git0.1.fc20.armv7hl
> > >> 
> > >> This is the latest Fedora ARM kernel. Config is available here:
> > >> http://pkgs.fedoraproject.org/cgit/kernel.git/tree/config-armv7
> > >> 
> > >> This is what I see in the kernel log:
> > >> 
> > >> $ dmesg |grep hdmi
> > >> [   33.403417] tegra-hdmi 54280000.hdmi: failed to get VDD regulator
> > >> [   33.403441] platform 54280000.hdmi: Driver tegra-hdmi requests probe
> > >> 
> > >> any ideas?
> > > 
> > > is the regulator (tps6586x) build-in?
> > 
> > No, it's a module.
> > 
> > > The make everything a module path isn't 
> > > well tested I guess. 
> > 
> It's not the problem here. The driver requests to be probed again and
> comes up once the regulator is there.
> 
> Though the pixel clock looks odd for a HD HDMI monitor. Try looking at
> the Xorg log to see what mode of your monitor get's chosen and why it
> fails.

X fails to start because of this error:

xf86OpenConsole: VT_ACTIVATE failed: No such device or address

> 
> Regards,
> Lucas

Re: No HDMI output on AC100

[Thomas Meyer]

Am Samstag, den 08.06.2013, 18:05 +0200 schrieb Lucas Stach:
> Am Samstag, den 08.06.2013, 16:21 +0200 schrieb Thomas Meyer:
> > > On Saturday 08 June 2013 10:33:55 Thomas Meyer wrote:
> > >> Kernel version: 3.10.0-0.rc4.git0.1.fc20.armv7hl
> > >> 
> > >> This is the latest Fedora ARM kernel. Config is available here:
> > >> http://pkgs.fedoraproject.org/cgit/kernel.git/tree/config-armv7
> > >> 
> > >> This is what I see in the kernel log:
> > >> 
> > >> $ dmesg |grep hdmi
> > >> [   33.403417] tegra-hdmi 54280000.hdmi: failed to get VDD regulator
> > >> [   33.403441] platform 54280000.hdmi: Driver tegra-hdmi requests probe
> > >> 
> > >> any ideas?
> > > 
> > > is the regulator (tps6586x) build-in?
> > 
> > No, it's a module.
> > 
> > > The make everything a module path isn't 
> > > well tested I guess. 
> > 
> It's not the problem here. The driver requests to be probed again and
> comes up once the regulator is there.
> 
> Though the pixel clock looks odd for a HD HDMI monitor. Try looking at
> the Xorg log to see what mode of your monitor get's chosen and why it
> fails.

Some more kernel logs:

[   34.087790] tps6586x-rtc tps6586x-rtc: rtc core: registered tps6586x-rtc as rtc1
[   34.089788] tegra-hdmi 54280000.hdmi: failed to get VDD regulator
[   34.089810] platform 54280000.hdmi: Driver tegra-hdmi requests probe deferral
[   34.102695] vdd_sys: no parameters
[   34.102731] vdd_sys: supplied by +5valw
[   34.104278] +1.2vs_sm0,vdd_core: 1200 mV 
[   34.104490] +1.2vs_sm0,vdd_core: supplied by vdd_sys
[   34.106047] +1.0vs_sm1,vdd_cpu: 1000 mV 
[   34.106240] +1.0vs_sm1,vdd_cpu: supplied by vdd_sys
[   34.107759] +3.7vs_sm2,vin_ldo*: 3700 mV 
[   34.108000] +3.7vs_sm2,vin_ldo*: supplied by vdd_sys
[   34.108773] REG-LDO_0: at 1200 mV 
[   34.108961] REG-LDO_0: supplied by +3.7vs_sm2,vin_ldo*
[   34.110586] +1.1vs_ldo1,avdd_pll*: 1100 mV 
[   34.110782] +1.1vs_ldo1,avdd_pll*: supplied by +3.7vs_sm2,vin_ldo*
[   34.112252] +1.2vs_ldo2,vdd_rtc: 1200 mV 
[   34.112747] +1.2vs_ldo2,vdd_rtc: supplied by +3.7vs_sm2,vin_ldo*
[   34.114529] +3.3vs_ldo3,avdd_usb*: 3300 mV 
[   34.114791] +3.3vs_ldo3,avdd_usb*: supplied by +3.7vs_sm2,vin_ldo*
[   34.116841] +1.8vs_ldo4,avdd_osc,vddio_sys: 1800 mV 
[   34.117077] +1.8vs_ldo4,avdd_osc,vddio_sys: supplied by +3.7vs_sm2,vin_ldo*
[   34.118239] +2.85vs_ldo5,vcore_mmc: 2850 mV 
[   34.119534] +2.85vs_ldo6,avdd_vdac: 1800 mV 
[   34.119726] +2.85vs_ldo6,avdd_vdac: supplied by +3.7vs_sm2,vin_ldo*
[   34.121021] +3.3vs_ldo7,avdd_hdmi: 3300 mV 
[   34.121212] +3.3vs_ldo7,avdd_hdmi: supplied by +3.7vs_sm2,vin_ldo*
[   34.122431] +1.8vs_ldo8,avdd_hdmi_pll: 1800 mV 
[   34.122620] +1.8vs_ldo8,avdd_hdmi_pll: supplied by +3.7vs_sm2,vin_ldo*
[   34.123690] +2.85vs_ldo9,vdd_ddr_rx: 2850 mV 
[   34.123954] +2.85vs_ldo9,vdd_ddr_rx: supplied by +3.7vs_sm2,vin_ldo*
[   34.125020] +3.3vs_rtc: 3300 mV 
[   34.126866] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[   34.126878] [drm] No driver support for vblank timestamp query.
[   34.189478] Console: switching to colour frame buffer device 240x67
[   34.214505] tegra-host1x 50000000.host1x: fb0:  frame buffer device
[   34.214517] tegra-host1x 50000000.host1x: registered panic notifier
[   34.214597] [drm] Initialized tegra 0.0.0 20120330 on minor 0

Re: No HDMI output on AC100

[Thomas Meyer]

Am Samstag, den 08.06.2013, 22:07 +0200 schrieb Marc Dietrich:
> On Saturday 08 June 2013 18:05:52 Lucas Stach wrote:
> > Am Samstag, den 08.06.2013, 16:21 +0200 schrieb Thomas Meyer:
> > > > On Saturday 08 June 2013 10:33:55 Thomas Meyer wrote:
> > > >> Kernel version: 3.10.0-0.rc4.git0.1.fc20.armv7hl
> > > >> 
> > > >> This is the latest Fedora ARM kernel. Config is available here:
> > > >> http://pkgs.fedoraproject.org/cgit/kernel.git/tree/config-armv7
> > > >> 
> > > >> This is what I see in the kernel log:
> > > >> 
> > > >> $ dmesg |grep hdmi
> > > >> [   33.403417] tegra-hdmi 54280000.hdmi: failed to get VDD regulator
> > > >> [   33.403441] platform 54280000.hdmi: Driver tegra-hdmi requests probe
> > > >> 
> > > >> any ideas?
> > > > 
> > > > is the regulator (tps6586x) build-in?
> > > 
> > > No, it's a module.
> > > 
> > > > The make everything a module path isn't
> > > > well tested I guess.
> > 
> > It's not the problem here. The driver requests to be probed again and
> > comes up once the regulator is there.
> > 
> > Though the pixel clock looks odd for a HD HDMI monitor. Try looking at
> > the Xorg log to see what mode of your monitor get's chosen and why it
> > fails.
> 
> I just checked myself. Found that tps6586x-regulator module can't be 
> autoloaded, so I connected my TV, booted and modprobed the module by hand.
> All works more or less fine, so probe deferral is no problem.
> 
> Thomas, did you add cma=64M to you kernel command line? HDMI needs some 
> memory.
> 
oops! I think everthing did always work correctly! But somehow Fedora 19
fails to spawn a getty on the tty1/fb0 console... so I just did see a
black screen :-)

> Marc
> 

Re: No HDMI output on AC100

[Marc Dietrich]

On Saturday 08 June 2013 20:45:17 Stephen Warren wrote:
> On 06/08/2013 02:07 PM, Marc Dietrich wrote:
> > On Saturday 08 June 2013 18:05:52 Lucas Stach wrote:
> >> Am Samstag, den 08.06.2013, 16:21 +0200 schrieb Thomas Meyer:
> >>>> On Saturday 08 June 2013 10:33:55 Thomas Meyer wrote:
> >>>>> Kernel version: 3.10.0-0.rc4.git0.1.fc20.armv7hl
> >>>>> 
> >>>>> This is the latest Fedora ARM kernel. Config is available here:
> >>>>> http://pkgs.fedoraproject.org/cgit/kernel.git/tree/config-armv7
> >>>>> 
> >>>>> This is what I see in the kernel log:
> >>>>> 
> >>>>> $ dmesg |grep hdmi
> >>>>> [   33.403417] tegra-hdmi 54280000.hdmi: failed to get VDD regulator
> >>>>> [   33.403441] platform 54280000.hdmi: Driver tegra-hdmi requests
> >>>>> probe
> >>>>> 
> >>>>> any ideas?
> >>>> 
> >>>> is the regulator (tps6586x) build-in?
> >>> 
> >>> No, it's a module.
> >>> 
> >>>> The make everything a module path isn't
> >>>> well tested I guess.
> >> 
> >> It's not the problem here. The driver requests to be probed again and
> >> comes up once the regulator is there.
> >> 
> >> Though the pixel clock looks odd for a HD HDMI monitor. Try looking at
> >> the Xorg log to see what mode of your monitor get's chosen and why it
> >> fails.
> > 
> > I just checked myself. Found that tps6586x-regulator module can't be
> > autoloaded, so I connected my TV, booted and modprobed the module by hand.
> > All works more or less fine, so probe deferral is no problem.
> 
> It could well just be that the tps6586x driver is missing the module
> correct MODULE_ALIAS that makes the module auto-load when the relevant
> entry is in the DT. The top-level MFD driver does have a
> MODULE_DEVICE_TABLE which should set this up automatically, so perhaps
> it's because there's nothing causing the regulator MFD component to load
> when the top-level MFD component loads?

the core driver adds sub devices, but in case of DT, the number of subdevices 
is zero AFAICS (tps6586x_parse_dt). However, these subdevs do not include the 
regulators.

Also, the regulator nodes don't have a compatibly property, so direct probing 
won't work.

I have no idea how the regulators are probed at all...

Re: No HDMI output on AC100

[Marc Dietrich]

On Sunday 09 June 2013 13:42:46 Marc Dietrich wrote:
> On Saturday 08 June 2013 20:45:17 Stephen Warren wrote:
> > On 06/08/2013 02:07 PM, Marc Dietrich wrote:
> > > On Saturday 08 June 2013 18:05:52 Lucas Stach wrote:
> > >> Am Samstag, den 08.06.2013, 16:21 +0200 schrieb Thomas Meyer:
> > >>>> On Saturday 08 June 2013 10:33:55 Thomas Meyer wrote:
> > >>>>> Kernel version: 3.10.0-0.rc4.git0.1.fc20.armv7hl
> > >>>>> 
> > >>>>> This is the latest Fedora ARM kernel. Config is available here:
> > >>>>> http://pkgs.fedoraproject.org/cgit/kernel.git/tree/config-armv7
> > >>>>> 
> > >>>>> This is what I see in the kernel log:
> > >>>>> 
> > >>>>> $ dmesg |grep hdmi
> > >>>>> [   33.403417] tegra-hdmi 54280000.hdmi: failed to get VDD regulator
> > >>>>> [   33.403441] platform 54280000.hdmi: Driver tegra-hdmi requests
> > >>>>> probe
> > >>>>> 
> > >>>>> any ideas?
> > >>>> 
> > >>>> is the regulator (tps6586x) build-in?
> > >>> 
> > >>> No, it's a module.
> > >>> 
> > >>>> The make everything a module path isn't
> > >>>> well tested I guess.
> > >> 
> > >> It's not the problem here. The driver requests to be probed again and
> > >> comes up once the regulator is there.
> > >> 
> > >> Though the pixel clock looks odd for a HD HDMI monitor. Try looking at
> > >> the Xorg log to see what mode of your monitor get's chosen and why it
> > >> fails.
> > > 
> > > I just checked myself. Found that tps6586x-regulator module can't be
> > > autoloaded, so I connected my TV, booted and modprobed the module by
> > > hand.
> > > All works more or less fine, so probe deferral is no problem.
> > 
> > It could well just be that the tps6586x driver is missing the module
> > correct MODULE_ALIAS that makes the module auto-load when the relevant
> > entry is in the DT. The top-level MFD driver does have a
> > MODULE_DEVICE_TABLE which should set this up automatically, so perhaps
> > it's because there's nothing causing the regulator MFD component to load
> > when the top-level MFD component loads?
> 
> the core driver adds sub devices, but in case of DT, the number of
> subdevices is zero AFAICS (tps6586x_parse_dt). However, these subdevs do
> not include the regulators.

ah, the driver is named tps6586x-pmic (and the module alias is tps6586x-
regulator), so in case of platform_device type init, it is probed.

> Also, the regulator nodes don't have a compatibly property, so direct
> probing won't work.
> 
> I have no idea how the regulators are probed at all...

just found subsys_initcall(tps6586x_regulator_init), so the regulator is 
forced probed if build-in.

I guess replacing this by module_init (or better the short hand macro) should 
work now that deferral probing is working. Correct? Will try out...

Marc

Re: No HDMI output on AC100

[Marc Dietrich]

On Sunday 09 June 2013 14:02:16 Marc Dietrich wrote:
> On Sunday 09 June 2013 13:42:46 Marc Dietrich wrote:
> > On Saturday 08 June 2013 20:45:17 Stephen Warren wrote:
> > > On 06/08/2013 02:07 PM, Marc Dietrich wrote:
> > > > On Saturday 08 June 2013 18:05:52 Lucas Stach wrote:
> > > >> Am Samstag, den 08.06.2013, 16:21 +0200 schrieb Thomas Meyer:
> > > >>>> On Saturday 08 June 2013 10:33:55 Thomas Meyer wrote:
> > > >>>>> Kernel version: 3.10.0-0.rc4.git0.1.fc20.armv7hl
> > > >>>>> 
> > > >>>>> This is the latest Fedora ARM kernel. Config is available here:
> > > >>>>> http://pkgs.fedoraproject.org/cgit/kernel.git/tree/config-armv7
> > > >>>>> 
> > > >>>>> This is what I see in the kernel log:
> > > >>>>> 
> > > >>>>> $ dmesg |grep hdmi
> > > >>>>> [   33.403417] tegra-hdmi 54280000.hdmi: failed to get VDD
> > > >>>>> regulator
> > > >>>>> [   33.403441] platform 54280000.hdmi: Driver tegra-hdmi requests
> > > >>>>> probe
> > > >>>>> 
> > > >>>>> any ideas?
> > > >>>> 
> > > >>>> is the regulator (tps6586x) build-in?
> > > >>> 
> > > >>> No, it's a module.
> > > >>> 
> > > >>>> The make everything a module path isn't
> > > >>>> well tested I guess.
> > > >> 
> > > >> It's not the problem here. The driver requests to be probed again and
> > > >> comes up once the regulator is there.
> > > >> 
> > > >> Though the pixel clock looks odd for a HD HDMI monitor. Try looking
> > > >> at
> > > >> the Xorg log to see what mode of your monitor get's chosen and why it
> > > >> fails.
> > > > 
> > > > I just checked myself. Found that tps6586x-regulator module can't be
> > > > autoloaded, so I connected my TV, booted and modprobed the module by
> > > > hand.
> > > > All works more or less fine, so probe deferral is no problem.
> > > 
> > > It could well just be that the tps6586x driver is missing the module
> > > correct MODULE_ALIAS that makes the module auto-load when the relevant
> > > entry is in the DT. The top-level MFD driver does have a
> > > MODULE_DEVICE_TABLE which should set this up automatically, so perhaps
> > > it's because there's nothing causing the regulator MFD component to load
> > > when the top-level MFD component loads?
> > 
> > the core driver adds sub devices, but in case of DT, the number of
> > subdevices is zero AFAICS (tps6586x_parse_dt). However, these subdevs do
> > not include the regulators.
> 
> ah, the driver is named tps6586x-pmic (and the module alias is tps6586x-
> regulator), so in case of platform_device type init, it is probed.
> 
> > Also, the regulator nodes don't have a compatibly property, so direct
> > probing won't work.
> > 
> > I have no idea how the regulators are probed at all...
> 

looks like this will become one of the my famous self-talks. I just changed 
the module alias as Stephen suggested and this seems to load the driver 
magically. Patch below:


Subject: [PATCH] regulator: tps6586x: correct module alias

Set the module alias to the actual driver name tps6586x-pmic. This
fixes kernel module loading.

Signed-off-by: Marc Dietrich <marvin24-Mmb7MZpHnFY@public.gmane.org>
---
 drivers/regulator/tps6586x-regulator.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/regulator/tps6586x-regulator.c 
b/drivers/regulator/tps6586x-regulator.c
index d8fa37d..c2e57ea 100644
--- a/drivers/regulator/tps6586x-regulator.c
+++ b/drivers/regulator/tps6586x-regulator.c
@@ -461,4 +461,4 @@ module_exit(tps6586x_regulator_exit);
 MODULE_LICENSE("GPL");
 MODULE_AUTHOR("Mike Rapoport <mike-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>");
 MODULE_DESCRIPTION("Regulator Driver for TI TPS6586X PMIC");
-MODULE_ALIAS("platform:tps6586x-regulator");
+MODULE_ALIAS("platform:tps6586x-pmic");
-- 
1.7.9.5

Re: No HDMI output on AC100

[Stephen Warren]

On 06/09/2013 06:22 AM, Marc Dietrich wrote:
...
> Subject: [PATCH] regulator: tps6586x: correct module alias
> 
> Set the module alias to the actual driver name tps6586x-pmic. This
> fixes kernel module loading.

> diff --git a/drivers/regulator/tps6586x-regulator.c 

> -MODULE_ALIAS("platform:tps6586x-regulator");
> +MODULE_ALIAS("platform:tps6586x-pmic");

This patch highlights the issue correctly, but I think it'd be better to
change tps6586x_cell[] in drivers/mfd/tps6586x.c instead; that keeps the
module alias and module filename more consistent (and really, pmic is
the whole chip, whereas regulator is the sub-component, I think).

Re: No HDMI output on AC100

[Thierry Reding]

On Sun, Jun 9, 2013 at 10:52 AM, Thomas Meyer <thomas-VsYtu1Qij5c@public.gmane.org> wrote:
[...]
> oops! I think everthing did always work correctly! But somehow Fedora 19
> fails to spawn a getty on the tty1/fb0 console... so I just did see a
> black screen :-)

Just to confirm. This isn't a tegra-drm issue, but rather Fedora 19 not
spawning getty? Or is something in tegra-drm causing getty to fail? That
would be surprising, but I'm trying to figure out if I need to
investigate or not. =)

Thierry

Re: No HDMI output on AC100

[Thomas Meyer]

Am 12.06.2013 um 12:50 schrieb Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:

> On Sun, Jun 9, 2013 at 10:52 AM, Thomas Meyer <thomas-VsYtu1Qij5c@public.gmane.org> wrote:
> [...]
>> oops! I think everthing did always work correctly! But somehow Fedora 19
>> fails to spawn a getty on the tty1/fb0 console... so I just did see a
>> black screen :-)
> 
> Just to confirm. This isn't a tegra-drm issue, but rather Fedora 19 not
> spawning getty? Or is something in tegra-drm causing getty to fail? That
> would be surprising, but I'm trying to figure out if I need to
> investigate or not. =)
> 
Hi,

Please forget the getty thing as it was nonsense. The tegra hdmi driver seems to work, once it decides to output a signal. I was somehow able to trigger this the last time, but I don't know how to reproduce this.

So when I boot with the hdmi monitor connected all I get is a blank screen with no backlight ( I'm talking about the external hdmi monitor here, not the LCD panel!)

And some unknow thing (load of a module? Loading udl driver? Restarting getty?) seems to trigger that the tegra hdmi driver starts to output a valid hdmi signal and the external monitor shows the tegra hdmi framebuffer console.

The ac100 is otherwise up and running and I can ssh into it.

Any ideas?

> Thierry

Re: No HDMI output on AC100

[Thierry Reding]

[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]

On Fri, Jun 14, 2013 at 08:27:00PM +0200, Thomas Meyer wrote:
> Am 12.06.2013 um 12:50 schrieb Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
> 
> > On Sun, Jun 9, 2013 at 10:52 AM, Thomas Meyer <thomas-VsYtu1Qij5c@public.gmane.org> wrote:
> > [...]
> >> oops! I think everthing did always work correctly! But somehow Fedora 19
> >> fails to spawn a getty on the tty1/fb0 console... so I just did see a
> >> black screen :-)
> > 
> > Just to confirm. This isn't a tegra-drm issue, but rather Fedora 19 not
> > spawning getty? Or is something in tegra-drm causing getty to fail? That
> > would be surprising, but I'm trying to figure out if I need to
> > investigate or not. =)
> > 
> Hi,
> 
> Please forget the getty thing as it was nonsense. The tegra hdmi driver seems to work, once it decides to output a signal. I was somehow able to trigger this the last time, but I don't know how to reproduce this.
> 
> So when I boot with the hdmi monitor connected all I get is a blank screen with no backlight ( I'm talking about the external hdmi monitor here, not the LCD panel!)
> 
> And some unknow thing (load of a module? Loading udl driver? Restarting getty?) seems to trigger that the tegra hdmi driver starts to output a valid hdmi signal and the external monitor shows the tegra hdmi framebuffer console.
> 
> The ac100 is otherwise up and running and I can ssh into it.
> 
> Any ideas?

Do you have the fbcon driver loaded? I think I've seen a similar issue
when that's not loaded, in which case DRM will turn off all outputs
because there's nothing to display. Alternatively you could try to run
an X server using the xf86-video-opentegra or xf86-video-modesetting
drivers. That should definitely get you output on HDMI.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: No HDMI output on AC100

[Thomas Meyer]

Am 14.06.2013 um 22:37 schrieb Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:

> On Fri, Jun 14, 2013 at 08:27:00PM +0200, Thomas Meyer wrote:
>> Am 12.06.2013 um 12:50 schrieb Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
>> 
>>> On Sun, Jun 9, 2013 at 10:52 AM, Thomas Meyer <thomas-VsYtu1Qij5c@public.gmane.org> wrote:
>>> [...]
>>>> oops! I think everthing did always work correctly! But somehow Fedora 19
>>>> fails to spawn a getty on the tty1/fb0 console... so I just did see a
>>>> black screen :-)
>>> 
>>> Just to confirm. This isn't a tegra-drm issue, but rather Fedora 19 not
>>> spawning getty? Or is something in tegra-drm causing getty to fail? That
>>> would be surprising, but I'm trying to figure out if I need to
>>> investigate or not. =)
>> Hi,
>> 
>> Please forget the getty thing as it was nonsense. The tegra hdmi driver seems to work, once it decides to output a signal. I was somehow able to trigger this the last time, but I don't know how to reproduce this.
>> 
>> So when I boot with the hdmi monitor connected all I get is a blank screen with no backlight ( I'm talking about the external hdmi monitor here, not the LCD panel!)
>> 
>> And some unknow thing (load of a module? Loading udl driver? Restarting getty?) seems to trigger that the tegra hdmi driver starts to output a valid hdmi signal and the external monitor shows the tegra hdmi framebuffer console.
>> 
>> The ac100 is otherwise up and running and I can ssh into it.
>> 
>> Any ideas?
> 
> Do you have the fbcon driver loaded?

Yes.

> I think I've seen a similar issue
> when that's not loaded, in which case DRM will turn off all outputs
> because there's nothing to display. Alternatively you could try to run
> an X server using the xf86-video-opentegra or xf86-video-modesetting
> drivers. That should definitely get you output on HDMI.

I did login blindly on tty2 and started xfce using the open tegra driver, but still no hdmi output. I can send you the Xorg log file if you want to.

Xfce seems to run correctly, as far as I can see all necessary processes are running. The monitor I connect to the hdmi is an dvi monitor using an dvi to hdmi adapter, so no sound is connected. But that shouldn't be a problem.

> 
> Thierry

Re: No HDMI output on AC100

[Thierry Reding]

[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]

On Fri, Jun 14, 2013 at 10:59:00PM +0200, Thomas Meyer wrote:
> Am 14.06.2013 um 22:37 schrieb Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
[...]
> > I think I've seen a similar issue
> > when that's not loaded, in which case DRM will turn off all outputs
> > because there's nothing to display. Alternatively you could try to run
> > an X server using the xf86-video-opentegra or xf86-video-modesetting
> > drivers. That should definitely get you output on HDMI.
> 
> I did login blindly on tty2 and started xfce using the open tegra driver,
> but still no hdmi output. I can send you the Xorg log file if you want
> to.

Yes, Xorg output would be good. Additionally, dmesg output might help.
Don't forget to pass drm.debug=0xf on the kernel command-line.

> Xfce seems to run correctly, as far as I can see all necessary processes
> are running. The monitor I connect to the hdmi is an dvi monitor using
> an dvi to hdmi adapter, so no sound is connected. But that shouldn't be
> a problem.

Audio over HDMI isn't working yet anyway.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: No HDMI output on AC100

[Thomas Meyer]

Am Freitag, den 14.06.2013, 23:26 +0200 schrieb Thierry Reding:
> On Fri, Jun 14, 2013 at 10:59:00PM +0200, Thomas Meyer wrote:
> > Am 14.06.2013 um 22:37 schrieb Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
> [...]
> > > I think I've seen a similar issue
> > > when that's not loaded, in which case DRM will turn off all outputs
> > > because there's nothing to display. Alternatively you could try to run
> > > an X server using the xf86-video-opentegra or xf86-video-modesetting
> > > drivers. That should definitely get you output on HDMI.
> > 
> > I did login blindly on tty2 and started xfce using the open tegra driver,
> > but still no hdmi output. I can send you the Xorg log file if you want
> > to.
> 
> Yes, Xorg output would be good. Additionally, dmesg output might help.
> Don't forget to pass drm.debug=0xf on the kernel command-line.
> 
> > Xfce seems to run correctly, as far as I can see all necessary processes
> > are running. The monitor I connect to the hdmi is an dvi monitor using
> > an dvi to hdmi adapter, so no sound is connected. But that shouldn't be
> > a problem.

btw. switching the mode with
$ xrandr  -d :0 --output HDMI-0 --mode 1680x1050

makes the external monitor output the display correctly...

also switching to the highest possible resolution works after the first
mode switch:
$ xrandr  -d :0 --output HDMI-0 --mode 1920x1080

> 
> Audio over HDMI isn't working yet anyway.
> 
> Thierry

Re: No HDMI output on AC100

[Thierry Reding]

[-- Attachment #1: Type: text/plain, Size: 1820 bytes --]

On Sat, Jun 15, 2013 at 11:37:46AM +0200, Thomas Meyer wrote:
> Am Freitag, den 14.06.2013, 23:26 +0200 schrieb Thierry Reding:
> > On Fri, Jun 14, 2013 at 10:59:00PM +0200, Thomas Meyer wrote:
> > > Am 14.06.2013 um 22:37 schrieb Thierry Reding <thierry.reding@gmail.com>:
> > [...]
> > > > I think I've seen a similar issue
> > > > when that's not loaded, in which case DRM will turn off all outputs
> > > > because there's nothing to display. Alternatively you could try to run
> > > > an X server using the xf86-video-opentegra or xf86-video-modesetting
> > > > drivers. That should definitely get you output on HDMI.
> > > 
> > > I did login blindly on tty2 and started xfce using the open tegra driver,
> > > but still no hdmi output. I can send you the Xorg log file if you want
> > > to.
> > 
> > Yes, Xorg output would be good. Additionally, dmesg output might help.
> > Don't forget to pass drm.debug=0xf on the kernel command-line.
> > 
> > > Xfce seems to run correctly, as far as I can see all necessary processes
> > > are running. The monitor I connect to the hdmi is an dvi monitor using
> > > an dvi to hdmi adapter, so no sound is connected. But that shouldn't be
> > > a problem.
> 
> btw. switching the mode with
> $ xrandr  -d :0 --output HDMI-0 --mode 1680x1050
> 
> makes the external monitor output the display correctly...
> 
> also switching to the highest possible resolution works after the first
> mode switch:
> $ xrandr  -d :0 --output HDMI-0 --mode 1920x1080

So perhaps the default configuration chosen at startup isn't one that
tegra-drm can properly deal with. Can you provide the output of

	$ xrandr --query

run immediately after booting (that is with the default configuration
before you make it work by setting a 1680x1050 mode).

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: No HDMI output on AC100

[Thomas Meyer]

Am Samstag, den 15.06.2013, 11:43 +0200 schrieb Thierry Reding:
> On Sat, Jun 15, 2013 at 11:37:46AM +0200, Thomas Meyer wrote:
> > Am Freitag, den 14.06.2013, 23:26 +0200 schrieb Thierry Reding:
> > > On Fri, Jun 14, 2013 at 10:59:00PM +0200, Thomas Meyer wrote:
> > > > Am 14.06.2013 um 22:37 schrieb Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
> > > [...]
> > > > > I think I've seen a similar issue
> > > > > when that's not loaded, in which case DRM will turn off all outputs
> > > > > because there's nothing to display. Alternatively you could try to run
> > > > > an X server using the xf86-video-opentegra or xf86-video-modesetting
> > > > > drivers. That should definitely get you output on HDMI.
> > > > 
> > > > I did login blindly on tty2 and started xfce using the open tegra driver,
> > > > but still no hdmi output. I can send you the Xorg log file if you want
> > > > to.
> > > 
> > > Yes, Xorg output would be good. Additionally, dmesg output might help.
> > > Don't forget to pass drm.debug=0xf on the kernel command-line.
> > > 
> > > > Xfce seems to run correctly, as far as I can see all necessary processes
> > > > are running. The monitor I connect to the hdmi is an dvi monitor using
> > > > an dvi to hdmi adapter, so no sound is connected. But that shouldn't be
> > > > a problem.
> > 
> > btw. switching the mode with
> > $ xrandr  -d :0 --output HDMI-0 --mode 1680x1050
> > 
> > makes the external monitor output the display correctly...
> > 
> > also switching to the highest possible resolution works after the first
> > mode switch:
> > $ xrandr  -d :0 --output HDMI-0 --mode 1920x1080
> 
> So perhaps the default configuration chosen at startup isn't one that
> tegra-drm can properly deal with. Can you provide the output of
> 
> 	$ xrandr --query
> 
> run immediately after booting (that is with the default configuration
> before you make it work by setting a 1680x1050 mode).

sorry, I wasn't able to get the infos. xrandr refused to connect to the
X server spawned by lightdm but I don't know why. Maybe some missing
Xauthority or something like that.

But I got these infos, after a fresh boot:

$ fbset -i

mode "1920x1080"
    geometry 1920 1080 1920 1080 32
    timings 0 0 0 0 0 0 0
    accel true
    rgba 8/16,8/8,8/0,0/0
endmode

Frame buffer device information:
    Name        : 
    Address     : 0x1a100000
    Size        : 8294400
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 1
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 7680
    Accelerator : No

$ fbset -i -fb /dev/fb1

mode "1024x768"
    geometry 1024 768 1024 768 16
    timings 0 0 0 0 0 0 0
    accel true
    rgba 5/11,6/5,5/0,0/0
endmode

Frame buffer device information:
    Name        : udldrmfb
    Address     : 0xe0dbc000
    Size        : 1572864
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 1
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 2048
    Accelerator : No

When I add the boot option "video=HDMI-A-1:1680x1050" I get a working fb
console even while booting up. Later on I can start X manually and then
X switches to 1920x1080 and everything works okay.

> 
> Thierry

Re: No HDMI output on AC100

[Thierry Reding]

[-- Attachment #1: Type: text/plain, Size: 4569 bytes --]

On Sat, Jun 15, 2013 at 05:02:57PM +0200, Thomas Meyer wrote:
> Am Samstag, den 15.06.2013, 11:43 +0200 schrieb Thierry Reding:
> > On Sat, Jun 15, 2013 at 11:37:46AM +0200, Thomas Meyer wrote:
> > > Am Freitag, den 14.06.2013, 23:26 +0200 schrieb Thierry Reding:
> > > > On Fri, Jun 14, 2013 at 10:59:00PM +0200, Thomas Meyer wrote:
> > > > > Am 14.06.2013 um 22:37 schrieb Thierry Reding <thierry.reding@gmail.com>:
> > > > [...]
> > > > > > I think I've seen a similar issue
> > > > > > when that's not loaded, in which case DRM will turn off all outputs
> > > > > > because there's nothing to display. Alternatively you could try to run
> > > > > > an X server using the xf86-video-opentegra or xf86-video-modesetting
> > > > > > drivers. That should definitely get you output on HDMI.
> > > > > 
> > > > > I did login blindly on tty2 and started xfce using the open tegra driver,
> > > > > but still no hdmi output. I can send you the Xorg log file if you want
> > > > > to.
> > > > 
> > > > Yes, Xorg output would be good. Additionally, dmesg output might help.
> > > > Don't forget to pass drm.debug=0xf on the kernel command-line.
> > > > 
> > > > > Xfce seems to run correctly, as far as I can see all necessary processes
> > > > > are running. The monitor I connect to the hdmi is an dvi monitor using
> > > > > an dvi to hdmi adapter, so no sound is connected. But that shouldn't be
> > > > > a problem.
> > > 
> > > btw. switching the mode with
> > > $ xrandr  -d :0 --output HDMI-0 --mode 1680x1050
> > > 
> > > makes the external monitor output the display correctly...
> > > 
> > > also switching to the highest possible resolution works after the first
> > > mode switch:
> > > $ xrandr  -d :0 --output HDMI-0 --mode 1920x1080
> > 
> > So perhaps the default configuration chosen at startup isn't one that
> > tegra-drm can properly deal with. Can you provide the output of
> > 
> > 	$ xrandr --query
> > 
> > run immediately after booting (that is with the default configuration
> > before you make it work by setting a 1680x1050 mode).
> 
> sorry, I wasn't able to get the infos. xrandr refused to connect to the
> X server spawned by lightdm but I don't know why. Maybe some missing
> Xauthority or something like that.
> 
> But I got these infos, after a fresh boot:
> 
> $ fbset -i
> 
> mode "1920x1080"
>     geometry 1920 1080 1920 1080 32
>     timings 0 0 0 0 0 0 0
>     accel true
>     rgba 8/16,8/8,8/0,0/0
> endmode
> 
> Frame buffer device information:
>     Name        : 
>     Address     : 0x1a100000
>     Size        : 8294400
>     Type        : PACKED PIXELS
>     Visual      : TRUECOLOR
>     XPanStep    : 1
>     YPanStep    : 1
>     YWrapStep   : 0
>     LineLength  : 7680
>     Accelerator : No
> 
> $ fbset -i -fb /dev/fb1
> 
> mode "1024x768"
>     geometry 1024 768 1024 768 16
>     timings 0 0 0 0 0 0 0
>     accel true
>     rgba 5/11,6/5,5/0,0/0
> endmode
> 
> Frame buffer device information:
>     Name        : udldrmfb
>     Address     : 0xe0dbc000
>     Size        : 1572864
>     Type        : PACKED PIXELS
>     Visual      : TRUECOLOR
>     XPanStep    : 1
>     YPanStep    : 1
>     YWrapStep   : 0
>     LineLength  : 2048
>     Accelerator : No
> 
> When I add the boot option "video=HDMI-A-1:1680x1050" I get a working fb
> console even while booting up. Later on I can start X manually and then
> X switches to 1920x1080 and everything works okay.

Hi Thomas,

This fell off the table. I discussed a similar issue with Marc on IRC
today. The issue, IIUC, seems to be that with HDMI connected, the system
comes up and when X starts it tries to find the best match amongst the
various combinations of video modes on all existing heads in an attempt
to clone the desktop to all outputs. It turns out that this causes the
HDMI output to be configured with a resolution we don't support on Tegra
because the clock can't provide the right frequency.

There may be reasons (which I'm not aware of) for X to behave the way it
does. It also points to an issue that we should be more clever within
the kernel to flag as bad all the modes for which we can't provide a
proper clock. I will have to look into that.

In the meantime I think Marc had some success setting up a more useful
output configuration using xrandr. Perhaps he can provide more
information on exactly what he had to do to make this work and you
(Thomas) can try to reproduce whether that gets you a usable system.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: No HDMI output on AC100

[Marc Dietrich]

On Wednesday 17 July 2013 06:39:41 Thierry Reding wrote:
> On Sat, Jun 15, 2013 at 05:02:57PM +0200, Thomas Meyer wrote:
> > Am Samstag, den 15.06.2013, 11:43 +0200 schrieb Thierry Reding:
> > > On Sat, Jun 15, 2013 at 11:37:46AM +0200, Thomas Meyer wrote:
> > > > Am Freitag, den 14.06.2013, 23:26 +0200 schrieb Thierry Reding:
> > > > > On Fri, Jun 14, 2013 at 10:59:00PM +0200, Thomas Meyer wrote:
> > > > > > Am 14.06.2013 um 22:37 schrieb Thierry Reding 
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
> > > > > [...]
> > > > > 
> > > > > > > I think I've seen a similar issue
> > > > > > > when that's not loaded, in which case DRM will turn off all
> > > > > > > outputs
> > > > > > > because there's nothing to display. Alternatively you could try
> > > > > > > to run
> > > > > > > an X server using the xf86-video-opentegra or
> > > > > > > xf86-video-modesetting
> > > > > > > drivers. That should definitely get you output on HDMI.
> > > > > > 
> > > > > > I did login blindly on tty2 and started xfce using the open tegra
> > > > > > driver,
> > > > > > but still no hdmi output. I can send you the Xorg log file if you
> > > > > > want
> > > > > > to.
> > > > > 
> > > > > Yes, Xorg output would be good. Additionally, dmesg output might
> > > > > help.
> > > > > Don't forget to pass drm.debug=0xf on the kernel command-line.
> > > > > 
> > > > > > Xfce seems to run correctly, as far as I can see all necessary
> > > > > > processes
> > > > > > are running. The monitor I connect to the hdmi is an dvi monitor
> > > > > > using
> > > > > > an dvi to hdmi adapter, so no sound is connected. But that
> > > > > > shouldn't be
> > > > > > a problem.
> > > > 
> > > > btw. switching the mode with
> > > > $ xrandr  -d :0 --output HDMI-0 --mode 1680x1050
> > > > 
> > > > makes the external monitor output the display correctly...
> > > > 
> > > > also switching to the highest possible resolution works after the
> > > > first
> > > > mode switch:
> > > > $ xrandr  -d :0 --output HDMI-0 --mode 1920x1080
> > > 
> > > So perhaps the default configuration chosen at startup isn't one that
> > > tegra-drm can properly deal with. Can you provide the output of
> > > 
> > > 	$ xrandr --query
> > > 
> > > run immediately after booting (that is with the default configuration
> > > before you make it work by setting a 1680x1050 mode).
> > 
> > sorry, I wasn't able to get the infos. xrandr refused to connect to the
> > X server spawned by lightdm but I don't know why. Maybe some missing
> > Xauthority or something like that.
> > 
> > But I got these infos, after a fresh boot:
> > 
> > $ fbset -i
> > 
> > mode "1920x1080"
> > 
> >     geometry 1920 1080 1920 1080 32
> >     timings 0 0 0 0 0 0 0
> >     accel true
> >     rgba 8/16,8/8,8/0,0/0
> > 
> > endmode
> > 
> > Frame buffer device information:
> >     Name        :
> >     Address     : 0x1a100000
> >     Size        : 8294400
> >     Type        : PACKED PIXELS
> >     Visual      : TRUECOLOR
> >     XPanStep    : 1
> >     YPanStep    : 1
> >     YWrapStep   : 0
> >     LineLength  : 7680
> >     Accelerator : No
> > 
> > $ fbset -i -fb /dev/fb1
> > 
> > mode "1024x768"
> > 
> >     geometry 1024 768 1024 768 16
> >     timings 0 0 0 0 0 0 0
> >     accel true
> >     rgba 5/11,6/5,5/0,0/0
> > 
> > endmode
> > 
> > Frame buffer device information:
> >     Name        : udldrmfb
> >     Address     : 0xe0dbc000
> >     Size        : 1572864
> >     Type        : PACKED PIXELS
> >     Visual      : TRUECOLOR
> >     XPanStep    : 1
> >     YPanStep    : 1
> >     YWrapStep   : 0
> >     LineLength  : 2048
> >     Accelerator : No
> > 
> > When I add the boot option "video=HDMI-A-1:1680x1050" I get a working fb
> > console even while booting up. Later on I can start X manually and then
> > X switches to 1920x1080 and everything works okay.
> 
> Hi Thomas,
> 
> This fell off the table. I discussed a similar issue with Marc on IRC
> today. The issue, IIUC, seems to be that with HDMI connected, the system
> comes up and when X starts it tries to find the best match amongst the
> various combinations of video modes on all existing heads in an attempt
> to clone the desktop to all outputs. It turns out that this causes the
> HDMI output to be configured with a resolution we don't support on Tegra
> because the clock can't provide the right frequency.
> 
> There may be reasons (which I'm not aware of) for X to behave the way it
> does. It also points to an issue that we should be more clever within
> the kernel to flag as bad all the modes for which we can't provide a
> proper clock. I will have to look into that.
> 
> In the meantime I think Marc had some success setting up a more useful
> output configuration using xrandr. Perhaps he can provide more
> information on exactly what he had to do to make this work and you
> (Thomas) can try to reproduce whether that gets you a usable system.
> 

I got dualhead working by using the following xorg.conf entries:

Section "Device"                                                                
    Identifier "gpu"                                                            
    Driver "opentegra"                                                          
EndSection                                                                      
                                                                                
Section "Monitor"                                                               
    Identifier "LVDS-0"                                                         
EndSection                                                                      
                                                                                
Section "Monitor"                                                               
    Identifier "HDMI-0"                                                         
    Option "LeftOf" "LVDS-0"                                                    
EndSection                                                                      
                                                                                
Section "Screen"                                                                
    Identifier "Screen0"                                                        
    Device "gpu"                                                                
    Monitor "HDMI-0"                                                            
    SubSection "Display"                                                        
        Modes "1920x1200"                                                       
    EndSubSection                                                               
EndSection 

HDMI is the primary screen in this case.

I hope this helps.

Marc