public inbox for linux-sound@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Jaroslav Kysela <perex@perex.cz>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Peter Ujfalusi <peter.ujfalusi@gmail.com>,
	Takashi Iwai <tiwai@suse.com>,
	linux-sound@vger.kernel.org
Subject: Re: [RFC][PATCH 0/3] ASoC: remove card->pop_time
Date: Thu, 09 Apr 2026 07:22:22 +0200	[thread overview]
Message-ID: <871pgolnch.wl-tiwai@suse.de> (raw)
In-Reply-To: <87h5pkda1r.wl-kuninori.morimoto.gx@renesas.com>

On Thu, 09 Apr 2026 06:36:48 +0200,
Kuninori Morimoto wrote:
> 
> Hi Mark, OMAP member
> 
> I'm now trying to cleanup snd_soc_card, and noticed that card->pop_time is used
> only from OMAP1 board-ams-delta.
> 
> card->pop_time user drivers are...
> 
> 	> git grep -w -l pop_time sound/soc include/sound
> 	include/sound/soc.h
> (A)	sound/soc/codecs/cx20442.c
> 	sound/soc/soc-card.c
> 	sound/soc/soc-dapm.c
> (B)	sound/soc/ti/ams-delta.c
> 
> Except ASoC framework, pop_time user is only cx20442 (A) / ams-delta (B).
> And board-ams-delta (Z) is using it.
> 
> (Z)	linux/arch/arm/mach-omap1/board-ams-delta.c
> 
> 	static struct platform_device ams_delta_audio_device = {
> (A)		.name   = "ams-delta-audio",
> 	};
> 
> 	static struct platform_device cx20442_codec_device = {
> (B)		.name   = "cx20442-codec",
> 	};
> 
> 	static struct platform_device *ams_delta_devices[] __initdata = {
> 		...
> (A)		&ams_delta_audio_device,
> 		...
> (B)		&cx20442_codec_device,
> 		...
> 	};
> 
> With off-list talk with Mark, this card->pop_time is is much less of a
> problem.

Hmm, are you sure?  IIUC, it's used for a flag in the modem desc for
cx81801, and a bunch of setup seems depending on it, and your second
patch removes the whole of those without alternative.

> So let's remove it. But it needs Acked-by from OMAP1 member.
> I added [RFC] on Subject.

So the actual question is whether the modem is utterly broken for this
hardware or not.  If yes, it'd be a good reason to drop and apply this
cleanup.

But if it's not, we'd need an alternative implementation, e.g. move
the flag and its handling to the modem's own object instead of the
ASoC core, instead.


thanks,

Takashi

  parent reply	other threads:[~2026-04-09  5:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09  4:36 [RFC][PATCH 0/3] ASoC: remove card->pop_time Kuninori Morimoto
2026-04-09  4:37 ` [RFC][PATCH 1/3] ASoC: ti: amx-delta: don't use card->pop_time Kuninori Morimoto
2026-04-09  4:37 ` [RFC][PATCH 2/3] ASoC: cx20442: " Kuninori Morimoto
2026-04-09  4:37 ` [RFC][PATCH 3/3] ASoC: soc-card: remvoe card->pop_time Kuninori Morimoto
2026-04-09  5:22 ` Takashi Iwai [this message]
2026-04-09 20:47   ` [RFC][PATCH 0/3] ASoC: remove card->pop_time Mark Brown
2026-04-09  8:14 ` Péter Ujfalusi
2026-04-09 19:11   ` Mark Brown
2026-04-10  3:14     ` Kuninori Morimoto
2026-04-10  7:06     ` Péter Ujfalusi

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=871pgolnch.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=broonie@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@gmail.com \
    --cc=tiwai@suse.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