Re: [Qemu-devel] [RFC PATCH 0/6] Clock and power gating support

From: Peter Maydell <peter.maydell@linaro.org>
To: Damien Hedde <damien.hedde@greensocs.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	qemu-arm <qemu-arm@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Edgar Iglesias <edgar.iglesias@xilinx.com>,
	Mark Burton <mark.burton@greensocs.com>,
	Sai Pavan Boddu <saipava@xilinx.com>,
	Luc Michel <luc.michel@greensocs.com>,
	Alistair Francis <alistair@alistair23.me>
Subject: Re: [Qemu-devel] [RFC PATCH 0/6] Clock and power gating support
Date: Fri, 27 Jul 2018 15:59:30 +0100	[thread overview]
Message-ID: <CAFEAcA-X=eziUHurc0SEcGEeM25t4YgkTczsVeF8myWHjfp3MQ@mail.gmail.com> (raw)
In-Reply-To: <cover.1532701430.git.damien.hedde@greensocs.com>

On 27 July 2018 at 15:37, Damien Hedde <damien.hedde@greensocs.com> wrote:
> This set of patches add support for power and clock gating in device objects.
> It adds two booleans to the state, one for power state and one of clock state.
>
> The state is controlled trough 2 functions, one for power and one for clock.
> Two new methods *power_update* and *clock_update* is added to the device class
> which are called on state change and can be overriden.

So, you folks at Greensocs had a series a couple of years ago to try
to add clocktree support (which included handling things like guests
configuring clock rates, some clocks being "downstream" of others, and
so on). It didn't make it into mainline, though it did get a fair amount
of design/code review. How does this approach fit into / compare with
that ?

thanks
-- PMM