linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: alexandre.belloni@bootlin.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 0/7] clocksource: rework Atmel TCB timer driver
Date: Tue, 25 Sep 2018 22:14:56 +0200	[thread overview]
Message-ID: <20180925201456.GD3112@piout.net> (raw)
In-Reply-To: <5f19043a-3be3-e25a-849f-6ca610ed6da2@linaro.org>

On 22/09/2018 13:29:48+0200, Daniel Lezcano wrote:
> On 13/09/2018 13:30, Alexandre Belloni wrote:
> > Hi,
> > 
> > This series reworks the Atmel TCB drivers. It introduces a new driver to handle
> > the clocksource and clockevent devices.
> > 
> > This is necessary because:
> >  - the current tcb_clksrc driver is probed too late to be able to be used at
> >    boot and we now have SoCs that don't have a PIT. They currently are not able
> >    to boot a mainline kernel.
> >  - using the PIT doesn't work well with preempt-rt because its interrupt is
> >    shared (in particular with the UART and their interrupt flags are
> >    incompatible)
> 
> You say for rt the PIT is not suitable because of the shared irq but in
> the driver, the interrupt is flagged as shared.
> 

Well, it is not simply sharing the interrupt that is an issue, it is the
mismatch between the PIT and the UART interrupt flags and that only
happens when using preempt-rt.

But still, the TCB is flagged as shared because it may be shared between
multiple TCB channels (it is the case for the more recent SoCs).
However, what happens is that the DBGU UART is always enabled on the
boards so when using the PIT, the interrupt is always shared. But, for
the TCB, the only driver currently able to use the interrupt is the
clockevent driver so the interrupt as almost no chance to actually be
shared.

-- 
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-09-25 20:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-13 11:30 [PATCH v7 0/7] clocksource: rework Atmel TCB timer driver Alexandre Belloni
2018-09-13 11:30 ` [PATCH v7 1/7] ARM: at91: add TCB registers definitions Alexandre Belloni
2018-09-13 11:30 ` [PATCH v7 2/7] clocksource/drivers: Add a new driver for the Atmel ARM TC blocks Alexandre Belloni
2018-09-24  1:59   ` Daniel Lezcano
2018-09-25 21:16     ` Alexandre Belloni
2018-10-01 21:24       ` Daniel Lezcano
2018-10-03 22:26         ` Alexandre Belloni
2018-09-13 11:30 ` [PATCH v7 3/7] clocksource/drivers: timer-atmel-tcb: add clockevent device on separate channel Alexandre Belloni
2018-09-13 11:30 ` [PATCH v7 4/7] clocksource/drivers: atmel-pit: make option silent Alexandre Belloni
2018-09-13 11:30 ` [PATCH v7 5/7] ARM: at91: Implement clocksource selection Alexandre Belloni
2018-09-13 11:30 ` [PATCH v7 6/7] ARM: configs: at91: use new TCB timer driver Alexandre Belloni
2018-09-13 11:30 ` [PATCH v7 7/7] ARM: configs: at91: unselect PIT Alexandre Belloni
2018-09-22 11:29 ` [PATCH v7 0/7] clocksource: rework Atmel TCB timer driver Daniel Lezcano
2018-09-25 20:14   ` Alexandre Belloni [this message]
2018-11-08 12:43     ` Sebastian Andrzej Siewior
2018-11-08 14:09       ` Alexandre Belloni
2018-11-08 14:30         ` Sebastian Andrzej Siewior

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=20180925201456.GD3112@piout.net \
    --to=alexandre.belloni@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).