public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Tim Harvey <tharvey@gateworks.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] TDA1997x: enable EDID support
Date: Mon, 07 Jun 2021 13:56:25 +0200	[thread overview]
Message-ID: <m3eeddhora.fsf@t19.piap.pl> (raw)
In-Reply-To: <dbb99d7b-18eb-317c-911a-b982486848fa@xs4all.nl> (Hans Verkuil's message of "Mon, 7 Jun 2021 13:11:54 +0200")

Hi Hans,

Hans Verkuil <hverkuil@xs4all.nl> writes:

>> Without this patch, the TDA19971 chip's EDID is inactive.
>
> Was this wrong from the very beginning? How can this ever have been tested
> without an EDID?

It seems so. I suspect it might have worked in tests because this
register isn't cleared on reboot. I.e., setting it once after power up
makes it work to the next power up.
Or, maybe, the HDMI signal source didn't need EDID.

I'm looking at the previous version of this driver from Gateworks and it
contains:

     /* Configure EDID
      *
      * EDID_ENABLE bits:
      *  7 - nack_off
      *  6 - edid_only
      *  1 - edid_b_en
      *  0 - edid_a_en
      */
     reg = io_read(REG_EDID_ENABLE);
     if (!tda1997x->internal_edid)
         reg &= ~0x83; /* EDID Nack ON */
     else
         reg |= 0x83;  /* EDID Nack OFF */
     io_write(REG_EDID_ENABLE, reg);

Not sure what the "non-internal" EDID could be - a separate I2C EEPROM
chip? I'm using this on Gateworks' GW54xx boards and I can't see any
such EEPROM in the vicinity of the TDA19971, but I don't know how it is
wired - perhaps Tim has some idea?
-- 
Krzysztof Hałasa

Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa

  reply	other threads:[~2021-06-07 11:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 10:56 [PATCH] TDA1997x: enable EDID support Krzysztof Hałasa
2021-06-07 11:11 ` Hans Verkuil
2021-06-07 11:56   ` Krzysztof Hałasa [this message]
2021-06-07 15:48     ` Tim Harvey
2021-06-08  4:54       ` Krzysztof Hałasa
2021-06-08  7:27         ` Hans Verkuil
2021-06-08  8:45           ` Krzysztof Hałasa
2021-06-08  8:47             ` Hans Verkuil

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=m3eeddhora.fsf@t19.piap.pl \
    --to=khalasa@piap.pl \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=tharvey@gateworks.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox