RPi warnings regarding irq enable
The IO Pi Plus is a 32 channel MCP23017 GPIO expander for the Raspberry Pi
31/05/2024
Posted by:
Erik63
Hello, I have an IO Pi Plus, and I am getting constant warnings filling my logs with:
WARNING: CPU: 0 PID: 451 at drivers/gpio/gpiolib.c:3367 gpiochip_enable_irq+0x84/0xa4
If I comment the overlay out of the /usr/config.txt they go away to I can tell it is the expander. Anyone seen this before. I have not been able to find anything in my searches.
Thanks!
WARNING: CPU: 0 PID: 451 at drivers/gpio/gpiolib.c:3367 gpiochip_enable_irq+0x84/0xa4
If I comment the overlay out of the /usr/config.txt they go away to I can tell it is the expander. Anyone seen this before. I have not been able to find anything in my searches.
Thanks!
31/05/2024
Posted by:
Erik63
I did find out I could stop the warnings if I disable interrupts with the noints parameter for dtoverlay
31/05/2024
Posted by:
andrew
Hello
This is not a problem I have seen before. Are you using one of our software libraires to access the IO Pi Plus or the mcp23017 dtoverlay?
If you are using the dtoverlay do you have any other hats or devices on the GPIO header that may be conflicting with the pins for the mcp23017?
This is not a problem I have seen before. Are you using one of our software libraires to access the IO Pi Plus or the mcp23017 dtoverlay?
If you are using the dtoverlay do you have any other hats or devices on the GPIO header that may be conflicting with the pins for the mcp23017?
31/05/2024
Posted by:
Erik63
Hi,
I am using the Raspberry Pi mcp23017 overlay. No, the IO PI plus is the only hat and no other devices. Note that with:
dtoverlay=mcp23017,addr=0x20,noints
dtoverlay=mcp23017,addr=0x21,noints
the problem goes away, of course I have no interrupts, which was ok for me since I am not using these GPIOs as inputs.
I am using the Raspberry Pi mcp23017 overlay. No, the IO PI plus is the only hat and no other devices. Note that with:
dtoverlay=mcp23017,addr=0x20,noints
dtoverlay=mcp23017,addr=0x21,noints
the problem goes away, of course I have no interrupts, which was ok for me since I am not using these GPIOs as inputs.
31/05/2024
Posted by:
andrew
It could be a conflict in the mcp23017 overlay when using two instances with interrupts. I found this thread on GitHub which mentions a problem with using multiple mcp23017 overlay and recommends disabling the interrupts. The thread is from 2019 but it looks like the problem hasn't been fixed yet.
31/05/2024
Posted by:
Erik63
Yes, interrupt disabling is the only thing that worked for me, the Warnings recorded by the /var/logs (syslog, kern.log, message) were filling by 5G per day and the massive writes to the uSD card would have killed it. I tried adding names to the GPIO pins in the driver overlay, but that did not work. Patching the mcp23017 kernel
23/08/2024
Posted by:
chitramishra
Hello,
As per my knowledge, the issue seems related to how the overlay interacts with the GPIO system. Disabling the overlay in the /usr/config.txt file seems to prevent the warnings, so the expander is likely the source. Others might have encountered this, but it might be worth checking if there's an updated driver or a different overlay configuration that could resolve the issue.
I hope this will help you!
As per my knowledge, the issue seems related to how the overlay interacts with the GPIO system. Disabling the overlay in the /usr/config.txt file seems to prevent the warnings, so the expander is likely the source. Others might have encountered this, but it might be worth checking if there's an updated driver or a different overlay configuration that could resolve the issue.
I hope this will help you!
Note: documents in Portable Document Format (PDF) require Adobe Acrobat Reader 5.0 or higher to view.
Download Adobe Acrobat Reader or other PDF reading software for your computer or mobile device.
