From: Florian Fainelli <f.fainelli@gmail.com>
To: Kevin Li <kevin-ke.li@broadcom.com>, Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Scott Branden <sbranden@broadcom.com>,
Liam Girdwood <lgirdwood@gmail.com>, Ray Jui <rjui@broadcom.com>,
Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
bcm-kernel-feedback-list@broadcom.com,
Stephen Boyd <swboyd@chromium.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: brcm: Add DSL/PON SoC audio driver
Date: Fri, 6 Mar 2020 15:02:34 -0800 [thread overview]
Message-ID: <26805c24-7339-d9c9-269c-d6c027a891d1@gmail.com> (raw)
In-Reply-To: <31b665e609f3cfee935f4489a073af21@mail.gmail.com>
On 3/6/20 2:50 PM, Kevin Li wrote:
> Hi Florian,
>
> It is called from bcm63xx-i2s-whistler.c.
> Maybe the name "_probe" function confused. It was 2 platform drivers, I
> combined them together now.
>
> Let me know if this answers your question, and what to do to address your
> question.
Ok, that makes sense now, sorry for not spotting it earlier.
PS: no top posting please ;)
>
> Regards!
> Kevin
>
> -----Original Message-----
> From: Florian Fainelli [mailto:f.fainelli@gmail.com]
> Sent: Friday, March 06, 2020 2:34 PM
> To: Kevin Li <kevin-ke.li@broadcom.com>; Mark Brown <broonie@kernel.org>
> Cc: alsa-devel@alsa-project.org; linux-kernel@vger.kernel.org; Kuninori
> Morimoto <kuninori.morimoto.gx@renesas.com>; Scott Branden
> <sbranden@broadcom.com>; Liam Girdwood <lgirdwood@gmail.com>; Ray Jui
> <rjui@broadcom.com>; Takashi Iwai <tiwai@suse.com>; Jaroslav Kysela
> <perex@perex.cz>; bcm-kernel-feedback-list@broadcom.com; Stephen Boyd
> <swboyd@chromium.org>; linux-arm-kernel@lists.infradead.org
> Subject: Re: [PATCH] ASoC: brcm: Add DSL/PON SoC audio driver
>
> On 3/6/20 2:27 PM, Kevin Li wrote:
>> This patch adds Broadcom DSL/PON SoC audio driver with Whistler I2S
>> block. The SoC supported by this patch are BCM63158B0,BCM63178 and
>> BCM47622/6755.
>>
>> Signed-off-by: Kevin Li <kevin-ke.li@broadcom.com>
>> ---
>
> [snip]
>
>> +int bcm63xx_soc_platform_probe(struct platform_device *pdev,
>> + struct bcm_i2s_priv *i2s_priv) {
>> + int ret;
>> +
>> + i2s_priv->r_irq = platform_get_resource(pdev, IORESOURCE_IRQ, 0);
>> + if (!i2s_priv->r_irq) {
>> + dev_err(&pdev->dev, "Unable to get register irq resource.\n");
>> + return -ENODEV;
>> + }
>> +
>> + ret = devm_request_irq(&pdev->dev, i2s_priv->r_irq->start, i2s_dma_isr,
>> + i2s_priv->r_irq->flags, "i2s_dma", (void *)i2s_priv);
>> + if (ret) {
>> + dev_err(&pdev->dev,
>> + "i2s_init: failed to request interrupt.ret=%d\n", ret);
>> + return ret;
>> + }
>> +
>> + return devm_snd_soc_register_component(&pdev->dev,
>> + &bcm63xx_soc_platform, NULL, 0); }
>> +
>> +int bcm63xx_soc_platform_remove(struct platform_device *pdev) {
>> + return 0;
>> +}
>
> How does one probe this module if the bcm63xx_soc_platform_probe() functions
> are not called from anywhere and/or hooked up to the module entry/exit
> points?
>
> Are you not missing a platform_driver entry which matches the compatible
> string you defined?
> --
> Florian
>
--
Florian
next prev parent reply other threads:[~2020-03-06 23:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 22:27 Kevin Li
2020-03-06 22:27 ` [PATCH] ASoC: brcm: DSL/PON SoC device tree bindings of " Kevin Li
2020-03-06 22:33 ` [PATCH] ASoC: brcm: Add DSL/PON SoC " Florian Fainelli
2020-03-06 22:50 ` Kevin Li
2020-03-06 23:02 ` Florian Fainelli [this message]
2020-03-09 12:33 ` Mark Brown
2020-03-09 17:33 ` Kevin Li
2020-03-09 17:52 ` Mark Brown
2020-03-09 18:14 ` Kevin Li
2020-03-09 19:18 ` Mark Brown
2020-03-10 15:49 ` Kevin Li
2020-03-10 16:28 ` 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=26805c24-7339-d9c9-269c-d6c027a891d1@gmail.com \
--to=f.fainelli@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=kevin-ke.li@broadcom.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=swboyd@chromium.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: 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
all inboxes | Powered by JetHome®