Benjamin Herrenschmidt wrote:
Now, in addition to that, we have another issue I haven't spotted
before, but it might be worth considering:
Do we actually want the sdma interrupts handled there ? Because if you
look closely, the SDMA is basically a cascaded interrupt controller. It
hangs of per interrupt 0 :)
I know. I already spot this point (IRQ as far as I remenber and in
private mails) and I got no answer so I assumed it was ok like I did.
It's also really simplier and easier to add SDMA has another irq_chip.
Keep is simple ;-)
Thus we could simply remove the code for it from that driver and
implement it as as separate controller with a separate interrupt domain.
I know you won't like that idea because it means having a different
interrupt tree but it's worth having the discussion.
The device tree won't change anyway...
I'll submit a new buch of patches pretty soon. Maybe the final version.
"On y est presque !" ;-)
Regards
begin:vcard
fn:Nicolas DET ( bplan GmbH )
n:DET;Nicolas
org:bplan GmbH
adr:;;;;;;Germany
email;internet:[EMAIL PROTECTED]
title:Software Entwicklung
tel;work:+49 6171 9187 - 31
x-mozilla-html:FALSE
url:http://www.bplan-gmbh.de
version:2.1
end:vcard
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
