From: Guo Ren <ren_guo@c-sky.com>
To: daniel.lezcano@linaro.org, tglx@linutronix.de
Cc: arnd@arndb.de, linux-arch@vger.kernel.org,
devicetree@vger.kernel.org, Guo Ren <ren_guo@c-sky.com>
Subject: [PATCH V13 0/2] C-SKY(csky) Timer Driver
Date: Wed, 31 Oct 2018 10:06:46 +0800 [thread overview]
Message-ID: <cover.1540947083.git.ren_guo@c-sky.com> (raw)
Hi Daniel & Thomas,
I sent you "PATCH V13" a few days ago, but no-reply:
https://lkml.org/lkml/2018/10/29/608
Now I send again.
Although csky subsystem has been merged into linux-4.20, but there is no
timer drivers for csky. A lot of boards need these timer drivers.
Please help merge them into linux-4.20, wait for you reply.
Thx
Guo Ren
Changelog:
- Move changelog to end of patch.
- Remove the set_irq_createmapping call back in csky-mp-intc.c.
- Convert the cpumask to an interrupt-controller specific representation
in driver's code, and not the SMP code's, and also modify the related
codes in csky kernel patchset.
- Add COMPILE_TEST for csky_mp_timer.
- Fixup smp boot error, cpuhp_setup_state must after timer_of_init()
for csky_mp_timer.
Guo Ren (2):
clocksource: add C-SKY SMP timer
clocksource: add gx6605s SOC system timer
drivers/clocksource/Kconfig | 18 ++++
drivers/clocksource/Makefile | 2 +
drivers/clocksource/timer-gx6605s.c | 154 ++++++++++++++++++++++++++++++++
drivers/clocksource/timer-mp-csky.c | 173 ++++++++++++++++++++++++++++++++++++
include/linux/cpuhotplug.h | 1 +
5 files changed, 348 insertions(+)
create mode 100644 drivers/clocksource/timer-gx6605s.c
create mode 100644 drivers/clocksource/timer-mp-csky.c
--
2.7.4
next reply other threads:[~2018-10-31 11:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 2:06 Guo Ren [this message]
2018-10-31 2:06 ` [PATCH V13 1/2] clocksource: add C-SKY SMP timer Guo Ren
2018-10-31 2:06 ` [PATCH V13 2/2] clocksource: add gx6605s SOC system timer Guo Ren
2018-11-02 11:16 ` [PATCH V13 0/2] C-SKY(csky) Timer Driver Daniel Lezcano
2018-11-02 12:17 ` Guo Ren
2018-11-02 15:59 ` Daniel Lezcano
2018-11-02 16:35 ` Guo Ren
2018-11-02 11:17 ` Daniel Lezcano
2018-11-02 11:24 ` Thomas Gleixner
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=cover.1540947083.git.ren_guo@c-sky.com \
--to=ren_guo@c-sky.com \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arch@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;
as well as URLs for NNTP newsgroup(s).