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: <0A09DA0F-86B4-4961-88E2-64FA0A4D380D@codeaurora.org>
Date:	Thu, 1 Aug 2013 09:10:30 -0500
From:	Kumar Gala <galak@...eaurora.org>
To:	Ohad Ben-Cohen <ohad@...ery.com>
Cc:	"linux-kernel@...r.kernel.org list" <linux-kernel@...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 Jul 29, 2013, at 4:54 PM, Kumar Gala 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.

- 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

Powered by Openwall GNU/*/Linux Powered by OpenVZ