diff for duplicates of <cf9ea98a3263ffb8fc8b542888ad0ad680facfc7.camel@mediatek.com> diff --git a/a/1.txt b/N1/1.txt index a6c2562..54fc10a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -21,8 +21,8 @@ On Tue, 2022-11-29 at 17:22 +0000, Mark Brown wrote: > > Let me describe the hardware connection about mt8186 with > > it6505(hdmi) > > and rt1015p(speakers). -> > ==>it6505 -> > = +> > ==>it6505 +> > = > > DL1(FE) ==>I2S3(BE) = > > = > > ==>rt1015p @@ -33,7 +33,7 @@ On Tue, 2022-11-29 at 17:22 +0000, Mark Brown wrote: > > resulting in > > sound on both devices. > > Is there another way to control them separately? Thank you. -> +> > If you just need power control for one or both devices then the > machine > driver can add a _PIN_SWITCH() on the output of the device, that'll @@ -56,24 +56,3 @@ Yes, we do use a _PIN_SWITCH() on the outout of the device: Which operation should I use to inform bridge driver to control audio on or off? I'm curious why I don't see .trigger in the structure hdmi_codec_ops compared to the structure snd_soc_dai_ops? - - - - - - - -************* MEDIATEK Confidentiality Notice - ******************** -The information contained in this e-mail message (including any -attachments) may be confidential, proprietary, privileged, or otherwise -exempt from disclosure under applicable laws. It is intended to be -conveyed only to the designated recipient(s). Any use, dissemination, -distribution, printing, retaining or copying of this e-mail (including its -attachments) by unintended recipient(s) is strictly prohibited and may -be unlawful. If you are not an intended recipient of this e-mail, or believe - -that you have received this e-mail in error, please notify the sender -immediately (by replying to this e-mail), delete any and all copies of -this e-mail (including any attachments) from your system, and do not -disclose the content of this e-mail to any other person. Thank you! diff --git a/a/content_digest b/N1/content_digest index 6e38e43..e321c73 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -7,22 +7,22 @@ "Subject\0Re: [PATCH v2 1/3] ASoC: hdmi-codec: Add event handler for hdmi TX\0" "Date\0Thu, 1 Dec 2022 15:06:04 +0000\0" "To\0broonie@kernel.org <broonie@kernel.org>\0" - "Cc\0alsa-devel@alsa-project.org <alsa-devel@alsa-project.org>" - neil.armstrong@linaro.org <neil.armstrong@linaro.org> - nfraprado@collabora.com <nfraprado@collabora.com> + "Cc\0linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>" + linux-mediatek@lists.infradead.org <linux-mediatek@lists.infradead.org> + ajye_huang@compal.corp-partner.google.com <ajye_huang@compal.corp-partner.google.com> " Chunxu Li (\346\235\216\346\230\245\346\227\255) <Chunxu.Li@mediatek.com>" " Allen-KH Cheng (\347\250\213\345\206\240\345\213\263) <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> + kuninori.morimoto.gx@renesas.com <kuninori.morimoto.gx@renesas.com> + andrzej.hajda@intel.com <andrzej.hajda@intel.com> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.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> + Laurent.pinchart@ideasonboard.com <Laurent.pinchart@ideasonboard.com> + neil.armstrong@linaro.org <neil.armstrong@linaro.org> 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>\0" + nfraprado@collabora.com <nfraprado@collabora.com> + " alsa-devel@alsa-project.org <alsa-devel@alsa-project.org>\0" "\00:1\0" "b\0" "On Tue, 2022-11-29 at 17:22 +0000, Mark Brown wrote:\n" @@ -48,8 +48,8 @@ "> > Let me describe the hardware connection about mt8186 with\n" "> > it6505(hdmi)\n" "> > and rt1015p(speakers).\n" - "> > ==>it6505\n" - "> > =\n" + "> > ==>it6505 \n" + "> > = \n" "> > DL1(FE) ==>I2S3(BE) =\n" "> > =\n" "> > ==>rt1015p\n" @@ -60,7 +60,7 @@ "> > resulting in\n" "> > sound on both devices.\n" "> > Is there another way to control them separately? Thank you.\n" - ">\n" + "> \n" "> If you just need power control for one or both devices then the\n" "> machine\n" "> driver can add a _PIN_SWITCH() on the output of the device, that'll\n" @@ -82,27 +82,6 @@ "\n" "Which operation should I use to inform bridge driver to control audio\n" "on or off? I'm curious why I don't see .trigger in the structure\n" - "hdmi_codec_ops compared to the structure snd_soc_dai_ops?\n" - "\n" - "\n" - "\n" - "\n" - "\n" - "\n" - "\n" - "************* MEDIATEK Confidentiality Notice\n" - " ********************\n" - "The information contained in this e-mail message (including any\n" - "attachments) may be confidential, proprietary, privileged, or otherwise\n" - "exempt from disclosure under applicable laws. It is intended to be\n" - "conveyed only to the designated recipient(s). Any use, dissemination,\n" - "distribution, printing, retaining or copying of this e-mail (including its\n" - "attachments) by unintended recipient(s) is strictly prohibited and may\n" - "be unlawful. If you are not an intended recipient of this e-mail, or believe\n" - "\n" - "that you have received this e-mail in error, please notify the sender\n" - "immediately (by replying to this e-mail), delete any and all copies of\n" - "this e-mail (including any attachments) from your system, and do not\n" - disclose the content of this e-mail to any other person. Thank you! + hdmi_codec_ops compared to the structure snd_soc_dai_ops? -d3b5d549ec401c580fad8801b23f9587dfce699996e291c2214e3b81937b9248 +a1078fd0b31e798b63c9a1b7fcfcd325ebb257788dbb6af7c6d15ac1cbbd667b
diff --git a/a/1.txt b/N2/1.txt index a6c2562..2be5787 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -21,8 +21,8 @@ On Tue, 2022-11-29 at 17:22 +0000, Mark Brown wrote: > > Let me describe the hardware connection about mt8186 with > > it6505(hdmi) > > and rt1015p(speakers). -> > ==>it6505 -> > = +> > ==>it6505 +> > = > > DL1(FE) ==>I2S3(BE) = > > = > > ==>rt1015p @@ -33,7 +33,7 @@ On Tue, 2022-11-29 at 17:22 +0000, Mark Brown wrote: > > resulting in > > sound on both devices. > > Is there another way to control them separately? Thank you. -> +> > If you just need power control for one or both devices then the > machine > driver can add a _PIN_SWITCH() on the output of the device, that'll @@ -61,19 +61,7 @@ hdmi_codec_ops compared to the structure snd_soc_dai_ops? - - -************* MEDIATEK Confidentiality Notice - ******************** -The information contained in this e-mail message (including any -attachments) may be confidential, proprietary, privileged, or otherwise -exempt from disclosure under applicable laws. It is intended to be -conveyed only to the designated recipient(s). Any use, dissemination, -distribution, printing, retaining or copying of this e-mail (including its -attachments) by unintended recipient(s) is strictly prohibited and may -be unlawful. If you are not an intended recipient of this e-mail, or believe - -that you have received this e-mail in error, please notify the sender -immediately (by replying to this e-mail), delete any and all copies of -this e-mail (including any attachments) from your system, and do not -disclose the content of this e-mail to any other person. Thank you! +_______________________________________________ +linux-arm-kernel mailing list +linux-arm-kernel@lists.infradead.org +http://lists.infradead.org/mailman/listinfo/linux-arm-kernel diff --git a/a/content_digest b/N2/content_digest index 6e38e43..0293f74 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -7,22 +7,22 @@ "Subject\0Re: [PATCH v2 1/3] ASoC: hdmi-codec: Add event handler for hdmi TX\0" "Date\0Thu, 1 Dec 2022 15:06:04 +0000\0" "To\0broonie@kernel.org <broonie@kernel.org>\0" - "Cc\0alsa-devel@alsa-project.org <alsa-devel@alsa-project.org>" - neil.armstrong@linaro.org <neil.armstrong@linaro.org> - nfraprado@collabora.com <nfraprado@collabora.com> + "Cc\0linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>" + linux-mediatek@lists.infradead.org <linux-mediatek@lists.infradead.org> + ajye_huang@compal.corp-partner.google.com <ajye_huang@compal.corp-partner.google.com> " Chunxu Li (\346\235\216\346\230\245\346\227\255) <Chunxu.Li@mediatek.com>" " Allen-KH Cheng (\347\250\213\345\206\240\345\213\263) <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> + kuninori.morimoto.gx@renesas.com <kuninori.morimoto.gx@renesas.com> + andrzej.hajda@intel.com <andrzej.hajda@intel.com> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.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> + Laurent.pinchart@ideasonboard.com <Laurent.pinchart@ideasonboard.com> + neil.armstrong@linaro.org <neil.armstrong@linaro.org> 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>\0" + nfraprado@collabora.com <nfraprado@collabora.com> + " alsa-devel@alsa-project.org <alsa-devel@alsa-project.org>\0" "\00:1\0" "b\0" "On Tue, 2022-11-29 at 17:22 +0000, Mark Brown wrote:\n" @@ -48,8 +48,8 @@ "> > Let me describe the hardware connection about mt8186 with\n" "> > it6505(hdmi)\n" "> > and rt1015p(speakers).\n" - "> > ==>it6505\n" - "> > =\n" + "> > ==>it6505 \n" + "> > = \n" "> > DL1(FE) ==>I2S3(BE) =\n" "> > =\n" "> > ==>rt1015p\n" @@ -60,7 +60,7 @@ "> > resulting in\n" "> > sound on both devices.\n" "> > Is there another way to control them separately? Thank you.\n" - ">\n" + "> \n" "> If you just need power control for one or both devices then the\n" "> machine\n" "> driver can add a _PIN_SWITCH() on the output of the device, that'll\n" @@ -88,21 +88,9 @@ "\n" "\n" "\n" - "\n" - "\n" - "************* MEDIATEK Confidentiality Notice\n" - " ********************\n" - "The information contained in this e-mail message (including any\n" - "attachments) may be confidential, proprietary, privileged, or otherwise\n" - "exempt from disclosure under applicable laws. It is intended to be\n" - "conveyed only to the designated recipient(s). Any use, dissemination,\n" - "distribution, printing, retaining or copying of this e-mail (including its\n" - "attachments) by unintended recipient(s) is strictly prohibited and may\n" - "be unlawful. If you are not an intended recipient of this e-mail, or believe\n" - "\n" - "that you have received this e-mail in error, please notify the sender\n" - "immediately (by replying to this e-mail), delete any and all copies of\n" - "this e-mail (including any attachments) from your system, and do not\n" - disclose the content of this e-mail to any other person. Thank you! + "_______________________________________________\n" + "linux-arm-kernel mailing list\n" + "linux-arm-kernel@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -d3b5d549ec401c580fad8801b23f9587dfce699996e291c2214e3b81937b9248 +4e9e4ae9ee084f2bca654dc1164815b85aa098601bc422b12d13337a4cfc00e0
diff --git a/N3/1.bin b/N3/1.bin new file mode 100644 index 0000000..f7f6ae1 --- /dev/null +++ b/N3/1.bin @@ -0,0 +1,80 @@ +<pre> +On Tue, 2022-11-29 at 17:22 +0000, Mark Brown wrote: +> On Mon, Nov 28, 2022 at 03:07:22PM +0000, Jiaxin Yu (俞家鑫) wrote: +> > On Fri, 2022-11-25 at 12:18 +0000, Mark Brown wrote: +> > > On Fri, Nov 25, 2022 at 05:44:11PM +0800, Jiaxin Yu wrote: +> > > I'm a little unclear why this is being implemented as a DAPM +> > > operation +> > > rather than having the driver forward the PCM trigger op if it's +> > > needed? +> > > Or alternatively if a DAPM callback is needed why not provide one +> > > directly rather than hooking into the trigger function - that's +> > > going +> > > to +> > > be called out of sequence with the rest of DAPM and be +> > > potentially +> > > confusing given the very different environments that trigger and +> > > DAPM +> > > operations run in.  A quick glance at the it6505 driver suggests +> > > it'd +> > > be +> > > happier with a DAPM callback. +> > Let me describe the hardware connection about mt8186 with +> > it6505(hdmi) +> > and rt1015p(speakers). +> >                        ==>it6505  +> >                      =  +> > DL1(FE) ==>I2S3(BE) = +> >                      = +> >                        ==>rt1015p +> > They shared the same one i2s port, but we'd like to control them +> > separately. So if hdmi-codec use the PCM trigger op, whne we turn +> > on +> > the speaker, hdmi-codec's PCM trigger op is also executed, +> > resulting in +> > sound on both devices. +> > Is there another way to control them separately? Thank you. +>  +> If you just need power control for one or both devices then the +> machine +> driver can add a _PIN_SWITCH() on the output of the device, that'll +> cause DAPM to keep the device powered down when not in use.  That +> should +> work well with the suggestion to provide a DAPM callback instead of a +> a +> trigger operation. + +Yes, we do use a _PIN_SWITCH() on the outout of the device: + +>  static const struct snd_kcontrol_new +>  mt8186_mt6366_rt1019_rt5682s_controls[] = { +>          SOC_DAPM_PIN_SWITCH("Speakers"), +>          SOC_DAPM_PIN_SWITCH("Headphone"), +>          SOC_DAPM_PIN_SWITCH("Headset Mic"), +>          SOC_DAPM_PIN_SWITCH("HDMI1"), +>  }; + +Which operation should I use to inform bridge driver to control audio +on or off? I'm curious why I don't see .trigger in the structure +hdmi_codec_ops compared to the structure snd_soc_dai_ops? + + + + + + +</pre><!--type:text--><!--{--><pre>************* MEDIATEK Confidentiality Notice + ******************** +The information contained in this e-mail message (including any +attachments) may be confidential, proprietary, privileged, or otherwise +exempt from disclosure under applicable laws. It is intended to be +conveyed only to the designated recipient(s). Any use, dissemination, +distribution, printing, retaining or copying of this e-mail (including its +attachments) by unintended recipient(s) is strictly prohibited and may +be unlawful. If you are not an intended recipient of this e-mail, or believe + +that you have received this e-mail in error, please notify the sender +immediately (by replying to this e-mail), delete any and all copies of +this e-mail (including any attachments) from your system, and do not +disclose the content of this e-mail to any other person. Thank you! +</pre><!--}--> diff --git a/N3/2.hdr b/N3/2.hdr new file mode 100644 index 0000000..45d76fc --- /dev/null +++ b/N3/2.hdr @@ -0,0 +1,3 @@ +Content-Type: text/plain; + charset="utf-8" +Content-Transfer-Encoding: base64 diff --git a/a/1.txt b/N3/2.txt similarity index 70% rename from a/1.txt rename to N3/2.txt index a6c2562..54fc10a 100644 --- a/a/1.txt +++ b/N3/2.txt @@ -21,8 +21,8 @@ On Tue, 2022-11-29 at 17:22 +0000, Mark Brown wrote: > > Let me describe the hardware connection about mt8186 with > > it6505(hdmi) > > and rt1015p(speakers). -> > ==>it6505 -> > = +> > ==>it6505 +> > = > > DL1(FE) ==>I2S3(BE) = > > = > > ==>rt1015p @@ -33,7 +33,7 @@ On Tue, 2022-11-29 at 17:22 +0000, Mark Brown wrote: > > resulting in > > sound on both devices. > > Is there another way to control them separately? Thank you. -> +> > If you just need power control for one or both devices then the > machine > driver can add a _PIN_SWITCH() on the output of the device, that'll @@ -56,24 +56,3 @@ Yes, we do use a _PIN_SWITCH() on the outout of the device: Which operation should I use to inform bridge driver to control audio on or off? I'm curious why I don't see .trigger in the structure hdmi_codec_ops compared to the structure snd_soc_dai_ops? - - - - - - - -************* MEDIATEK Confidentiality Notice - ******************** -The information contained in this e-mail message (including any -attachments) may be confidential, proprietary, privileged, or otherwise -exempt from disclosure under applicable laws. It is intended to be -conveyed only to the designated recipient(s). Any use, dissemination, -distribution, printing, retaining or copying of this e-mail (including its -attachments) by unintended recipient(s) is strictly prohibited and may -be unlawful. If you are not an intended recipient of this e-mail, or believe - -that you have received this e-mail in error, please notify the sender -immediately (by replying to this e-mail), delete any and all copies of -this e-mail (including any attachments) from your system, and do not -disclose the content of this e-mail to any other person. Thank you! diff --git a/a/content_digest b/N3/content_digest index 6e38e43..ca2efa0 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -23,7 +23,89 @@ 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>\0" - "\00:1\0" + "\01:1\0" + "b\0" + "<pre>\r\n" + "On Tue, 2022-11-29 at 17:22 +0000, Mark Brown wrote:\r\n" + "> On Mon, Nov 28, 2022 at 03:07:22PM +0000, Jiaxin Yu (俞家鑫) wrote:\r\n" + "> > On Fri, 2022-11-25 at 12:18 +0000, Mark Brown wrote:\r\n" + "> > > On Fri, Nov 25, 2022 at 05:44:11PM +0800, Jiaxin Yu wrote:\r\n" + "> > > I'm a little unclear why this is being implemented as a DAPM\r\n" + "> > > operation\r\n" + "> > > rather than having the driver forward the PCM trigger op if it's\r\n" + "> > > needed?\r\n" + "> > > Or alternatively if a DAPM callback is needed why not provide one\r\n" + "> > > directly rather than hooking into the trigger function - that's\r\n" + "> > > going\r\n" + "> > > to\r\n" + "> > > be called out of sequence with the rest of DAPM and be\r\n" + "> > > potentially\r\n" + "> > > confusing given the very different environments that trigger and\r\n" + "> > > DAPM\r\n" + "> > > operations run in.  A quick glance at the it6505 driver suggests\r\n" + "> > > it'd\r\n" + "> > > be\r\n" + "> > > happier with a DAPM callback.\r\n" + "> > Let me describe the hardware connection about mt8186 with\r\n" + "> > it6505(hdmi)\r\n" + "> > and rt1015p(speakers).\r\n" + "> >                        ==>it6505 \r\n" + "> >                      = \r\n" + "> > DL1(FE) ==>I2S3(BE) =\r\n" + "> >                      =\r\n" + "> >                        ==>rt1015p\r\n" + "> > They shared the same one i2s port, but we'd like to control them\r\n" + "> > separately. So if hdmi-codec use the PCM trigger op, whne we turn\r\n" + "> > on\r\n" + "> > the speaker, hdmi-codec's PCM trigger op is also executed,\r\n" + "> > resulting in\r\n" + "> > sound on both devices.\r\n" + "> > Is there another way to control them separately? Thank you.\r\n" + "> \r\n" + "> If you just need power control for one or both devices then the\r\n" + "> machine\r\n" + "> driver can add a _PIN_SWITCH() on the output of the device, that'll\r\n" + "> cause DAPM to keep the device powered down when not in use.  That\r\n" + "> should\r\n" + "> work well with the suggestion to provide a DAPM callback instead of a\r\n" + "> a\r\n" + "> trigger operation.\r\n" + "\r\n" + "Yes, we do use a _PIN_SWITCH() on the outout of the device:\r\n" + "\r\n" + ">  static const struct snd_kcontrol_new\r\n" + ">  mt8186_mt6366_rt1019_rt5682s_controls[] = {\r\n" + ">          SOC_DAPM_PIN_SWITCH("Speakers"),\r\n" + ">          SOC_DAPM_PIN_SWITCH("Headphone"),\r\n" + ">          SOC_DAPM_PIN_SWITCH("Headset Mic"),\r\n" + ">          SOC_DAPM_PIN_SWITCH("HDMI1"),\r\n" + ">  };\r\n" + "\r\n" + "Which operation should I use to inform bridge driver to control audio\r\n" + "on or off? I'm curious why I don't see .trigger in the structure\r\n" + "hdmi_codec_ops compared to the structure snd_soc_dai_ops?\r\n" + "\r\n" + "\r\n" + "\r\n" + "\r\n" + "\r\n" + "\r\n" + "</pre><!--type:text--><!--{--><pre>************* MEDIATEK Confidentiality Notice\r\n" + " ********************\r\n" + "The information contained in this e-mail message (including any \r\n" + "attachments) may be confidential, proprietary, privileged, or otherwise\r\n" + "exempt from disclosure under applicable laws. It is intended to be \r\n" + "conveyed only to the designated recipient(s). Any use, dissemination, \r\n" + "distribution, printing, retaining or copying of this e-mail (including its \r\n" + "attachments) by unintended recipient(s) is strictly prohibited and may \r\n" + "be unlawful. If you are not an intended recipient of this e-mail, or believe\r\n" + " \r\n" + "that you have received this e-mail in error, please notify the sender \r\n" + "immediately (by replying to this e-mail), delete any and all copies of \r\n" + "this e-mail (including any attachments) from your system, and do not\r\n" + "disclose the content of this e-mail to any other person. Thank you!\r\n" + </pre><!--}--> + "\01:2\0" "b\0" "On Tue, 2022-11-29 at 17:22 +0000, Mark Brown wrote:\n" "> On Mon, Nov 28, 2022 at 03:07:22PM +0000, Jiaxin Yu (\344\277\236\345\256\266\351\221\253) wrote:\n" @@ -48,8 +130,8 @@ "> > Let me describe the hardware connection about mt8186 with\n" "> > it6505(hdmi)\n" "> > and rt1015p(speakers).\n" - "> > ==>it6505\n" - "> > =\n" + "> > ==>it6505 \n" + "> > = \n" "> > DL1(FE) ==>I2S3(BE) =\n" "> > =\n" "> > ==>rt1015p\n" @@ -60,7 +142,7 @@ "> > resulting in\n" "> > sound on both devices.\n" "> > Is there another way to control them separately? Thank you.\n" - ">\n" + "> \n" "> If you just need power control for one or both devices then the\n" "> machine\n" "> driver can add a _PIN_SWITCH() on the output of the device, that'll\n" @@ -82,27 +164,6 @@ "\n" "Which operation should I use to inform bridge driver to control audio\n" "on or off? I'm curious why I don't see .trigger in the structure\n" - "hdmi_codec_ops compared to the structure snd_soc_dai_ops?\n" - "\n" - "\n" - "\n" - "\n" - "\n" - "\n" - "\n" - "************* MEDIATEK Confidentiality Notice\n" - " ********************\n" - "The information contained in this e-mail message (including any\n" - "attachments) may be confidential, proprietary, privileged, or otherwise\n" - "exempt from disclosure under applicable laws. It is intended to be\n" - "conveyed only to the designated recipient(s). Any use, dissemination,\n" - "distribution, printing, retaining or copying of this e-mail (including its\n" - "attachments) by unintended recipient(s) is strictly prohibited and may\n" - "be unlawful. If you are not an intended recipient of this e-mail, or believe\n" - "\n" - "that you have received this e-mail in error, please notify the sender\n" - "immediately (by replying to this e-mail), delete any and all copies of\n" - "this e-mail (including any attachments) from your system, and do not\n" - disclose the content of this e-mail to any other person. Thank you! + hdmi_codec_ops compared to the structure snd_soc_dai_ops? -d3b5d549ec401c580fad8801b23f9587dfce699996e291c2214e3b81937b9248 +516313440f08d85da203b64d87a1e17ae90d3b7bfed4204c2f0a39bb79c71424
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.