From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Noam Camus <noamca@mellanox.com>,
tglx@linutronix.de, linux-snps-arc@lists.infradead.org,
linux-kernel@vger.kernel.org, Alexey.Brodkin@synopsys.com
Subject: Re: [PATCH v2 10/10] clocksource: import ARC timer driver
Date: Fri, 4 Nov 2016 00:01:46 +0100 [thread overview]
Message-ID: <20161103230146.GF15759@mai> (raw)
In-Reply-To: <249006fa-262e-f290-7aa1-95f8fa38b47c@synopsys.com>
On Thu, Nov 03, 2016 at 03:50:21PM -0700, Vineet Gupta wrote:
> On 11/03/2016 03:38 PM, Daniel Lezcano wrote:
> > On Thu, Nov 03, 2016 at 02:31:41PM -0700, Vineet Gupta wrote:
> >> This adds support for
> >>
> >> - CONFIG_ARC_TIMERS : legacy 32-bit TIMER0 and TIMER1 which count UP
> >> from @CNT to @LIMIT, before optionally triggering an interrupt.
> >> These are programmed using ARC auxiliary register interface.
> >> These are present in all ARC cores (ARC700 and ARC HS38)
> >> TIMER0 serves as clockevent for all ARC linux builds.
> >> TIMER1 is used for clocksource in arc700 builds.
> >>
> >> - CONFIG_ARC_TIMERS_64BIT: 64-bit counters, RTC and GFRC found in
> >> ARC HS38 cores. These are independnet IP blocks with different
> >> programming model respectively.
> >>
> >> Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
> >> ---
> >
> > [ ... ]
> >
> >> #include <linux/of_irq.h>
> >> -#include <asm/irq.h>
> >>
> >> #include <soc/arc/timers.h>
> >> #include <soc/arc/mcip.h>
> >> @@ -263,7 +248,7 @@ static irqreturn_t timer_irq_handler(int irq, void *dev_id)
> >> * irq_set_chip_and_handler() asked for handle_percpu_devid_irq()
> >> */
> >> struct clock_event_device *evt = this_cpu_ptr(&arc_clockevent_device);
> >> - int irq_reenable = clockevent_state_periodic(evt);
> >> + int irq_reenable __maybe_unused = clockevent_state_periodic(evt);
> >
> > Why is needed __maybe_unused ? I see in the previous driver 'irq_reenable' is
> > used or is there a change in the previous patches I missed ?
>
> This is needed when not building for CONFIG_ARC (saw this when building for ARM)
> write_aux_reg() becomes a no-op which causes a warning:
>
> write_aux_reg(ARC_REG_TIMER0_CTRL, irq_reenable | TIMER_CTRL_NH);
Instead of adding the __maybe_unused, changing in patch 7/10:
#define read_aux_reg(r) 0
#define write_aux_reg(r, v)
by
static inline int read_aux_reg(void *)
{
return 0;
}
static inline void write_aux_reg(void *, u32)
{
;
}
Should fix the warning.
next prev parent reply other threads:[~2016-11-03 23:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 21:31 [PATCH v2 00/10] Move ARC timer code into drivers/clocksource/ Vineet Gupta
2016-11-03 21:31 ` [PATCH v2 01/10] ARC: timer: rtc: implement read loop in "C" vs. inline asm Vineet Gupta
2016-11-03 21:52 ` Daniel Lezcano
2016-11-03 22:23 ` Vineet Gupta
2016-11-03 22:35 ` Daniel Lezcano
2016-11-03 22:44 ` Vineet Gupta
2016-11-03 22:46 ` Daniel Lezcano
2016-11-04 17:58 ` Alexey Brodkin
2016-11-03 21:31 ` [PATCH v2 02/10] ARC: timer: gfrc, rtc: deuglify big endian code Vineet Gupta
2016-11-03 21:55 ` Daniel Lezcano
2016-11-03 22:15 ` Vineet Gupta
2016-11-04 18:11 ` Alexey Brodkin
2016-11-03 21:31 ` [PATCH v2 03/10] ARC: timer: gfrc, rtc: Read BCR to detect whether hardware exists Vineet Gupta
2016-11-03 21:31 ` [PATCH v2 04/10] ARC: timer: gfrc: boot print alongside other timers Vineet Gupta
2016-11-03 21:31 ` [PATCH v2 05/10] ARC: time: move time_init() out of the driver Vineet Gupta
2016-11-03 21:31 ` [PATCH v2 06/10] ARC: timer: Build gfrc, rtc under same option (64-bit timers) Vineet Gupta
2016-11-03 22:13 ` Daniel Lezcano
2016-11-03 21:31 ` [PATCH v2 07/10] ARC: breakout aux handling into a separate header Vineet Gupta
2016-11-03 21:31 ` [PATCH v2 08/10] ARC: move mcip.h into include/soc and adjust the includes Vineet Gupta
2016-11-03 21:31 ` [PATCH v2 09/10] ARC: breakout timer include code into separate header Vineet Gupta
2016-11-03 21:31 ` [PATCH v2 10/10] clocksource: import ARC timer driver Vineet Gupta
2016-11-03 22:38 ` Daniel Lezcano
2016-11-03 22:50 ` Vineet Gupta
2016-11-03 23:01 ` Daniel Lezcano [this message]
2016-11-03 23:06 ` Vineet Gupta
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=20161103230146.GF15759@mai \
--to=daniel.lezcano@linaro.org \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=noamca@mellanox.com \
--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