From: Ohad Ben-Cohen <ohad@wizery.com>
To: Andy Gross <agross@codeaurora.org>
Cc: Lina Iyer <lina.iyer@linaro.org>,
Bjorn Andersson <bjorn.andersson@sonymobile.com>,
Jeffrey Hugo <jhugo@codeaurora.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC v2 0/2] hwspinlock: Introduce raw capability for hwspinlock_device
Date: Fri, 14 Aug 2015 13:52:28 +0300 [thread overview]
Message-ID: <CAK=WgbZdO==vmDNh5=E=th9+O_08aUtXSn5hy=kEgja9-GikGg@mail.gmail.com> (raw)
In-Reply-To: <20150813152508.GA4627@qualcomm.com>
On Thu, Aug 13, 2015 at 6:25 PM, Andy Gross <agross@codeaurora.org> wrote:
> The issue in hardwiring this into the driver itself means forfeiting
> extensibility. So on one side (w/ raw support), we get the ability to deal with
> the lock number changing. On the other side (w/o raw), we'd have to probably
> tie this to chip compat to figure out which lock is the 'special' if it ever
> changes.
It sounds like the decision "which lock to use" is a separate problem
from "can it go raw".
If the hardware doesn't prohibit raw mode, then every lock can be used
in raw mode. So you just have to pick one and make sure both sides
know which lock you use --- which is a classic multi-processor
synchronization issue.
> It's arbitrary right now. The remote processor selected a number, not the
> processor running Linux.
Is the number hardcoded right now? and you're using
hwspin_lock_request_specific on the Linux side to acquire the lock?
next prev parent reply other threads:[~2015-08-14 10:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 16:23 [PATCH RFC v2 0/2] hwspinlock: Introduce raw capability for hwspinlock_device Lina Iyer
2015-06-09 16:23 ` [PATCH RFC v2 1/2] hwspinlock: Introduce raw capability for hwspinlocks Lina Iyer
2015-06-09 16:59 ` Jeffrey Hugo
2015-06-09 16:23 ` [PATCH RFC v2 2/2] hwspinlock: qcom: Lock #7 is special lock, uses dynamic proc_id Lina Iyer
2015-06-10 17:33 ` Bjorn Andersson
2015-06-10 20:13 ` Lina Iyer
2015-06-27 3:05 ` [PATCH RFC v2 0/2] hwspinlock: Introduce raw capability for hwspinlock_device Lina Iyer
2015-06-27 11:25 ` Ohad Ben-Cohen
2015-07-02 20:30 ` Lina Iyer
2015-07-18 11:31 ` Ohad Ben-Cohen
2015-07-28 21:51 ` Lina Iyer
2015-08-13 6:34 ` Ohad Ben-Cohen
2015-08-13 15:25 ` Andy Gross
2015-08-14 10:52 ` Ohad Ben-Cohen [this message]
2015-08-14 13:52 ` Lina Iyer
2015-08-14 15:24 ` Lina Iyer
2015-09-20 13:02 ` Ohad Ben-Cohen
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='CAK=WgbZdO==vmDNh5=E=th9+O_08aUtXSn5hy=kEgja9-GikGg@mail.gmail.com' \
--to=ohad@wizery.com \
--cc=agross@codeaurora.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=jhugo@codeaurora.org \
--cc=lina.iyer@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).