From: Noam Camus <noamca@mellanox.com>
To: Rob Herring <robh@kernel.org>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
John Stultz <john.stultz@linaro.org>
Subject: RE: [PATCH 3/3] clocksource: Add clockevent support to NPS400 driver
Date: Tue, 18 Oct 2016 14:51:05 +0000 [thread overview]
Message-ID: <DB6PR0501MB251897240ABCBAFAA50CD925AAD30@DB6PR0501MB2518.eurprd05.prod.outlook.com> (raw)
In-Reply-To: 20161018135722.oflcjm5hfy6eugiy@rob-hp-laptop
>From: Noam Camus
>Sent: Tuesday, October 18, 2016 5:33 PM
>>You're letting Linux details define the binding. Are these blocks different (the block itself, not connections to >the block like interrupts)?
>>If you need a particular timer instance to be used, then describe whatever is the difference in the h/w. For >example, the clockevent timer has to be the timer with an interrupt.
>Yes, blocks are different.
>The difference is that only second timer instance are actually producing timer interrupt served by Linux for the clockevent framework.
>Please note that the numbering used here for timer (i.e. 0 or 1) are derived from HW blocks and are not any Linux detail I used for binding definition (It is a note at this patch set cover letter).
The timers actually are: first instance (timer 0) for clockevents and second instance (timer 1) for clocksource.
Sorry for the confusion.
Noam
WARNING: multiple messages have this Message-ID (diff)
From: Noam Camus <noamca-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: "mark.rutland-5wv7dgnIgG8@public.gmane.org"
<mark.rutland-5wv7dgnIgG8@public.gmane.org>,
"daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org"
<tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
John Stultz <john.stultz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: RE: [PATCH 3/3] clocksource: Add clockevent support to NPS400 driver
Date: Tue, 18 Oct 2016 14:51:05 +0000 [thread overview]
Message-ID: <DB6PR0501MB251897240ABCBAFAA50CD925AAD30@DB6PR0501MB2518.eurprd05.prod.outlook.com> (raw)
In-Reply-To: 20161018135722.oflcjm5hfy6eugiy@rob-hp-laptop
>From: Noam Camus
>Sent: Tuesday, October 18, 2016 5:33 PM
>>You're letting Linux details define the binding. Are these blocks different (the block itself, not connections to >the block like interrupts)?
>>If you need a particular timer instance to be used, then describe whatever is the difference in the h/w. For >example, the clockevent timer has to be the timer with an interrupt.
>Yes, blocks are different.
>The difference is that only second timer instance are actually producing timer interrupt served by Linux for the clockevent framework.
>Please note that the numbering used here for timer (i.e. 0 or 1) are derived from HW blocks and are not any Linux detail I used for binding definition (It is a note at this patch set cover letter).
The timers actually are: first instance (timer 0) for clockevents and second instance (timer 1) for clocksource.
Sorry for the confusion.
Noam
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-10-18 18:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 14:52 [PATCH 0/3] Add clockevet for timer-nps driver to NPS400 SoC Noam Camus
2016-10-13 14:52 ` Noam Camus
2016-10-13 14:52 ` [PATCH 1/3] soc: Support for NPS HW scheduling Noam Camus
2016-10-13 14:52 ` Noam Camus
2016-10-21 13:52 ` Daniel Lezcano
2016-10-13 14:52 ` [PATCH 2/3] ARC: [plat-eznps] remove macros for timer0 TSI Noam Camus
2016-10-13 14:52 ` Noam Camus
2016-10-21 14:12 ` Daniel Lezcano
2016-10-21 14:12 ` Daniel Lezcano
2016-10-13 14:52 ` [PATCH 3/3] clocksource: Add clockevent support to NPS400 driver Noam Camus
2016-10-13 14:52 ` Noam Camus
2016-10-18 13:57 ` Rob Herring
2016-10-18 14:32 ` Noam Camus
2016-10-18 14:32 ` Noam Camus
2016-10-18 14:51 ` Noam Camus [this message]
2016-10-18 14:51 ` Noam Camus
2016-10-21 15:08 ` Daniel Lezcano
2016-10-21 15:08 ` Daniel Lezcano
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=DB6PR0501MB251897240ABCBAFAA50CD925AAD30@DB6PR0501MB2518.eurprd05.prod.outlook.com \
--to=noamca@mellanox.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.