From: Lars-Peter Clausen <lars@metafoo.de> To: kernel@martin.sperl.org, Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>, Stephen Warren <swarren@wwwdotorg.org>, Lee Jones <lee@kernel.org>, Eric Anholt <eric@anholt.net>, alsa-devel@alsa-project.org, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, Matthias Reichl <hias@horus.com>, Florian Meier <florian.meier@koalo.de> Subject: Re: [PATCH 3/3] ASoC: bcm2835: Register also as PCM device Date: Mon, 25 Apr 2016 15:54:18 +0200 [thread overview] Message-ID: <571E218A.7050508@metafoo.de> (raw) In-Reply-To: <1461591580-7565-3-git-send-email-kernel@martin.sperl.org> On 04/25/2016 03:39 PM, kernel@martin.sperl.org wrote: > From: Matthias Reichl <hias@horus.com> > > Register i2s also as pcm device. This is not really what this patch does. > > Code ported from bcm2708-i2s driver in Raspberry Pi tree. > > Signed-off-by: Florian Meier <florian.meier@koalo.de> > Signed-off-by: Matthias Reichl <hias@horus.com> > Signed-off-by: Martin Sperl <kernel@martin.sperl.org> > --- > sound/soc/bcm/bcm2835-i2s.c | 25 ++++++++++++++++++++++++- > 1 file changed, 24 insertions(+), 1 deletion(-) > > diff --git a/sound/soc/bcm/bcm2835-i2s.c b/sound/soc/bcm/bcm2835-i2s.c > index a0026e2..8e93295 100644 > --- a/sound/soc/bcm/bcm2835-i2s.c > +++ b/sound/soc/bcm/bcm2835-i2s.c > @@ -632,6 +632,27 @@ static const struct snd_soc_component_driver bcm2835_i2s_component = { > .name = "bcm2835-i2s-comp", > }; > > +static const struct snd_pcm_hardware bcm2835_pcm_hardware = { > + .info = SNDRV_PCM_INFO_INTERLEAVED | > + SNDRV_PCM_INFO_JOINT_DUPLEX | > + SNDRV_PCM_INFO_MMAP | > + SNDRV_PCM_INFO_MMAP_VALID, > + .formats = SNDRV_PCM_FMTBIT_S16_LE | > + SNDRV_PCM_FMTBIT_S24_LE | > + SNDRV_PCM_FMTBIT_S32_LE, > + .period_bytes_min = 32, > + .period_bytes_max = 64 * PAGE_SIZE, > + .periods_min = 2, > + .periods_max = 255, > + .buffer_bytes_max = 128 * PAGE_SIZE, > +}; > + > +static const struct snd_dmaengine_pcm_config bcm2835_dmaengine_pcm_config = { > + .prepare_slave_config = snd_dmaengine_pcm_prepare_slave_config, > + .pcm_hardware = &bcm2835_pcm_hardware, > + .prealloc_buffer_size = 256 * PAGE_SIZE, > +}; The generic dmaengine PCM driver auto-discovers these things, no need to provide them. The code is OK as it is. > + > static int bcm2835_i2s_probe(struct platform_device *pdev) > { > struct bcm2835_i2s_dev *dev; > @@ -704,7 +725,9 @@ static int bcm2835_i2s_probe(struct platform_device *pdev) > return ret; > } > > - ret = devm_snd_dmaengine_pcm_register(&pdev->dev, NULL, 0); > + ret = devm_snd_dmaengine_pcm_register( > + &pdev->dev, &bcm2835_dmaengine_pcm_config, > + SND_DMAENGINE_PCM_FLAG_COMPAT); > if (ret) { > dev_err(&pdev->dev, "Could not register PCM: %d\n", ret); > return ret; >
WARNING: multiple messages have this Message-ID (diff)
From: lars@metafoo.de (Lars-Peter Clausen) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 3/3] ASoC: bcm2835: Register also as PCM device Date: Mon, 25 Apr 2016 15:54:18 +0200 [thread overview] Message-ID: <571E218A.7050508@metafoo.de> (raw) In-Reply-To: <1461591580-7565-3-git-send-email-kernel@martin.sperl.org> On 04/25/2016 03:39 PM, kernel at martin.sperl.org wrote: > From: Matthias Reichl <hias@horus.com> > > Register i2s also as pcm device. This is not really what this patch does. > > Code ported from bcm2708-i2s driver in Raspberry Pi tree. > > Signed-off-by: Florian Meier <florian.meier@koalo.de> > Signed-off-by: Matthias Reichl <hias@horus.com> > Signed-off-by: Martin Sperl <kernel@martin.sperl.org> > --- > sound/soc/bcm/bcm2835-i2s.c | 25 ++++++++++++++++++++++++- > 1 file changed, 24 insertions(+), 1 deletion(-) > > diff --git a/sound/soc/bcm/bcm2835-i2s.c b/sound/soc/bcm/bcm2835-i2s.c > index a0026e2..8e93295 100644 > --- a/sound/soc/bcm/bcm2835-i2s.c > +++ b/sound/soc/bcm/bcm2835-i2s.c > @@ -632,6 +632,27 @@ static const struct snd_soc_component_driver bcm2835_i2s_component = { > .name = "bcm2835-i2s-comp", > }; > > +static const struct snd_pcm_hardware bcm2835_pcm_hardware = { > + .info = SNDRV_PCM_INFO_INTERLEAVED | > + SNDRV_PCM_INFO_JOINT_DUPLEX | > + SNDRV_PCM_INFO_MMAP | > + SNDRV_PCM_INFO_MMAP_VALID, > + .formats = SNDRV_PCM_FMTBIT_S16_LE | > + SNDRV_PCM_FMTBIT_S24_LE | > + SNDRV_PCM_FMTBIT_S32_LE, > + .period_bytes_min = 32, > + .period_bytes_max = 64 * PAGE_SIZE, > + .periods_min = 2, > + .periods_max = 255, > + .buffer_bytes_max = 128 * PAGE_SIZE, > +}; > + > +static const struct snd_dmaengine_pcm_config bcm2835_dmaengine_pcm_config = { > + .prepare_slave_config = snd_dmaengine_pcm_prepare_slave_config, > + .pcm_hardware = &bcm2835_pcm_hardware, > + .prealloc_buffer_size = 256 * PAGE_SIZE, > +}; The generic dmaengine PCM driver auto-discovers these things, no need to provide them. The code is OK as it is. > + > static int bcm2835_i2s_probe(struct platform_device *pdev) > { > struct bcm2835_i2s_dev *dev; > @@ -704,7 +725,9 @@ static int bcm2835_i2s_probe(struct platform_device *pdev) > return ret; > } > > - ret = devm_snd_dmaengine_pcm_register(&pdev->dev, NULL, 0); > + ret = devm_snd_dmaengine_pcm_register( > + &pdev->dev, &bcm2835_dmaengine_pcm_config, > + SND_DMAENGINE_PCM_FLAG_COMPAT); > if (ret) { > dev_err(&pdev->dev, "Could not register PCM: %d\n", ret); > return ret; >
next prev parent reply other threads:[~2016-04-25 13:54 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-04-25 13:39 [PATCH 1/3] ASoC: bcm2835: add 24bit support kernel 2016-04-25 13:39 ` kernel at martin.sperl.org 2016-04-25 13:39 ` [PATCH 2/3] ASoC: bcm2835: setup clock only if CPU is clock master kernel 2016-04-25 13:39 ` kernel at martin.sperl.org 2016-04-25 13:39 ` [PATCH 3/3] ASoC: bcm2835: Register also as PCM device kernel 2016-04-25 13:39 ` kernel at martin.sperl.org 2016-04-25 13:54 ` Lars-Peter Clausen [this message] 2016-04-25 13:54 ` Lars-Peter Clausen 2016-04-25 17:15 ` Matthias Reichl 2016-04-25 17:15 ` Matthias Reichl 2016-04-26 8:47 ` Lars-Peter Clausen 2016-04-26 8:47 ` [alsa-devel] " Lars-Peter Clausen 2016-04-26 13:09 ` Matthias Reichl 2016-04-26 13:09 ` [alsa-devel] " Matthias Reichl 2016-04-26 13:22 ` Lars-Peter Clausen 2016-04-26 13:22 ` [alsa-devel] " Lars-Peter Clausen 2016-04-26 15:18 ` Matthias Reichl 2016-04-26 15:18 ` [alsa-devel] " Matthias Reichl 2016-04-26 15:30 ` Lars-Peter Clausen 2016-04-26 15:30 ` [alsa-devel] " Lars-Peter Clausen 2016-04-26 18:05 ` Matthias Reichl 2016-04-26 18:05 ` [alsa-devel] " Matthias Reichl 2016-04-26 19:09 ` Lars-Peter Clausen 2016-04-26 19:09 ` [alsa-devel] " Lars-Peter Clausen
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=571E218A.7050508@metafoo.de \ --to=lars@metafoo.de \ --cc=alsa-devel@alsa-project.org \ --cc=broonie@kernel.org \ --cc=eric@anholt.net \ --cc=florian.meier@koalo.de \ --cc=hias@horus.com \ --cc=kernel@martin.sperl.org \ --cc=lee@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-rpi-kernel@lists.infradead.org \ --cc=perex@perex.cz \ --cc=swarren@wwwdotorg.org \ --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: 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.