It is redundant to do irqsave and irqrestore in hardIRQ context, where
it has been in a irq-disabled context.

Signed-off-by: Xiaofei Tan <tanxiao...@huawei.com>
---
 drivers/rtc/rtc-tegra.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/rtc/rtc-tegra.c b/drivers/rtc/rtc-tegra.c
index 8925015..85f7ad5 100644
--- a/drivers/rtc/rtc-tegra.c
+++ b/drivers/rtc/rtc-tegra.c
@@ -232,7 +232,7 @@ static irqreturn_t tegra_rtc_irq_handler(int irq, void 
*data)
 {
        struct device *dev = data;
        struct tegra_rtc_info *info = dev_get_drvdata(dev);
-       unsigned long events = 0, flags;
+       unsigned long events = 0;
        u32 status;
 
        status = readl(info->base + TEGRA_RTC_REG_INTR_STATUS);
@@ -240,10 +240,10 @@ static irqreturn_t tegra_rtc_irq_handler(int irq, void 
*data)
                /* clear the interrupt masks and status on any IRQ */
                tegra_rtc_wait_while_busy(dev);
 
-               spin_lock_irqsave(&info->lock, flags);
+               spin_lock(&info->lock);
                writel(0, info->base + TEGRA_RTC_REG_INTR_MASK);
                writel(status, info->base + TEGRA_RTC_REG_INTR_STATUS);
-               spin_unlock_irqrestore(&info->lock, flags);
+               spin_unlock(&info->lock);
        }
 
        /* check if alarm */
-- 
2.8.1

Reply via email to