drivers/ioexpander/iso1i813t.c: fix error startup condition - #19571
Merged
Conversation
The reference manual (section 3.2.1) states the user has to read GLERR and INTERR registers to clear their bits and release ERR pin after the startup sequence. Error bits are set to 1 after the startup if external power supply is used. Not clearing the bits leads to subsequent read call errors if VBB errors are checked. Signed-off-by: Michal Lenc <michallenc@seznam.cz>
xiaoxiang781216
approved these changes
Jul 28, 2026
linguini1
approved these changes
Jul 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The reference manual (section 3.2.1) states the user has to read
GLERRandINTERRregisters to clear their bits and release ERR pin after the startup sequence. Error bits are set to 1 after the startup if external power supply is used.Not clearing the bits leads to subsequent read call errors if VBB errors are checked.
Impact
Reading the data after startup doesn't return error for first two calls (one clears
GLERR, otherINTERR) anymore.Testing
With a simple application that reads from the expander. First two reads after the boot failed before the change, the issue is not present anymore.