The enable_irq unbalanced messages are harmless. It just means that when the driver called disable_irq there were no devices already using the irq, and as such it was already disabled, so the call to disable_irq was forgotten by the kernel, so when we call enable_irq the core kernel cod...
The enable_irq unbalanced messages are harmless. It just means that when the driver called disable_irq there were no devices already using the irq, and as such it was already disabled, so the call to disable_irq was forgotten by the kernel, so when we call enable_irq the core kernel cod...
> > i have this problem that the kernel says "enable_irq(some_number) > > unbalaced". what does it mean? > > i tried to google but haven't found any clear hint. > > I'd say that it happens if you called enable_irq() two times without > calling disable_irq() in-between. ...
space/builder/repo/sprdroid6.0_trunk_k318_dev/kernel/kernel/irq/manage.c:444 __enable_irq+0x50/0x94() Unbalanced...unsigned int irq) { switch (desc->depth) { case 0: err_out: WARN(1, KERN_WARNING "Unbalanced...SyS_ioct->do_vfs_ioctl->spidev_ioctl->enable_irq->__enable_irq ...
> unbalanced pm_runtime_enable. Let's fix this. Note that we > need to do this after the child musb-core platform_device is > removed because of pm_runtime_irq_safe being set at the child. > > Cc: Bin Liu > Cc: Felipe Balbi...