On Thu, Nov 20, 2014 at 03:01:33PM -0500, Lennart Sorensen wrote:
> On Wed, Nov 19, 2014 at 11:38:48PM +0100, Gilles Chanteperdrix wrote:
> > I do not know what to say. At software level, it is not really hard
> > to get the I-pipe code to trigger a write to a register when the
> > first RT irq is enabled in a bank and another write when the last RT
> > irq gets disabled, because we keep track of that in the
> > enable_irqdesc/disable_irqdesc callbacks.
>
> Sure, but other power management calls to the hardware is allowed to
> change the register too at any time.
Then we have a problem, because once the irq has been enabled for
Xenomai, it is almost certainly wrong for a power management call to
change its register. So, probably power management should be
disabled like on x86.
> By setting the flag I make sure
> the other calls will NEVER enable smartidle. So making it a dtb option
> means the board maker gets to specify that they want smartidle off for
> a given piece of hardware. I did want to make it only get changed when
> an IRQ was enabled but that was a mess given it is in a totally different
> part of the code.
Yes that I what I meant, getting back the pointer to the structure
needed by the hwmod layer is going to be hard, since this pointer is
well hidden under the carpet.
Anyway, if anyone wants a better solution, he will implement it, I
will merge your patch in the current version of the I-pipe patch
(3.16.0).
--
Gilles.
_______________________________________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/mailman/listinfo/xenomai
