linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xiaofei Tan <tanxiaofei@huawei.com>
To: <a.zummo@towertech.it>, <alexandre.belloni@bootlin.com>
Cc: Xiaofei Tan <tanxiaofei@huawei.com>, <linux-rtc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>
Subject: [PATCH 0/6] spin lock usage optimization for RTC drivers
Date: Wed, 3 Feb 2021 20:39:35 +0800	[thread overview]
Message-ID: <1612355981-6764-1-git-send-email-tanxiaofei@huawei.com> (raw)

Replace spin_lock_irqsave with spin_lock in hard IRQ of RTC drivers.
There is no function changes, but may speed up if interrupt happen
too often.

Xiaofei Tan (6):
  rtc: cmos: Replace spin_lock_irqsave with spin_lock in hard IRQ
  rtc: pm8xxx: Replace spin_lock_irqsave with spin_lock in hard IRQ
  rtc: r7301: Replace spin_lock_irqsave with spin_lock in hard IRQ
  rtc: tegra: Replace spin_lock_irqsave with spin_lock in hard IRQ
  rtc: mxc: Replace spin_lock_irqsave with spin_lock in hard IRQ
  rtc: mxc_v2: Replace spin_lock_irqsave with spin_lock in hard IRQ

 drivers/rtc/rtc-cmos.c   | 5 ++---
 drivers/rtc/rtc-mxc.c    | 5 ++---
 drivers/rtc/rtc-mxc_v2.c | 7 +++----
 drivers/rtc/rtc-pm8xxx.c | 9 ++++-----
 drivers/rtc/rtc-r7301.c  | 5 ++---
 drivers/rtc/rtc-tegra.c  | 6 +++---
 6 files changed, 16 insertions(+), 21 deletions(-)

-- 
2.8.1


             reply	other threads:[~2021-02-03 12:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03 12:39 Xiaofei Tan [this message]
2021-02-03 12:39 ` [PATCH 1/6] rtc: cmos: Replace spin_lock_irqsave with spin_lock in hard IRQ Xiaofei Tan
2021-02-03 12:39 ` [PATCH 2/6] rtc: pm8xxx: " Xiaofei Tan
2021-02-03 12:39 ` [PATCH 3/6] rtc: r7301: " Xiaofei Tan
2021-02-03 12:39 ` [PATCH 4/6] rtc: tegra: " Xiaofei Tan
2021-02-03 12:39 ` [PATCH 5/6] rtc: mxc: " Xiaofei Tan
2021-02-03 12:39 ` [PATCH 6/6] rtc: mxc_v2: " Xiaofei Tan
2021-02-05 23:52 ` [PATCH 0/6] spin lock usage optimization for RTC drivers Alexandre Belloni

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=1612355981-6764-1-git-send-email-tanxiaofei@huawei.com \
    --to=tanxiaofei@huawei.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    /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).