[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <B26378B6-0E26-4EBA-A016-854EF2E01F1B@codeaurora.org>
Date: Tue, 13 Aug 2013 08:58:18 -0500
From: Kumar Gala <galak@...eaurora.org>
To: Ohad Ben-Cohen <ohad@...ery.com>
Cc: Grant Likely <grant.likely@...retlab.ca>,
"linux-kernel@...r.kernel.org list" <linux-kernel@...r.kernel.org>,
"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
devicetree@...r.kernel.org, Jeffrey Hugo <jhugo@...eaurora.org>,
Stephen Boyd <sboyd@...eaurora.org>,
Eric Holmberg <eholmber@...eaurora.org>
Subject: Re: [PATCH] hwspinlock/msm: Add support for Qualcomm MSM HW Mutex block
On Aug 13, 2013, at 1:01 AM, Ohad Ben-Cohen wrote:
> On Mon, Aug 12, 2013 at 8:24 PM, Kumar Gala <galak@...eaurora.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists