public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Rob Clark <robdclark@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Zanoni, Paulo R" <paulo.r.zanoni@intel.com>,
	"Takashi Iwai (tiwai@suse.de)" <tiwai@suse.de>,
	"Lin, Mengdong" <mengdong.lin@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	"Barnes, Jesse" <jesse.barnes@intel.com>
Subject: Re: [Intel-gfx] Need your advice: Add a new communication inteface between HD-Audio and Gfx drivers for hotplug notification/ELD update
Date: Wed, 22 Jan 2014 16:20:55 +0100	[thread overview]
Message-ID: <20140122152055.GK9772@phenom.ffwll.local> (raw)
In-Reply-To: <CAF6AEGtfNzy_NZC64u2hhZMcWi=N2fFELKDYJ+Qyxh3TCyz9Hw@mail.gmail.com>

On Wed, Jan 22, 2014 at 10:04:14AM -0500, Rob Clark wrote:
> sorry to jump into this a bit late, so maybe this was covered already earlier..

It just started, I've quoted everything when cc'ing dri-devel. But good to
have examples outside of x86 (where things are mostly standardized by the
Eye of Redmond).

> For drm/msm the hdmi code needs something along these lines from audio:
> 
> int hdmi_audio_info_setup(struct platform_device *pdev, bool enabled,
>         uint32_t num_of_channels, uint32_t channel_allocation,
>         uint32_t level_shift, bool down_mix);
> void hdmi_audio_set_sample_rate(struct platform_device *pdev, int rate);
> 
> (former is mainly to setup avi audio infoframe, latter for clks)
> 
> in addition to hotplug and ELD stuff

Can you elaborate a bit on what you need for msm? On intel (and I think
the other x86 platforms are similar) we have separate buffers in the hw
for avi infoframes and audio infoframes, so the drm and alsa driver can
bash the right stuff into the hardware on their own. I'm mostly confused
since you say _AVI_ infoframe here, which is purely generated by the drm
side of the code here. Or at least that's been my understanding.

The clocks are also funny really, but I'm not sure whether this fits. I'd
have expected some DT-based generic clock source which the audio driver
just grabs as part of his multi-device beast (maybe using Russell's new
driver core code) and used directly. What's the reason that this has to go
through the drm driverr?

Cheers, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-01-22 15:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21 12:35 Need your advice: Add a new communication inteface between HD-Audio and Gfx drivers for hotplug notification/ELD update Lin, Mengdong
2014-01-21 13:10 ` Daniel Vetter
2014-01-21 13:11   ` Daniel Vetter
2014-01-22 12:48   ` Lin, Mengdong
2014-01-22 14:18     ` Daniel Vetter
2014-01-22 15:04       ` [Intel-gfx] " Rob Clark
2014-01-22 15:20         ` Daniel Vetter [this message]
2014-01-22 15:45           ` Rob Clark
2014-01-22 17:23             ` Takashi Iwai
2014-01-22 18:15               ` [Intel-gfx] " Rob Clark
2014-01-22 17:19       ` Takashi Iwai
2014-01-23  6:35         ` Lin, Mengdong
2014-01-23  7:57           ` Takashi Iwai
2014-01-23  8:13             ` Jaroslav Kysela
2014-01-23  8:26             ` Daniel Vetter
2014-01-24  8:23               ` Raymond Yau
2014-01-24 17:38                 ` [alsa-devel] " Alex Deucher
2014-02-18 13:58               ` Lin, Mengdong
2014-02-18 14:22                 ` Ville Syrjälä
2014-02-19  9:08                   ` Lin, Mengdong
2014-02-19 11:29                     ` Ville Syrjälä
2014-02-20  5:15                       ` Lin, Mengdong

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=20140122152055.GK9772@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=alsa-devel@alsa-project.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jesse.barnes@intel.com \
    --cc=mengdong.lin@intel.com \
    --cc=paulo.r.zanoni@intel.com \
    --cc=robdclark@gmail.com \
    --cc=tiwai@suse.de \
    /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