diff for duplicates of <dc50d0b21795acbcc44c77e5fd81e7cb92c65c67.camel@mediatek.com> diff --git a/a/content_digest b/N1/content_digest index 70d1c0a..a507d70 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -11,22 +11,22 @@ "Subject\0Re: [PATCH v2 1/3] ASoC: hdmi-codec: Add event handler for hdmi TX\0" "Date\0Tue, 13 Dec 2022 14:23:32 +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 Mon, 2022-12-05 at 12:07 +0000, Mark Brown wrote:\n" @@ -68,4 +68,4 @@ "Thanks,\n" Jiaxin.Yu -9f600993e908cab9f5c52f9eed943e0f72ad3b8eacf00c189f00a3560093c6b8 +68bf7e8e6aaeb04d124d370f1c862026c586078f65b457d46bcff572f2f16526
diff --git a/a/1.txt b/N2/1.txt index e852981..d509206 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -36,3 +36,7 @@ Then provide handles for these events in the it6505 driver. Am I right? Thanks, Jiaxin.Yu +_______________________________________________ +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 70d1c0a..a0f3927 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -11,22 +11,22 @@ "Subject\0Re: [PATCH v2 1/3] ASoC: hdmi-codec: Add event handler for hdmi TX\0" "Date\0Tue, 13 Dec 2022 14:23:32 +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 Mon, 2022-12-05 at 12:07 +0000, Mark Brown wrote:\n" @@ -66,6 +66,10 @@ "\n" "\n" "Thanks,\n" - Jiaxin.Yu + "Jiaxin.Yu\n" + "_______________________________________________\n" + "linux-arm-kernel mailing list\n" + "linux-arm-kernel@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -9f600993e908cab9f5c52f9eed943e0f72ad3b8eacf00c189f00a3560093c6b8 +8a15fca18b8a692fd825df30f3abfa8c6cc4b5ed2210bf186c29f5ac8ee9f30b
diff --git a/N3/1.bin b/N3/1.bin new file mode 100644 index 0000000..04aa550 --- /dev/null +++ b/N3/1.bin @@ -0,0 +1,55 @@ +<pre> +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 + +</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 100% rename from a/1.txt rename to N3/2.txt diff --git a/a/content_digest b/N3/content_digest index 70d1c0a..c98d8e5 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -27,7 +27,64 @@ 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 Mon, 2022-12-05 at 12:07 +0000, Mark Brown wrote:\r\n" + "> On Mon, Dec 05, 2022 at 09:34:17AM +0000, Jiaxin Yu (俞家鑫) wrote:\r\n" + "> \r\n" + "> > 1. I have added a DAPM widget that is "SDB", when we open or close\r\n" + "> > HDMI\r\n" + "> > PIN_SWITCH, the callback 'hdmi_tx_event' registered in the widget\r\n" + "> > will\r\n" + "> > be triggered. Maybe you mean I shouldn't use\r\n" + "> > SNDRV_PCM_TRIGGER_START\r\n" + "> > and SNDRV_PCM_TRIGGER_STOP?\r\n" + "> \r\n" + "> No, I mean that if you want to control the enable and disable of the\r\n" + "> output path you should implement a DAPM widget.\r\n" + "> \r\n" + "May I ask which driver file to add a new DAPM widget? Is it the bridge\r\n" + "ic driver like it6505.c? Or is it linke the "SDB" added in this patch?\r\n" + "\r\n" + "> > 2. If I don't use hcd.ops->trigger notifies the bridge ic driver to\r\n" + "> > switch the audio, which ops should I use?\r\n" + "> > I actually want to know hdmi-codec.c and it6505.c except\r\n" + "> > hdmi_codec_ops, is there any other way to communicate?\r\n" + "> \r\n" + "> Like I said you should use the event on the DAPM widget.  This will\r\n" + "> require providing operations for the events to the drivers.\r\n" + "Yes, I should add a new set of events, such as:\r\n" + "\r\n" + "enum {\r\n" + "    HDMI_CODEC_TRIGGER_EVENT_STOP,\r\n" + "    HDMI_CODEC_TRIGGER_EVENT_START,\r\n" + "    HDMI_CODEC_TRIGGER_EVENT_SUSPEND,\r\n" + "    HDMI_CODEC_TRIGGER_EVENT_RESUME,\r\n" + "}\r\n" + "\r\n" + "Then provide handles for these events in the it6505 driver. Am I right?\r\n" + "\r\n" + "\r\n" + "Thanks,\r\n" + "Jiaxin.Yu\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 Mon, 2022-12-05 at 12:07 +0000, Mark Brown wrote:\n" "> On Mon, Dec 05, 2022 at 09:34:17AM +0000, Jiaxin Yu (\344\277\236\345\256\266\351\221\253) wrote:\n" @@ -68,4 +125,4 @@ "Thanks,\n" Jiaxin.Yu -9f600993e908cab9f5c52f9eed943e0f72ad3b8eacf00c189f00a3560093c6b8 +68aba3403fa590d764a5340534d2ff79bbf279baa58d7a101a2740c97e75410e
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.