All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Dietrich <marvin24-Mmb7MZpHnFY@public.gmane.org>
To: Thomas Meyer <thomas-VsYtu1Qij5c@public.gmane.org>
Cc: linux-tegra <linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Thierry Reding
	<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: No HDMI output on AC100
Date: Sat, 08 Jun 2013 17:12:48 +0200	[thread overview]
Message-ID: <4976225.B4ibccLaIu@ax5200p> (raw)
In-Reply-To: <68C7110D-C493-4A1F-8011-5F9259C2F4E7-VsYtu1Qij5c@public.gmane.org>

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

  parent reply	other threads:[~2013-06-08 15:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-08  8:33 No HDMI output on AC100 Thomas Meyer
     [not found] ` <1370680435.24531.12.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2013-06-08 13:00   ` Marc Dietrich
2013-06-08 14:21     ` Thomas Meyer
     [not found]       ` <68C7110D-C493-4A1F-8011-5F9259C2F4E7-VsYtu1Qij5c@public.gmane.org>
2013-06-08 15:12         ` Marc Dietrich [this message]
2013-06-08 16:05         ` Lucas Stach
     [not found]           ` <1370707552.1829.4.camel-6fNNZcyRN12a6lf8Wg2v7Z5kstrrjoWp@public.gmane.org>
2013-06-08 20:07             ` Marc Dietrich
2013-06-09  2:45               ` Stephen Warren
     [not found]                 ` <51B3EC3D.3080306-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-06-09 11:42                   ` Marc Dietrich
2013-06-09 12:02                     ` Marc Dietrich
2013-06-09 12:22                       ` Marc Dietrich
2013-06-10 16:13                         ` Stephen Warren
2013-06-09  8:31               ` Thomas Meyer
2013-06-09  8:52               ` Thomas Meyer
     [not found]                 ` <1370767921.2283.8.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2013-06-12 10:50                   ` Thierry Reding
2013-06-14 18:27                     ` Thomas Meyer
     [not found]                       ` <EF2DBD80-3DDD-416F-935C-E48261BF6CF5-VsYtu1Qij5c@public.gmane.org>
2013-06-14 20:37                         ` Thierry Reding
2013-06-14 20:59                           ` Thomas Meyer
     [not found]                             ` <C2E8F821-5848-4FC0-992C-385D48611324-VsYtu1Qij5c@public.gmane.org>
2013-06-14 21:26                               ` Thierry Reding
2013-06-15  9:37                                 ` Thomas Meyer
     [not found]                                   ` <1371289066.3792.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2013-06-15  9:43                                     ` Thierry Reding
2013-06-15 15:02                                       ` Thomas Meyer
     [not found]                                         ` <1371308577.2480.6.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2013-07-17  4:39                                           ` Thierry Reding
2013-07-17 19:24                                             ` Marc Dietrich
2013-06-09  8:33             ` Thomas Meyer
2013-06-09  8:38             ` Thomas Meyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4976225.B4ibccLaIu@ax5200p \
    --to=marvin24-mmb7mzphnfy@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=thomas-VsYtu1Qij5c@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.