alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: oder_chiou@realtek.com, cezary.rojewski@intel.com,
	regressions@lists.linux.dev, Jason Montleon <jmontleo@redhat.com>,
	Takashi Iwai <tiwai@suse.com>,
	alsa-devel@alsa-project.org,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] Fix kbl_rt5663_rt5514_max98927 regression
Date: Thu, 3 Nov 2022 09:54:04 +0000	[thread overview]
Message-ID: <20221103095404.GI92394@ediswmail.ad.cirrus.com> (raw)
In-Reply-To: <87a658o4e0.wl-tiwai@suse.de>

On Thu, Nov 03, 2022 at 08:59:03AM +0100, Takashi Iwai wrote:
> On Wed, 02 Nov 2022 23:05:14 +0100,
> Pierre-Louis Bossart wrote:
> > 
> > On 11/2/22 16:05, Jason Montleon wrote:
> > > Starting with 6.0-rc1 these messages are logged and the sound card
> > > is unavailable. Adding legacy_dai_naming to the rt5514-spi causes
> > > it to function properly again.
> > > 
> > > [   16.928454] kbl_r5514_5663_max kbl_r5514_5663_max: ASoC: CPU DAI
> > > spi-PRP0001:00 not registered
> > > [   16.928561] platform kbl_r5514_5663_max: deferred probe pending
> > 
> > Thanks for reporting this regression, much appreciated.
> > 
> > a) you need to CC: maintainers Mark Brown and Takashi Iwai
> > b) the commit title should be something like "ASoC: rt5514: fix legacy
> > dai naming".
> > c) it's not clear if this is actually enough. there's no
> > legacy_dai_naming for e.g. rt5663 and the .endianness member is not set.
> 
> IIUC, rt5663.c should be fine; it used to have non_legacy_dai_naming
> flag and it was dropped after the switch.
> 
> But, through a quick glance, rt5677-spi.c seems to be the same pattern
> as rt5514-spi.c.  The rt5677.c was covered properly but the *-spi.c
> wan't.
> 

Yeah I think these got missed as they are effectively CPU side
devices but living in the CODEC space. Looks like it would be
reasonable to add legacy_dai_naming to both of them to me.

Thanks,
Charles

> > >  static const struct snd_soc_component_driver rt5514_spi_component = {
> > > -	.name		= DRV_NAME,
> > > -	.probe		= rt5514_spi_pcm_probe,
> > > -	.open		= rt5514_spi_pcm_open,
> > > -	.hw_params	= rt5514_spi_hw_params,
> > > -	.hw_free	= rt5514_spi_hw_free,
> > > -	.pointer	= rt5514_spi_pcm_pointer,
> > > -	.pcm_construct	= rt5514_spi_pcm_new,
> > > +	.name			= DRV_NAME,
> > > +	.probe			= rt5514_spi_pcm_probe,
> > > +	.open			= rt5514_spi_pcm_open,
> > > +	.hw_params		= rt5514_spi_hw_params,
> > > +	.hw_free		= rt5514_spi_hw_free,
> > > +	.pointer		= rt5514_spi_pcm_pointer,
> > > +	.pcm_construct		= rt5514_spi_pcm_new,
> > > +	.legacy_dai_naming	= 1,
> > >  };
> > >  
> > >  /**
> > 

  reply	other threads:[~2022-11-03  9:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 20:05 [PATCH] Fix kbl_rt5663_rt5514_max98927 regression Jason Montleon
2022-11-02 22:05 ` Pierre-Louis Bossart
2022-11-03  7:59   ` Takashi Iwai
2022-11-03  9:54     ` Charles Keepax [this message]
2022-11-03 11:13       ` Takashi Iwai
2022-11-03 13:11         ` [PATCH v2 1/2] ASoC: rt5514: fix legacy dai naming Jason Montleon
2022-11-03 13:11           ` [PATCH v2 2/2] ASoC: rt5677: " Jason Montleon
2022-11-03 13:19           ` [PATCH v2 1/2] ASoC: rt5514: " Mark Brown
2022-11-03 13:21           ` Takashi Iwai
2022-11-03 13:24             ` Takashi Iwai
2022-11-03 15:00               ` Thorsten Leemhuis
2022-11-03 13:20         ` [PATCH] Fix kbl_rt5663_rt5514_max98927 regression Jason Montleon
2022-11-03 11:57 ` [PATCH] Fix kbl_rt5663_rt5514_max98927 regression #forregzbot Thorsten Leemhuis
2022-11-05 10:13   ` Thorsten Leemhuis

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=20221103095404.GI92394@ediswmail.ad.cirrus.com \
    --to=ckeepax@opensource.cirrus.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=jmontleo@redhat.com \
    --cc=oder_chiou@realtek.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).