mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
	Dominik Brodowski <linux@dominikbrodowski.net>
Cc: hch@lst.de, 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,
	perex@perex.cz, tiwai@suse.com, Vinod Koul <vinod.koul@intel.com>
Subject: Re: x86/dma conversion for v4.17-rc1 breaks sound / sst-acpi (commit 6e4bf5867783)
Date: Fri, 6 Apr 2018 09:02:44 -0500	[thread overview]
Message-ID: <700ea637-3c58-5cbf-a7ac-fc242172acd9@linux.intel.com> (raw)
In-Reply-To: <20180406011418.GE12349@sirena.org.uk>



On 04/05/2018 08:14 PM, Mark Brown wrote:
> On Thu, Apr 05, 2018 at 10:56:57PM +0200, Dominik Brodowski wrote:
>> Christoph,
>>
>> unfortunately, commit 6e4bf5867783 breaks sound on my Dell XPS13, see the
>> dmesg diff between fec777c385b6 and 6e4bf5867783:
> Adding Vinod and Pierre from Intel in case they have any ideas here.
> Which model of XPS13 is this (2015?)?
No clear idea, but this patch is odd. It claims to replace a dma_ops 
structure by an equivalent one but the
callbacks for alloc/free are different.

-void *x86_swiotlb_alloc_coherent(struct device *hwdev, size_t size,
-                    dma_addr_t *dma_handle, gfp_t flags,
-                    unsigned long attrs)
-{
-    void *vaddr;
-
-    /*
-     * Don't print a warning when the first allocation attempt fails.
-     * swiotlb_alloc_coherent() will print a warning when the DMA
-     * memory allocation ultimately failed.
-     */
-    flags |= __GFP_NOWARN;
-
-    vaddr = dma_direct_alloc(hwdev, size, dma_handle, flags, attrs);
-    if (vaddr)
-        return vaddr;
-
-    return swiotlb_alloc_coherent(hwdev, size, dma_handle, flags);
-}
-
-void x86_swiotlb_free_coherent(struct device *dev, size_t size,
-                      void *vaddr, dma_addr_t dma_addr,
-                      unsigned long attrs)
-{
-    if (is_swiotlb_buffer(dma_to_phys(dev, dma_addr)))
-        swiotlb_free_coherent(dev, size, vaddr, dma_addr);
-    else
-        dma_direct_free(dev, size, vaddr, dma_addr, attrs);
-}

>
>> -sst-acpi INT3438:00: DesignWare DMA Controller, 8 channels
>> -haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2
>> -haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2)
>> -haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19
>> -broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok
>> -broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok
>> -broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok
>> -broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok
>> -broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok
>> -input: broadwell-rt286 Headset as /devices/pci0000:00/INT3438:00/broadwell-audio/sound/card1/input15
>> +broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
>> So it seems that sst-acpi is unhappy with this patch. Any ideas?
>> Thanks,
>> 	Dominik

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 20:56 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 [this message]
2018-04-06 14:14 ` Christoph Hellwig
2018-04-06 14:52   ` Dominik Brodowski

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=700ea637-3c58-5cbf-a7ac-fc242172acd9@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --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=linux@dominikbrodowski.net \
    --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 \
    --cc=vinod.koul@intel.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®