From: Paul Brook <paul@codesourcery.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Extending qemu_irq for reset signals
Date: Wed, 15 Aug 2007 17:34:09 +0100 [thread overview]
Message-ID: <200708151734.10040.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580708150913k631126bche7fde54f55e73643@mail.gmail.com>
On Wednesday 15 August 2007, Blue Swirl wrote:
> Hi,
>
> I'd like to use similar mechanism as qemu_irq as reset signal for
> devices. The difference is that the opaque data and callback are not
> specified at the time of creating the signal at upstream device, but
> when the receiving device is created. This does not fit current
> qemu_irq model.
Either your confused, or not expressing what you want very well. What you
describe is how qemu_irq works.
The "upstream device" and "receiving device" are the same thing.
The whole point of qemu_irq is to be able to send a single-bit signal without
having to know or care where it's going. ie. when creating the board/cpu, you
create the qemu_irq object with appropriate parameters. Then the device
initiating the reset uses that qemu_irq object.
If the device initiating the reset needs to pass additional information, then
you're no longer dealing with a single bit of state, so I don't think
qemu_irq is really appropriate.
Paul
next prev parent reply other threads:[~2007-08-15 16:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 16:13 [Qemu-devel] Extending qemu_irq for reset signals Blue Swirl
2007-08-15 16:34 ` Paul Brook [this message]
2007-08-15 16:53 ` [Qemu-devel] " Blue Swirl
2007-08-15 17:21 ` Paul Brook
2007-08-15 17:22 ` Paul Brook
2007-08-15 17:35 ` Blue Swirl
2007-08-15 17:42 ` Paul Brook
2007-08-15 17:52 ` Blue Swirl
2007-08-15 19:33 ` Blue Swirl
2007-08-15 19:44 ` Paul Brook
2007-08-15 17:47 ` Blue Swirl
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=200708151734.10040.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=blauwirbel@gmail.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 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).