From: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
broonie@kernel.org, alsa-devel@alsa-project.org
Cc: Sunil-kumar.Dommati@amd.com,
open list <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Alexander.Deucher@amd.com, krisman@collabora.com
Subject: Re: [PATCH V3 06/12] ASoC: amd: irq handler changes for ACP5x PCM dma driver
Date: Tue, 20 Jul 2021 00:38:40 +0530 [thread overview]
Message-ID: <0785f67b-e927-6eb4-9ab0-cff284768fe5@amd.com> (raw)
In-Reply-To: <a9566929-0fa0-f8f0-58ce-99a1e111e6a2@linux.intel.com>
On 7/19/21 11:41 PM, Pierre-Louis Bossart wrote:
>
>> +static irqreturn_t i2s_irq_handler(int irq, void *dev_id)
>> +{
>> + struct i2s_dev_data *vg_i2s_data;
>> + u16 irq_flag;
>> + u32 val;
>> +
>> + vg_i2s_data = dev_id;
>> + if (!vg_i2s_data)
>> + return IRQ_NONE;
>> +
>> + irq_flag = 0;
>> + val = acp_readl(vg_i2s_data->acp5x_base + ACP_EXTERNAL_INTR_STAT);
>> + if ((val & BIT(HS_TX_THRESHOLD)) && vg_i2s_data->play_stream) {
>> + acp_writel(BIT(HS_TX_THRESHOLD), vg_i2s_data->acp5x_base +
>> + ACP_EXTERNAL_INTR_STAT);
>> + snd_pcm_period_elapsed(vg_i2s_data->play_stream);
>> + irq_flag = 1;
>> + }
>> + if ((val & BIT(I2S_TX_THRESHOLD)) &&
>> + vg_i2s_data->i2ssp_play_stream) {
>
> use single line?
will fix it.
>
>> + acp_writel(BIT(I2S_TX_THRESHOLD),
>> + vg_i2s_data->acp5x_base + ACP_EXTERNAL_INTR_STAT);
>> + snd_pcm_period_elapsed(vg_i2s_data->i2ssp_play_stream);
>> + irq_flag = 1;
>> + }
>> +
>> + if ((val & BIT(HS_RX_THRESHOLD)) && vg_i2s_data->capture_stream) {
>> + acp_writel(BIT(HS_RX_THRESHOLD), vg_i2s_data->acp5x_base +
>> + ACP_EXTERNAL_INTR_STAT);
>> + snd_pcm_period_elapsed(vg_i2s_data->capture_stream);
>> + irq_flag = 1;
>> + }
>> + if ((val & BIT(I2S_RX_THRESHOLD)) &&
>> + vg_i2s_data->i2ssp_capture_stream) {
>
> use single line?
Will fix it.
>
>> + acp_writel(BIT(I2S_RX_THRESHOLD),
>> + vg_i2s_data->acp5x_base + ACP_EXTERNAL_INTR_STAT);
>> + snd_pcm_period_elapsed(vg_i2s_data->i2ssp_capture_stream);
>> + irq_flag = 1;
>> + }
>> +
>> + if (irq_flag)
>> + return IRQ_HANDLED;
>> + else
>> + return IRQ_NONE;
>> +}
>> +
>> static int acp5x_audio_probe(struct platform_device *pdev)
>> {
>> struct resource *res;
>> struct i2s_dev_data *adata;
>> + unsigned int irqflags;
>> int status;
>>
>> if (!pdev->dev.platform_data) {
>> @@ -47,6 +94,14 @@ static int acp5x_audio_probe(struct platform_device *pdev)
>> resource_size(res));
>> if (!adata->acp5x_base)
>> return -ENOMEM;
>> +
>> + res = platform_get_resource(pdev, IORESOURCE_IRQ, 0);
>> + if (!res) {
>> + dev_err(&pdev->dev, "IORESOURCE_IRQ FAILED\n");
>> + return -ENODEV;
>> + }
>> +
>> + adata->i2s_irq = res->start;
>> dev_set_drvdata(&pdev->dev, adata);
>> status = devm_snd_soc_register_component(&pdev->dev,
>> &acp5x_i2s_component,
>> @@ -55,6 +110,12 @@ static int acp5x_audio_probe(struct platform_device *pdev)
>> dev_err(&pdev->dev, "Fail to register acp i2s component\n");
>> return -ENODEV;
>> }
>> + status = devm_request_irq(&pdev->dev, adata->i2s_irq, i2s_irq_handler,
>> + irqflags, "ACP5x_I2S_IRQ", adata);
>> + if (status) {
>> + dev_err(&pdev->dev, "ACP5x I2S IRQ request failed\n");
>> + return -ENODEV;
>> + }
>
> return status?
>
Will fix it and post the new version.
>> return 0;
>> }
>>
>> diff --git a/sound/soc/amd/vangogh/acp5x.h b/sound/soc/amd/vangogh/acp5x.h
>> index d2853738eb17..18df2b5a4283 100644
>> --- a/sound/soc/amd/vangogh/acp5x.h
>> +++ b/sound/soc/amd/vangogh/acp5x.h
>> @@ -31,9 +31,18 @@
>> #define ACP5x_HS_TDM_REG_END 0x1242824
>> #define I2S_MODE 0x00
>> #define ACP5x_I2S_MODE 0x00
>> +#define I2S_RX_THRESHOLD 27
>> +#define I2S_TX_THRESHOLD 28
>> +#define HS_TX_THRESHOLD 24
>> +#define HS_RX_THRESHOLD 23
>>
>> struct i2s_dev_data {
>> + unsigned int i2s_irq;
>> void __iomem *acp5x_base;
>> + struct snd_pcm_substream *play_stream;
>> + struct snd_pcm_substream *capture_stream;
>> + struct snd_pcm_substream *i2ssp_play_stream;
>> + struct snd_pcm_substream *i2ssp_capture_stream;
>> };
>>
>> /* common header file uses exact offset rather than relative
>>
next prev parent reply other threads:[~2021-07-19 19:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210719165140.16143-1-vijendar.mukunda@amd.com>
2021-07-19 16:51 ` [PATCH V3 01/12] ASoC: amd: add Vangogh ACP5x IP register header Vijendar Mukunda
2021-07-19 16:51 ` [PATCH V3 02/12] ASoC: amd: add Vangogh ACP PCI driver Vijendar Mukunda
2021-07-19 16:51 ` [PATCH V3 03/12] ASoc: amd: add acp5x init/de-init functions Vijendar Mukunda
2021-07-19 16:51 ` [PATCH V3 04/12] ASoC: amd: create acp5x platform devices Vijendar Mukunda
2021-07-19 18:07 ` Pierre-Louis Bossart
2021-07-19 19:17 ` Mukunda,Vijendar
2021-07-19 16:51 ` [PATCH V3 05/12] ASoC: amd: add ACP5x PCM platform driver Vijendar Mukunda
2021-07-19 18:09 ` Pierre-Louis Bossart
2021-07-19 19:05 ` Mukunda,Vijendar
2021-07-19 16:51 ` [PATCH V3 06/12] ASoC: amd: irq handler changes for ACP5x PCM dma driver Vijendar Mukunda
2021-07-19 18:11 ` Pierre-Louis Bossart
2021-07-19 19:08 ` Mukunda,Vijendar [this message]
2021-07-19 16:51 ` [PATCH V3 07/12] ASoC: amd: add ACP5x pcm dma driver ops Vijendar Mukunda
2021-07-19 16:51 ` [PATCH V3 08/12] ASoC: amd: add vangogh i2s controller driver Vijendar Mukunda
2021-07-19 16:51 ` [PATCH V3 09/12] ASoC: amd: add vangogh i2s dai driver ops Vijendar Mukunda
2021-07-19 16:51 ` [PATCH V3 10/12] ASoC: amd: add vangogh pci driver pm ops Vijendar Mukunda
2021-07-19 16:51 ` [PATCH V3 11/12] ASoC: amd: add vangogh i2s dma " Vijendar Mukunda
2021-07-19 18:13 ` Pierre-Louis Bossart
2021-07-19 19:19 ` Mukunda,Vijendar
2021-07-19 16:51 ` [PATCH V3 12/12] ASoC: amd: enable vangogh acp5x driver build Vijendar Mukunda
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=0785f67b-e927-6eb4-9ab0-cff284768fe5@amd.com \
--to=vijendar.mukunda@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=krisman@collabora.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--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®