From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] xen/arm: register clocks used by the hypervisor
Date: Wed, 22 Jun 2016 16:46:13 +0100 [thread overview]
Message-ID: <20160622154613.GC31817@leverpostej> (raw)
In-Reply-To: <576AAE36.9070501@arm.com>
On Wed, Jun 22, 2016 at 04:26:46PM +0100, Julien Grall wrote:
> Hello Dirk,
>
> On 21/06/16 11:16, Dirk Behme wrote:
> >Some clocks might be used by the Xen hypervisor and not by the Linux
> >kernel. If these are not registered by the Linux kernel, they might be
> >disabled by clk_disable_unused() as the kernel doesn't know that they
> >are used. The clock of the serial console handled by Xen is one
> >example for this. It might be disabled by clk_disable_unused() which
> >stops the whole serial output, even from Xen, then.
> >
> >Up to now, the workaround for this has been to use the Linux kernel
> >command line parameter 'clk_ignore_unused'. See Xen bug
> >
> >http://bugs.xenproject.org/xen/bug/45
> >
> >too.
> >
> >To fix this, we will add the "unused" clocks in Xen to the hypervisor
> >node. The Linux kernel has to register the clocks from the hypervisor
> >node, then.
> >
> >Therefore, check if there is a "clocks" entry in the hypervisor node
> >and if so register the given clocks to the Linux kernel clock
> >framework and with this mark them as used. This prevents the clocks
> >from being disabled.
>
> This new property would need to be documented in:
> - linux/Documentation/devicetree/bindings/arm/xen.txt
> - xen/docs/misc/arm/device-tree/guest.txt
This (series) should also be CC'd to devicetree at vger.kernel.org, and to
the clock framework maintainers.
I have further questions, but I will wait for that posting.
Thanks,
Mark.
next prev parent reply other threads:[~2016-06-22 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 10:16 [PATCH] xen/arm: register clocks used by the hypervisor Dirk Behme
2016-06-21 10:16 ` Dirk Behme
2016-06-21 10:22 ` Dirk Behme
2016-06-21 10:22 ` Dirk Behme
2016-06-22 15:26 ` Julien Grall
2016-06-22 15:26 ` Julien Grall
2016-06-22 15:46 ` Mark Rutland
2016-06-22 15:46 ` Mark Rutland [this message]
2016-06-29 15:49 ` Dirk Behme
2016-06-29 15:49 ` Dirk Behme
2016-06-30 9:19 ` Julien Grall
2016-06-30 9:19 ` Julien Grall
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=20160622154613.GC31817@leverpostej \
--to=mark.rutland@arm.com \
--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 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.