From: Julien Grall <julien.grall@arm.com>
To: Dirk Behme <dirk.behme@de.bosch.com>,
Michael Turquette <mturquette@baylibre.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Stefano Stabellini <sstabellini@kernel.org>,
Stephen Boyd <sboyd@codeaurora.org>,
xen-devel@lists.xenproject.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] xen/arm: enable clocks used by the hypervisor
Date: Fri, 8 Jul 2016 11:49:33 +0100 [thread overview]
Message-ID: <577F853D.405__25601.6553649262$1467975041$gmane$org@arm.com> (raw)
In-Reply-To: <437b5eff-4294-3493-b1b2-0ff2c10525e3@de.bosch.com>
On 08/07/16 11:40, Dirk Behme wrote:
> Hi Michael and Julien,
>
> On 08.07.2016 11:34, Julien Grall wrote:
>> Hi Dirk,
>>
>> On 08/07/16 08:44, Dirk Behme wrote:
>>> Xen hypervisor drivers might replace native OS drivers. The result is
>>> that some important clocks that are enabled by the OS in the non-Xen
>>> case are not properly enabled in the presence of Xen. The clocks
>>> property enumerates the clocks that must be enabled by the Xen clock
>>> consumer.
>>>
>>> An example is a serial driver enabled by the hypervisor. Xen must
>>
>> I would say "An example is the UART used by the hypervisor."
>>
>>> consume and enable these clocks in the OS to ensure behavior continues
>>> after firmware configures the UART hardware and corresponding clock
>>> harder.
>>
>> What do you mean by "harder"?
>>
>> Also, relying on DOM0 to enable the clock looks very wrong to me and you
>> give an example which prove that. The UART will be used before hand by
>> Xen, however it will not be possible to use it if you expect DOM0 to
>> enable the clock (or even modify the clock frequency).
>>
>> The clock should be enabled either by the firmware or Xen. But not DOM0.
>> DOM0 should not touch this clock at all.
>>
>> Furthermore, this property could be used for clock associated to device
>> that will be passthrough-ed to a guest. In this case, the clock would be
>> enabled even if the device is not in use which will result more power
>> consumption.
>
>
> I took the description directly from Michael's proposal
>
> http://www.spinics.net/lists/arm-kernel/msg516576.html
>
> Would it be possible that you two experts agree on the exact wording you
> like to see?
I think the wording suggested by Mark in [1] represents better what we
would like to achieve with this property.
Regards,
[1] https://www.spinics.net/lists/arm-kernel/msg516158.html
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-08 10:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 7:44 [PATCH v3] xen/arm: enable clocks used by the hypervisor Dirk Behme
2016-07-08 7:44 ` Dirk Behme
2016-07-08 7:44 ` Dirk Behme
2016-07-08 9:34 ` Julien Grall
2016-07-08 9:34 ` Julien Grall
2016-07-08 9:34 ` Julien Grall
2016-07-08 10:40 ` Dirk Behme
2016-07-08 10:40 ` Dirk Behme
2016-07-08 10:40 ` Dirk Behme
2016-07-08 10:49 ` Julien Grall [this message]
2016-07-08 10:49 ` Julien Grall
2016-07-08 10:49 ` Julien Grall
2016-07-08 17:00 ` Michael Turquette
2016-07-08 17:00 ` Michael Turquette
2016-07-08 17:00 ` Michael Turquette
2016-07-08 17:00 ` Michael Turquette
2016-07-08 10:40 ` Dirk Behme
2016-07-08 17:06 ` Michael Turquette
2016-07-08 17:06 ` Michael Turquette
2016-07-08 17:06 ` Michael Turquette
2016-07-12 9:21 ` Julien Grall
2016-07-12 9:21 ` Julien Grall
2016-07-12 18:11 ` Michael Turquette
2016-07-12 18:11 ` Michael Turquette
2016-07-12 18:11 ` Michael Turquette
2016-07-12 18:11 ` Michael Turquette
2016-07-12 9:21 ` Julien Grall
2016-07-08 17:06 ` Michael Turquette
2016-07-08 7:44 Dirk Behme
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='577F853D.405__25601.6553649262$1467975041$gmane$org@arm.com' \
--to=julien.grall@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dirk.behme@de.bosch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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.