From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: Romain Perier <romain.perier@collabora.com>,
Jose Abreu <Jose.Abreu@synopsys.com>,
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: Mon, 13 Mar 2017 09:36:30 +0000 [thread overview]
Message-ID: <20170313093630.GE21222@n2100.armlinux.org.uk> (raw)
In-Reply-To: <25ad96a7-d907-2bcb-3a96-15a2956e7652@baylibre.com>
On Mon, Mar 13, 2017 at 10:27:08AM +0100, Neil Armstrong wrote:
> On 03/10/2017 10:35 AM, 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().
> >
> > Signed-off-by: Romain Perier <romain.perier@collabora.com>
> > ---
> > drivers/gpu/drm/bridge/dw-hdmi.c | 15 +++++++++------
> > 1 file changed, 9 insertions(+), 6 deletions(-)
> >
>
> Hi Romain, Russell, Jose,
>
> This is a little out of scope, but I was wondering why the CTS calculation
> was not left in AUTO mode in the dw-hdmi driver ?
There is no indication in the iMX6 manuals that the iMX6 supports
automatic CTS calculation. Bits 7:4 of the AUD_CTS3 register are
marked as "reserved".
We're reliant on the information in the iMX6 manuals as we don't have
access to Synopsis' databooks for these parts (I understand you have
to be a customer to have access to that.)
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2017-03-13 9:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 9:35 [PATCH] drm: dw_hdmi: Gate audio sampler clock from the enablement functions Romain Perier
[not found] ` <20170310093509.19044-1-romain.perier-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2017-03-10 9:46 ` Russell King - ARM Linux
2017-03-10 10:21 ` Romain Perier
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 [this message]
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=20170313093630.GE21222@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Jose.Abreu@synopsys.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=narmstrong@baylibre.com \
--cc=romain.perier@collabora.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