From: Takashi Iwai <tiwai@suse.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Zanoni, Paulo R" <paulo.r.zanoni@intel.com>,
"Li, Jocelyn" <jocelyn.li@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
Wang Xingchao <xingchao.wang@linux.intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
"Hindman, Gavin" <gavin.hindman@intel.com>,
"Barnes, Jesse" <jesse.barnes@intel.com>,
"Lin, Mengdong" <mengdong.lin@intel.com>
Subject: Re: [alsa-devel] [PATCH] drm/i915: Add private api for power well usage -- alignment between graphic team and audio team
Date: Fri, 03 May 2013 16:31:34 +0200 [thread overview]
Message-ID: <s5hehdob0e1.wl%tiwai@suse.de> (raw)
In-Reply-To: <5183A73C.1030205@canonical.com>
At Fri, 03 May 2013 14:02:04 +0200,
David Henningsson wrote:
>
> On 05/03/2013 10:28 AM, Wang, Xingchao wrote:
> > Hi David,
> >
> > Thank you very much for your draft patch.
> > I have some more work on a new patchset, some ideas are from your patch.
>
> Thanks.
>
> > Here's a brief introduction of attached patchset:
> >
> > 1. a new bus type in /sound/had_bus.c, used to bind the single module and codec device
> > It looks like ac97_bus.c
>
> I don't understand why this is needed. It does not look like it's used
> from the gfx side either, or anything like that?
>
> > 2. add a new device node in "struct hda_codec", it's used to register for new bus type.
> >
> > 3. a new single module hdmi_i915, which compiled in only when DRM_I915 and CODEC_HDMI enabled.
> > It stores the private API for gfx part.
> > There's no support to probe haswell hdmi codec only yet. Power well will be used only for haswell display audio.
> >
> > 4. power well API implementation in gfx side.
> >
> > Please feel free to add your idea and I will help test your patch too.
>
> Ok. So the patch I wrote would (if it works) be combined with your patch
> 3, which implements the gfx side. The gfx side is not my area of expertise.
>
> The proposed way in my patch would be more elegant since it does not
> introduce any i915 related code in hda_codec* files.
>
> Still, Takashi is the boss here so he has the final say :-)
Indeed. If the reference to power well API is limited in a newly
split snd-hda-codec-hdmi-i915 driver, we don't have to create yet
another driver instance. The snd-hda-codec-hdmi-i915 can simply
depend on i915, by referring to a symbol exported from i915 driver.
If we now touch the whole PM sequence in both gfx and audio drivers
(i.e. it influences on the HD-audio controller code, hda_intel.c),
then we may need a different management. But I thought it's not yet
discussed here, right?
Takashi
next prev parent reply other threads:[~2013-05-03 14:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 6:58 [PATCH] drm/i915: Add private api for power well usage -- alignment between graphic team and audio team Li, Jocelyn
2013-04-26 7:24 ` Daniel Vetter
2013-04-26 7:53 ` Li, Jocelyn
2013-04-26 14:57 ` Daniel Vetter
2013-04-26 15:12 ` Takashi Iwai
2013-04-26 15:42 ` Daniel Vetter
2013-04-26 15:45 ` Takashi Iwai
2013-04-26 17:17 ` Daniel Vetter
2013-04-27 9:20 ` Wang, Xingchao
2013-04-27 11:35 ` Daniel Vetter
2013-04-29 15:02 ` Jesse Barnes
2013-04-30 10:29 ` David Henningsson
2013-04-30 14:38 ` Jesse Barnes
2013-05-02 3:17 ` Lin, Mengdong
2013-04-30 14:41 ` [alsa-devel] " Liam Girdwood
2013-05-02 14:49 ` David Henningsson
2013-05-03 8:28 ` [alsa-devel] " Wang, Xingchao
2013-05-03 12:02 ` David Henningsson
2013-05-03 14:31 ` Takashi Iwai [this message]
2013-05-02 7:11 ` Wang, Xingchao
2013-05-03 14:26 ` Takashi Iwai
2013-05-03 15:17 ` Wang, Xingchao
2013-04-27 8:54 ` Wang, Xingchao
2013-04-27 8:46 ` Wang, Xingchao
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=s5hehdob0e1.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=daniel.vetter@ffwll.ch \
--cc=david.henningsson@canonical.com \
--cc=gavin.hindman@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jesse.barnes@intel.com \
--cc=jocelyn.li@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=mengdong.lin@intel.com \
--cc=paulo.r.zanoni@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=xingchao.wang@linux.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