[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210127122733.GC4387@sirena.org.uk>
Date: Wed, 27 Jan 2021 12:27:33 +0000
From: Mark Brown <broonie@...nel.org>
To: "Vaittinen, Matti" <Matti.Vaittinen@...rohmeurope.com>
Cc: "lgirdwood@...il.com" <lgirdwood@...il.com>,
"angelogioacchino.delregno@...ainline.org"
<angelogioacchino.delregno@...ainline.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: short-circuit and over-current IRQs
On Wed, Jan 27, 2021 at 12:01:55PM +0000, Vaittinen, Matti wrote:
> Anyways - I was wondering if this is common thing amongst many PMICs?
> If yes - then, perhaps some generally useful regulator helper could be
> added to help implementing the IRQ disabling + scheduling worker to
> check status and re-enable IRQs? I think it *might* save some time in
> the future - and help making same mistakes many times :]
If we've got two that's enough for a helper. TBH I'm a bit surprised
that people are implementing hardware that leaves the outputs enabled
when it detects this sort of error, it's something that's usually an
emergency that needs shutting off quickly to prevent hardware damage.
Download attachment "signature.asc" of type "application/pgp-signature" (485 bytes)
Powered by blists - more mailing lists