From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: "Herbrechtsmeier Dr.-Ing. ,
Stefan"
<stefan.herbrechtsmeier-oss-2t/0UIm1CeVDOHtkgc7UlQ@public.gmane.org>
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Execute spi transfers inside FIQ (NMI) or panic
Date: Wed, 26 Feb 2020 11:33:33 +0000 [thread overview]
Message-ID: <20200226113333.GC4136@sirena.org.uk> (raw)
In-Reply-To: <d07a46e6-6c8f-c4eb-0ed1-d57b7604a5be-2t/0UIm1CeVDOHtkgc7UlQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
On Wed, Feb 26, 2020 at 08:36:37AM +0100, Herbrechtsmeier Dr.-Ing. , Stefan wrote:
> I see two possible solutions.
> a) The complexity is handled inside the client. The client uses the
> controller exclusive and isn’t allowed to use the new panic transfer during
> a normal transfer.
Then someone builds a system with two devices attached to a single SPI
controller... besides, you've got no mechanism for controlling when a
kernel might panic or power might be lost. I'm not sure a scheme that
relies on being able to control when stuff happens is going to be what
you need.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-26 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 13:27 Execute spi transfers inside FIQ (NMI) or panic Herbrechtsmeier Dr.-Ing. , Stefan
[not found] ` <b22800b8-9c03-63a5-7ade-d8b63c562580-2t/0UIm1CeVDOHtkgc7UlQ@public.gmane.org>
2020-02-25 15:53 ` Mark Brown
[not found] ` <20200225155354.GF4633-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2020-02-26 7:36 ` Herbrechtsmeier Dr.-Ing. , Stefan
[not found] ` <d07a46e6-6c8f-c4eb-0ed1-d57b7604a5be-2t/0UIm1CeVDOHtkgc7UlQ@public.gmane.org>
2020-02-26 11:33 ` Mark Brown [this message]
[not found] ` <20200226113333.GC4136-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2020-02-26 15:28 ` Herbrechtsmeier Dr.-Ing. , Stefan
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=20200226113333.GC4136@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=stefan.herbrechtsmeier-oss-2t/0UIm1CeVDOHtkgc7UlQ@public.gmane.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;
as well as URLs for NNTP newsgroup(s).