linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [V1 3/3] RTC: sa1100: support sa1100, pxa and mmp soc families
Date: Fri, 25 Nov 2011 21:14:37 +0100	[thread overview]
Message-ID: <87bos0vu1e.fsf@free.fr> (raw)
In-Reply-To: <1322219217-1866-1-git-send-email-jtzhou@marvell.com> (Jett Zhou's message of "Fri, 25 Nov 2011 19:06:57 +0800")

"Jett.Zhou" <jtzhou@marvell.com> writes:

> Since the regmap of rtc on sa1100, pxa and mmp Marvell soc families are
> almost the same, so re-arch the rtc-sa1100 to support them.
Hi Jett.Zhou,
That's a very good work.

...zip...
>  static int sa1100_rtc_remove(struct platform_device *pdev)
>  {
> -	struct rtc_device *rtc = platform_get_drvdata(pdev);
> +	struct sa1100_rtc *sa1100_rtc = platform_get_drvdata(pdev);
>  
> -	if (rtc)
> -		rtc_device_unregister(rtc);
> +	rtc_device_unregister(sa1100_rtc->rtc);
> +	if (sa1100_rtc->id == RTC_MMP) {
> +		clk_unprepare(sa1100_rtc->clk);
> +		clk_disable(sa1100_rtc->clk);
> +	}
>  
> +	spin_lock_irq(&sa1100_rtc->lock);
> +	iounmap(sa1100_rtc->base);
> +	spin_unlock_irq(&sa1100_rtc->lock);
Why the spin lock here ?

Cheers.

--
Robert

      parent reply	other threads:[~2011-11-25 20:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-25 11:06 [V1 3/3] RTC: sa1100: support sa1100, pxa and mmp soc families Jett.Zhou
2011-11-25 15:05 ` Arnd Bergmann
2011-11-25 16:56   ` Haojian Zhuang
2011-11-25 17:19     ` Arnd Bergmann
2011-11-25 18:42       ` Alessandro Zummo
     [not found]         ` <78895A20B3CF7D49B5589B604D36692B1A00C694BD@SC-VEXCH4.marvell.com>
2011-11-26 20:16           ` Alessandro Zummo
2011-11-28  1:06         ` Haojian Zhuang
2011-11-25 20:14 ` Robert Jarzmik [this message]

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=87bos0vu1e.fsf@free.fr \
    --to=robert.jarzmik@free.fr \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).