From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"tiwai@suse.de" <tiwai@suse.de>,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v4 4/4] drm/i915: set proper N/CTS in modeset
Date: Wed, 12 Aug 2015 17:18:31 +0300 [thread overview]
Message-ID: <87614ktwso.fsf@intel.com> (raw)
In-Reply-To: <20150812134310.GW17734@phenom.ffwll.local>
On Wed, 12 Aug 2015, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Aug 12, 2015 at 04:23:12PM +0300, Jani Nikula wrote:
>> On Wed, 12 Aug 2015, Daniel Vetter <daniel@ffwll.ch> wrote:
>> > It sounds like we actually need to ping the audio side _before_ we do the
>>
>> Do you mean "read _HSW_AUD_STR_DESC_*" by "ping the audio side" above?
>
> No, I mean call into snd-hda-intel before we do the modeset to ask it for
> what it actually wants to have set up. At least it feels a bit like only
> reacting to a modeset after it's done leads to confusion. Or maybe we just
> need to update the register values we want at compute_time instead of
> doing rwm fun ...
>
> Pure gut feeling comment, I didn't look into details ;-)
The audio driver calls us, not vice versa...
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-08-12 14:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 7:32 [PATCH v2 1/4] drm/i915: Add audio set_ncts callback libin.yang
2015-08-10 7:32 ` [PATCH v2 2/4] drm/i915: implement " libin.yang
2015-08-10 12:00 ` Jani Nikula
2015-08-11 2:49 ` Yang, Libin
2015-08-12 13:04 ` Daniel Vetter
2015-08-12 14:31 ` Yang, Libin
2015-08-10 12:16 ` Jani Nikula
2015-08-11 2:55 ` Yang, Libin
2015-08-12 13:06 ` Daniel Vetter
2015-08-12 14:36 ` Yang, Libin
2015-08-12 14:45 ` Jani Nikula
2015-08-12 14:48 ` Yang, Libin
2015-08-10 7:32 ` [PATCH v3 3/4] ALSA: hda - display audio call ncts callback libin.yang
2015-08-10 12:03 ` Jani Nikula
2015-08-11 2:51 ` Yang, Libin
2015-08-10 7:32 ` [PATCH v4 4/4] drm/i915: set proper N/CTS in modeset libin.yang
2015-08-10 8:04 ` Takashi Iwai
2015-08-10 8:30 ` Yang, Libin
2015-08-10 12:10 ` Jani Nikula
2015-08-11 3:10 ` Yang, Libin
2015-08-11 7:13 ` Jani Nikula
2015-08-11 7:46 ` Yang, Libin
2015-08-11 8:14 ` Jani Nikula
2015-08-12 2:41 ` Yang, Libin
2015-08-12 6:20 ` Jani Nikula
2015-08-12 7:28 ` Yang, Libin
2015-08-12 13:10 ` Daniel Vetter
2015-08-12 13:23 ` Jani Nikula
2015-08-12 13:43 ` Daniel Vetter
2015-08-12 14:18 ` Jani Nikula [this message]
2015-08-12 14:57 ` Yang, Libin
2015-08-10 11:46 ` [PATCH v2 1/4] drm/i915: Add audio set_ncts callback Jani Nikula
2015-08-11 2:40 ` Yang, Libin
2015-08-12 3:16 ` Yang, Libin
2015-08-12 6:14 ` [Intel-gfx] " Jani Nikula
2015-08-11 5:51 ` Yang, Libin
-- strict thread matches above, loose matches on Subject: below --
2015-08-18 6:35 [PATCH v4 1/4] drm/i915: Add audio sync_audio_rate callback libin.yang
2015-08-18 6:35 ` [PATCH v4 4/4] drm/i915: set proper N/CTS in modeset libin.yang
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=87614ktwso.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--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