On Thu, Dec 15, 2016 at 12:14:30PM +0100, Takashi Iwai wrote:
> The interaction between i915 and audio is simple, yes, it just exposes
> a few things, mmio ptr, irq, etc. But still I don't understand why
> multiple layers of indirect accesses are needed *inside* lpe audio
> driver itself. For ex
On Thu, 15 Dec 2016 11:55:23 +0100,
Anand, Jerome wrote:
>
>
>
> > -Original Message-
> > From: Takashi Iwai [mailto:ti...@suse.de]
> > Sent: Wednesday, December 14, 2016 6:16 PM
> > To: Anand, Jerome
> > Cc: intel-gfx@lists.freedesktop.org; alsa-de...@alsa-project.org;
> > ville.syrj..
> -Original Message-
> From: Takashi Iwai [mailto:ti...@suse.de]
> Sent: Wednesday, December 14, 2016 6:16 PM
> To: Anand, Jerome
> Cc: intel-gfx@lists.freedesktop.org; alsa-de...@alsa-project.org;
> ville.syrj...@linux.intel.com; broo...@kernel.org; pierre-
> louis.boss...@linux.intel.c
On Mon, 12 Dec 2016 19:10:39 +0100,
Jerome Anand wrote:
>
> On Baytrail and Cherrytrail, HDaudio may be fused out or disabled
> by the BIOS. This driver enables an alternate path to the i915
> display registers and DMA.
>
> Although there is no hardware path between i915 display and LPE/SST
> aud
On Baytrail and Cherrytrail, HDaudio may be fused out or disabled
by the BIOS. This driver enables an alternate path to the i915
display registers and DMA.
Although there is no hardware path between i915 display and LPE/SST
audio clusters, this HDMI capability is referred to in the documentation
a
