mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v4 2/7] ARM: rpi: retrieve miniuart clock from firmware
Date: Tue, 18 Dec 2018 08:21:14 +0100	[thread overview]
Message-ID: <20181218072114.thijfcbgack4sprf@pengutronix.de> (raw)
In-Reply-To: <39d36e54718c9c5c75175e3836de5425b1f73fb3.1545034218.git-series.r.czerwinski@pengutronix.de>

On Mon, Dec 17, 2018 at 09:10:40AM +0100, Rouven Czerwinski wrote:
> The miniuart uses the core clock as the clock source. This clock is fixed by the
> firmware to 250Mhz if enable_uart=1 is set in the config.txt file.
> However a user could still choose to overclock the core frequency,
> which would result in wrong baudrates computed by barebox.
> Retrieve the core clock frequency from the firmware to allow all potential
> firmware configurations to work with barebox.
> 
> Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
> ---
>  arch/arm/boards/raspberry-pi/rpi-common.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/arch/arm/boards/raspberry-pi/rpi-common.c b/arch/arm/boards/raspberry-pi/rpi-common.c
> index 490aeef..e29177d 100644
> --- a/arch/arm/boards/raspberry-pi/rpi-common.c
> +++ b/arch/arm/boards/raspberry-pi/rpi-common.c
> @@ -309,6 +309,13 @@ static int rpi_console_clock_init(void)
>  	clkdev_add_physbase(clk, 0x20201000, NULL);
>  	clkdev_add_physbase(clk, 0x3f201000, NULL);
>  
> +	clk = rpi_register_firmware_clock(BCM2835_MBOX_CLOCK_ID_CORE,
> +					  "uart1-8250");

We don't have this function anywhere in the tree, this breaks
compilation.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2018-12-18  7:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17  8:10 [PATCH v4 0/7] Raspberry Pi miniuart support Rouven Czerwinski
2018-12-17  8:10 ` [PATCH v4 1/7] ARM: rpi: move clks into board specific rpi-common Rouven Czerwinski
2018-12-17  8:10 ` [PATCH v4 2/7] ARM: rpi: retrieve miniuart clock from firmware Rouven Czerwinski
2018-12-18  3:26   ` Roland Hieber
2018-12-18  7:17     ` Sascha Hauer
2018-12-18  7:21   ` Sascha Hauer [this message]
2018-12-18  8:39     ` Rouven Czerwinski
2018-12-18  8:45       ` Sascha Hauer
2018-12-17  8:10 ` [PATCH v4 3/7] serial_ns16550: handle default reg-io-width Rouven Czerwinski
2018-12-17  8:10 ` [PATCH v4 4/7] serial_ns16550: add raspberry pi compatible and init Rouven Czerwinski
2018-12-18  3:29   ` Roland Hieber
2018-12-17  8:10 ` [PATCH v4 5/7] ARM: rpi: add NS16550 support Rouven Czerwinski
2018-12-17  8:10 ` [PATCH v4 6/7] ARM: rpi: choose miniuart as stdout Rouven Czerwinski
2018-12-17  8:10 ` [PATCH v4 7/7] doc: bcm283x: remove miniuart overlay instruction Rouven Czerwinski
2018-12-17 10:13 ` [PATCH v4 0/7] Raspberry Pi miniuart support Sascha Hauer

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=20181218072114.thijfcbgack4sprf@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=r.czerwinski@pengutronix.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