From: Carlo Caione <carlo@caione.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"jslaby@suse.cz" <jslaby@suse.cz>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"b.galvani@gmail.com" <b.galvani@gmail.com>
Subject: Re: [PATCH 3/7] ARM: meson6: clocksource: add Meson6 timer support
Date: Tue, 19 Aug 2014 18:01:53 +0200 [thread overview]
Message-ID: <20140819160153.GA869@carlo-MacBookPro> (raw)
In-Reply-To: <20140818162726.GE3302@leverpostej>
On lun, ago 18, 2014 at 05:27:26 +0100, Mark Rutland wrote:
> On Sun, Aug 17, 2014 at 11:49:50AM +0100, Carlo Caione wrote:
> > +enum {
> > + A = 0,
> > + B,
> > + C,
> > + D,
> > +};
>
> That's a very terse set of enum names. I would recomment something a
> little longer.
>
> Any reason for missing E?
TIMER_E is a slightly different timer so I preferred to leave it apart.
> > +#define TIMER_ISA_MUX 0
> > +#define TIMER_ISA_E_VAL 0x14
> > +#define TIMER_ISA_t_VAL(t) ((t + 1) << 2)
> > +
> > +#define TIMER_t_INPUT_BIT(t) (2 * t)
> > +#define TIMER_E_INPUT_BIT 8
> > +#define TIMER_t_INPUT_MASK(t) (3UL << TIMER_t_INPUT_BIT(t))
> > +#define TIMER_E_INPUT_MASK (7UL << TIMER_E_INPUT_BIT)
> > +#define TIMER_t_ENABLE_BIT(t) (16 + t)
> > +#define TIMER_E_ENABLE_BIT 20
> > +#define TIMER_t_PERIODIC_BIT(t) (12 + t)
>
> While I don't think it matters for any of these, it's usually good
> practice to add parentheses around arguments, e.g.
>
> #define FOO(x) ((x) * 2)
>
> So you can avoid bad expansions in cases like:
>
> FOO(reg + 4)
Agree. I'll change it.
> > +
> > +#define TIMER_UNIT_1us 0
> > +#define TIMER_E_UNIT_1us 1
> > +
> > +static void __iomem *timer_base;
> > +
> > +static cycle_t cycle_read_timer_e(struct clocksource *cs)
> > +{
> > + return (cycle_t)readl(timer_base + TIMER_ISA_E_VAL);
> > +}
> > +
> > +static struct clocksource clocksource_timer_e = {
> > + .name = "meson6_timerE",
>
> Do we really care which specific timer we're using within the block?
>
> Why not just "meson6_clocksource"?
Just a reminder of which timer we are using. I'll fix it.
> > + .rating = 300,
> > + .read = cycle_read_timer_e,
> > + .mask = CLOCKSOURCE_MASK(32),
> > + .flags = CLOCK_SOURCE_IS_CONTINUOUS,
> > +};
>
> [...]
>
> > +static irqreturn_t meson6_timer_interrupt(int irq, void *dev_id)
> > +{
> > + struct clock_event_device *evt = (struct clock_event_device *)dev_id;
> > +
> > + evt->event_handler(evt);
> > +
> > + return IRQ_HANDLED;
> > +}
> > +
> > +static struct irqaction meson6_timer_irq = {
> > + .name = "meson6_timerA",
>
> Similarly to the clocksource naming, this might be better as
> "meson6_timer", without the 'A'.
Yep.
Thanks for the review,
--
Carlo Caione
next prev parent reply other threads:[~2014-08-19 16:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 10:49 [PATCH 0/7] ARM: meson: add preliminary support for MesonX/Meson6 SoCs Carlo Caione
2014-08-17 10:49 ` [PATCH 1/7] ARM: meson: debug: add debug UART for earlyprintk support Carlo Caione
2014-08-17 10:49 ` [PATCH 2/7] ARM: meson: serial: add MesonX SoC on-chip uart driver Carlo Caione
2014-08-28 7:51 ` Carlo Caione
2014-09-06 18:28 ` Carlo Caione
2014-09-06 18:38 ` Greg KH
2014-09-06 18:51 ` Carlo Caione
2014-08-17 10:49 ` [PATCH 3/7] ARM: meson6: clocksource: add Meson6 timer support Carlo Caione
2014-08-18 11:59 ` Matthias Brugger
2014-08-18 14:11 ` Carlo Caione
2014-08-18 16:27 ` Mark Rutland
2014-08-19 16:01 ` Carlo Caione [this message]
2014-08-17 10:49 ` [PATCH 4/7] ARM: meson: add basic support for MesonX SoCs Carlo Caione
2014-08-17 14:21 ` Maxime Ripard
2014-08-18 13:27 ` Carlo Caione
2014-08-18 15:10 ` Matthias Brugger
2014-08-18 19:11 ` Maxime Ripard
2014-08-17 10:49 ` [PATCH 5/7] ARM: meson: dts: add basic Meson/Meson6/Meson6-atv1200 DTSI/DTS Carlo Caione
2014-08-17 14:42 ` Beniamino Galvani
2014-08-17 15:21 ` Carlo Caione
2014-08-18 16:15 ` Mark Rutland
2014-08-18 16:17 ` Mark Rutland
2014-08-19 16:16 ` Carlo Caione
2014-08-23 11:27 ` Andreas Färber
2014-08-17 10:49 ` [PATCH 6/7] ARM: meson: update defconfigs Carlo Caione
2014-08-18 10:31 ` Matthias Brugger
2014-08-18 13:31 ` Carlo Caione
[not found] ` <1408272594-10814-1-git-send-email-carlo-KA+7E9HrN00dnm+yROfE0A@public.gmane.org>
2014-08-17 10:49 ` [PATCH 7/7] ARM: meson: update documentation (uart, timer and vendors) Carlo Caione
2014-08-18 10:36 ` Matthias Brugger
2014-08-18 13:33 ` Carlo Caione
2014-08-23 12:24 ` Andreas Färber
2014-08-17 14:29 ` [PATCH 0/7] ARM: meson: add preliminary support for MesonX/Meson6 SoCs Beniamino Galvani
2014-08-17 15:25 ` Carlo Caione
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=20140819160153.GA869@carlo-MacBookPro \
--to=carlo@caione.org \
--cc=b.galvani@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jslaby@suse.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).