From: Lars-Peter Clausen <lars@metafoo.de>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linus.walleij@linaro.org,
broonie@kernel.org, alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] [PATCH 3/3] ASoC: ux500: Dynamically fill DAI driver data on probe
Date: Mon, 02 Dec 2013 19:10:55 +0100 [thread overview]
Message-ID: <529CCD2F.3060206@metafoo.de> (raw)
In-Reply-To: <1386007222-10081-3-git-send-email-lee.jones@linaro.org>
On 12/02/2013 07:00 PM, Lee Jones wrote:
[...]
> +void ux500_msp_populate_dai_drv(struct snd_soc_dai_driver *ux500_msp_dai_drv)
> +{
> + ux500_msp_dai_drv->probe = ux500_msp_dai_probe;
> + ux500_msp_dai_drv->suspend = NULL;
> + ux500_msp_dai_drv->resume = NULL;
> + ux500_msp_dai_drv->playback.channels_min = UX500_MSP_MIN_CHANNELS;
> + ux500_msp_dai_drv->playback.channels_max = UX500_MSP_MAX_CHANNELS;
> + ux500_msp_dai_drv->playback.rates = UX500_I2S_RATES;
> + ux500_msp_dai_drv->playback.formats = UX500_I2S_FORMATS;
> + ux500_msp_dai_drv->capture.channels_min = UX500_MSP_MIN_CHANNELS;
> + ux500_msp_dai_drv->capture.channels_max = UX500_MSP_MAX_CHANNELS;
> + ux500_msp_dai_drv->capture.rates = UX500_I2S_RATES;
> + ux500_msp_dai_drv->capture.formats = UX500_I2S_FORMATS;
> + ux500_msp_dai_drv->ops = ux500_msp_dai_ops;
> };
You can just use the same static driver for all devices. No need to
dynamically allocate it.
>
> static const struct snd_soc_component_driver ux500_msp_component = {
> @@ -809,6 +742,7 @@ static const struct snd_soc_component_driver ux500_msp_component = {
> static int ux500_msp_drv_probe(struct platform_device *pdev)
> {
> struct ux500_msp_i2s_drvdata *drvdata;
> + struct snd_soc_dai_driver *ux500_msp_dai_drv;
> int ret = 0;
>
> dev_dbg(&pdev->dev, "%s: Enter (pdev->name = %s).\n", __func__,
> @@ -863,8 +797,18 @@ static int ux500_msp_drv_probe(struct platform_device *pdev)
> }
> dev_set_drvdata(&pdev->dev, drvdata);
>
> + ux500_msp_dai_drv = devm_kzalloc(&pdev->dev,
> + sizeof(*ux500_msp_dai_drv),
> + GFP_KERNEL);
> + if (!ux500_msp_dai_drv) {
> + ret = -ENOMEM;
> + goto err_init_msp;
> + }
> +
> + ux500_msp_populate_dai_drv(ux500_msp_dai_drv);
> +
> ret = snd_soc_register_component(&pdev->dev, &ux500_msp_component,
> - &ux500_msp_dai_drv[drvdata->msp->id], 1);
> + ux500_msp_dai_drv, 1);
> if (ret < 0) {
> dev_err(&pdev->dev, "Error: %s: Failed to register MSP%d!\n",
> __func__, drvdata->msp->id);
>
next prev parent reply other threads:[~2013-12-02 18:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 18:00 [PATCH 1/3] ASoC: ux500_pcm: Stop pretending that we support varying address widths Lee Jones
2013-12-02 18:00 ` [PATCH 2/3] ASoC: ux500_pcm: Differentiate between pdata and DT initialisation Lee Jones
2013-12-02 18:13 ` [alsa-devel] " Lars-Peter Clausen
2013-12-03 8:36 ` Lee Jones
2013-12-03 8:56 ` Lars-Peter Clausen
2013-12-03 10:03 ` Lee Jones
2013-12-02 18:00 ` [PATCH 3/3] ASoC: ux500: Dynamically fill DAI driver data on probe Lee Jones
2013-12-02 18:10 ` Lars-Peter Clausen [this message]
2013-12-03 8:40 ` [alsa-devel] " Lee Jones
2013-12-03 8:57 ` Lars-Peter Clausen
2013-12-03 9:59 ` Lee Jones
2013-12-02 18:34 ` [alsa-devel] [PATCH 1/3] ASoC: ux500_pcm: Stop pretending that we support varying address widths Lars-Peter Clausen
2013-12-03 8:31 ` Lee Jones
2013-12-02 19:09 ` Mark Brown
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=529CCD2F.3060206@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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: 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).