From: Tero Kristo <t-kristo@ti.com>
To: Lokesh Vutla <lokeshvutla@ti.com>, Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Rob Herring <robh+dt@kernel.org>
Cc: Device Tree Mailing List <devicetree@vger.kernel.org>,
Sekhar Nori <nsekhar@ti.com>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 2/5] dt-bindings: ti_sci_pm_domains: Add support for exclusive and shared access
Date: Wed, 10 Apr 2019 11:04:16 +0300 [thread overview]
Message-ID: <2087d79b-67b0-5ce4-bf2f-f659ef1a5494@ti.com> (raw)
In-Reply-To: <20190410053728.17374-3-lokeshvutla@ti.com>
On 10/04/2019 08:37, Lokesh Vutla wrote:
> TISCI protocol supports for enabling the device either with exclusive
> permissions for the requesting host or with sharing across the hosts.
> There are certain devices which are exclusive to Linux context and
> there are certain devices that are shared across different host contexts.
> So add support for getting this information from DT by increasing
> the power-domain cells to 2.
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
> ---
> .../devicetree/bindings/soc/ti/sci-pm-domain.txt | 11 +++++++++--
> MAINTAINERS | 1 +
> include/dt-bindings/soc/ti,sci_pm_domain.h | 9 +++++++++
> 3 files changed, 19 insertions(+), 2 deletions(-)
> create mode 100644 include/dt-bindings/soc/ti,sci_pm_domain.h
>
> diff --git a/Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt b/Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt
> index f7b00a7c0f68..f541d1f776a2 100644
> --- a/Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt
> +++ b/Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt
> @@ -19,8 +19,15 @@ child of the pmmc node.
> Required Properties:
> --------------------
> - compatible: should be "ti,sci-pm-domain"
> -- #power-domain-cells: Must be 1 so that an id can be provided in each
> - device node.
> +- #power-domain-cells: Can be one of the following:
> + 1: Containing the device id of each node
> + 2: First entry should be device id
> + Second entry should be one of the floowing:
> + TI_SCI_PD_EXCLUSIVE: To allow device to be
> + exclusively controlled by
> + the requesting hosts.
> + TI_SCI_PD_SHARED: To allow device to be shared
> + by multiple hosts.
One thing should be noted on this, the added flag is purely for software
configuration, and is not telling us anything about the HW / firmware.
Software can decide to have the flag either way and it will work. I just
wonder if DT is the correct location to have something like this...
Expect to have plenty of churn on this by people swapping the
permissions around according to their use-case needs.
-Tero
>
> Example (K2G):
> -------------
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 2359e12e4c41..dc7a19cc1831 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15345,6 +15345,7 @@ F: drivers/firmware/ti_sci*
> F: include/linux/soc/ti/ti_sci_protocol.h
> F: Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt
> F: drivers/soc/ti/ti_sci_pm_domains.c
> +F: include/dt-bindings/soc/ti,sci_pm_domain.h
> F: Documentation/devicetree/bindings/reset/ti,sci-reset.txt
> F: Documentation/devicetree/bindings/clock/ti,sci-clk.txt
> F: drivers/clk/keystone/sci-clk.c
> diff --git a/include/dt-bindings/soc/ti,sci_pm_domain.h b/include/dt-bindings/soc/ti,sci_pm_domain.h
> new file mode 100644
> index 000000000000..8f2a7360b65e
> --- /dev/null
> +++ b/include/dt-bindings/soc/ti,sci_pm_domain.h
> @@ -0,0 +1,9 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +
> +#ifndef __DT_BINDINGS_TI_SCI_PM_DOMAIN_H
> +#define __DT_BINDINGS_TI_SCI_PM_DOMAIN_H
> +
> +#define TI_SCI_PD_EXCLUSIVE 1
> +#define TI_SCI_PD_SHARED 0
> +
> +#endif /* __DT_BINDINGS_TI_SCI_PM_DOMAIN_H */
>
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2019-04-10 8:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 5:37 [PATCH v3 0/5] soc: ti: k3-am654: Allow for exclusive and shared device requests Lokesh Vutla
2019-04-10 5:37 ` [PATCH v3 1/5] firmware: ti_sci: Allow for device shared and exclusive requests Lokesh Vutla
2019-04-10 5:37 ` [PATCH v3 2/5] dt-bindings: ti_sci_pm_domains: Add support for exclusive and shared access Lokesh Vutla
2019-04-10 8:04 ` Tero Kristo [this message]
2019-04-10 12:37 ` Lokesh Vutla
2019-04-10 12:49 ` Tero Kristo
2019-04-10 13:15 ` Lokesh Vutla
2019-04-10 15:38 ` Tero Kristo
2019-04-11 14:34 ` Tony Lindgren
2019-05-02 9:24 ` Tero Kristo
2019-06-11 12:34 ` Tero Kristo
2019-06-13 22:22 ` Rob Herring
2019-04-10 5:37 ` [PATCH v3 3/5] soc: ti: " Lokesh Vutla
2019-06-05 5:44 ` Lokesh Vutla
2019-04-10 5:37 ` [PATCH v3 4/5] soc: ti: ti_sci_pm_domains: Switch to SPDX Licensing Lokesh Vutla
2019-04-10 5:37 ` [PATCH v3 5/5] arm64: dts: ti: k3-am654: Update the power domain cells Lokesh Vutla
2019-05-29 8:58 ` [PATCH v3 0/5] soc: ti: k3-am654: Allow for exclusive and shared device requests Lokesh Vutla
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=2087d79b-67b0-5ce4-bf2f-f659ef1a5494@ti.com \
--to=t-kristo@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.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).