Hi Suman,
On Wed, Nov 12, 2014 at 9:32 PM, Suman Anna <s-anna@xxxxxx> wrote:
>> Is this the validation you mentioned which requires the existence of
>> "hwspinlock/core: maintain a list of registered hwspinlock banks" ?
>
> Well, not exactly. The validation is on the following segment,
>
> + id = of_hwspin_lock_simple_xlate(bank, &args);
> + if (id < 0 || id >= bank->num_locks) {
> + ret = -EINVAL;
> + goto out;
> + }
I'm not entirely convinced that this justifies adding the proposed
linked list. Can't we can get the base_id and number of locks by
traversing the DT?
> That said, it is also needed to provide the support for deferred probing
> without changing the return code conventions on the existing API.
Here too, adding a data structure maintaining memory objects and
taking care of it life cycle seems a bit overkill for anything to do
with return values.
> Yes, and wouldn't that require that the id is validated? It just cannot
> return any return value, and expect it will be verified somewhere else
> or in a following API call. Not doing the validation unnecessarily
> complicates the system usage of a lock as you are sharing an invalid
> lock to a remote processor and then you have two validation failure
> paths on different processors.
Validation is great but I'm still not convinced it can't be done
without maintaining another data structure.
Please show me specific technical issues that can't be resolved
without adding the proposed linked list.
Thanks,
Ohad.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
