From: Mark Brown <broonie@kernel.org>
To: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
Cc: "lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"angelogioacchino.delregno@somainline.org"
<angelogioacchino.delregno@somainline.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: short-circuit and over-current IRQs
Date: Wed, 27 Jan 2021 12:27:33 +0000 [thread overview]
Message-ID: <20210127122733.GC4387@sirena.org.uk> (raw)
In-Reply-To: <6046836e22b8252983f08d5621c35ececb97820d.camel@fi.rohmeurope.com>
[-- Attachment #1: Type: text/plain, Size: 693 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2021-01-27 12:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 12:01 Vaittinen, Matti
2021-01-27 12:27 ` Mark Brown [this message]
2021-01-27 12:56 ` Matti Vaittinen
2021-01-27 14:34 ` AngeloGioacchino Del Regno
2021-01-27 14:42 ` Vaittinen, Matti
2021-01-27 16:32 ` Mark Brown
2021-01-28 9:23 ` Vaittinen, Matti
2021-01-28 12:10 ` Mark Brown
2021-01-28 12:49 ` Vaittinen, Matti
[not found] ` <a89bf6f0e6c1e4b9afe980908b7e36b70b304a96.camel@fi.rohmeurope.com>
2021-01-30 15:43 ` AngeloGioacchino Del Regno
2021-02-01 7:14 ` Matti Vaittinen
2021-02-01 13:17 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210127122733.GC4387@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Matti.Vaittinen@fi.rohmeurope.com \
--cc=angelogioacchino.delregno@somainline.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®