From: Thierry Reding <thierry.reding@gmail.com>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: Hans Verkuil <hans.verkuil@cisco.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-media@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/2] media: tegra-cec: Support Tegra186 and Tegra194
Date: Tue, 11 Dec 2018 11:00:32 +0100 [thread overview]
Message-ID: <20181211100032.GC14426@ulmo> (raw)
In-Reply-To: <26035940-2364-1fa0-68ab-8b9327705eb4@xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 3591 bytes --]
On Tue, Dec 11, 2018 at 10:40:55AM +0100, Hans Verkuil wrote:
> (Resend, this time with a proper reply)
>
> On 12/11/18 10:38 AM, Thierry Reding wrote:
> > On Tue, Dec 11, 2018 at 10:19:48AM +0100, Hans Verkuil wrote:
> >> On 12/10/18 9:59 PM, Thierry Reding wrote:
> >>> On Mon, Dec 10, 2018 at 06:07:10PM +0100, Hans Verkuil wrote:
> >>>> Hi Thierry,
> >>>>
> >>>> On 12/10/18 5:00 PM, Thierry Reding wrote:
> >>>>> From: Thierry Reding <treding@nvidia.com>
> >>>>>
> >>>>> The CEC controller found on Tegra186 and Tegra194 is the same as on
> >>>>> earlier generations.
> >>>>
> >>>> Well... at least for the Tegra186 there is a problem that needs to be addressed first.
> >>>> No idea if this was solved for the Tegra194, it might be present there as well.
> >>>>
> >>>> The Tegra186 hardware connected the CEC lines of both HDMI outputs together. This is
> >>>> a HW bug, and it means that only one of the two HDMI outputs can use the CEC block.
> >>>
> >>> I don't know where you got that information from, but I can't find any
> >>> indication of that in the documentation. My understanding is that there
> >>> is a single CEC block that is completely independent and it is merely a
> >>> decision of the board designer where to connect it. I'm not aware of any
> >>> boards that expose more than a single CEC.
> >>
> >> Sorry, my memory was not completely correct.
> >>
> >> The problem is that the 186 can be configured with two HDMI outputs, but it has
> >> only one CEC block. So CEC can be used for only one of the two. I checked the TRM
> >> for the Tegra194 and that has up to four HDMI outputs, but still only one CEC
> >> block.
> >>
> >> And yes, it is the responsibility for the board designer to hook up the CEC pin
> >> to only one of the outputs, but the TRM never explicitly mentions this and given
> >> the general lack of knowledge about CEC it wouldn't surprise me at all if there
> >> will be wrong board designs.
> >>
> >> But be that as it may, the core problem remains: you cannot allow multiple
> >> HDMI outputs to be connected to the same CEC device.
> >>
> >> However, I now realize that your patches will actually work fine since each
> >> HDMI connector tries to get a cec notifier for its own HDMI device, but the
> >> tegra-cec driver will only register a notifier for the HDMI device pointed
> >> to by the hdmi-phandle property. So only one of the HDMI devices will actually
> >> get a working CEC.
> >>
> >> Although if board designers mess this up and connect multiple CEC lines to
> >> the same CEC pin, this would still break, but there is nothing that can be
> >> done about that. I still believe the TRM should have made this clear since
> >> it is not obvious. Even better would be to have the same number of CEC blocks
> >> as there are configurable HDMI outputs. Typically, if you support CEC on one
> >> HDMI output, you want to support it for all. And today that's not possible
> >> without adding external CEC devices (as we - Cisco - do).
> >
> > I wasn't aware that anyone was using a Tegra with support for multiple
> > HDMI outputs. Do you have a contact that you can forward this kind of
> > request to? It certainly sounds like something that would be useful to
> > add in future chips if there's a customer need.
>
> We have contacts, and we did report it, but nothing happened with it
> AFAIK. It was likely too late for changes to the Tegra194 design in any
> case.
Okay. I'll follow up internally, see if I can find out what the story
is.
Thanks,
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-11 10:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 16:00 [PATCH 1/2] media: tegra-cec: Support Tegra186 and Tegra194 Thierry Reding
2018-12-10 16:00 ` [PATCH 2/2] media: tegra-cec: Export OF device ID match table Thierry Reding
2018-12-10 17:07 ` [PATCH 1/2] media: tegra-cec: Support Tegra186 and Tegra194 Hans Verkuil
2018-12-10 20:59 ` Thierry Reding
2018-12-11 9:19 ` Hans Verkuil
2018-12-11 9:38 ` Thierry Reding
2018-12-11 9:39 ` Hans Verkuil
2018-12-11 9:40 ` Hans Verkuil
2018-12-11 10:00 ` Thierry Reding [this message]
2018-12-11 9:26 ` Hans Verkuil
2018-12-11 9:39 ` Thierry Reding
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=20181211100032.GC14426@ulmo \
--to=thierry.reding@gmail.com \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jonathanh@nvidia.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mchehab@kernel.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).