From: Paolo Bonzini <pbonzini@redhat.com>
To: li guang <lig.fnst@cn.fujitsu.com>
Cc: stefanha@gmail.com, Peter Maydell <peter.maydell@linaro.org>,
aliguori@us.ibm.com, qemu-devel@nongnu.org, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH][RFC v2 2/7] hw/power: add main power chip implementation
Date: Tue, 09 Apr 2013 10:29:35 +0200 [thread overview]
Message-ID: <5163D16F.2090209@redhat.com> (raw)
In-Reply-To: <1365495274.9553.53.camel@liguang.fnst.cn.fujitsu.com>
Il 09/04/2013 10:14, li guang ha scritto:
> The approach of power-control may be specific for architectures,
> but, I think the thought beneath is common, e.g. for some ARM and MIPS
> platforms, OS issue commands to a embedded controller's firmware,
> then this firmware will help to do the real power-control job(
> on/off, of course no suspend), and also, there are some platforms
> directly generate power signals on some specific GPIOs then,
> these signals via a power chip will affect other devices.
> 1. 2.
> ----- -----
> | OS | | OS |
> --+-- -----
> |on/off |on/off
> ---------------------------------------------
> | -----+----- -----+----- |
> | | firmware | | GPIO | |
> | -----+----- -----+----- |
> ---------+----------------- | | part 2
> |on/off | |on/off |
> +------+------+ | ----+----- |
> | | | | |power chip| |
> ------ ----- ---- | ---------- |
> | dev0 ||dev1 ||dev2| --------|on/off---
> ------ ----- ---- +------+------+
> | | |
> ------ ----- ----
> | dev0 ||dev1 ||dev2|
> ------ ----- ----
> so, in graph 1, firmware acts like the power chip and related gpios
> in graph 2, then, I boldly assume a conceptual power chip exist,
> it can either be part 2 of graph 1 or 2.
But QEMU doesn't treat conceptual things as devices. It models them as
APIs, such as the memory API or the one that I pointed out in my
previous message.
Paolo
> as you said, qemu should only model real hardware,
> I am confused, can the demonstration above part 2 be consider a
> real hardware? but it does not have vendor and dev-id ...
> and it's not real hardware? but it dose work just same with
> real hardware.
next prev parent reply other threads:[~2013-04-09 8:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 4:28 [Qemu-devel] [PATCH][RFC v2 0/7] implement power chip liguang
2013-04-05 4:28 ` [Qemu-devel] [PATCH][RFC v2 1/7] hw/irq: move struct IRQState to irq.h liguang
2013-04-05 8:34 ` Peter Maydell
2013-04-05 8:39 ` li guang
2013-04-05 4:28 ` [Qemu-devel] [PATCH][RFC v2 2/7] hw/power: add main power chip implementation liguang
2013-04-05 8:35 ` Peter Maydell
2013-04-05 8:45 ` li guang
2013-04-05 9:23 ` Peter Maydell
2013-04-08 0:32 ` li guang
2013-04-08 9:21 ` Peter Maydell
2013-04-09 8:14 ` li guang
2013-04-09 8:29 ` Paolo Bonzini [this message]
2013-04-05 4:28 ` [Qemu-devel] [PATCH][RFC v2 3/7] vl: create power chip device liguang
2013-04-05 11:48 ` Paolo Bonzini
2013-04-08 0:18 ` li guang
2013-04-08 9:53 ` Paolo Bonzini
2013-04-09 7:34 ` li guang
2013-04-09 7:43 ` Paolo Bonzini
2013-04-09 8:26 ` li guang
2013-04-09 11:06 ` Paolo Bonzini
2013-04-10 0:09 ` li guang
2013-04-10 9:40 ` Paolo Bonzini
2013-04-10 12:09 ` Andreas Färber
2013-04-10 13:41 ` guang li
2013-04-10 13:52 ` Paolo Bonzini
2013-04-11 1:30 ` li guang
2013-04-16 20:45 ` Anthony Liguori
2013-04-17 0:07 ` li guang
2013-04-05 4:28 ` [Qemu-devel] [PATCH][RFC v2 4/7] sysemu: remove PowerReason in sysemu.h liguang
2013-04-05 4:28 ` [Qemu-devel] [PATCH][RFC v2 5/7] qdev: add power_signal_in for DeviceState liguang
2013-04-05 4:28 ` [Qemu-devel] [PATCH][RFC v2 6/7] ich9: refactor wakeup/reset function liguang
2013-04-05 4:28 ` [Qemu-devel] [PATCH][RFC v2 7/7] vl: run power_management liguang
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=5163D16F.2090209@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=lig.fnst@cn.fujitsu.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).