mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mukunda, Vijendar" <Vijendar.Mukunda@amd.com>
To: Yu Zhao <yuzhao@google.com>, Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, aroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>
Cc: Daniel Kurtz <djkurtz@chromium.org>,
	"Agrawal, Akshu" <Akshu.Agrawal@amd.com>,
	"Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] ASoC: use dma_ops of parent device for acp_audio_dma
Date: Wed, 5 Dec 2018 06:45:59 +0000	[thread overview]
Message-ID: <cc34f15e-c8a3-da32-4a61-a6c34bed8281@amd.com> (raw)
In-Reply-To: <20181204224253.216075-2-yuzhao@google.com>



On 05/12/18 4:12 AM, Yu Zhao wrote:
> AMD platform device acp_audio_dma can only be created by parent PCI
> device driver (drivers/gpu/drm/amd/amdgpu/amdgpu_acp.c). Pass struct
> device of the parent to snd_pcm_lib_preallocate_pages() so
> dma_alloc_coherent() can use correct dma_ops. Otherwise, it will
> use default dma_ops which is nommu_dma_ops on x86_64 even when
> IOMMU is enabled and set to non passthrough mode.
> 
> Though platform device inherits some dma related fields during its
> creation in mfd_add_device(), we can't simply pass its struct device
> to snd_pcm_lib_preallocate_pages() because dma_ops is not among the
> inherited fields. Even it were, drivers/iommu/amd_iommu.c would
> ignore it because get_device_id() doesn't handle platform device.
> 
> This change shouldn't give us any trouble even struct device of the
> parent becomes null or represents some non PCI device in the future,
> because get_dma_ops() correctly handles null struct device or uses
> the default dma_ops if struct device doesn't have it set.
> 

This is really a good fix. We will also apply this fix for Raven platform.

Thanks,
Vijendar
> Signed-off-by: Yu Zhao <yuzhao@google.com>
> ---
>   sound/soc/amd/acp-pcm-dma.c | 7 +++++--
>   1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/sound/soc/amd/acp-pcm-dma.c b/sound/soc/amd/acp-pcm-dma.c
> index fd3db4c37882..f4011bebc7ec 100644
> --- a/sound/soc/amd/acp-pcm-dma.c
> +++ b/sound/soc/amd/acp-pcm-dma.c
> @@ -1146,18 +1146,21 @@ static int acp_dma_new(struct snd_soc_pcm_runtime *rtd)
>   	struct snd_soc_component *component = snd_soc_rtdcom_lookup(rtd,
>   								    DRV_NAME);
>   	struct audio_drv_data *adata = dev_get_drvdata(component->dev);
> +	struct device *parent = component->dev->parent;
>   
>   	switch (adata->asic_type) {
>   	case CHIP_STONEY:
>   		ret = snd_pcm_lib_preallocate_pages_for_all(rtd->pcm,
>   							    SNDRV_DMA_TYPE_DEV,
> -							    NULL, ST_MIN_BUFFER,
> +							    parent,
> +							    ST_MIN_BUFFER,
>   							    ST_MAX_BUFFER);
>   		break;
>   	default:
>   		ret = snd_pcm_lib_preallocate_pages_for_all(rtd->pcm,
>   							    SNDRV_DMA_TYPE_DEV,
> -							    NULL, MIN_BUFFER,
> +							    parent,
> +							    MIN_BUFFER,
>   							    MAX_BUFFER);
>   		break;
>   	}
> 

  reply	other threads:[~2018-12-05  6:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 22:42 [PATCH 1/2] ASoC: use DMA addr rather than CPU pa " Yu Zhao
2018-12-04 22:42 ` [PATCH 2/2] ASoC: use dma_ops of parent device " Yu Zhao
2018-12-05  6:45   ` Mukunda, Vijendar [this message]
2018-12-06 20:26   ` Applied "ASoC: use dma_ops of parent device for acp_audio_dma" to the asoc tree Mark Brown
2018-12-05  6:42 ` [PATCH 1/2] ASoC: use DMA addr rather than CPU pa for acp_audio_dma Mukunda, Vijendar
2018-12-06 20:26 ` Applied "ASoC: use DMA addr rather than CPU pa for acp_audio_dma" to the asoc tree 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=cc34f15e-c8a3-da32-4a61-a6c34bed8281@amd.com \
    --to=vijendar.mukunda@amd.com \
    --cc=Akshu.Agrawal@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=djkurtz@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=yuzhao@google.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®