linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Thierry Reding <thierry.reding@gmail.com>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: 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: Mon, 10 Dec 2018 18:07:10 +0100	[thread overview]
Message-ID: <643e8da6-a8ed-145a-604d-f028e501add9@xs4all.nl> (raw)
In-Reply-To: <20181210160038.16122-1-thierry.reding@gmail.com>

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.

HDMI inputs CAN share the CEC line, but never outputs. There should have been two
CEC blocks, one for each HDMI output.

It should not be possible to use the same CEC block for both HDMI outputs on the 186.
Ideally it should be a required dts property that determines this. I'm not sure where
that should happen. One option might be to use the cec_notifier_get_conn() function
so you can register the CEC adapter for a specific connector only. For older tegra
versions the connector name would be NULL (i.e. don't care), for the 186 (and perhaps 194)
it would be a required property that tells the CEC driver which connector it is associated
with.

Just a suggestion, there might be other ways to implement this as well.

So before I can merge this I need to know first how you plan to handle this HW bug.

Regards,

	Hans

> 
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
>  drivers/media/platform/tegra-cec/tegra_cec.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/media/platform/tegra-cec/tegra_cec.c b/drivers/media/platform/tegra-cec/tegra_cec.c
> index aba488cd0e64..8a1e10d008d0 100644
> --- a/drivers/media/platform/tegra-cec/tegra_cec.c
> +++ b/drivers/media/platform/tegra-cec/tegra_cec.c
> @@ -472,6 +472,8 @@ static const struct of_device_id tegra_cec_of_match[] = {
>  	{ .compatible = "nvidia,tegra114-cec", },
>  	{ .compatible = "nvidia,tegra124-cec", },
>  	{ .compatible = "nvidia,tegra210-cec", },
> +	{ .compatible = "nvidia,tegra186-cec", },
> +	{ .compatible = "nvidia,tegra194-cec", },
>  	{},
>  };
>  
> 


  parent reply	other threads:[~2018-12-10 17:07 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 ` Hans Verkuil [this message]
2018-12-10 20:59   ` [PATCH 1/2] media: tegra-cec: Support Tegra186 and Tegra194 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
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=643e8da6-a8ed-145a-604d-f028e501add9@xs4all.nl \
    --to=hverkuil-cisco@xs4all.nl \
    --cc=hans.verkuil@cisco.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).