linux-kernel - Re: [PATCH] gma500: Add option to disable LVDS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BANLkTikz+PrQY2egkPTiacDSH5-Gkqkbww@mail.gmail.com>
Date:	Wed, 11 May 2011 01:18:07 +0200
From:	Patrik Jakobsson <patrik.r.jakobsson@...il.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	alan@...ux.intel.com, greg@...ah.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] gma500: Add option to disable LVDS

On Tue, May 10, 2011 at 11:46 PM, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> On Tue, 10 May 2011 23:20:38 +0200
> Patrik Jakobsson <patrik.r.jakobsson@...il.com> wrote:
>
>> This patch adds the option to load the driver without LVDS support. Some platforms with the gma500 have nothing hooked up to LVDS but only uses SDVO. LVDS is still detected and added as an encoder which causes SDVO mode-setting to fail.
>>
>> Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@...il.com>
>
> What platform is this - I'd really like to keep such things automatic and
> also if possible make the code handle the case not blow up. The user
> shouldn't have to deal with such funnies.
>
> Alan
>

This is for the FIT-PC2.

I agree, it's not a good way to handle it, but since I haven't been
able to pinpoint the problem (and this is staging) it's something that
works for now. Perhaps a nicer way to get around it is by checking
against the dmi system id. That way it would be transparent to the
user. But you might prefer we fix the real problem instead of hacking
around it.

When both LVDS and SDVO is enabled the driver tries to set up both
pipes and LVDS only finds a bogus mode of 0x0 pixels. Not sure why
LVDS takes over instead of SDVO since it has valid modes, but my
screen just goes into powersave when no proper PLL can be set for the
bogus mode.

I'll do some more debugging tomorrow.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/