All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Damien Hedde" <damien.hedde@greensocs.com>,
	"Mark Burton" <mark.burton@greensocs.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] multi phase reset
Date: Mon, 4 Mar 2019 11:29:12 +0100	[thread overview]
Message-ID: <20190304102912.GC6010@toto> (raw)
In-Reply-To: <CAFEAcA8L1qKaNwpr8sMZC8jQXbaLtCctaV8ecTFxXTVy0sWjVw@mail.gmail.com>

Hi Damien and others,

A few questions from my side.

We sometimes see that wires from generic GPIO blocks get connected to reset inputs.
This happens both to off-chip perihperals but we also see it on-chip.

To avoid having GPIO modules know that some of their outputs are being used as
reset signals it would be nice to have a reset proxy that allows any qemu_irq to
drive resets for a given device. Perhaps even with built-in options for both interpreting
"active-low" and "active-high". I think it would even be useful to have this
in qdev but that may be pushing it too far. Any thoughts on that?

Have you thought about what happens if someone does an MMIO access to a device while
its reset is active? Were you planning to have some "default" SysBus level handling to
block MMIO while in reset or anything like that? Or would that be handled individually
by each device model?

Another question is regarding reset of CPUs. It would be nice to be able to expose
similar interfaces and have some defined behaviour for CPUs that are in reset. E.g,
if reset is active the CPU does not execute etc.

Cheers,
Edgar

  parent reply	other threads:[~2019-03-04 10:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-25 10:49 [Qemu-devel] [RFC] multi phase reset Damien Hedde
2019-02-25 10:54 ` Peter Maydell
2019-03-01 11:43 ` Peter Maydell
2019-03-01 15:34   ` Damien Hedde
2019-03-01 16:52     ` Peter Maydell
2019-03-02 19:41       ` Philippe Mathieu-Daudé
2019-03-03 10:59         ` Peter Maydell
2019-03-04 10:18           ` Edgar E. Iglesias
2019-03-04 10:29           ` Edgar E. Iglesias [this message]
2019-03-06  9:05             ` Damien Hedde
2019-03-04 14:04       ` Damien Hedde

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=20190304102912.GC6010@toto \
    --to=edgar.iglesias@xilinx.com \
    --cc=damien.hedde@greensocs.com \
    --cc=mark.burton@greensocs.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.