public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Christoph Hellwig <hch@lst.de>
Cc: thomas.lendacky@amd.com, tglx@linutronix.de, dwmw2@infradead.org,
	joro@8bytes.org, jdmason@kudzu.us, konrad.wilk@oracle.com,
	torvalds@linux-foundation.org, mulix@mulix.org,
	peterz@infradead.org, iommu@lists.linux-foundation.org,
	mingo@kernel.org, linux-kernel@vger.kernel.org,
	lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
	tiwai@suse.com
Subject: Re: x86/dma conversion for v4.17-rc1 breaks sound / sst-acpi (commit 6e4bf5867783)
Date: Fri, 6 Apr 2018 16:52:39 +0200	[thread overview]
Message-ID: <20180406145239.GA1845@light.dominikbrodowski.net> (raw)
In-Reply-To: <20180406141452.GA29724@lst.de>

On Fri, Apr 06, 2018 at 04:14:52PM +0200, Christoph Hellwig wrote:
> Hi Dominik,
> 
> can you try current Linus' master with the following hack applied and
> see if that works?
> 
> diff --git a/lib/swiotlb.c b/lib/swiotlb.c
> index 47aeb04c1997..32aacd0d56a8 100644
> --- a/lib/swiotlb.c
> +++ b/lib/swiotlb.c
> @@ -1087,6 +1087,6 @@ const struct dma_map_ops swiotlb_dma_ops = {
>  	.unmap_sg		= swiotlb_unmap_sg_attrs,
>  	.map_page		= swiotlb_map_page,
>  	.unmap_page		= swiotlb_unmap_page,
> -	.dma_supported		= swiotlb_dma_supported,
> +	.dma_supported		= dma_direct_supported,
>  };
>  #endif /* CONFIG_DMA_DIRECT_OPS */

Yes, it solves the issue.

Thanks,
	Dominik

      reply	other threads:[~2018-04-06 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 20:56 x86/dma conversion for v4.17-rc1 breaks sound / sst-acpi (commit 6e4bf5867783) Dominik Brodowski
2018-04-05 21:14 ` Christoph Hellwig
2018-04-06  1:14 ` Mark Brown
2018-04-06  4:35   ` Dominik Brodowski
2018-04-06 14:02   ` Pierre-Louis Bossart
2018-04-06 14:14 ` Christoph Hellwig
2018-04-06 14:52   ` Dominik Brodowski [this message]

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=20180406145239.GA1845@light.dominikbrodowski.net \
    --to=linux@dominikbrodowski.net \
    --cc=broonie@kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jdmason@kudzu.us \
    --cc=joro@8bytes.org \
    --cc=konrad.wilk@oracle.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mulix@mulix.org \
    --cc=perex@perex.cz \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=tiwai@suse.com \
    --cc=torvalds@linux-foundation.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