From: Mark Rutland <mark.rutland@arm.com>
To: Rob Herring <robherring2@gmail.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>, Bjorn Andersson <bjorn@kryo.se>,
Tim Bird <tbird20d@gmail.com>,
Bjorn Andersson <bjorn.andersson@sonymobile.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <Pawel.Moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>, Suman Anna <s-anna@ti.com>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Jeffrey Hugo <jhugo@codeaurora.org>,
Andy Gross <agross@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kevin Hilman <khilman@linaro.org>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v6 1/2] DT: hwspinlock: Add binding documentation for Qualcomm hwmutex
Date: Thu, 16 Apr 2015 13:01:27 +0100 [thread overview]
Message-ID: <20150416120127.GM2866@leverpostej> (raw)
In-Reply-To: <CAL_Jsq+GhhhoHgRDOkK4=oWtSVmvw=UpLoU-Ey5M7tdNi5OZ2Q@mail.gmail.com>
> The part I'm not clear what the purpose of "pool-hwlock" was.
One use-case was a set of hwlocks having no fixed purpose, and being
available for dynamic allocation between the OS and other entities (e.g.
some RTOS on another core).
The set of locks forming a reusable pool, and any information associated
with them (e.g. the logical IDs used by the other entity) are a property
of that interface rather than the hwlock provider.
So you'd describe those pools of locks in some interface-specific
manner, consuming hwlocks from a set of hwlock providers.
Hopefully that doesn't maek things less clear...
Mark.
next prev parent reply other threads:[~2015-04-16 12:01 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 22:30 [PATCH v6 1/2] DT: hwspinlock: Add binding documentation for Qualcomm hwmutex Bjorn Andersson
2015-02-27 22:30 ` [PATCH v6 2/2] hwspinlock: qcom: Add support for Qualcomm HW Mutex block Bjorn Andersson
2015-03-11 21:09 ` Andy Gross
2015-03-12 19:31 ` Lina Iyer
2015-03-12 19:43 ` Andy Gross
2015-03-12 19:55 ` Lina Iyer
2015-03-18 16:10 ` Bjorn Andersson
2015-03-18 15:55 ` Bjorn Andersson
2015-03-18 16:45 ` Lina Iyer
2015-03-18 21:59 ` Bjorn Andersson
2015-03-12 19:38 ` [PATCH] Lock 7 is cpuidle specific, use non-generic value for locking Lina Iyer
2015-03-12 20:35 ` Stephen Boyd
2015-03-12 20:48 ` Lina Iyer
2015-03-12 21:12 ` Stephen Boyd
2015-03-12 22:16 ` Lina Iyer
2015-03-13 20:02 ` Andy Gross
2015-03-13 21:27 ` Lina Iyer
2015-03-12 20:49 ` Andy Gross
2015-03-12 20:56 ` Lina Iyer
2015-03-12 22:29 ` [PATCH v6 2/2] hwspinlock: qcom: Add support for Qualcomm HW Mutex block Lina Iyer
2015-03-18 16:12 ` Bjorn Andersson
2015-03-18 19:41 ` Lina Iyer
2015-03-16 22:38 ` Jeffrey Hugo
2015-03-02 5:05 ` [PATCH v6 1/2] DT: hwspinlock: Add binding documentation for Qualcomm hwmutex Andy Gross
2015-03-12 9:29 ` Ohad Ben-Cohen
2015-04-01 21:32 ` Tim Bird
2015-04-02 4:40 ` Ohad Ben-Cohen
2015-04-02 18:11 ` Tim Bird
2015-04-03 13:55 ` Ohad Ben-Cohen
2015-04-06 16:22 ` Tim Bird
2015-04-06 16:31 ` Ohad Ben-Cohen
2015-04-06 16:48 ` Bjorn Andersson
2015-04-06 19:04 ` Ohad Ben-Cohen
2015-04-13 10:23 ` Ohad Ben-Cohen
2015-04-15 19:40 ` Rob Herring
2015-04-16 12:01 ` Mark Rutland [this message]
2015-03-12 9:51 ` Mark Rutland
2015-03-12 11:14 ` Bjorn Andersson
2015-03-16 22:35 ` Jeffrey Hugo
2015-04-14 19:18 ` Kumar Gala
2015-04-15 18:20 ` Ohad Ben-Cohen
2015-04-16 11:52 ` Mark Rutland
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=20150416120127.GM2866@leverpostej \
--to=mark.rutland@arm.com \
--cc=Pawel.Moll@arm.com \
--cc=agross@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@sonymobile.com \
--cc=bjorn@kryo.se \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jhugo@codeaurora.org \
--cc=khilman@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.com \
--cc=s-anna@ti.com \
--cc=tbird20d@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox