optimsoc/Lobby

OpTiMSoC main chat

Pedro Henrique Penna

@ppenna

ok...

Stefan Wallentowitz

@wallento

its easier to discuss such things here I think

Pedro Henrique Penna

@ppenna

thanks

Stefan Wallentowitz

@wallento

Pedro Henrique Penna

@ppenna

yeah....

ok... I'll ping you

thanks for the help

Stefan Wallentowitz

@wallento

you are welcome

Pedro Henrique Penna

@ppenna

@wallento where exactly in the verilog code I van check the IRQ num that se are using?

Stefan Wallentowitz

@wallento

https://github.com/optimsoc/optimsoc/commit/054c6e358b31145a609ae42f54e38e63e0b6db78#diff-f0fcb5f6e25cb0375cb08f8400208b1fL622

Pedro Henrique Penna

@ppenna

thanks

Pedro Henrique Penna

@ppenna

I have pushed mu code...

https://github.com/cart-pucminas/bluedragon/commits/master

*my

I'm having a weird problem, in which the driver does not load oftentimes

whenever I register the interrupt handler

Ghost

@ghost~5910ddcfd73408ce4f5dfa87

@ppenna what do you mean doesnt load, the interrupt handler is registered when the driver loads.

do you mean the interrupt handler register hangs?

Pedro Henrique Penna

@ppenna

https://github.com/ppenna/linux/blob/2bfd7bdcc7cc8786f93234b7c014b99b66fcc356/drivers/char/optimsoc-noc.c#L361

once I register the interrupt handler, the system freezes

the boot sequence does not proceed

if I use the right IRQ (no. 4)

however, if I build the module using the bad IRQ (no. 3) ir boots fine

Ghost

@ghost~5910ddcfd73408ce4f5dfa87

I see, well, maybe the itnerrupt handler is getting called and then not returning?

Pedro Henrique Penna

@ppenna

however, I'm obviously not able to receive right interrupts

I have put a printf there

*printk

and it nothing is printed on the screen

it's kind, the interrupt handler does not get called

or something...

Ghost

@ghost~5910ddcfd73408ce4f5dfa87

ok, maybe its related to the change you made about the -level setting for the interrupt handler?

Pedro Henrique Penna

@ppenna

I was thinking about spurious interrupts

what do you mean level setting?

Ghost

@ghost~5910ddcfd73408ce4f5dfa87

is there any way you can print out the interrupt level before you call register?

Pedro Henrique Penna

@ppenna

I changed nothing

I don't know... how would you normally do that?

https://github.com/ppenna/linux/blob/2bfd7bdcc7cc8786f93234b7c014b99b66fcc356/drivers/char/optimsoc-noc.c#L346

I'm registering IRQ 4 as IRQF_SHARED | IRQF_TRIGGER_HIGH;

Ghost

@ghost~5910ddcfd73408ce4f5dfa87

Well... I mean this line in DTS...
https://github.com/ppenna/linux/blob/2bfd7bdcc7cc8786f93234b7c014b99b66fcc356/arch/openrisc/boot/dts/optimsoc.dts#L33

Pedro Henrique Penna

@ppenna

maybe this is not good

Ghost

@ghost~5910ddcfd73408ce4f5dfa87

it says -level...

Pedro Henrique Penna

@ppenna

so I assume that I'm registering the handler correctly

because

IRQF_SHARED | IRQF_TRIGGER_HIGH;

am I wrong?

Ghost

@ghost~5910ddcfd73408ce4f5dfa87

Here is a simple example we have of the ompic

https://github.com/stffrdhrn/linux/blob/openrisc-4.13-smp-qspinlock/drivers/irqchip/irq-ompic.c

Pedro Henrique Penna

@ppenna

am I registering the interrupt handler wrong?

Ghost

@ghost~5910ddcfd73408ce4f5dfa87

        int irq;

        irq = irq_of_parse_and_map(node, 0);
        setup_irq(irq, &ompi_ipi_irqaction);

It looks ok at first glance, but a bit more complicated, I am nost sure you need those flags too i.e. why are you doing 'IRQF_TRIGGER_HIGH'? Is it opposite normal?

Where communities thrive

People

Repo info

Activity