From: Boris BREZILLON <b.brezillon@overkiz.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Boris BREZILLON <b.brezillon@overkiz.com>
Subject: [PATCH 0/3] ARM: at91/tc/clocksource: various robustness improvements
Date: Wed, 2 Oct 2013 14:34:25 +0200 [thread overview]
Message-ID: <1380717265-6497-1-git-send-email-b.brezillon@overkiz.com> (raw)
Hello,
This series include several improvements regarding the at91 tc clocksource
driver:
- use clk_prepare/unprepare_enable/disable functions instead of the
clk_enable/disable functions to prepare the transition to the common clk
framework
- check several function return values instead of considering these functions
always suceed.
- remove the deprecated IRQF_DISABLED flag
Best Regards,
Boris
Boris BREZILLON (3):
ARM: at91/tc/clocksource: replace clk_enable/disable with
clk_prepare_enable/disable_unprepare
ARM: at91/tc/clocksource: improve driver robustness
ARM: at91/tc/clocksource: remove IRQF_DISABLED
drivers/clocksource/tcb_clksrc.c | 61 +++++++++++++++++++++++++++++++-------
1 file changed, 50 insertions(+), 11 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-10-02 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 12:34 Boris BREZILLON [this message]
2013-10-02 12:34 ` [PATCH 1/3] ARM: at91/tc/clocksource: replace clk_enable/disable with clk_prepare_enable/disable_unprepare Boris BREZILLON
2013-10-02 12:35 ` Boris BREZILLON
2013-10-02 12:35 ` [PATCH 2/3] ARM: at91/tc/clocksource: improve driver robustness Boris BREZILLON
2013-10-02 12:47 ` Nicolas Ferre
2013-10-02 12:35 ` [PATCH 3/3] ARM: at91/tc/clocksource: remove IRQF_DISABLED Boris BREZILLON
2013-10-02 12:47 ` Nicolas Ferre
2013-10-03 14:31 ` [PATCH 0/3] ARM: at91/tc/clocksource: various robustness improvements 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=1380717265-6497-1-git-send-email-b.brezillon@overkiz.com \
--to=b.brezillon@overkiz.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--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®