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:18:19 +0100	[thread overview]
Message-ID: <20190304101819.GB6010@toto> (raw)
In-Reply-To: <CAFEAcA8L1qKaNwpr8sMZC8jQXbaLtCctaV8ecTFxXTVy0sWjVw@mail.gmail.com>

On Sun, Mar 03, 2019 at 10:59:30AM +0000, Peter Maydell wrote:
> On Sat, 2 Mar 2019 at 19:41, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
> >
> > Hi Damien,
> >
> > On 3/1/19 5:52 PM, Peter Maydell wrote:
> > > On Fri, 1 Mar 2019 at 15:34, Damien Hedde <damien.hedde@greensocs.com> wrote:
> > >> On 3/1/19 12:43 PM, Peter Maydell wrote:
> > >>> In my design the only thing that I thought would happen in phase 3
> > >>> was the "clear the resetting flag", but you've moved that to RELEASE.
> > >>> What's left ? Do you have a concrete example where we'd need this?
> > >>
> > >> I hesitated to remove this phase (would be easy to add it after if it is
> > >> really needed). I see 2 cases where it might be useful.
> >
> > If I RELEASE a PLL which need some time to warm up and stabilize, once
> > stabilized it moves the device to the POST phase where it is ready?
> 
> No, I think that things like that where the device is not ready
> for some period of time after reset should be handled by
> the device itself. Typically we just ignore this and have
> PLLs become stable instantaneously. If you really needed to
> model it you'd just have a timer of some kind inside the
> device model.

Right, this is how we tend to model things for the Xilinx parts. We usually don't care
about the delayed behaviour though.


> 
> (This matches h/w behaviour -- a PLL which is not yet stable
> is not still in reset, it's out of reset but has different
> behaviour for an initial period of time before it stabilizes.)
> 
> thanks
> -- PMM

  reply	other threads:[~2019-03-04 10:18 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 [this message]
2019-03-04 10:29           ` Edgar E. Iglesias
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=20190304101819.GB6010@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.