From: Jerome Brunet <jbrunet@baylibre.com>
To: Zhengqiao Xia <xiazhengqiao@huaqin.corp-partner.google.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
Mark Brown <broonie@kernel.org>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Hsin-Yi Wang <hsinyi@google.com>
Subject: Re: [PATCH] ASoC: hdmi-codec: register hpd callback on component probe
Date: Fri, 15 Dec 2023 08:57:39 +0100 [thread overview]
Message-ID: <1jil4zq2on.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <CADYyEwTNyY+fR9SgfDa-g6iiDwkU3MUdPVCYexs2_3wbcM8_vg@mail.gmail.com>
On Fri 15 Dec 2023 at 12:51, Zhengqiao Xia <xiazhengqiao@huaqin.corp-partner.google.com> wrote:
> Hi Jerome,
>
> After my testing, I found that this patch will cause the audio on the external display to not work properly after
> restart.
> You move the plugged_cb to run in hdmi_probe, at this time hcp- > jack = NULL, the driver cannot report `SND_JACK_LINEOUT
> ` normally.
> static void hdmi_codec_jack_report(struct hdmi_codec_priv *hcp,
> unsigned int jack_status)
> {
> printk("xzq-866 hdmi_codec_jack_report: jack=%x, jack_status=%d", hcp->jack, jack_status != hcp->jack_status);
> if (hcp->jack && jack_status != hcp->jack_status) {
> snd_soc_jack_report(hcp->jack, jack_status, SND_JACK_LINEOUT);
> hcp->jack_status = jack_status;
> }
> }
> So we must call plugged_cb in hdmi_codec_set_jack, Can you make some changes?
Hi Zhengqiao,
That is unfortunate. Sorry.
This patch has changed when the hpd callback is registered, no when it
comes in effect. This is still dependent on calling .set_jack() and it
is not happening any later than it was before. So, in theory, it should
not have changed anything, if your driver actually relies on the HPD
event.
Trying to guess what is happening for you, I suppose your HDMI driver is
"faking" an HPD event to report the initial jack status when the
hook_plugged_cb() is called. Could you point me to the hdmi driver you
are using so I can have a look ?
My reference when testing this was dw-hdmi-i2s-audio and it does not do
that, it just registers the callback. I think this is what it supposed
to do TBH.
An idea I have been thinking about for a while is have the hdmi-codec
insert the jack in the card itself, instead of the card doing. That
would give the jack "for free" to any user of the HDMI codec and might
also solve your issue. It would require a small rework of the cards doing
the hdmi jack register, but there are not many of these AFAIK.
>
> On Mon, Nov 6, 2023 at 6:40 PM Jerome Brunet <jbrunet@baylibre.com> wrote:
>
> The HDMI hotplug callback to the hdmi-codec is currently registered when
> jack is set.
>
> The hotplug not only serves to report the ASoC jack state but also to get
> the ELD. It should be registered when the component probes instead, so it
> does not depend on the card driver registering a jack for the HDMI to
> properly report the ELD.
>
> Fixes: 25ce4f2b3593 ("ASoC: hdmi-codec: Get ELD in before reporting plugged event")
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
> ---
> sound/soc/codecs/hdmi-codec.c | 27 +++++++++++++++++++--------
> 1 file changed, 19 insertions(+), 8 deletions(-)
>
> diff --git a/sound/soc/codecs/hdmi-codec.c b/sound/soc/codecs/hdmi-codec.c
> index 09eef6042aad..20da1eaa4f1c 100644
> --- a/sound/soc/codecs/hdmi-codec.c
> +++ b/sound/soc/codecs/hdmi-codec.c
> @@ -877,18 +877,13 @@ static int hdmi_codec_set_jack(struct snd_soc_component *component,
> void *data)
> {
> struct hdmi_codec_priv *hcp = snd_soc_component_get_drvdata(component);
> - int ret = -ENOTSUPP;
>
> if (hcp->hcd.ops->hook_plugged_cb) {
> hcp->jack = jack;
> - ret = hcp->hcd.ops->hook_plugged_cb(component->dev->parent,
> - hcp->hcd.data,
> - plugged_cb,
> - component->dev);
> - if (ret)
> - hcp->jack = NULL;
> + return 0;
> }
> - return ret;
> +
> + return -ENOTSUPP;
> }
>
> static int hdmi_dai_spdif_probe(struct snd_soc_dai *dai)
> @@ -982,6 +977,21 @@ static int hdmi_of_xlate_dai_id(struct snd_soc_component *component,
> return ret;
> }
>
> +static int hdmi_probe(struct snd_soc_component *component)
> +{
> + struct hdmi_codec_priv *hcp = snd_soc_component_get_drvdata(component);
> + int ret = 0;
> +
> + if (hcp->hcd.ops->hook_plugged_cb) {
> + ret = hcp->hcd.ops->hook_plugged_cb(component->dev->parent,
> + hcp->hcd.data,
> + plugged_cb,
> + component->dev);
> + }
> +
> + return ret;
> +}
> +
> static void hdmi_remove(struct snd_soc_component *component)
> {
> struct hdmi_codec_priv *hcp = snd_soc_component_get_drvdata(component);
> @@ -992,6 +1002,7 @@ static void hdmi_remove(struct snd_soc_component *component)
> }
>
> static const struct snd_soc_component_driver hdmi_driver = {
> + .probe = hdmi_probe,
> .remove = hdmi_remove,
> .dapm_widgets = hdmi_widgets,
> .num_dapm_widgets = ARRAY_SIZE(hdmi_widgets),
--
Jerome
next prev parent reply other threads:[~2023-12-15 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 10:40 Jerome Brunet
2023-11-06 13:03 ` Mark Brown
[not found] ` <CADYyEwTNyY+fR9SgfDa-g6iiDwkU3MUdPVCYexs2_3wbcM8_vg@mail.gmail.com>
2023-12-15 7:57 ` Jerome Brunet [this message]
2023-12-15 22:55 ` Hsin-Yi Wang
2023-12-18 10:28 ` Jerome Brunet
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=1jil4zq2on.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=hsinyi@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiazhengqiao@huaqin.corp-partner.google.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
all inboxes | Powered by JetHome®