From: Romain Perier <romain.perier@collabora.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Archit Taneja <architt@codeaurora.org>,
David Airlie <airlied@linux.ie>, Heiko Stuebner <heiko@sntech.de>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] drm: dw_hdmi: Gate audio sampler clock from the enablement functions
Date: Fri, 10 Mar 2017 11:21:53 +0100 [thread overview]
Message-ID: <7888eb1f-2781-d4ed-6f26-cb76e1ead4d2@collabora.com> (raw)
In-Reply-To: <20170310094613.GQ21222@n2100.armlinux.org.uk>
Hello,
Le 10/03/2017 à 10:46, Russell King - ARM Linux a écrit :
> On Fri, Mar 10, 2017 at 10:35:09AM +0100, Romain Perier wrote:
>> Currently, the audio sampler clock is enabled from dw_hdmi_setup() at
>> step E. and is kept enabled for later use. This clock should be enabled
>> and disabled along with the actual audio stream and not always on (that
>> is bad for PM). Futhermore, this might cause sound glitches with some
>> HDMI devices, as the CTS+N is forced to zero when the stream is disabled
>> while the audio clock is still running.
>>
>> This commit adds a parameter to hdmi_audio_enable_clk() that controls
>> when the audio sample clock must be enabled or disabled. Then, it moves
>> the call to this function into dw_hdmi_audio_enable() and
>> dw_hdmi_audio_disable().
> How does this interact with the workaround given in my commit introducing
> these functions? (Commit b90120a96608).
>
> Setting N=0 is a work-around for iMX6, and we need the audio FIFO to be
> loaded with data prior to setting N non-zero. If disabling the audio
> clock prevents the audio FIFO being loaded, your patch will break iMX6.
>
Mhhh, the fact is I have no IMX6 devices here (only Rockchip). So
I only tested on Rockchip devices. An approach might be to introduce an
option for handling this errata, because that's platform specific and
other platforms (like Rockchip) are in conflict with this.
Romain
next prev parent reply other threads:[~2017-03-10 10:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 9:35 Romain Perier
2017-03-10 9:46 ` Russell King - ARM Linux
2017-03-10 10:21 ` Romain Perier [this message]
2017-03-10 10:27 ` Russell King - ARM Linux
2017-03-10 10:58 ` Romain Perier
2017-03-10 11:15 ` Russell King - ARM Linux
2017-03-10 12:58 ` Romain Perier
2017-03-13 9:27 ` Neil Armstrong
2017-03-13 9:36 ` Russell King - ARM Linux
2017-03-13 12:55 ` Jose Abreu
2017-03-13 13:10 ` Russell King - ARM Linux
2017-03-13 18:49 ` Jose Abreu
2017-03-14 7:53 ` Romain Perier
2017-03-14 8:13 ` Neil Armstrong
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=7888eb1f-2781-d4ed-6f26-cb76e1ead4d2@collabora.com \
--to=romain.perier@collabora.com \
--cc=airlied@linux.ie \
--cc=architt@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@armlinux.org.uk \
/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®