microblaze device-tree description - pair intc/buses and timers

Grant Likely grant.likely at secretlab.ca
Wed Jun 12 19:16:33 EST 2013


On Wed, Jun 12, 2013 at 7:30 AM, Michal Simek <monstr at monstr.eu> wrote:
> On 06/12/2013 12:22 AM, Grant Likely wrote:
>> On Tue, 11 Jun 2013 16:08:11 +0200, Michal Simek <monstr at monstr.eu> wrote:
>> It would mean every device driver needs to be polled. As long as the
>> polling frequency is high enough for the work load then it should be
>> okay. I don't see a problem with there being no interrupt controller,
>> unless there needs to be a dummy one just to keep the kernel happy.
>
> Interesting. I have tried to compile the fragment below by dtc
> and there is no warning. It also means that there is missing checking
> in DTC for interrupt-cells.
>
> What I am worried about is that request_irq in the driver will require
> irq chip functions which there are not.

A driver cannot call request_irq if it doesn't have an irq number to
call it with, and it won't have an IRQ number if there is no irq
specifier in the DT, so you should be fine in that regard.

g.


More information about the devicetree-discuss mailing list