LKML Archive on
help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <>
To: Alexandre Belloni <>
Cc: Daniel Lezcano <>,
	Thomas Gleixner <>,
	Nicolas Ferre <>,
	Boris Brezillon <>,,
Subject: Re: [PATCH v4 0/6] clocksource: rework Atmel TCB timer driver
Date: Wed, 2 May 2018 15:34:18 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2018-04-26 20:52:33 [+0200], Alexandre Belloni wrote:
> I don't remember you posted anything for the TCB. Wasn't it focused on
> getting rid of the PIT irq?

the PIT irq which was shared with the UART one some devices, yes this
was part of it. The other essential piece was using a higher frequency
for the device:

> As said below, this is solving multiple issues, including the one for
> SoCs that don't have the PIT.
will the PIT be removed? Where it needs the PIT?

> Ok, if I understand correctly tc_clkevt2_set_oneshot is called from
> atomic context so it shouldn't call tc_clkevt2_shutdown.
> Back in 2016, tglx said:
> "There was an earlier discussion about the clk stuff. Actually the lock
> protecting disable/enable should be made raw, but there was some crap going on
> in some of the clk callbacks which made that impossible. We realy should
> revisit this."
> Anyway, I'll try to avoid disabling the clock just to reenable it
> afterwards.
> (Actually, I've just checked before sending and I've found your patch,
> I'll do something similar)

> > >  - the current solution is wasting some TCB channels
> > > 
> > > The plan is to get this driver upstream, then convert the TCB PWM driver to be
> > > able to get rid of the tcb_clksrc driver along with atmel_tclib.
> > 
> > The config options are now less than optimal (for me at least). On
> > oldconfig it asks you for PIT and I say selected no because I wanted the
> > new one. So I end up with nothing.
> > Not sure you want do something about it…
> > 
> I don't think you ending up with nothing but probably you removed the
> PIT and kept ATMEL_TCLIB which is the combination that is really
> difficult to protect from. I don't think it is worth the added Kconfig
> complexity.

TCLIB was still enabled yes. It is 'oldconfig'.

> > Is the resolution more or the same compared what we have in -RT? On an
> > idle system this clocks goes up to 180us/ 190us while the old clock
> > started at 160us and moved to around 180us after one hackbench
> > invocation. This could be nothing, it could be a lower frequency of the
> > clockevents device.
> > 
> The driver shouldn't change anything on that side.
> > If you intend to stick with this driver then I would replace the current
> > hack in -RT with this series.
> > 
> That is one of the goal, yes.
> The remaining one would be "clocksource: TCLIB: Allow higher clock rates
> for clock events"

I see. So I would need to keep that patch in queue after it was
dismissed from duty…


  reply	other threads:[~2018-05-02 13:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-18 10:51 Alexandre Belloni
2018-04-18 10:51 ` [PATCH v4 1/6] ARM: at91: add TCB registers definitions Alexandre Belloni
2018-04-26 16:52   ` Sebastian Andrzej Siewior
2018-04-26 17:48     ` Alexandre Belloni
2018-04-18 10:51 ` [PATCH v4 2/6] clocksource/drivers: Add a new driver for the Atmel ARM TC blocks Alexandre Belloni
2018-04-18 10:51 ` [PATCH v4 3/6] clocksource/drivers: atmel-pit: make option silent Alexandre Belloni
2018-04-18 10:51 ` [PATCH v4 4/6] ARM: at91: Implement clocksource selection Alexandre Belloni
2018-04-18 10:51 ` [PATCH v4 5/6] ARM: configs: at91: use new TCB timer driver Alexandre Belloni
2018-04-18 10:51 ` [PATCH v4 6/6] ARM: configs: at91: unselect PIT Alexandre Belloni
2018-04-26 16:46 ` [PATCH v4 0/6] clocksource: rework Atmel TCB timer driver Sebastian Andrzej Siewior
2018-04-26 18:52   ` Alexandre Belloni
2018-05-02 13:34     ` Sebastian Andrzej Siewior [this message]
2018-05-02 18:10       ` Alexandre Belloni
2018-05-15 17:26         ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH v4 0/6] clocksource: rework Atmel TCB timer driver' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).