public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peng Fan <van.freenix@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot,2/3] imx: mx6: correct IPU clock
Date: Wed, 6 Sep 2017 10:18:47 +0800	[thread overview]
Message-ID: <20170906021844.GB12592@linux-7smt.suse> (raw)
In-Reply-To: <0004f64b-813a-4f75-698f-e8c740f0a783@cox.net>

On Mon, Sep 04, 2017 at 07:37:01PM -0700, Eric Nelson wrote:
>Hi Peng,
>
>Pardon the reference to an old update, but do you have a description
>of the symptoms that brought about this patch?

Sorry for late reply. Runtime calculation is better.

The clk here is IPU HSP clock, which default sources mmdc ch clock.
To DL, the mmdc ch clock is 396M and the IPU HSP podf is 2, so the lock
is 198M.

Regards,
Peng.

>
>On 03/09/2016 01:07 AM, Peng Fan wrote:
>>The CONFIG_IPUV3_CLK should be 264000000, to i.MX6DL, it should be
>>198000000.
>>
>>Signed-off-by: Peng Fan <van.freenix@gmail.com>
>>Signed-off-by: Sandor Yu <sandor.yu@nxp.com>
>>Cc: Stefano Babic <sbabic@denx.de>
>>Cc: Fabio Estevam <fabio.estevam@nxp.com>
>>Cc: Peter Robinson <pbrobinson@gmail.com>
>>---
>>  include/configs/mx6sabre_common.h | 6 +++++-
>>  1 file changed, 5 insertions(+), 1 deletion(-)
>>
>>diff --git a/include/configs/mx6sabre_common.h b/include/configs/mx6sabre_common.h
>>index 29d1f91..a6d821b 100644
>>--- a/include/configs/mx6sabre_common.h
>>+++ b/include/configs/mx6sabre_common.h
>>@@ -225,7 +225,11 @@
>>  #define CONFIG_BMP_16BPP
>>  #define CONFIG_VIDEO_LOGO
>>  #define CONFIG_VIDEO_BMP_LOGO
>>-#define CONFIG_IPUV3_CLK 260000000
>>+#ifdef CONFIG_MX6DL
>>+#define CONFIG_IPUV3_CLK 198000000
>>+#else
>>+#define CONFIG_IPUV3_CLK 264000000
>>+#endif
>
>
>Note that this should probably be applied for other boards
>which are compiled for multiple CPU types.
>
>At least the Boundary Nitrogen boards, but probably others
>like Wand have ordering options for DL or Solo processors
>and may need the reduced clock rate.
>
>
>>  #define CONFIG_IMX_HDMI
>>  #define CONFIG_IMX_VIDEO_SKIP
>
>Please advise,
>
>
>Eric

  parent reply	other threads:[~2017-09-06  2:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09  8:07 [U-Boot] [PATCH 1/3] video: ipu: avoid overflow issue Peng Fan
2016-03-09  8:07 ` [U-Boot] [PATCH 2/3] imx: mx6: correct IPU clock Peng Fan
2016-03-14 21:56   ` Anatolij Gustschin
2017-09-05  2:37   ` [U-Boot] [U-Boot,2/3] " Eric Nelson
2017-09-05  2:43     ` Eric Nelson
2017-09-05 12:56     ` Fabio Estevam
2017-09-05 13:30       ` Stefano Babic
2017-09-05 13:41         ` Eric Nelson
2017-09-06 13:52           ` Fabio Estevam
2017-09-06  2:18     ` Peng Fan [this message]
2017-09-06  9:37     ` Ye Li
2017-09-06 17:38       ` Eric Nelson
2016-03-09  8:07 ` [U-Boot] [PATCH 3/3] imx: mx6: hdmi: handle overflow condition Peng Fan
2016-03-14 21:57   ` Anatolij Gustschin
2016-03-14 21:56 ` [U-Boot] [PATCH 1/3] video: ipu: avoid overflow issue Anatolij Gustschin

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=20170906021844.GB12592@linux-7smt.suse \
    --to=van.freenix@gmail.com \
    --cc=u-boot@lists.denx.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