Hi Ohad,
On 07/03/2014 11:58 PM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, Jul 3, 2014 at 8:35 PM, Suman Anna s-a...@ti.com wrote:
Not at the moment, with the existing platform implementations. So, if I
understand you correctly, you are asking to leave out the xlate ops and
make the
Hi Suman,
On Thu, Jul 3, 2014 at 12:14 AM, Suman Anna s-a...@ti.com wrote:
Do we have a use case today that require the xlate() method?
If not, let's remove it as we could always add it back if some new
hardware shows up that needs it.
The xlate() method is to support the phandle + args
Hi Ohad,
On 07/03/2014 02:15 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, Jul 3, 2014 at 12:14 AM, Suman Anna s-a...@ti.com wrote:
Do we have a use case today that require the xlate() method?
If not, let's remove it as we could always add it back if some new
hardware shows up that needs
Hi Suman,
On Thu, Jul 3, 2014 at 8:35 PM, Suman Anna s-a...@ti.com wrote:
Not at the moment, with the existing platform implementations. So, if I
understand you correctly, you are asking to leave out the xlate ops and
make the of_hwspin_lock_simple_xlate() internal until a need for an
xlate
Hi Ohad,
On Thu, May 1, 2014 at 3:34 AM, Suman Anna s-a...@ti.com wrote:
2. The of_hwspin_lock_simple_xlate() is a simple default
translator function for hwspinlock provider implementations
that use a single cell number for requesting a specific lock
(relatively indexed) within a
Hi Suman,
On Thu, May 1, 2014 at 3:34 AM, Suman Anna s-a...@ti.com wrote:
2. The of_hwspin_lock_simple_xlate() is a simple default
translator function for hwspinlock provider implementations
that use a single cell number for requesting a specific lock
(relatively indexed) within a
This patch adds three new OF helper functions to use/request
locks from a hwspinlock device instantiated through a
device-tree blob.
1. The of_hwspin_lock_get_num_locks() is a common helper
function to read the common 'hwlock-num-locks' property.
2. The of_hwspin_lock_simple_xlate() is a