From: "Jiaxin Yu (俞家鑫)" <Jiaxin.Yu@mediatek.com>
To: "broonie@kernel.org" <broonie@kernel.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"neil.armstrong@linaro.org" <neil.armstrong@linaro.org>,
"nfraprado@collabora.com" <nfraprado@collabora.com>,
"Chunxu Li (李春旭)" <Chunxu.Li@mediatek.com>,
"Allen-KH Cheng (程冠勳)" <Allen-KH.Cheng@mediatek.com>,
"kuninori.morimoto.gx@renesas.com"
<kuninori.morimoto.gx@renesas.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"robert.foss@linaro.org" <robert.foss@linaro.org>,
"andrzej.hajda@intel.com" <andrzej.hajda@intel.com>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"ajye_huang@compal.corp-partner.google.com"
<ajye_huang@compal.corp-partner.google.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Laurent.pinchart@ideasonboard.com"
<Laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH v2 1/3] ASoC: hdmi-codec: Add event handler for hdmi TX
Date: Tue, 13 Dec 2022 14:23:32 +0000 [thread overview]
Message-ID: <dc50d0b21795acbcc44c77e5fd81e7cb92c65c67.camel@mediatek.com> (raw)
In-Reply-To: <Y43e+EsNCrCpZSIH@sirena.org.uk>
On Mon, 2022-12-05 at 12:07 +0000, Mark Brown wrote:
> On Mon, Dec 05, 2022 at 09:34:17AM +0000, Jiaxin Yu (俞家鑫) wrote:
>
> > 1. I have added a DAPM widget that is "SDB", when we open or close
> > HDMI
> > PIN_SWITCH, the callback 'hdmi_tx_event' registered in the widget
> > will
> > be triggered. Maybe you mean I shouldn't use
> > SNDRV_PCM_TRIGGER_START
> > and SNDRV_PCM_TRIGGER_STOP?
>
> No, I mean that if you want to control the enable and disable of the
> output path you should implement a DAPM widget.
>
May I ask which driver file to add a new DAPM widget? Is it the bridge
ic driver like it6505.c? Or is it linke the "SDB" added in this patch?
> > 2. If I don't use hcd.ops->trigger notifies the bridge ic driver to
> > switch the audio, which ops should I use?
> > I actually want to know hdmi-codec.c and it6505.c except
> > hdmi_codec_ops, is there any other way to communicate?
>
> Like I said you should use the event on the DAPM widget. This will
> require providing operations for the events to the drivers.
Yes, I should add a new set of events, such as:
enum {
HDMI_CODEC_TRIGGER_EVENT_STOP,
HDMI_CODEC_TRIGGER_EVENT_START,
HDMI_CODEC_TRIGGER_EVENT_SUSPEND,
HDMI_CODEC_TRIGGER_EVENT_RESUME,
}
Then provide handles for these events in the it6505 driver. Am I right?
Thanks,
Jiaxin.Yu
next prev parent reply other threads:[~2022-12-13 14:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 9:44 [PATCH v2 0/3] ASoC: mediatek:mt8186: fix both the speaker and hdmi Jiaxin Yu
2022-11-25 9:44 ` [PATCH v2 1/3] ASoC: hdmi-codec: Add event handler for hdmi TX Jiaxin Yu
2022-11-25 12:18 ` Mark Brown
2022-11-28 15:07 ` Jiaxin Yu (俞家鑫)
2022-11-29 17:22 ` Mark Brown
2022-12-01 15:06 ` Jiaxin Yu (俞家鑫)
2022-12-01 15:23 ` Mark Brown
2022-12-05 9:34 ` Jiaxin Yu (俞家鑫)
2022-12-05 12:07 ` Mark Brown
2022-12-13 14:23 ` Jiaxin Yu (俞家鑫) [this message]
2022-12-13 16:35 ` Mark Brown
2024-12-01 17:15 ` Jiaxin Yu (俞家鑫)
2024-12-02 13:16 ` Mark Brown
2024-12-06 15:39 ` Jiaxin Yu (俞家鑫)
2024-12-06 16:06 ` Mark Brown
2022-11-25 9:44 ` [PATCH v2 2/3] ASoC: mediatek: mt8186: correct the HDMI widgets Jiaxin Yu
2022-11-25 9:44 ` [PATCH v2 3/3] drm/bridge: it6505: Add audio support Jiaxin Yu
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=dc50d0b21795acbcc44c77e5fd81e7cb92c65c67.camel@mediatek.com \
--to=jiaxin.yu@mediatek.com \
--cc=Allen-KH.Cheng@mediatek.com \
--cc=Chunxu.Li@mediatek.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=ajye_huang@compal.corp-partner.google.com \
--cc=alsa-devel@alsa-project.org \
--cc=andrzej.hajda@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=nfraprado@collabora.com \
--cc=robert.foss@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).