From: Matt Flax <flatmax@flatmax.org> To: Mark Brown <broonie@kernel.org> Cc: alsa-devel@alsa-project.org, Stephen Warren <swarren@wwwdotorg.org>, Lee Jones <lee@kernel.org>, phil@raspberrypi.org, Eric Anholt <eric@anholt.net>, Florian Meier <florian.meier@koalo.de>, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] ASoC: bcm2835: Add 8 channel (multitrack) capability Date: Thu, 9 Feb 2017 07:41:49 +1100 [thread overview] Message-ID: <21a531f2-4efb-fd92-b709-90f97ec73a92@flatmax.org> (raw) In-Reply-To: <20170208182835.6hpwcxiae2lh56d5@sirena.org.uk> On 09/02/17 05:28, Mark Brown wrote: > On Tue, Feb 07, 2017 at 10:09:36AM +1100, Matt Flax wrote: > >> case SND_SOC_DAIFMT_CBS_CFM: >> clk_set_rate(dev->clk, sampling_rate * bclk_ratio); >> + case SND_SOC_DAIFMT_CBM_CFS: > Is this fall through deliberate? > >> + /* Default data delay to 1 bit. >> + In I2S mode, we must have 2 channels */ >> switch (dev->fmt & SND_SOC_DAIFMT_FORMAT_MASK) { >> case SND_SOC_DAIFMT_I2S: >> + if (params_channels(params) != 2) >> + return -EINVAL; >> + case SND_SOC_DAIFMT_DSP_A: >> + case SND_SOC_DAIFMT_DSP_B: >> data_delay = 1; >> break; >> default: > Same here. This is also buggy in that it treats DSP A and DSP B > identically, they are different so the configuration must be incorrect > for one of them. I suspect this is configuring for DSP A. I can remove DSP_B. In actual fact this isn't the real problem. > You should also really have a setup() function that imposes a channel > constraint when in I2S mode, wm8988 is one example here. > I had a look at wm8988.c and couldn't see this channel constraint linking to I2S. Can you point me to it ? thanks Matt
WARNING: multiple messages have this Message-ID (diff)
From: flatmax@flatmax.org (Matt Flax) To: linux-arm-kernel@lists.infradead.org Subject: [alsa-devel] [PATCH] ASoC: bcm2835: Add 8 channel (multitrack) capability Date: Thu, 9 Feb 2017 07:41:49 +1100 [thread overview] Message-ID: <21a531f2-4efb-fd92-b709-90f97ec73a92@flatmax.org> (raw) In-Reply-To: <20170208182835.6hpwcxiae2lh56d5@sirena.org.uk> On 09/02/17 05:28, Mark Brown wrote: > On Tue, Feb 07, 2017 at 10:09:36AM +1100, Matt Flax wrote: > >> case SND_SOC_DAIFMT_CBS_CFM: >> clk_set_rate(dev->clk, sampling_rate * bclk_ratio); >> + case SND_SOC_DAIFMT_CBM_CFS: > Is this fall through deliberate? > >> + /* Default data delay to 1 bit. >> + In I2S mode, we must have 2 channels */ >> switch (dev->fmt & SND_SOC_DAIFMT_FORMAT_MASK) { >> case SND_SOC_DAIFMT_I2S: >> + if (params_channels(params) != 2) >> + return -EINVAL; >> + case SND_SOC_DAIFMT_DSP_A: >> + case SND_SOC_DAIFMT_DSP_B: >> data_delay = 1; >> break; >> default: > Same here. This is also buggy in that it treats DSP A and DSP B > identically, they are different so the configuration must be incorrect > for one of them. I suspect this is configuring for DSP A. I can remove DSP_B. In actual fact this isn't the real problem. > You should also really have a setup() function that imposes a channel > constraint when in I2S mode, wm8988 is one example here. > I had a look at wm8988.c and couldn't see this channel constraint linking to I2S. Can you point me to it ? thanks Matt
next prev parent reply other threads:[~2017-02-08 20:41 UTC|newest] Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-02-06 23:09 [PATCH] ASoC: bcm2835: Add 8 channel (multitrack) capability Matt Flax 2017-02-06 23:09 ` Matt Flax 2017-02-08 18:28 ` Mark Brown 2017-02-08 18:28 ` Mark Brown 2017-02-08 18:54 ` Matthias Reichl 2017-02-08 18:54 ` Matthias Reichl 2017-02-08 21:13 ` Matt Flax 2017-02-08 21:13 ` [alsa-devel] " Matt Flax 2017-02-08 22:48 ` Matt Flax 2017-02-08 22:48 ` [alsa-devel] " Matt Flax 2017-02-09 9:29 ` Matthias Reichl 2017-02-09 9:29 ` [alsa-devel] " Matthias Reichl 2017-02-08 20:41 ` Matt Flax [this message] 2017-02-08 20:41 ` Matt Flax 2017-02-08 21:14 ` Matt Flax 2017-02-08 21:14 ` [alsa-devel] " Matt Flax 2017-02-12 23:27 ` [PATCH v2] " Matt Flax 2017-02-12 23:27 ` Matt Flax 2017-02-13 20:51 ` Eric Anholt 2017-02-13 20:51 ` Eric Anholt 2017-02-14 9:32 ` Charles Keepax 2017-02-14 9:32 ` [alsa-devel] " Charles Keepax 2017-02-14 20:36 ` Matt Flax 2017-02-14 20:36 ` [alsa-devel] " Matt Flax 2017-02-14 20:52 ` [PATCH v3] " Matt Flax 2017-02-14 20:52 ` Matt Flax 2017-02-14 21:00 ` Matt Flax 2017-02-14 21:00 ` [alsa-devel] " Matt Flax 2017-02-14 21:04 ` [PATCH v4] " Matt Flax 2017-02-14 21:04 ` Matt Flax 2017-02-15 8:30 ` Arnaud Mouiche 2017-02-22 5:15 ` Matt Flax 2017-02-15 9:24 ` Charles Keepax 2017-02-15 9:24 ` Charles Keepax 2017-02-15 12:37 ` Florian Kauer 2017-02-15 12:37 ` Florian Kauer 2017-02-15 19:26 ` Eric Anholt 2017-02-15 19:26 ` Eric Anholt 2017-02-22 5:18 ` [PATCH v5] " Matt Flax 2017-02-22 5:18 ` Matt Flax 2017-02-22 5:20 ` Matt Flax 2017-02-22 5:20 ` Matt Flax 2017-02-22 5:22 ` [PATCH v6] " Matt Flax 2017-02-22 5:22 ` Matt Flax 2017-02-22 6:49 ` [alsa-devel] " kbuild test robot 2017-02-22 6:49 ` kbuild test robot 2017-02-22 18:28 ` Mark Brown 2017-02-22 18:28 ` Mark Brown 2017-02-22 22:45 ` Matt Flax 2017-02-22 22:45 ` [alsa-devel] " Matt Flax 2017-02-23 17:28 ` Mark Brown 2017-02-23 17:28 ` [alsa-devel] " Mark Brown 2017-02-22 6:56 ` [PATCH v8] " Matt Flax 2017-02-22 6:56 ` Matt Flax 2017-02-24 12:18 ` Matthias Reichl 2017-02-24 12:18 ` [alsa-devel] " Matthias Reichl 2017-02-24 13:50 ` Matt Flax 2017-02-24 13:50 ` [alsa-devel] " Matt Flax 2017-02-24 20:25 ` Matthias Reichl 2017-02-24 20:25 ` [alsa-devel] " Matthias Reichl 2017-02-24 21:30 ` Matt Flax 2017-02-24 21:30 ` [alsa-devel] " Matt Flax 2017-02-24 23:02 ` Matthias Reichl 2017-02-24 23:02 ` [alsa-devel] " Matthias Reichl 2017-02-25 0:08 ` Emmanuel Fusté 2017-02-25 0:08 ` [alsa-devel] " Emmanuel Fusté 2017-02-25 2:38 ` Matt Flax 2017-02-25 2:38 ` [alsa-devel] " Matt Flax 2017-02-25 5:04 ` Matt Flax 2017-02-25 5:04 ` [alsa-devel] " Matt Flax 2017-02-26 20:28 ` Matt Flax 2017-02-26 20:28 ` [alsa-devel] " Matt Flax
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=21a531f2-4efb-fd92-b709-90f97ec73a92@flatmax.org \ --to=flatmax@flatmax.org \ --cc=alsa-devel@alsa-project.org \ --cc=broonie@kernel.org \ --cc=eric@anholt.net \ --cc=florian.meier@koalo.de \ --cc=lee@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-rpi-kernel@lists.infradead.org \ --cc=phil@raspberrypi.org \ --cc=swarren@wwwdotorg.org \ /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: linkBe 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.