From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Joao Pinto <Joao.Pinto@synopsys.com>
Cc: linux-kernel@vger.kernel.org, ijc+devicetree@hellion.org.uk,
liviu.dudau@arm.com, ryan.harkin@linaro.org
Subject: Re: [PATCH 3/3] tda998x: add HPD delay to avoid disabling sound when EDID checksum fails.
Date: Mon, 30 May 2016 20:10:44 +0100 [thread overview]
Message-ID: <20160530191044.GR19428@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <2f242f545c99fc604fb70eeffcfd5d7703ace18d.1464619185.git.jpinto@synopsys.com>
On Mon, May 30, 2016 at 04:15:54PM +0100, Joao Pinto wrote:
> When using ffplay to reproduce video+sound it was noticed that sometimes the
> sound was disabled. The cause was an initial EDID checksum error that disabled
> the HDMI sound. By adding this tweak, it was noticed that the sound is not
> even when initial EDID checksum error ocurres.
>
> Signed-off-by: Joao Pinto <jpinto@synopsys.com>
> ---
> drivers/gpu/drm/i2c/tda998x_drv.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/gpu/drm/i2c/tda998x_drv.c b/drivers/gpu/drm/i2c/tda998x_drv.c
> index 7020b50..fc7c1c3 100644
> --- a/drivers/gpu/drm/i2c/tda998x_drv.c
> +++ b/drivers/gpu/drm/i2c/tda998x_drv.c
> @@ -587,6 +587,17 @@ static void tda998x_detect_work(struct work_struct *work)
> drm_kms_helper_hotplug_event(dev);
> }
>
> +/* handle HDMI connect/disconnect */
> +static void tda998x_hpd(struct work_struct *work)
> +{
> + struct delayed_work *dwork = to_delayed_work(work);
> + struct tda998x_priv *priv =
> + container_of(dwork, struct tda998x_priv, dwork);
> +
> + if (&priv->encoder && priv->encoder.dev)
> + drm_kms_helper_hotplug_event(priv->encoder.dev);
> +}
> +
> /*
> * only 2 interrupts may occur: screen plug/unplug and EDID read
> */
> @@ -1313,6 +1324,7 @@ static int tda998x_create(struct i2c_client *client, struct tda998x_priv *priv)
>
> /* init read EDID waitqueue and HDP work */
> init_waitqueue_head(&priv->wq_edid);
> + INIT_DELAYED_WORK(&priv->dwork, tda998x_hpd);
>
> /* clear pending interrupts */
> reg_read(priv, REG_INT_FLAGS_0);
Clearly, this patch is incomplete. There's nothing that schedules this
work to be run.
In any case, this is reintroducing the code which I deleted when I fixed
the (rather crappy) previous implemention of delaying the EDID read after
a hotplug event. You should not need this patch.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-05-30 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 15:15 [PATCH 0/3] tda998x: add sound support Joao Pinto
2016-05-30 15:15 ` [PATCH 1/3] tda998x: adding " Joao Pinto
2016-05-30 15:15 ` [PATCH 2/3] tda998x: adding sound support for Juno in the DT Joao Pinto
2016-05-30 15:15 ` [PATCH 3/3] tda998x: add HPD delay to avoid disabling sound when EDID checksum fails Joao Pinto
2016-05-30 19:10 ` Russell King - ARM Linux [this message]
2016-05-31 16:58 ` Joao Pinto
2016-06-01 16:32 ` Russell King - ARM Linux
2016-06-01 16:38 ` Joao Pinto
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=20160530191044.GR19428@n2100.arm.linux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Joao.Pinto@synopsys.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=ryan.harkin@linaro.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).