From: Jose Abreu <Jose.Abreu@synopsys.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>,
Jose Abreu <Jose.Abreu@synopsys.com>
Cc: <dri-devel@lists.freedesktop.org>,
Carlos Palminha <CARLOS.PALMINHA@synopsys.com>,
Archit Taneja <architt@codeaurora.org>,
David Airlie <airlied@linux.ie>,
Fabio Estevam <fabio.estevam@freescale.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Takashi Iwai <tiwai@suse.de>,
Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
Thierry Reding <treding@nvidia.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3 v3] drm: bridge/dw-hdmi: Enable ISCR1, ISCR2 and ACP packets
Date: Thu, 4 Aug 2016 17:18:12 +0100 [thread overview]
Message-ID: <57A36AC4.9000408@synopsys.com> (raw)
In-Reply-To: <20160804153206.GX1041@n2100.armlinux.org.uk>
Hi Russell,
On 04-08-2016 16:32, Russell King - ARM Linux wrote:
> On Thu, Aug 04, 2016 at 11:44:50AM +0100, Jose Abreu wrote:
>> Currently ISCR and ACP packets are not being sent causing
>> HDMI compliance tests like CTS 7-19 HDMI 1.4b to fail.
> Hmm. Reading the HDMI specifications (v1.3, being the publically
> available one), the specification does _not_ say that a source _must_
> transmit ISRC and ACP packets if Supports_AI is set.
>
> What it does say is that:
> * a sink shall set Supports_AI if it supports at least one function
> which uses ISRC or ACP packets, and it shall accept such packets.
> * a source shall not transmit ISRC or ACP packets to a sink that
> has Supports_AI=0.
>
> I don't see anything that mandates the transmission of ISRC and ACP
> packets when Supports_AI is set.
>
> Moreover, transmission of wrong ISRC information probably goes against
> the HDMI spec section 8.8, which requires specific ISRC status values
> in HB1 - I don't see how that _could_ be handled, as the kernel has no
> knowledge about the EAN of the audio content being played, nor when a
> track starts or finishes.
>
> Please clarify.
You are correct. I ran the test again and indeed it is not
failing but it is skipped. Sorry for the confusion. Anyway, with
this patch the test that verifies the ISRC packets succeeds so I
think it would be a nice addition.
>
>> + /* Set ISCR1, ISCR2, and ACP packets to automatic scheduling */
>> + if (hdmi->sink_supports_ai) {
>> + dev_dbg(hdmi->dev, "sink supports AI packets\n");
>> + hdmi_writeb(hdmi, 0x06, HDMI_FC_ISCR1_0);
>> + hdmi_writeb(hdmi, 0x03, HDMI_FC_DATAUTO0);
>> + hdmi_writeb(hdmi, 0x01, HDMI_FC_DATAUTO1);
>> + hdmi_writeb(hdmi, 0x11, HDMI_FC_DATAUTO2);
> So what data gets sent in these packets - I guess whatever random data
> happens to be in the HDMI_FC_ACP* and HDMI_FC_ISCR1_* registers at the
> time the sending is enabled. I don't think that's particularly a good
> idea.
It is not random as the registers defaults to zero per databook.
It is sending an empty packet.
>> @@ -1474,8 +1490,13 @@ static int dw_hdmi_connector_get_modes(struct drm_connector *connector)
>> /* Store the ELD */
>> drm_edid_to_eld(connector, edid);
>> kfree(edid);
>> +
>> + hdmi->sink_supports_ai = connector->eld[5] & (0x1 << 1);
> We have a definition for this bit - DRM_ELD_SUPPORTS_AI.
>
Thanks. Will change in next version if you agree with this
addition. If not I will drop the patch.
Best regards,
Jose Miguel Abreu
next prev parent reply other threads:[~2016-08-04 16:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 10:44 [PATCH 0/3 v3] drm: bridge/dw-hdmi: Fixes for dw-hdmi and DWC support Jose Abreu
2016-08-04 10:44 ` [PATCH 1/3 v3] drm: bridge/dw-hdmi: Add support for DWC Phy Jose Abreu
2016-08-04 10:44 ` [PATCH 2/3 v3] drm: bridge/dw-hdmi: Enable ISCR1, ISCR2 and ACP packets Jose Abreu
2016-08-04 15:32 ` Russell King - ARM Linux
2016-08-04 16:18 ` Jose Abreu [this message]
2016-08-04 10:44 ` [PATCH 3/3 v3] drm: bridge/dw-hdmi: Move edid reading to .detect() callback Jose Abreu
2016-08-04 10:47 ` Russell King - ARM Linux
2016-08-04 13:58 ` Jose Abreu
2016-08-04 14:31 ` Russell King - ARM Linux
2016-08-04 14:57 ` Jose Abreu
2016-08-04 15:04 ` Russell King - ARM Linux
2016-08-04 17:13 ` Jose Abreu
2016-08-04 23:01 ` Russell King - ARM Linux
2016-08-05 8:06 ` Daniel Vetter
2016-08-05 8:13 ` Chris Wilson
2016-08-08 16:25 ` Jose Abreu
2016-08-09 6:09 ` Daniel Vetter
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=57A36AC4.9000408@synopsys.com \
--to=jose.abreu@synopsys.com \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=airlied@linux.ie \
--cc=architt@codeaurora.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabio.estevam@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=tiwai@suse.de \
--cc=treding@nvidia.com \
--cc=vladimir_zapolskiy@mentor.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).