mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Kochetkov <al.kochet@gmail.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clockevents: Add a clkevt-of mechanism like clksrc-of
Date: Mon, 30 Jan 2017 14:04:42 +0300	[thread overview]
Message-ID: <452A0749-9C76-4A55-81C0-FF426DD20A4B@gmail.com> (raw)
In-Reply-To: <1485346876-28506-1-git-send-email-daniel.lezcano@linaro.org>


> 25 янв. 2017 г., в 15:21, Daniel Lezcano <daniel.lezcano@linaro.org> написал(а):
> 
> Hopefully, that can help to do some housework in the directory, perhaps
> split the drivers in to entities, for example:
> 	- clksrc-rockchip.c
> 	- clkevt-rockchip.c
> 
> Also, it gives the possibility to declare clocksources separately in the
> DT and then use a clocksource from IP block while while clockevents are
> used from another IP block.

Hello, Daniel!

There is no way to do declare clocksources and clockevents in the DT now.
As I understood, it is incorrect to add properties like ‘clocksource’ or ‘clockevent’
to timer entries because this sounds like linux specific configuration. While
device tree must contain only hardware description. Thus many timer
drivers has implicit assumption: first DT timer became clocksource, second
clockevent.

If we can find the way to describe timer role in the DT, than many timer drivers
could be rewritten such a way.

Also, there is timers what use single IP to provide clocksource and clockevent
at the same time. So splitting them into two files result into more complex code.

Regards,
Alexander.

  reply	other threads:[~2017-01-30 11:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 12:21 Daniel Lezcano
2017-01-30 11:04 ` Alexander Kochetkov [this message]
2017-01-30 11:36   ` 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=452A0749-9C76-4A55-81C0-FF426DD20A4B@gmail.com \
    --to=al.kochet@gmail.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®