From: Mark Brown <broonie@kernel.org>
To: Jiaxin Yu <jiaxin.yu@mediatek.com>
Cc: neil.armstrong@linaro.org, alsa-devel@alsa-project.org,
chunxu.li@mediatek.com, nfraprado@collabora.com,
kuninori.morimoto.gx@renesas.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
robert.foss@linaro.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-mediatek@lists.infradead.org,
Laurent.pinchart@ideasonboard.com, andrzej.hajda@intel.com,
allen-kh.cheng@mediatek.com,
ajye_huang@compal.corp-partner.google.com,
linux-arm-kernel@lists.infradead.org,
angelogioacchino.delregno@collabora.com
Subject: Re: [PATCH v2 1/3] ASoC: hdmi-codec: Add event handler for hdmi TX
Date: Fri, 25 Nov 2022 12:18:58 +0000 [thread overview]
Message-ID: <Y4Cysgk5Gic5ae9B@sirena.org.uk> (raw)
In-Reply-To: <20221125094413.4940-2-jiaxin.yu@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
On Fri, Nov 25, 2022 at 05:44:11PM +0800, Jiaxin Yu wrote:
> + /*
> + * PCM trigger callback.
> + * Mandatory
> + */
> + int (*trigger)(struct device *dev, int cmd);
> +
Making this mandatory would break all existing users, though...
> + switch (event) {
> + case SND_SOC_DAPM_PRE_PMU:
> + if (hcp->hcd.ops->trigger)
> + hcp->hcd.ops->trigger(component->dev->parent, SNDRV_PCM_TRIGGER_START);
...it's not actually mandatory so it's just the comment that's wrong.
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Jiaxin Yu <jiaxin.yu@mediatek.com>
Cc: andrzej.hajda@intel.com, neil.armstrong@linaro.org,
robert.foss@linaro.org, Laurent.pinchart@ideasonboard.com,
kuninori.morimoto.gx@renesas.com,
angelogioacchino.delregno@collabora.com, nfraprado@collabora.com,
chunxu.li@mediatek.com,
ajye_huang@compal.corp-partner.google.com,
allen-kh.cheng@mediatek.com, dri-devel@lists.freedesktop.org,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v2 1/3] ASoC: hdmi-codec: Add event handler for hdmi TX
Date: Fri, 25 Nov 2022 12:18:58 +0000 [thread overview]
Message-ID: <Y4Cysgk5Gic5ae9B@sirena.org.uk> (raw)
In-Reply-To: <20221125094413.4940-2-jiaxin.yu@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
On Fri, Nov 25, 2022 at 05:44:11PM +0800, Jiaxin Yu wrote:
> + /*
> + * PCM trigger callback.
> + * Mandatory
> + */
> + int (*trigger)(struct device *dev, int cmd);
> +
Making this mandatory would break all existing users, though...
> + switch (event) {
> + case SND_SOC_DAPM_PRE_PMU:
> + if (hcp->hcd.ops->trigger)
> + hcp->hcd.ops->trigger(component->dev->parent, SNDRV_PCM_TRIGGER_START);
...it's not actually mandatory so it's just the comment that's wrong.
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Jiaxin Yu <jiaxin.yu@mediatek.com>
Cc: andrzej.hajda@intel.com, neil.armstrong@linaro.org,
robert.foss@linaro.org, Laurent.pinchart@ideasonboard.com,
kuninori.morimoto.gx@renesas.com,
angelogioacchino.delregno@collabora.com, nfraprado@collabora.com,
chunxu.li@mediatek.com,
ajye_huang@compal.corp-partner.google.com,
allen-kh.cheng@mediatek.com, dri-devel@lists.freedesktop.org,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v2 1/3] ASoC: hdmi-codec: Add event handler for hdmi TX
Date: Fri, 25 Nov 2022 12:18:58 +0000 [thread overview]
Message-ID: <Y4Cysgk5Gic5ae9B@sirena.org.uk> (raw)
In-Reply-To: <20221125094413.4940-2-jiaxin.yu@mediatek.com>
[-- Attachment #1.1: Type: text/plain, Size: 996 bytes --]
On Fri, Nov 25, 2022 at 05:44:11PM +0800, Jiaxin Yu wrote:
> + /*
> + * PCM trigger callback.
> + * Mandatory
> + */
> + int (*trigger)(struct device *dev, int cmd);
> +
Making this mandatory would break all existing users, though...
> + switch (event) {
> + case SND_SOC_DAPM_PRE_PMU:
> + if (hcp->hcd.ops->trigger)
> + hcp->hcd.ops->trigger(component->dev->parent, SNDRV_PCM_TRIGGER_START);
...it's not actually mandatory so it's just the comment that's wrong.
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.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-25 12:20 UTC|newest]
Thread overview: 49+ 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 ` Jiaxin Yu
2022-11-25 9:44 ` 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 9:44 ` Jiaxin Yu
2022-11-25 9:44 ` Jiaxin Yu
2022-11-25 12:18 ` Mark Brown [this message]
2022-11-25 12:18 ` Mark Brown
2022-11-25 12:18 ` Mark Brown
2022-11-28 15:07 ` Jiaxin Yu (俞家鑫)
2022-11-28 15:07 ` Jiaxin Yu (俞家鑫)
2022-11-28 15:07 ` Jiaxin Yu (俞家鑫)
2022-11-28 15:07 ` Jiaxin Yu (俞家鑫)
2022-11-29 17:22 ` Mark Brown
2022-11-29 17:22 ` Mark Brown
2022-11-29 17:22 ` Mark Brown
2022-12-01 15:06 ` Jiaxin Yu (俞家鑫)
2022-12-01 15:06 ` Jiaxin Yu (俞家鑫)
2022-12-01 15:06 ` Jiaxin Yu (俞家鑫)
2022-12-01 15:06 ` Jiaxin Yu (俞家鑫)
2022-12-01 15:23 ` Mark Brown
2022-12-01 15:23 ` Mark Brown
2022-12-01 15:23 ` Mark Brown
2022-12-05 9:34 ` Jiaxin Yu (俞家鑫)
2022-12-05 9:34 ` Jiaxin Yu (俞家鑫)
2022-12-05 9:34 ` Jiaxin Yu (俞家鑫)
2022-12-05 9:34 ` Jiaxin Yu (俞家鑫)
2022-12-05 12:07 ` Mark Brown
2022-12-05 12:07 ` Mark Brown
2022-12-05 12:07 ` Mark Brown
2022-12-13 14:23 ` Jiaxin Yu (俞家鑫)
2022-12-13 14:23 ` Jiaxin Yu (俞家鑫)
2022-12-13 14:23 ` Jiaxin Yu (俞家鑫)
2022-12-13 14:23 ` Jiaxin Yu (俞家鑫)
2022-12-13 16:35 ` Mark Brown
2022-12-13 16:35 ` Mark Brown
2022-12-13 16:35 ` Mark Brown
2024-12-01 17:15 ` Jiaxin Yu (俞家鑫)
2024-12-01 17:15 ` Jiaxin Yu (俞家鑫)
2024-12-02 13:16 ` Mark Brown
2024-12-06 15:39 ` Jiaxin Yu (俞家鑫)
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 ` Jiaxin Yu
2022-11-25 9:44 ` Jiaxin Yu
2022-11-25 9:44 ` [PATCH v2 3/3] drm/bridge: it6505: Add audio support Jiaxin Yu
2022-11-25 9:44 ` Jiaxin Yu
2022-11-25 9:44 ` 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=Y4Cysgk5Gic5ae9B@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=ajye_huang@compal.corp-partner.google.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=alsa-devel@alsa-project.org \
--cc=andrzej.hajda@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunxu.li@mediatek.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jiaxin.yu@mediatek.com \
--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 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.