From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] tda998x: allow use with bridge based devices
Date: Wed, 1 Aug 2018 10:35:28 +0100 [thread overview]
Message-ID: <20180801093528.GC30658@n2100.armlinux.org.uk> (raw)
In-Reply-To: <59eeb1c4-163c-4fda-d51e-27f2f404fe3e@axentia.se>
On Wed, Aug 01, 2018 at 11:01:12AM +0200, Peter Rosin wrote:
> I don't think it's a problem with the atmel I2C driver. IIRC, the
> tda998x driver issues the command a initiate the EDID read, but that
> times out. So it appears to be the TDA19988 that fails to read the
> EDID over the DDC bus? Which brings me to the double problem with the
> scopes mentioned above...
It sounds like it.
It may be helpful to know that there are HDMI pass-through boards
available that give access to all the HDMI signals:
https://elabbay.myshopify.com/collections/camera
https://elabbay.myshopify.com/collections/camera/products/hdmi-af-af-v1a-hdmi-type-a-female-to-hdmi-type-a-male-pass-through-adapter-breakout-board
I've never bought from them, so please don't take this as a
recommendation - the fact that there seems to be no company details
on their site doesn't seem good, and as the whois for elabbay.com is
obscured also doesn't give me any confidence to buy from them.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 13.8Mbps down 630kbps up
According to speedtest.net: 13Mbps down 490kbps up
next prev parent reply other threads:[~2018-08-01 9:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 16:41 [PATCH v2 0/7] tda998x: allow use with bridge based devices Russell King - ARM Linux
2018-07-30 16:42 ` [PATCH v2 1/7] drm/i2c: tda998x: find the drm_device via the drm_connector Russell King
2018-07-30 16:42 ` [PATCH v2 2/7] drm/i2c: tda998x: split tda998x_encoder_dpms into enable/disable Russell King
2018-07-31 5:46 ` Peter Rosin
2018-07-30 16:42 ` [PATCH v2 3/7] drm/i2c: tda998x: move tda998x_set_config() into tda998x_create() Russell King
2018-07-30 16:42 ` [PATCH v2 4/7] drm/i2c: tda998x: convert to bridge driver Russell King
2018-07-31 7:37 ` Peter Rosin
2018-08-08 19:09 ` Sean Paul
2018-08-08 22:15 ` Russell King - ARM Linux
2018-08-10 16:11 ` Sean Paul
2018-08-10 16:50 ` Russell King - ARM Linux
2018-08-10 17:02 ` Sean Paul
2018-08-10 17:16 ` Russell King - ARM Linux
2018-08-14 10:42 ` Daniel Vetter
2018-08-14 10:48 ` Russell King - ARM Linux
2018-08-14 11:11 ` Daniel Vetter
2018-08-27 16:15 ` Andrzej Hajda
2018-08-27 17:59 ` Russell King - ARM Linux
2018-08-28 7:31 ` Andrzej Hajda
2018-07-30 16:42 ` [PATCH v2 5/7] drm/i2c: tda998x: allocate tda998x_priv inside tda998x_create() Russell King
2018-07-30 16:42 ` [PATCH v2 6/7] drm/i2c: tda998x: cleanup from previous changes Russell King
2018-07-30 16:42 ` [PATCH v2 7/7] drm/i2c: tda998x: register bridge outside of component helper Russell King
2018-08-27 16:19 ` Andrzej Hajda
2018-07-31 5:44 ` [PATCH v2 0/7] tda998x: allow use with bridge based devices Peter Rosin
2018-07-31 7:41 ` Russell King - ARM Linux
2018-07-31 7:53 ` Peter Rosin
2018-07-31 9:23 ` Russell King - ARM Linux
2018-07-31 9:26 ` [PATCH 1/4] drm/i2c: tda998x: move mode_valid() to bridge Russell King
2018-08-27 16:24 ` Andrzej Hajda
2018-07-31 9:26 ` [PATCH 2/4] drm/i2c: tda998x: get rid of private fill_modes function Russell King
2018-07-31 9:26 ` [PATCH 3/4] drm/i2c: tda998x: correct PLL divider calculation Russell King
2018-07-31 9:26 ` [PATCH 4/4] drm/i2c: tda998x: add support for pixel repeated modes Russell King
2018-07-31 9:42 ` Russell King - ARM Linux
2018-07-31 10:43 ` [PATCH v2 0/7] tda998x: allow use with bridge based devices Peter Rosin
2018-07-31 11:15 ` Russell King - ARM Linux
2018-08-01 9:01 ` Peter Rosin
2018-08-01 9:35 ` Russell King - ARM Linux [this message]
2018-08-02 6:06 ` Peter Rosin
2018-11-12 16:50 ` Peter Rosin
2018-11-12 17:00 ` Russell King - ARM Linux
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=20180801093528.GC30658@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).