All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: htl10@users.sourceforge.net
Cc: alsa-devel@alsa-project.org
Subject: Re: ASoc / PCM recording-related regression between v5.4 and v5.5
Date: 20 Apr 2021 07:35:25 +0900	[thread overview]
Message-ID: <87h7k152du.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <1772063602.5910217.1618841824599@mail.yahoo.com>


Hi Hin-Tak


> it was not setting .non_legacy_dai_naming - this was a 4.16 change . The similar hardware but working
> sibling device has one single ADC codec, while the broken device has two such ADC codec plus a 3rd DAC
> codec; I see that this flag started to matter in v5.6 for codec2codec links . I don't know if this
> qualifies as a codec 2 codec link - it is running two 4-mic ADC in parallel to read from 6 mics...
> 
> Anyway, I tried putting that flag in, but it has not fix problem with 5.10, so I am back to trimming
> the difference between v5.4 and v5.5 slowly.

v5.3 has other big change on ALSA SoC for each driver.
Out-of-tree might get this effect.

	ASoC: xxxx: use modern dai_link style

For example,
05ab66178cb27ee795aa458b43818d2caa2d3953
("ASoC: mediatek: mt8173-rt5650-rt5676: use modern dai_link style")

Thank you for your help !!

Best regards
---
Kuninori Morimoto

  reply	other threads:[~2021-04-19 22:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <148484793.4894421.1618654607945.ref@mail.yahoo.com>
2021-04-17 10:16 ` ASoc / PCM recording-related regression between v5.4 and v5.5 Hin-Tak Leung
2021-04-18 22:46   ` Kuninori Morimoto
2021-04-19 14:17     ` Hin-Tak Leung
2021-04-19 22:35       ` Kuninori Morimoto [this message]
2021-04-20 11:18         ` Hin-Tak Leung
2021-04-20 22:32           ` Kuninori Morimoto
2021-04-20 14:19         ` Hin-Tak Leung
2021-04-20 16:04           ` Hin-Tak Leung
2021-04-22 14:01             ` Péter Ujfalusi
2021-04-23 11:22               ` Hin-Tak Leung
2021-04-23 22:30                 ` Hin-Tak Leung
     [not found]                   ` <2120463681.1712899.1619524438345@mail.yahoo.com>
2021-04-27 11:56                     ` Hin-Tak Leung

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=87h7k152du.wl-kuninori.morimoto.gx@renesas.com \
    --to=kuninori.morimoto.gx@renesas.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=htl10@users.sourceforge.net \
    /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.