From: Jorge Ramirez-Ortiz, Foundries <jorge@foundries.io>
To: u-boot@lists.denx.de
Subject: [PATCH] mx6: peripheral clock from oscillator
Date: Fri, 16 Oct 2020 14:41:16 +0200 [thread overview]
Message-ID: <20201016124116.GA25143@trex> (raw)
In-Reply-To: <20201014130726.21984-1-jorge@foundries.io>
any thoughts?
On 14/10/20, Jorge Ramirez-Ortiz wrote:
> In order to be able to run the I2C bus at 400Khz, the chip errata[1]
> recommends that the peripheral clock runs out of the 24MHz oscillator.
>
> [1] Rev 2, 10/2019, ERR007805
>
> Signed-off-by: Jorge Ramirez-Ortiz <jorge@foundries.io>
> ---
> arch/arm/mach-imx/mx6/soc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-imx/mx6/soc.c b/arch/arm/mach-imx/mx6/soc.c
> index e129286065..1da250bbcd 100644
> --- a/arch/arm/mach-imx/mx6/soc.c
> +++ b/arch/arm/mach-imx/mx6/soc.c
> @@ -469,7 +469,7 @@ int arch_cpu_init(void)
> }
>
> /* Set perclk to source from OSC 24MHz */
> - if (is_mx6sl())
> + if (is_mx6sl() || is_mx6ull())
> setbits_le32(&ccm->cscmr1, MXC_CCM_CSCMR1_PER_CLK_SEL_MASK);
>
> imx_wdog_disable_powerdown(); /* Disable PDE bit of WMCR register */
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-10-16 12:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 13:07 [PATCH] mx6: peripheral clock from oscillator Jorge Ramirez-Ortiz
2020-10-16 12:41 ` Jorge [this message]
2020-10-19 6:40 ` Peng Fan
2020-10-19 12:32 ` Fabio Estevam
2020-10-19 12:57 ` Jorge
2020-10-19 14:24 ` Jorge
-- strict thread matches above, loose matches on Subject: below --
2020-10-19 14:23 Jorge Ramirez-Ortiz
2020-10-22 15:18 ` Jorge
2020-10-22 20:51 ` Fabio Estevam
2020-10-22 21:24 ` Jorge
2020-10-22 21:30 ` Fabio Estevam
2020-10-23 6:35 ` Jorge
2020-10-23 12:13 ` Fabio Estevam
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=20201016124116.GA25143@trex \
--to=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