From: Stephen Boyd <sboyd@codeaurora.org>
To: Stefan Agner <stefan@agner.ch>
Cc: jianwei.wang.chn@gmail.com, meng.yi@nxp.com, pawel.moll@arm.com,
alison.wang@freescale.com, daniel.vetter@ffwll.ch,
mturquette@baylibre.com, ijc+devicetree@hellion.org.uk,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, robh+dt@kernel.org,
kernel@pengutronix.de, galak@codeaurora.org,
mark.rutland@arm.com, shawnguo@kernel.org,
linux-arm-kernel@lists.infradead.org,
alexander.stein@systec-electronic.com
Subject: Re: [PATCH v3 1/9] ARM: imx: clk-vf610: fix DCU clock tree
Date: Fri, 15 Apr 2016 17:31:28 -0700 [thread overview]
Message-ID: <20160416003128.GJ26353@codeaurora.org> (raw)
In-Reply-To: <1459834121-25997-2-git-send-email-stefan@agner.ch>
On 04/04, Stefan Agner wrote:
> Similar to an earlier fix for the SAI clocks, the DCU clock hierarchy
> mixes the bus clock with the display controllers pixel clock. Tests
> have shown that the gates in CCM_CCGR3/9 registers do not control
> the DCU pixel clock, but only the register access clock (bus clock).
>
> Fix this by defining the parent clock of VF610_CLK_DCUx to be the bus
> clock (ipg_bus).
>
> Since the clock has not been used far, there are no further changes
> needed.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
> ---
Acked-by: Stephen Boyd <sboyd@codeaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-04-16 0:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 5:28 [PATCH v3 0/9] add TCON and Vybrid support Stefan Agner
2016-04-05 5:28 ` [PATCH v3 1/9] ARM: imx: clk-vf610: fix DCU clock tree Stefan Agner
2016-04-12 1:38 ` Shawn Guo
2016-04-13 5:21 ` Stefan Agner
2016-04-16 0:31 ` Stephen Boyd [this message]
2016-04-05 5:28 ` [PATCH v3 2/9] ARM: imx: clk-vf610: add TCON ipg clock Stefan Agner
2016-04-05 5:28 ` [PATCH v3 3/9] drm/fsl-dcu: disable clock on initialization failure and remove Stefan Agner
2016-04-05 5:28 ` [PATCH v3 4/9] drm/fsl-dcu: add extra clock for pixel clock Stefan Agner
2016-04-07 17:57 ` Rob Herring
2016-04-05 5:28 ` [PATCH v3 5/9] drm/fsl-dcu: use common clock framework for pixel clock divider Stefan Agner
2016-04-05 5:28 ` [PATCH v3 6/9] drm/fsl-dcu: add TCON driver Stefan Agner
2016-04-05 5:28 ` [PATCH v3 7/9] ARM: dts: vf610: add display nodes Stefan Agner
2016-04-13 6:13 ` Shawn Guo
2016-04-05 5:28 ` [PATCH v3 8/9] ARM: dts: vf610-colibri: enable display controller Stefan Agner
2016-04-05 5:28 ` [PATCH v3 9/9] ARM: dts: ls1021a: add pix clock to DCU dts node Stefan Agner
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=20160416003128.GJ26353@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=alexander.stein@systec-electronic.com \
--cc=alison.wang@freescale.com \
--cc=daniel.vetter@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jianwei.wang.chn@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=meng.yi@nxp.com \
--cc=mturquette@baylibre.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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;
as well as URLs for NNTP newsgroup(s).