Generic Linux architectural discussions
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Guo Ren <ren_guo@c-sky.com>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
	tglx@linutronix.de, daniel.lezcano@linaro.org,
	jason@lakedaemon.net, arnd@arndb.de,
	c-sky_gcc_upstream@c-sky.com, gnu-csky@mentor.com,
	thomas.petazzoni@bootlin.com, wbx@uclibc-ng.org
Subject: Re: [PATCH 18/19] clocksource: add timer-nationalchip.c
Date: Mon, 19 Mar 2018 04:15:35 +0000	[thread overview]
Message-ID: <20180319041522.zyjdjrxtd2va3m2a@salmiak> (raw)
In-Reply-To: <04f5a0702fc14e934e6f5a456cad8682d0b15aa2.1521399976.git.ren_guo@c-sky.com>

Hi,

On Mon, Mar 19, 2018 at 03:51:40AM +0800, Guo Ren wrote:
> +#define NC_VA_COUNTER_1_STATUS		(void *)(timer_reg + 0x00)
> +#define NC_VA_COUNTER_1_VALUE		(void *)(timer_reg + 0x04)
> +#define NC_VA_COUNTER_1_CONTROL		(void *)(timer_reg + 0x10)
> +#define NC_VA_COUNTER_1_CONFIG		(void *)(timer_reg + 0x20)
> +#define NC_VA_COUNTER_1_PRE		(void *)(timer_reg + 0x24)
> +#define NC_VA_COUNTER_1_INI		(void *)(timer_reg + 0x28)
> +#define NC_VA_COUNTER_2_STATUS		(void *)(timer_reg + 0x40)
> +#define NC_VA_COUNTER_2_VALUE		(void *)(timer_reg + 0x44)
> +#define NC_VA_COUNTER_2_CONTROL		(void *)(timer_reg + 0x50)
> +#define NC_VA_COUNTER_2_CONFIG		(void *)(timer_reg + 0x60)
> +#define NC_VA_COUNTER_2_PRE		(void *)(timer_reg + 0x64)
> +#define NC_VA_COUNTER_2_INI		(void *)(timer_reg + 0x68)
> +#define NC_VA_COUNTER_3_STATUS		(void *)(timer_reg + 0x80)
> +#define NC_VA_COUNTER_3_VALUE		(void *)(timer_reg + 0x84)
> +#define NC_VA_COUNTER_3_CONTROL		(void *)(timer_reg + 0x90)
> +#define NC_VA_COUNTER_3_CONFIG		(void *)(timer_reg + 0xa0)
> +#define NC_VA_COUNTER_3_PRE		(void *)(timer_reg + 0xa4)
> +#define NC_VA_COUNTER_3_INI		(void *)(timer_reg + 0xa8)

Please define the offsets alone, e.g.

#define NC_VA_COUNTER_1_STATUS	0x00
#define NC_VA_COUNTER_1_VALUE	0x04

... the base address should be added when calling the io accessor. Please see
below.

> +static unsigned int timer_reg;

This should be a void __iomem *, e.g.

static void __iomem *timer_base;

... though it would be better for this to be associated with the instance of
the clock_event_device, so that there can be multiple instances in a system.

> +
> +static inline void timer_reset(void)
> +{
> +	__raw_writel(0x1,	NC_VA_COUNTER_1_CONTROL);
> +	__raw_writel(0x0,	NC_VA_COUNTER_1_CONTROL);
> +	__raw_writel(0x3,	NC_VA_COUNTER_1_CONFIG);
> +	__raw_writel(26,	NC_VA_COUNTER_1_PRE);

Should this be 26 or 0x26?

It would be nice to have mnemonics for these magic numbers.

Please use writel_relaxed() rather than __raw_writel(). e.g.

	writel_relaxed(0x1, timer_base + NC_VA_COUNTER_1_CONTROL);
	writel_relaxed(0x0, timer_base + NC_VA_COUNTER_1_CONTROL);
	writel_relaxed(0x3, timer_base + NC_VA_COUNTER_1_CONTROL);
	writel_relaxed(26, timer_base + NC_VA_COUNTER_1_PRE);

[...]

> +static int __init nc_timer_init(struct device_node *np)
> +{
> +	unsigned int irq;
> +	unsigned int freq;
> +
> +	/* parse from devicetree */
> +	timer_reg = (unsigned int) of_iomap(np, 0);
> +	if (!timer_reg)
> +		panic("%s, of_iomap err.\n", __func__);
> +
> +	irq = irq_of_parse_and_map(np, 0);
> +	if (!irq)
> +		panic("%s, irq_parse err.\n", __func__);
> +
> +	if (of_property_read_u32(np, "clock-frequency", &freq))
> +		panic("%s, clock-frequency error.\n", __func__);
> +
> +	pr_info("Nationalchip Timer Init, reg: %x, irq: %d, freq: %d.\n",
> +		timer_reg, irq, freq);
> +
> +	/* setup irq */
> +	if (request_irq(irq, timer_interrupt, IRQF_TIMER, np->name, &nc_ced))
> +		panic("%s timer_interrupt error.\n", __func__);
> +
> +	/* register */
> +	clockevents_config_and_register(&nc_ced, freq, 1, ULONG_MAX);
> +
> +	nc_csd_enable();
> +	clocksource_mmio_init(NC_VA_COUNTER_2_VALUE, "nationalchip-clksource", freq, 200, 32, clocksource_mmio_readl_up);
> +
> +	sched_clock_register(nc_sched_clock_read, 32, freq);
> +
> +	return 0;
> +}
> +CLOCKSOURCE_OF_DECLARE(nc_timer, "nationalchip,timer-v1", nc_timer_init);

This needs a devicetree binding document. Please see Documentation/devicetree/bindings/submitting-patches.txt.

Thanks,
Mark

  parent reply	other threads:[~2018-03-19  4:15 UTC|newest]

Thread overview: 126+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-18 19:51 [PATCH 00/19] C-SKY(csky) Linux Kernel Port Guo Ren
2018-03-18 19:51 ` Guo Ren
2018-03-18 19:51 ` [PATCH 01/19] csky: Kernel booting Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-18 19:51 ` [PATCH 02/19] csky: Exception handling and syscall Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-19  1:48   ` Mark Rutland
2018-03-19  1:48     ` Mark Rutland
2018-03-19  6:47     ` Guo Ren
2018-03-19  6:47       ` Guo Ren
2018-03-19  8:50   ` Dominik Brodowski
2018-03-19  8:50     ` Dominik Brodowski
2018-03-19 11:03     ` Guo Ren
2018-03-19 11:03       ` Guo Ren
2018-03-18 19:51 ` [PATCH 03/19] csky: Cache and TLB routines Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-18 19:51 ` [PATCH 04/19] csky: MMU and page talbe management Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-18 19:51 ` [PATCH 05/19] csky: Process management Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-18 19:51 ` [PATCH 06/19] csky: IRQ handling Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-19 13:16   ` Thomas Gleixner
2018-03-19 13:16     ` Thomas Gleixner
2018-03-20  2:06     ` Guo Ren
2018-03-20  2:06       ` Guo Ren
2018-03-18 19:51 ` [PATCH 07/19] csky: Atomic operations Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-18 19:51 ` [PATCH 08/19] csky: ELF and module probe Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-18 19:51 ` [PATCH 09/19] csky: VDSO and rt_sigreturn Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-18 19:51 ` [PATCH 10/19] csky: Signal handling Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-26 13:04   ` Arnd Bergmann
2018-03-26 13:04     ` Arnd Bergmann
2018-03-27  2:41     ` Guo Ren
2018-03-27  2:41       ` Guo Ren
2018-03-18 19:51 ` [PATCH 11/19] csky: Library functions Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-18 19:51 ` [PATCH 12/19] csky: Debug and Ptrace GDB Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-26 13:06   ` Arnd Bergmann
2018-03-26 13:06     ` Arnd Bergmann
2018-03-18 19:51 ` [PATCH 13/19] csky: User access Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-18 19:51 ` [PATCH 14/19] csky: Misc headers Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-19 16:11   ` Arnd Bergmann
2018-03-19 16:11     ` Arnd Bergmann
2018-03-20  3:36     ` Guo Ren
2018-03-20  3:36       ` Guo Ren
2018-03-20  7:54       ` Arnd Bergmann
2018-03-20  7:54         ` Arnd Bergmann
2018-03-20 13:22         ` Guo Ren
2018-03-20 13:22           ` Guo Ren
2018-03-18 19:51 ` [PATCH 15/19] csky: Build infrastructure Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-19 15:45   ` Arnd Bergmann
2018-03-19 15:45     ` Arnd Bergmann
2018-03-20 13:13     ` Guo Ren
2018-03-20 13:13       ` Guo Ren
2018-03-21  7:36       ` Arnd Bergmann
2018-03-21  7:36         ` Arnd Bergmann
2018-03-21 12:41         ` Guo Ren
2018-03-21 12:41           ` Guo Ren
2018-03-26 13:00           ` Arnd Bergmann
2018-03-26 13:00             ` Arnd Bergmann
2018-03-27  2:39             ` Guo Ren
2018-03-27  2:39               ` Guo Ren
2018-03-27  7:38               ` Arnd Bergmann
2018-03-27  7:38                 ` Arnd Bergmann
2018-03-28  3:49                 ` Guo Ren
2018-03-28  3:49                   ` Guo Ren
2018-03-28  7:40                   ` Arnd Bergmann
2018-03-28  7:40                     ` Arnd Bergmann
2018-03-28  8:04                     ` Guo Ren
2018-03-28  8:04                       ` Guo Ren
2018-03-18 19:51 ` [PATCH 16/19] csky: Device tree Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-19 15:28   ` Arnd Bergmann
2018-03-19 15:28     ` Arnd Bergmann
2018-03-20 13:55     ` Guo Ren
2018-03-20 13:55       ` Guo Ren
2018-03-18 19:51 ` [PATCH 17/19] csky: defconfig Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-26 13:16   ` Arnd Bergmann
2018-03-26 13:16     ` Arnd Bergmann
2018-03-27  2:21     ` Guo Ren
2018-03-27  2:21       ` Guo Ren
2018-03-27  7:48       ` Arnd Bergmann
2018-03-27  7:48         ` Arnd Bergmann
2018-03-28  3:59         ` Guo Ren
2018-03-28  3:59           ` Guo Ren
2018-03-18 19:51 ` [PATCH 18/19] clocksource: add timer-nationalchip.c Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-18 22:07   ` Daniel Lezcano
2018-03-18 22:07     ` Daniel Lezcano
2018-03-19  6:59     ` Guo Ren
2018-03-19  6:59       ` Guo Ren
2018-03-19  4:15   ` Mark Rutland [this message]
2018-03-19  4:15     ` Mark Rutland
2018-03-19  7:03     ` Guo Ren
2018-03-19  7:03       ` Guo Ren
2018-03-18 19:51 ` [PATCH 19/19] irqchip: add irq-nationalchip.c and irq-csky.c Guo Ren
2018-03-18 19:51   ` Guo Ren
2018-03-19  4:26   ` Mark Rutland
2018-03-19  4:26     ` Mark Rutland
2018-03-19  7:08     ` Guo Ren
2018-03-19  7:08       ` Guo Ren
2018-03-19 13:30   ` Thomas Gleixner
2018-03-19 13:30     ` Thomas Gleixner
2018-03-20 14:23     ` Guo Ren
2018-03-20 14:23       ` Guo Ren
2018-03-18 20:25 ` [PATCH 00/19] C-SKY(csky) Linux Kernel Port Joe Perches
2018-03-18 20:25   ` Joe Perches
2018-03-19  7:11   ` Guo Ren
2018-03-19  7:11     ` Guo Ren
2018-03-26 13:30 ` Arnd Bergmann
2018-03-26 13:30   ` Arnd Bergmann
2018-03-26 15:06   ` [gnu-csky] " Sandra Loosemore
2018-03-26 15:06     ` Sandra Loosemore
2018-03-26 15:11     ` Arnd Bergmann
2018-03-26 15:11       ` Arnd Bergmann
2018-03-27  1:58   ` Guo Ren
2018-03-27  1:58     ` Guo Ren

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=20180319041522.zyjdjrxtd2va3m2a@salmiak \
    --to=mark.rutland@arm.com \
    --cc=arnd@arndb.de \
    --cc=c-sky_gcc_upstream@c-sky.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=gnu-csky@mentor.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ren_guo@c-sky.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wbx@uclibc-ng.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