From: Alexandre Mergnat <amergnat@baylibre.com>
To: Trevor Wu <trevor.wu@mediatek.com>,
broonie@kernel.org, lgirdwood@gmail.com, tiwai@suse.com,
perex@perex.cz, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com
Cc: alsa-devel@alsa-project.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 5/7] ASoC: soc-dapm.c: clean up debugfs for freed widget
Date: Wed, 24 May 2023 16:51:07 +0200 [thread overview]
Message-ID: <e13c2670-4877-7e75-aaa2-623f4ed927c0@baylibre.com> (raw)
In-Reply-To: <20230523021933.3422-6-trevor.wu@mediatek.com>
On 23/05/2023 04:19, Trevor Wu wrote:
> When a widget is added to dapm via snd_soc_dapm_new_widgets,
> dapm_debugfs_add_widget is also called to create a corresponding debugfs
> file. However, when a widget is freed by snd_soc_dapm_free_widget, the
> corresponding debugfs is not cleared. As a result, the freed widget is
> still seen in the dapm directory.
>
> This patch adds dapm_debugfs_free_widget to free the debugfs of a
> specified widget, and it's called at snd_soc_dapm_free_widget to clean
> up the debugfs for freed widget.
>
> Signed-off-by: Trevor Wu<trevor.wu@mediatek.com>
Reviewed-by: Alexandre Mergnat <amergnat@baylibre.com>
--
Regards,
Alexandre
next prev parent reply other threads:[~2023-05-24 14:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 2:19 [PATCH v2 0/7] ASoC: mt8188: add new board support Trevor Wu
2023-05-23 2:19 ` [PATCH v2 1/7] ASoC: mediatek: mt8188: separate ADDA playback dai from capture dai Trevor Wu
2023-05-23 14:22 ` Alexandre Mergnat
2023-05-24 2:09 ` Trevor Wu (吳文良)
2023-05-23 2:19 ` [PATCH v2 2/7] ASoC: dt-bindings: mediatek,mt8188-mt6359: remove ADDA_BE from link-name Trevor Wu
2023-05-23 16:26 ` Alexandre Mergnat
2023-05-24 2:25 ` Trevor Wu (吳文良)
2023-05-24 13:28 ` Alexandre Mergnat
2023-05-24 13:45 ` Trevor Wu (吳文良)
2023-05-24 14:46 ` Alexandre Mergnat
2023-05-25 3:20 ` Trevor Wu (吳文良)
2023-05-23 2:19 ` [PATCH v2 3/7] ASoC: mediatek: mt8188-mt6359: register hdmi/dp jack pins Trevor Wu
2023-05-24 13:35 ` Alexandre Mergnat
2023-05-23 2:19 ` [PATCH v2 4/7] ASoC: mediatek: common: soundcard driver add dai_fmt support Trevor Wu
2023-05-24 14:12 ` Alexandre Mergnat
2023-05-25 3:07 ` Trevor Wu (吳文良)
2023-05-23 2:19 ` [PATCH v2 5/7] ASoC: soc-dapm.c: clean up debugfs for freed widget Trevor Wu
2023-05-24 14:51 ` Alexandre Mergnat [this message]
2023-05-23 2:19 ` [PATCH v2 6/7] ASoC: mediatek: mt8188-mt6359: support new board with nau88255 Trevor Wu
2023-05-24 15:51 ` Alexandre Mergnat
2023-05-25 3:44 ` Trevor Wu (吳文良)
2023-05-25 7:47 ` Alexandre Mergnat
2023-05-23 2:19 ` [PATCH v2 7/7] ASoC: dt-bindings: mediatek,mt8188-mt6359: add NAU8825 support Trevor Wu
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=e13c2670-4877-7e75-aaa2-623f4ed927c0@baylibre.com \
--to=amergnat@baylibre.com \
--cc=alsa-devel@alsa-project.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.com \
--cc=trevor.wu@mediatek.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