regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Jason Montleon <jmontleo@redhat.com>,
	regressions@lists.linux.dev, oder_chiou@realtek.com,
	cezary.rojewski@intel.com, alsa-devel@alsa-project.org,
	Mark Brown <broonie@kernel.org>, Takashi Iwai <tiwai@suse.com>,
	Charles Keepax <ckeepax@opensource.cirrus.com>
Subject: Re: [PATCH] Fix kbl_rt5663_rt5514_max98927 regression
Date: Thu, 03 Nov 2022 08:59:03 +0100	[thread overview]
Message-ID: <87a658o4e0.wl-tiwai@suse.de> (raw)
In-Reply-To: <2bbe7bed-21d4-018a-8957-10d9dbe0c661@linux.intel.com>

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.


Takashi

> 
> Adding Charles Keepax for comments.
> 
> > ---
> >  sound/soc/codecs/rt5514-spi.c | 15 ++++++++-------
> >  1 file changed, 8 insertions(+), 7 deletions(-)
> > 
> > diff --git a/sound/soc/codecs/rt5514-spi.c b/sound/soc/codecs/rt5514-spi.c
> > index 1a25a3787935..362663abcb89 100644
> > --- a/sound/soc/codecs/rt5514-spi.c
> > +++ b/sound/soc/codecs/rt5514-spi.c
> > @@ -298,13 +298,14 @@ static int rt5514_spi_pcm_new(struct snd_soc_component *component,
> >  }
> >  
> >  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  7:59 UTC|newest]

Thread overview: 16+ 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 21:09 ` Jason Montleon
2022-11-03 11:54   ` [PATCH] Fix kbl_rt5663_rt5514_max98927 regression #forregzbot Thorsten Leemhuis
2022-11-02 22:05 ` [PATCH] Fix kbl_rt5663_rt5514_max98927 regression Pierre-Louis Bossart
2022-11-03  7:59   ` Takashi Iwai [this message]
2022-11-03  9:54     ` Charles Keepax
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=87a658o4e0.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=ckeepax@opensource.cirrus.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 \
    /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).