From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] xen/arm: Add a clock property
Date: Wed, 20 Jul 2016 14:46:43 +0200 [thread overview]
Message-ID: <CAMuHMdWdqdT4jnae8h9tDDzzh8ZAbJJwiMW-scPBNVwmjYSiWQ@mail.gmail.com> (raw)
In-Reply-To: <04d9dbfb-196d-a775-7fbb-526aba8085f4@arm.com>
Hi Julien,
On Wed, Jul 20, 2016 at 2:10 PM, Julien Grall <julien.grall@arm.com> wrote:
> On 20/07/16 12:49, Geert Uytterhoeven wrote:
>> On Wed, Jul 20, 2016 at 1:01 PM, Julien Grall <julien.grall@arm.com>
>> wrote:
>>> On 20/07/16 10:43, Geert Uytterhoeven wrote:
>>>> On Tue, Jul 12, 2016 at 9:46 AM, Dirk Behme <dirk.behme@de.bosch.com>
>>>> wrote:
>>>>> Clocks described by this property are reserved for use by Xen, and the
>>>>> OS
>>>>> must not alter their state any way, such as disabling or gating a
>>>>> clock,
>>>>> or modifying its rate. Ensuring this may impose constraints on parent
>>>>> clocks or other resources used by the clock tree.
>>>>>
>>>>> This property is used to proxy clocks for devices Xen has taken
>>>>> ownership
>>>>> of, such as UARTs, for which the associated clock controller(s) remain
>>>>> under the control of Dom0.
>>>>
>>>> I'm not familiar with using XEN at all, but I'm a bit puzzled...
>>>>
>>>> Can't you just add a clocks property to the (virtual) serial device node
>>>> in DT?
>>>> Then the (virtual) serial device driver can get and enable the clock?
>>>
>>> There is no DT node for the Xen console (hvc). The UART used by Xen will
>>> be
>>> completely removed from the Device tree.
>>
>> Why is it removed?
>
> Because the device is used exclusively by Xen and DOM0 should not touch it
> at all (IRQs and MMIOs are not mapped).
IMHO then it's Xen's responsability to make sure not to disable the clock(s).
Who removes the device node from the DT? If Xen, can't it just remember
which clocks were present in removed device nodes?
What to do on SoCs where the serial device is part of a power area (e.g.
Renesas SH/R-Mobile)? Who will make sure it is not powered down?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2016-07-20 12:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 7:46 [PATCH v4] xen/arm: Add a clock property Dirk Behme
2016-07-12 22:26 ` Michael Turquette
2016-07-13 8:35 ` Dirk Behme
2016-07-13 18:43 ` Stefano Stabellini
2016-07-13 18:56 ` [Xen-devel] " Dirk Behme
2016-07-13 21:03 ` Michael Turquette
2016-07-14 6:31 ` Dirk Behme
2016-07-14 10:14 ` Julien Grall
2016-07-14 10:32 ` Dirk Behme
2016-07-14 10:38 ` Stefano Stabellini
2016-07-14 10:49 ` Dirk Behme
2016-07-14 15:55 ` Stefano Stabellini
2016-07-14 16:30 ` Dirk Behme
2016-07-14 17:14 ` Julien Grall
2016-07-15 7:53 ` Dirk Behme
2016-07-22 0:07 ` Michael Turquette
2016-07-22 1:16 ` Stefano Stabellini
2016-07-27 5:05 ` Dirk Behme
2016-07-28 11:17 ` Julien Grall
2016-07-28 14:35 ` Dirk Behme
2016-07-14 10:25 ` Stefano Stabellini
2016-07-13 18:35 ` Stefano Stabellini
2016-07-13 18:47 ` [Xen-devel] " Dirk Behme
2016-07-13 19:07 ` Stefano Stabellini
2016-07-14 6:11 ` Dirk Behme
2016-07-14 10:28 ` Stefano Stabellini
2016-07-20 9:43 ` Geert Uytterhoeven
2016-07-20 11:01 ` Julien Grall
2016-07-20 11:49 ` Geert Uytterhoeven
2016-07-20 12:10 ` Julien Grall
2016-07-20 12:46 ` Geert Uytterhoeven [this message]
2016-07-20 12:53 ` Dirk Behme
2016-07-20 13:21 ` Julien Grall
2016-07-22 0:14 ` Michael Turquette
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=CAMuHMdWdqdT4jnae8h9tDDzzh8ZAbJJwiMW-scPBNVwmjYSiWQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.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).