All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Michael Turquette <mturquette@baylibre.com>
Cc: <balbi@ti.com>, Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Nishanth Menon <nm@ti.com>, Thomas Gleixner <tglx@linutronix.de>,
	<linux-rt-users@vger.kernel.org>, Sekhar Nori <nsekhar@ti.com>,
	<linux-clk@vger.kernel.org>
Subject: Re: Common clock framework API vs RT patchset
Date: Wed, 12 Aug 2015 14:08:22 -0500	[thread overview]
Message-ID: <20150812190822.GA20390@saruman.tx.rr.com> (raw)
In-Reply-To: <20150812164649.31346.9236@quantum>

[-- Attachment #1: Type: text/plain, Size: 1980 bytes --]

On Wed, Aug 12, 2015 at 09:46:49AM -0700, Michael Turquette wrote:
> Quoting Felipe Balbi (2015-08-12 08:02:53)
> > On Wed, Aug 12, 2015 at 11:11:51AM +0100, Russell King - ARM Linux wrote:
> > > On Wed, Aug 12, 2015 at 01:05:58PM +0300, Grygorii Strashko wrote:
> > > > On 08/12/2015 01:06 AM, Michael Turquette wrote:
> > > > > Quoting Russell King - ARM Linux (2015-08-11 12:25:15)
> > > > >>
> > > > >> clk_enable/clk_disable _should_ be usable from atomic contexts.
> > > > 
> > > > Thanks Russell - above is not true on -RT.
> > > 
> > > What I'm saying is that it _should_ be true.  You _should_ be able to
> > > call clk_enable()/clk_disable() from atomic contexts.  It's been
> > > documented since forever:
> > > 
> > > /**
> > >  * clk_enable - inform the system when the clock source should be running.
> > >  * @clk: clock source
> > >  *
> > >  * If the clock can not be enabled/disabled, this should return success.
> > >  *
> > >  * May be called from atomic contexts.
> > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > 
> > > /**
> > >  * clk_disable - inform the system when the clock source is no longer required.
> > >  * @clk: clock source
> > >  *
> > >  * Inform the system that a clock source is no longer required by
> > >  * a driver and may be shut down.
> > >  *
> > >  * May be called from atomic contexts.
> > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > 
> > > If that's not true with CCF, that's a CCF bug, not a usage bug.
> > 
> > in that case, CCF's clock need to be converted to raw_spin_locks, that's
> > the only way to prevent its locks from being reimplemented as rt
> > mutexes.
> 
> I do not keep up much with rt stuff, so I am going to ask a naive
> question: is it common to simply do s/spin_lock/raw_spin_lock/g for
> driver subsystems when using rt? Sounds like that is all that is
> required...

depends, if you want to guarantee your code isn't preemptable, then
yeah.

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-08-12 19:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 12:00 Common clock framework API vs RT patchset Grygorii Strashko
2015-08-04 12:06 ` Thomas Gleixner
2015-08-04 15:23   ` Nishanth Menon
2015-08-04 15:36     ` Russell King - ARM Linux
2015-08-11 19:23       ` Grygorii Strashko
2015-08-11 19:25         ` Russell King - ARM Linux
2015-08-11 22:06           ` Michael Turquette
2015-08-11 22:06             ` Michael Turquette
2015-08-12 10:05             ` Grygorii Strashko
2015-08-12 10:11               ` Russell King - ARM Linux
2015-08-12 15:02                 ` Felipe Balbi
2015-08-12 16:46                   ` Michael Turquette
2015-08-12 16:46                     ` Michael Turquette
2015-08-12 19:08                     ` Felipe Balbi [this message]
2015-09-21 13:06       ` Thomas Gleixner
2015-09-21 13:52         ` Russell King - ARM Linux
2015-09-21 16:08           ` Common clock framework API vs RT patchset\ 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=20150812190822.GA20390@saruman.tx.rr.com \
    --to=balbi@ti.com \
    --cc=grygorii.strashko@ti.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mturquette@baylibre.com \
    --cc=nm@ti.com \
    --cc=nsekhar@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.