Hi Ohad,
On 07/04/2014 12:01 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, Jul 3, 2014 at 8:28 PM, Suman Anna s-a...@ti.com wrote:
OK, but we would still require this function to lookup the registered
device from the controller-phandle to retrieve the base_id.
Can we retrieve the base_id
Hi Suman,
On Thu, Jul 3, 2014 at 12:14 AM, Suman Anna s-a...@ti.com wrote:
I'm not sure we need this patch.
This patch is needed if we use the controller-phandle + args specifier
for requesting hwlocks by a client, as we need to translate
controller-phandle to the corresponding
Hi Ohad,
On 07/03/2014 02:00 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, Jul 3, 2014 at 12:14 AM, Suman Anna s-a...@ti.com wrote:
I'm not sure we need this patch.
This patch is needed if we use the controller-phandle + args specifier
for requesting hwlocks by a client, as we need to
Hi Suman,
On Thu, Jul 3, 2014 at 8:28 PM, Suman Anna s-a...@ti.com wrote:
OK, but we would still require this function to lookup the registered
device from the controller-phandle to retrieve the base_id.
Can we retrieve the base_id from the parent DT node itself?
Thanks,
Ohad.
--
To
Hi Ohad,
On 07/01/2014 07:26 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, May 1, 2014 at 3:34 AM, Suman Anna s-a...@ti.com wrote:
The hwspinlock_device structure is used for registering a bank of
locks with the driver core. The structure already contains the
necessary members to identify
Hi Suman,
On Thu, May 1, 2014 at 3:34 AM, Suman Anna s-a...@ti.com wrote:
The hwspinlock_device structure is used for registering a bank of
locks with the driver core. The structure already contains the
necessary members to identify the bank of locks. The core does not
maintain the
The hwspinlock_device structure is used for registering a bank of
locks with the driver core. The structure already contains the
necessary members to identify the bank of locks. The core does not
maintain the hwspinlock_devices itself, but maintains only a radix
tree for all the registered locks.
