On 9/8/2011 4:47 PM, Arnd Bergmann wrote:
On Thursday 08 September 2011, Ohad Ben-Cohen wrote:
On Thu, Sep 8, 2011 at 11:07 AM, Cousson, Benoit<b-cous...@ti.com> wrote:
The (small) issue for my point of view is that the #hwspinlock is already
encoded in the IP itself. So adding a baseid directly in DT will look like
duplicating indirectly something that is already there in the HW.
That being said, since we cannot rely on the order, we will not be able to
get the proper baseid until the driver probe every hwspinlock devices :-(
So baseid might be a easier choice.
Sounds good. Thanks a lot !
I think a number would work here but is not optimal for the device tree
representation. I think a better binding would be to encode it like
interrupt numbers, where every device that uses a hwspinlock will describe
that as a combination of phandle to the hwspinlock controller and
identifier to be used by that controller, e.g.
spinlock1 {
compatible = "ti,omap-spinlock";
regs = ...
interrupts =<42>;
interrupt-parent =&irq-controller;
};
dsp {
compatible = ...
regs = ...
spinlocks =<23>; // local number withing&spinlock1;
spinlock-controller =&spinlock1;
};
OK, this is indeed much more aligned with the current practice, and what
DMA should do as well.
Practically speaking, that change will go beyond the original scope of
that patch that was just adding the DT support based on the existing
functionality.
Is it OK to handle that improvement in a further patch / series?
Thanks,
Benoit
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
