All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media <linux-media@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] TDA1997x: enable EDID support
Date: Tue, 08 Jun 2021 06:54:57 +0200	[thread overview]
Message-ID: <m3k0n57y72.fsf@t19.piap.pl> (raw)
In-Reply-To: <CAJ+vNU0E_0pB-1T+VpdmjJNVirAwCUNjKVbEV4wEbqHOzURj_A@mail.gmail.com> (Tim Harvey's message of "Mon, 7 Jun 2021 08:48:19 -0700")

Tim,

Tim Harvey <tharvey@gateworks.com> writes:

>> 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 where the source above is from (this was all so long ago) but

That's your gateworks_fslc_3.14_1.0.x_ga branch (3.14 is the kernel and
1.0.x_ga is IIRC some Freescale versioning) :-)

> my guess is that 'internal_edid' meant an EDID had been provided via
> software and the else case meant there was no EDID available.
> There is no support on that chip for an external EEPROM.

Right. I guess the else meant it was available and &= ~83 meant no
EDID... Anyway one could simply drop a 24c02 or a similar chip directly
to SDA/SCL HDMI lines, that's what the monitor makers had been doing for
a long time. Then, I guess, you would need the internal_edid = 0
(otherwise the TDA chip would be fighting the EEPROM on the SDA line).
Not that I know of any such design using this driver, I guess we can
safely skip this part.
-- 
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-08  4:55 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
2021-06-07 15:48     ` Tim Harvey
2021-06-08  4:54       ` Krzysztof Hałasa [this message]
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=m3k0n57y72.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 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.