From: Kumar Gala <galak@codeaurora.org>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
"linux-kernel@vger.kernel.org list"
<linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
devicetree@vger.kernel.org, Jeffrey Hugo <jhugo@codeaurora.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Eric Holmberg <eholmber@codeaurora.org>
Subject: Re: [PATCH] hwspinlock/msm: Add support for Qualcomm MSM HW Mutex block
Date: Tue, 13 Aug 2013 08:58:18 -0500 [thread overview]
Message-ID: <B26378B6-0E26-4EBA-A016-854EF2E01F1B@codeaurora.org> (raw)
In-Reply-To: <CAK=WgbbdY-uZjiO2KBsYGshagykcL0X8PYEByb9K-Wp5R5g+hQ@mail.gmail.com>
On Aug 13, 2013, at 1:01 AM, Ohad Ben-Cohen wrote:
> On Mon, Aug 12, 2013 at 8:24 PM, Kumar Gala <galak@codeaurora.org> wrote:
>> So I think I'd ask you to recommend a name, should we just us 'hwspinlock'. The general view from ePAPR and dts is the node name should be a bit more generic (like ethernet or pci). So what would you suggest?
>
> How about 'hwlock' ?
>
> This should be generic enough to cover all instances of hardware locks
> (we already know hwspinlock isn't generic enough, as there are some
> mutex-like hardware locks which doesn't require busy looping).
hwlock sounds good to me, I'll go with it.
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
prev parent reply other threads:[~2013-08-13 13:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 20:11 Kumar Gala
2013-07-29 20:14 ` Kumar Gala
2013-07-29 21:40 ` Stephen Boyd
2013-07-29 21:54 ` Kumar Gala
2013-07-30 0:28 ` Stephen Boyd
2013-08-01 14:10 ` Kumar Gala
2013-08-10 19:11 ` Ohad Ben-Cohen
2013-08-12 16:30 ` Stephen Boyd
2013-08-12 17:00 ` Kumar Gala
2013-08-12 17:24 ` Kumar Gala
2013-08-13 6:01 ` Ohad Ben-Cohen
2013-08-13 13:58 ` Kumar Gala [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=B26378B6-0E26-4EBA-A016-854EF2E01F1B@codeaurora.org \
--to=galak@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=eholmber@codeaurora.org \
--cc=grant.likely@secretlab.ca \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=sboyd@codeaurora.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
all inboxes | Powered by JetHome®