View Single Post
Old 09-29-2019, 09:48 PM   #15
DomesticExtremis
Addict
DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.
 
DomesticExtremis's Avatar
 
Posts: 243
Karma: 359054
Join Date: Nov 2012
Device: default
Quote:
Originally Posted by pazos View Post
I know it is tagged as an error in kernel code but I'm not sure if that is the cause, a consequence of another circuitry error or totally unrelated.
I took a poke around in your source archive and looked for the DCDC1 error.
The way the function is structured, and the way the interrupt register holds its error codes means that there can only be single error reported and it seems to be detected unambiguously.
That is to say we do not have a hidden UVLO or DCDC2 error - the one reported is the one we have.
DomesticExtremis is offline   Reply With Quote