linux-kernel - Re: [PATCH] hwspinlock/msm: Add support for Qualcomm MSM HW Mutex block

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <9BC13262-0803-4790-B1B5-0B46F7DB8D30@codeaurora.org>
Date:	Mon, 12 Aug 2013 12:24:28 -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 10, 2013, at 2:11 PM, Ohad Ben-Cohen wrote:

> + Grant
> 
> On Thu, Aug 1, 2013 at 5:10 PM, Kumar Gala <galak@...eaurora.org> wrote:
>>> On Jul 29, 2013, at 4:40 PM, Stephen Boyd wrote:
>>>> On 07/29, Kumar Gala wrote:
>>>>>> diff --git a/Documentation/devicetree/bindings/arm/msm/tcsr-mutex.txt b/Documentation/devicetree/bindings/arm/msm/tcsr-mutex.txt
>>>>>> new file mode 100644
>>>>>> index 0000000..ddd6889
>>>>>> --- /dev/null
>>>>>> +++ b/Documentation/devicetree/bindings/arm/msm/tcsr-mutex.txt
>>>> 
>>>> Maybe this should go under a new hwspinlock directory?
>>> 
>>> Will look for Ohad to comment on this.
>>> 
>>>> 
>>>>>> @@ -0,0 +1,20 @@
>>>>>> +Qualcomm MSM Hardware Mutex Block:
>>>>>> +
>>>>>> +The hardware block provides mutexes utilized between different processors
>>>>>> +on the SoC as part of the communication protocol used by these processors.
>>>>>> +
>>>>>> +Required properties:
>>>>>> +- compatible: should be "qcom,tcsr-mutex"
>>>>>> +- reg: Should contain registers location and length of mutex registers
>>>>>> +- reg-names:
>>>>>> +  "mutex-base"  - string to identify mutex registers
>>>>>> +- qcom,num-locks: the number of locks/mutexes supported
>>>>>> +
>>>>>> +Example:
>>>>>> +
>>>>>> +  qcom,tcsr-mutex@...84000 {
>>>> 
>>>> Maybe it should be hw-mutex@...84000?
>>> 
>>> again, will look for Ohad to make some comment on this.
>>> 
>>>>>> +          compatible = "qcom,tcsr-mutex";
>>>>>> +          reg = <0xfd484000 0x1000>;
>>>>>> +          reg-names = "mutex-base";
>>>>>> +          qcom,num-locks = <32>;
>>>>>> +  };
>> 
>> Ohad, ping.
> 
> I'd prefer a DT maintainer to take a look at your two open questions
> above, especially if I'm to merge a new file into the devicetree
> Documentation folder.
> 
> Grant, any chance you have a moment to take a look?
> 
> Otherwise, Stephen - do we have your Ack here? I was happy to see your
> review but not sure what's the latest status.
> 
> Thanks,
> Ohad.
> --

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?

- 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/