All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: "Que, Simon" <sque@ti.com>, LKML <linux-kernel@vger.kernel.org>
Cc: "Kanigeri, Hari" <h-kanigeri2@ti.com>,
	Linux Omap <linux-omap@vger.kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
	"Cousson, Benoit" <b-cousson@ti.com>
Subject: linux hardware spinlock framework for heterogeneous processor SOCs?
Date: Wed, 11 Aug 2010 21:02:12 -0500	[thread overview]
Message-ID: <4C635624.1090407@ti.com> (raw)
In-Reply-To: <F39349C6FA641B4A831B7BF4EBF4D4E1480D9D14@dlee03.ent.ti.com>

Changing subject, the original thread is at [1], looping in lkml for a 
wider audience for advice.

Que, Simon had written, on 08/11/2010 05:03 PM, the following:
>> just a curious question:
>>
>> Is there no h/w spinlock implementation for other architectures in
>> linux? I mean the concept does not seem unique for a heterogenous
>> processor environments now a days.. if it does exist, maybe we have two
>> options:
>> * extend standard spinlock architecture to handle h/w spinlocks as well
>> * establish a new framework for h/w spinlocks..
>>
> 
> Thank you for bringing that to my attention.  I did a quick search and
 > haven't found any hwspinlock module elsewhere.  But should there be
 > hwspinlocks over multiple architectures in the future, we can definitely
 > consider something like the two solutions that you suggested, so that
 > they can be used from platform-independent kernel code.  However, right
 > now we can develop OMAP hwspinlock independently of that.

I did glance through the kernel commit log, and nothing remotely seems 
to match up at least in my opinion (closest seemed to be [2] 
drivers/gpu/drm/ - but it did not seem relevant here). If this concept 
is unique to OMAP family alone, then I guess it makes sense to introduce 
SOC specific API library for usage. hoping for some suggestions to 
enlighten us.

Ref:
[1] http://marc.info/?t=127955774200003&r=1&w=2
[2] http://dri.sourceforge.net/doc/hardware_locking_low_level.html

-- 
Regards,
Nishanth Menon

  reply	other threads:[~2010-08-12  2:02 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19 16:50 [PATCH 0/5] omap:hwspinlock support-omap4 Hari Kanigeri
2010-07-19 16:50 ` [PATCH 1/5] omap:hwmod-hwspinlock-enable Hari Kanigeri
2010-07-27 15:57   ` Premi, Sanjeev
2010-07-27 16:05     ` Cousson, Benoit
2010-07-19 16:50 ` [PATCH 2/5] omap:hwspinlock-define HWSPINLOCK base address Hari Kanigeri
2010-07-27 15:59   ` Premi, Sanjeev
2010-07-27 16:50     ` Kanigeri, Hari
2010-07-28 14:11       ` Premi, Sanjeev
2010-07-28 14:22         ` Kanigeri, Hari
2010-07-28 14:33           ` Premi, Sanjeev
2010-07-28 14:55             ` Kanigeri, Hari
2010-07-19 16:50 ` [PATCH 3/5] omap:hwspinlock-added hwspinlock driver Hari Kanigeri
2010-07-24 16:43   ` Cousson, Benoit
2010-07-26 20:39     ` Kanigeri, Hari
2010-07-28 16:58   ` Premi, Sanjeev
2010-07-29  4:56     ` Marathe, Yogesh
2010-07-29 13:14       ` Kanigeri, Hari
2010-07-29 13:23         ` Cousson, Benoit
2010-07-30  6:53         ` Marathe, Yogesh
2010-08-02  1:55           ` Kanigeri, Hari
2010-07-29 13:29     ` Kanigeri, Hari
2010-07-29 14:05   ` Nishanth Menon
2010-08-11 22:03     ` Que, Simon
2010-08-12  2:02       ` Nishanth Menon [this message]
2010-07-19 16:50 ` [PATCH 4/5] omap:hwspinlock-add build support Hari Kanigeri
2010-07-19 16:50 ` [PATCH 5/5] omap:hwspinlocks-ensure the order of registration Hari Kanigeri
2010-07-28 17:00   ` Premi, Sanjeev
2010-07-28 17:05     ` Kanigeri, Hari
2010-07-20  5:37 ` [PATCH 0/5] omap:hwspinlock support-omap4 Shilimkar, Santosh
2010-07-20 14:12   ` Kanigeri, Hari
2010-07-24 15:04     ` Cousson, Benoit
2010-07-24 15:35       ` Shilimkar, Santosh
2010-07-24 15:47         ` Cousson, Benoit

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=4C635624.1090407@ti.com \
    --to=nm@ti.com \
    --cc=b-cousson@ti.com \
    --cc=h-kanigeri2@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@ti.com \
    --cc=sque@ti.com \
    --cc=tony@atomide.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 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.