Port-arm archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Interrupt questions



Vincent DEFERT <vincent.defert%posteo.net@localhost> wrote:
> I'm working on an I2C driver for the Meson architecture, which I'm 
> testing on an ODROID C2.
> So far, the driver correctly attaches to the FDT and successfully 
> receives the ioctl from my test program.
> However, it looks like the interrupt handler doesn't get called.
>
> Is calling fdtbus_intr_establish_xname() enough to configure and enable 
> the interrupt, or is there anything else I should do?

That should be enough to configure interrupts, do you see an
"... interrupting on XXX" string in the dmesg?

Do you need it to work in interrupt mode, or would it be enough to
use PIO mode at first?

What is connected to i2c on the Odroid-C2 anyway?

Some of us have that board, so could try out what you have done so far
if that helps.

> Is it legal to call uprintf() inside an interrupt handler?
> If not, is there another way to add traces?

I have only used printf(), it just writes to the console, seems slightly
simpler than uprintf().


Home | Main Index | Thread Index | Old Index