Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@mvista.com>
To: John Crispin <blogic@openwrt.org>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH V2 07/10] MIPS: ralink: adds early_printk support
Date: Sun, 27 Jan 2013 23:26:22 +0400	[thread overview]
Message-ID: <51057F5E.80708@mvista.com> (raw)
In-Reply-To: <1359309842-31925-8-git-send-email-blogic@openwrt.org>

Hello.

On 27-01-2013 22:03, John Crispin wrote:

> Add the code needed to make early printk work.

> Signed-off-by: John Crispin <blogic@openwrt.org>
> ---
>   arch/mips/ralink/early_printk.c |   45 +++++++++++++++++++++++++++++++++++++++
>   1 file changed, 45 insertions(+)
>   create mode 100644 arch/mips/ralink/early_printk.c

> diff --git a/arch/mips/ralink/early_printk.c b/arch/mips/ralink/early_printk.c
> new file mode 100644
> index 0000000..7a9b474
> --- /dev/null
> +++ b/arch/mips/ralink/early_printk.c
> @@ -0,0 +1,45 @@
> +/*
> + *  This program is free software; you can redistribute it and/or modify it
> + *  under the terms of the GNU General Public License version 2 as published
> + *  by the Free Software Foundation.
> + *
> + *  Copyright (C) 2011-2012 Gabor Juhos <juhosg@openwrt.org>
> + */
> +
> +#include <linux/io.h>
> +#include <linux/serial_reg.h>
> +
> +#include <asm/addrspace.h>
> +
> +/* UART registers */
> +#define EARLY_UART_BASE         0x10000c00
> +
> +#define UART_REG_RX             0
> +#define UART_REG_TX             1
> +#define UART_REG_IER            2
> +#define UART_REG_IIR            3
> +#define UART_REG_FCR            4
> +#define UART_REG_LCR            5
> +#define UART_REG_MCR            6
> +#define UART_REG_LSR            7

    Isn;t it better to have register offsets premultiplied by 4? Saves you a 
multiplication in read/write functions (although they probably would be 
optmized out by gcc anyway).

> +
> +static __iomem void *uart_membase = (__iomem void *) KSEG1ADDR(EARLY_UART_BASE);
> +
> +static inline void uart_w32(u32 val, unsigned reg)
> +{
> +	__raw_writel(val, uart_membase + (4 * reg));
> +}
> +
> +static inline u32 uart_r32(unsigned reg)
> +{
> +	return __raw_readl(uart_membase + (4 * reg));
> +}

WBR, Sergei

  reply	other threads:[~2013-01-27 19:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-27 18:03 [PATCH V2 00/10] MIPS: ralink: adds support for ralink platform John Crispin
2013-01-27 18:03 ` [PATCH V2 01/10] MIPS: ralink: adds include files John Crispin
2013-01-27 18:03 ` [PATCH V2 02/10] MIPS: ralink: adds irq code John Crispin
2013-01-27 18:03 ` [PATCH V2 03/10] MIPS: ralink: adds reset code John Crispin
2013-01-27 18:03 ` [PATCH V2 04/10] MIPS: ralink: adds prom and cmdline code John Crispin
2013-01-27 18:03 ` [PATCH V2 05/10] MIPS: ralink: adds clkdev code John Crispin
2013-01-27 18:03 ` [PATCH V2 06/10] MIPS: ralink: adds OF code John Crispin
2013-01-27 18:03 ` [PATCH V2 07/10] MIPS: ralink: adds early_printk support John Crispin
2013-01-27 19:26   ` Sergei Shtylyov [this message]
2013-01-27 18:04 ` [PATCH V2 08/10] MIPS: ralink: adds support for RT305x SoC family John Crispin
2013-01-27 18:04 ` [PATCH V2 09/10] MIPS: ralink: adds rt305x devicetree John Crispin
2013-01-27 18:04 ` [PATCH V2 10/10] MIPS: ralink: adds Kbuild files John Crispin

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=51057F5E.80708@mvista.com \
    --to=sshtylyov@mvista.com \
    --cc=blogic@openwrt.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    /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