From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] imx: nitrogen6x: mx6qsabrelite: Add support for DVI monitors
Date: Tue, 23 Jul 2013 15:12:33 -0700 [thread overview]
Message-ID: <51EEFFD1.7040901@boundarydevices.com> (raw)
In-Reply-To: <CAOMZO5BkbwHXXOYQ5DCAaa-=nnwD=iR5S4o3qhdOL3q0k7+rsQ@mail.gmail.com>
Hi Fabio,
On 07/23/2013 02:46 PM, Fabio Estevam wrote:
> Hi Eric,
>
> On Tue, Jul 23, 2013 at 6:43 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>
>> A little background is probably appropriate for this patch.
>>
>> Since "the beginning" of usage of the SABRE Lite and Nitrogen6x
>> boards, DVI detection has been somewhat broken.
>>
>> Some (most) DVI monitors don't produce the "HPD" bit in
>> the PHY_STAT0 register, but do show proper toggling of the
>> RX_SENSE0..3 bits.
>>
>> Creating a new the bit-mask to include all five bits and
>> modifying the 'hdmidet' command and internal detection
>> routines allows these monitors to function properly in U-Boot.
>>
>> A related patch to our kernels allows things to work under
>> Linux:
>>
>> https://github.com/boundarydevices/linux-imx6/commit/7d8752905c118af9063738a533227de0b2f6ecd4
>
> Thanks for the excellent explanation and for finding the root cause!
>
> It would be really nice if Robert could send a v2 adding your text
> into the commit log.
>
Seems to be already done.
Also note that this patch will be smaller with a V3 of your patch
collapsing SABRE Lite into the nitrogen6x/ tree (nudge nudge)...
Regards,
Eric
prev parent reply other threads:[~2013-07-23 22:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 20:33 [U-Boot] [PATCH] imx: nitrogen6x: mx6qsabrelite: Add support for DVI monitors Robert Winkler
2013-07-23 21:43 ` Eric Nelson
2013-07-23 21:46 ` Fabio Estevam
2013-07-23 22:12 ` Eric Nelson [this message]
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=51EEFFD1.7040901@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=u-boot@lists.denx.de \
/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.