From: Julien Grall <julien.grall-5wv7dgnIgG8@public.gmane.org>
To: Stefano Stabellini
<sstabellini-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Dirk Behme <dirk.behme-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
xen-devel-GuqFBffKawtpuQazS67q72D2FQJk+8+b@public.gmane.org,
linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Michael Turquette
<mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Subject: Re: [PATCH v2] xen/arm: register clocks used by the hypervisor
Date: Tue, 5 Jul 2016 15:02:19 +0100 [thread overview]
Message-ID: <577BBDEB.7000305@arm.com> (raw)
In-Reply-To: <577BBC1A.8020209-5wv7dgnIgG8@public.gmane.org>
On 05/07/16 14:54, Julien Grall wrote:
>
>
> On 05/07/16 14:53, Stefano Stabellini wrote:
>> On Thu, 30 Jun 2016, Dirk Behme wrote:
>>> +- clocks: one or more clocks to be registered.
>>> + Xen hypervisor drivers might replace native drivers, resulting in
>>> + clocks not registered by these native drivers. To avoid that these
>>> + unregistered clocks are disabled, then, e.g. by clk_disable_unused(),
>>> + register them in the hypervisor node.
>>> + An example for this are the clocks of the serial driver. If the
>>> clocks
>>> + used by the serial hardware interface are not registered by the
>>> serial
>>> + driver the serial output might stop once clk_disable_unused() is
>>> called.
>>
>> What if we use the "status" property of the clocks? Could we set it to
>> "disabled" in Xen? Would that be enough for Linux to leave them alone?
>
> clocks could be shared between multiple devices. So it is not possible
> to disable the clock.
To give an example, below the UART node for juno
(arch/arm64/boot/dts/arm/juno-base.dtsi):
soc_uart0: uart@7ff80000 {
compatible = "arm,pl011", "arm,primecell";
reg = <0x0 0x7ff80000 0x0 0x1000>;
interrupts = <GIC_SPI 83 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&soc_uartclk>, <&soc_refclk100mhz>;
clock-names = "uartclk", "apb_pclk";
};
The clock soc_refclk100mhz is shared with the mailbox.
Regards,
--
Julien Grall
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
Dirk Behme <dirk.behme@de.bosch.com>
Cc: linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, xen-devel@lists.xenproject.org,
linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: [PATCH v2] xen/arm: register clocks used by the hypervisor
Date: Tue, 5 Jul 2016 15:02:19 +0100 [thread overview]
Message-ID: <577BBDEB.7000305@arm.com> (raw)
In-Reply-To: <577BBC1A.8020209@arm.com>
On 05/07/16 14:54, Julien Grall wrote:
>
>
> On 05/07/16 14:53, Stefano Stabellini wrote:
>> On Thu, 30 Jun 2016, Dirk Behme wrote:
>>> +- clocks: one or more clocks to be registered.
>>> + Xen hypervisor drivers might replace native drivers, resulting in
>>> + clocks not registered by these native drivers. To avoid that these
>>> + unregistered clocks are disabled, then, e.g. by clk_disable_unused(),
>>> + register them in the hypervisor node.
>>> + An example for this are the clocks of the serial driver. If the
>>> clocks
>>> + used by the serial hardware interface are not registered by the
>>> serial
>>> + driver the serial output might stop once clk_disable_unused() is
>>> called.
>>
>> What if we use the "status" property of the clocks? Could we set it to
>> "disabled" in Xen? Would that be enough for Linux to leave them alone?
>
> clocks could be shared between multiple devices. So it is not possible
> to disable the clock.
To give an example, below the UART node for juno
(arch/arm64/boot/dts/arm/juno-base.dtsi):
soc_uart0: uart@7ff80000 {
compatible = "arm,pl011", "arm,primecell";
reg = <0x0 0x7ff80000 0x0 0x1000>;
interrupts = <GIC_SPI 83 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&soc_uartclk>, <&soc_refclk100mhz>;
clock-names = "uartclk", "apb_pclk";
};
The clock soc_refclk100mhz is shared with the mailbox.
Regards,
--
Julien Grall
WARNING: multiple messages have this Message-ID (diff)
From: julien.grall@arm.com (Julien Grall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] xen/arm: register clocks used by the hypervisor
Date: Tue, 5 Jul 2016 15:02:19 +0100 [thread overview]
Message-ID: <577BBDEB.7000305@arm.com> (raw)
In-Reply-To: <577BBC1A.8020209@arm.com>
On 05/07/16 14:54, Julien Grall wrote:
>
>
> On 05/07/16 14:53, Stefano Stabellini wrote:
>> On Thu, 30 Jun 2016, Dirk Behme wrote:
>>> +- clocks: one or more clocks to be registered.
>>> + Xen hypervisor drivers might replace native drivers, resulting in
>>> + clocks not registered by these native drivers. To avoid that these
>>> + unregistered clocks are disabled, then, e.g. by clk_disable_unused(),
>>> + register them in the hypervisor node.
>>> + An example for this are the clocks of the serial driver. If the
>>> clocks
>>> + used by the serial hardware interface are not registered by the
>>> serial
>>> + driver the serial output might stop once clk_disable_unused() is
>>> called.
>>
>> What if we use the "status" property of the clocks? Could we set it to
>> "disabled" in Xen? Would that be enough for Linux to leave them alone?
>
> clocks could be shared between multiple devices. So it is not possible
> to disable the clock.
To give an example, below the UART node for juno
(arch/arm64/boot/dts/arm/juno-base.dtsi):
soc_uart0: uart at 7ff80000 {
compatible = "arm,pl011", "arm,primecell";
reg = <0x0 0x7ff80000 0x0 0x1000>;
interrupts = <GIC_SPI 83 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&soc_uartclk>, <&soc_refclk100mhz>;
clock-names = "uartclk", "apb_pclk";
};
The clock soc_refclk100mhz is shared with the mailbox.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2016-07-05 14:02 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 10:32 [PATCH v2] xen/arm: register clocks used by the hypervisor Dirk Behme
2016-06-30 10:32 ` Dirk Behme
2016-06-30 10:32 ` Dirk Behme
2016-06-30 14:21 ` Mark Rutland
2016-06-30 14:21 ` Mark Rutland
2016-06-30 14:21 ` Mark Rutland
2016-06-30 14:56 ` [Xen-devel] " Dirk Behme
2016-06-30 14:56 ` Dirk Behme
2016-06-30 15:18 ` Mark Rutland
2016-06-30 15:18 ` [Xen-devel] " Mark Rutland
2016-06-30 15:18 ` Mark Rutland
2016-06-30 15:33 ` Julien Grall
2016-06-30 15:33 ` [Xen-devel] " Julien Grall
2016-06-30 15:33 ` Julien Grall
2016-06-30 15:33 ` Julien Grall
2016-06-30 14:56 ` Dirk Behme
2016-07-05 13:53 ` Stefano Stabellini
2016-07-05 13:53 ` Stefano Stabellini
2016-07-05 13:53 ` Stefano Stabellini
2016-07-05 13:54 ` Julien Grall
2016-07-05 13:54 ` Julien Grall
2016-07-05 13:54 ` Julien Grall
2016-07-05 13:54 ` Julien Grall
2016-07-05 14:02 ` Julien Grall
[not found] ` <577BBC1A.8020209-5wv7dgnIgG8@public.gmane.org>
2016-07-05 14:02 ` Julien Grall [this message]
2016-07-05 14:02 ` Julien Grall
2016-07-05 14:02 ` Julien Grall
2016-07-05 14:04 ` Stefano Stabellini
2016-07-05 14:04 ` Stefano Stabellini
2016-07-05 14:08 ` Julien Grall
2016-07-05 14:08 ` Julien Grall
2016-07-05 14:37 ` Stefano Stabellini
2016-07-05 14:37 ` Stefano Stabellini
2016-07-05 14:37 ` Stefano Stabellini
2016-07-05 14:08 ` Julien Grall
2016-07-05 14:04 ` Stefano Stabellini
2016-07-05 13:53 ` Stefano Stabellini
2016-07-06 1:34 ` Michael Turquette
2016-07-06 1:34 ` Michael Turquette
2016-07-06 1:34 ` Michael Turquette
2016-07-06 1:34 ` Michael Turquette
2016-07-06 13:10 ` Julien Grall
2016-07-06 13:10 ` Julien Grall
2016-07-06 13:10 ` Julien Grall
2016-07-06 13:16 ` Stefano Stabellini
2016-07-06 13:16 ` Stefano Stabellini
2016-07-06 13:16 ` Stefano Stabellini
2016-07-06 13:26 ` Julien Grall
2016-07-06 13:26 ` Julien Grall
2016-07-06 13:26 ` Julien Grall
2016-07-06 13:48 ` Mark Rutland
2016-07-06 13:48 ` Mark Rutland
2016-07-06 13:48 ` Mark Rutland
2016-07-06 20:42 ` Michael Turquette
2016-07-06 20:42 ` Michael Turquette
2016-07-06 20:42 ` Michael Turquette
2016-07-07 7:32 ` Dirk Behme
2016-07-07 7:32 ` Dirk Behme
2016-07-07 7:32 ` Dirk Behme
2016-07-07 7:32 ` Dirk Behme
2016-07-08 2:50 ` Michael Turquette
2016-07-08 2:50 ` Michael Turquette
2016-07-08 2:50 ` Michael Turquette
2016-07-08 5:51 ` [Xen-devel] " Dirk Behme
2016-07-08 5:51 ` Dirk Behme
2016-07-08 5:51 ` Dirk Behme
2016-07-08 9:21 ` Julien Grall
2016-07-08 9:21 ` [Xen-devel] " Julien Grall
2016-07-08 9:21 ` Julien Grall
2016-07-08 5:51 ` Dirk Behme
2016-07-08 2:50 ` Michael Turquette
2016-07-06 20:42 ` Michael Turquette
2016-07-08 6:48 ` Dirk Behme
2016-07-08 6:48 ` Dirk Behme
2016-07-08 6:48 ` Dirk Behme
2016-07-08 6:48 ` Dirk Behme
2016-07-08 9:35 ` Julien Grall
[not found] ` <20733b68-9529-bdb9-2a7d-576c8193f15c-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
2016-07-08 9:35 ` Julien Grall
2016-07-08 9:35 ` Julien Grall
2016-07-08 9:35 ` Julien Grall
2016-06-30 10:32 Dirk Behme
2016-07-05 6:50 Dirk Behme
2016-07-05 6:50 ` Dirk Behme
2016-07-05 6:50 ` Dirk Behme
2016-07-05 10:39 ` Mark Rutland
2016-07-05 10:39 ` Mark Rutland
2016-07-05 10:39 ` Mark Rutland
2016-07-05 10:45 ` Dirk Behme
2016-07-05 10:45 ` Dirk Behme
2016-07-05 10:45 ` Dirk Behme
[not found] ` <b2431af6-f415-41db-5651-8cb8d3b08822-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
2016-07-05 11:07 ` Mark Rutland
2016-07-05 11:07 ` Mark Rutland
2016-07-05 11:07 ` Mark Rutland
2016-07-06 23:38 ` Michael Turquette
2016-07-06 23:38 ` Michael Turquette
2016-07-06 23:38 ` Michael Turquette
2016-07-06 23:38 ` Michael Turquette
2016-07-05 11:07 ` Mark Rutland
2016-07-05 10:45 ` Dirk Behme
2016-07-05 6:50 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=577BBDEB.7000305@arm.com \
--to=julien.grall-5wv7dgnigg8@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dirk.behme-V5te9oGctAVWk0Htik3J/w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=sstabellini-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=xen-devel-GuqFBffKawtpuQazS67q72D2FQJk+8+b@public.gmane.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.