public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Adam Ford <aford173@gmail.com>
To: u-boot@lists.denx.de
Cc: Adam Ford <aford173@gmail.com>,
	"Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>,
	Jagan Teki <jagan@amarulasolutions.com>,
	Matteo Lisi <matteo.lisi@engicam.com>,
	Marek Vasut <marex@denx.de>,
	Olaf Mandel <o.mandel@menlosystems.com>,
	Peng Fan <peng.fan@nxp.com>, Tim Harvey <tharvey@gateworks.com>,
	"Ariel D'Alessandro" <ariel.dalessandro@collabora.com>,
	Michael Trimarchi <michael@amarulasolutions.com>,
	Ilko Iliev <iliev@ronetix.at>, Fabio Estevam <festevam@gmail.com>,
	Marco Franchi <marcofrk@gmail.com>,
	Alifer Moraes <alifer.wsdm@gmail.com>
Subject: [RFC 3/3] imx8: imx8mm_beacon: Remove manual UART clock initialization
Date: Sat, 30 Apr 2022 11:14:22 -0500	[thread overview]
Message-ID: <20220430161422.558361-4-aford173@gmail.com> (raw)
In-Reply-To: <20220430161422.558361-1-aford173@gmail.com>

SPL has a manual call to init_uart_clk in order to start the
clocks.  If the CCF has the UART clocks available, the
serial driver can enable and query the clock when needed, so
the manual call to init_uart_clk can be dropped.

Signed-off-by: Adam Ford <aford173@gmail.com>

diff --git a/board/beacon/imx8mm/spl.c b/board/beacon/imx8mm/spl.c
index f92b4c3ed0..fc0935bc97 100644
--- a/board/beacon/imx8mm/spl.c
+++ b/board/beacon/imx8mm/spl.c
@@ -114,8 +114,6 @@ void board_init_f(ulong dummy)
 
 	arch_cpu_init();
 
-	init_uart_clk(1);
-
 	board_early_init_f();
 
 	timer_init();
-- 
2.34.1


      parent reply	other threads:[~2022-04-30 16:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-30 16:14 [RFC 0/3] imx8m: Remove manual UART clock initialization Adam Ford
2022-04-30 16:14 ` [RFC 1/3] clk: imx8mm: Add UART clocks Adam Ford
2022-04-30 16:14 ` [RFC 2/3] serial: mxc: Enable getting and enabling clocks with CCF Composite Adam Ford
2022-05-01  9:48   ` Peng Fan (OSS)
2022-05-01 15:16     ` Adam Ford
2022-04-30 16:14 ` Adam Ford [this message]

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=20220430161422.558361-4-aford173@gmail.com \
    --to=aford173@gmail.com \
    --cc=alifer.wsdm@gmail.com \
    --cc=ariel.dalessandro@collabora.com \
    --cc=festevam@gmail.com \
    --cc=iliev@ronetix.at \
    --cc=jagan@amarulasolutions.com \
    --cc=marcofrk@gmail.com \
    --cc=marex@denx.de \
    --cc=matteo.lisi@engicam.com \
    --cc=michael@amarulasolutions.com \
    --cc=o.mandel@menlosystems.com \
    --cc=paul.liu@linaro.org \
    --cc=peng.fan@nxp.com \
    --cc=tharvey@gateworks.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