From: Rob Herring <robh@kernel.org>
To: Lokesh Vutla <lokeshvutla@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
Device Tree Mailing List <devicetree@vger.kernel.org>,
Sekhar Nori <nsekhar@ti.com>, Tero Kristo <t-kristo@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/5] dt-bindings: ti_sci_pm_domains: Add support for exclusive access
Date: Tue, 12 Mar 2019 10:43:01 -0500 [thread overview]
Message-ID: <20190312154301.GA21389@bogus> (raw)
In-Reply-To: <20190223093232.29003-3-lokeshvutla@ti.com>
On Sat, Feb 23, 2019 at 03:02:29PM +0530, Lokesh Vutla wrote:
> TISCI protocol supports for enabling the device with exclusive
> permissions. Certain remoteproc devices or some shared devices
> across VM doesn't wants to request devices with this flag set.
The wording here is weird. You want to add exclusive support, but you
are talking about devices which don't want exclusive support.
> So add support for getting this information from DT by increasing
> the power-domain cells to 2.
Seems like this would be racy. Whomever wants exclusive access would
have to be the first to request a device. Seems like whether devices are
able to be shared or not would be known because generally h/w has to be
designed for that.
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
> ---
> Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt b/Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt
> index f7b00a7c0f68..5fdda7475023 100644
> --- a/Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt
> +++ b/Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt
> @@ -19,8 +19,11 @@ 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 1 or 0. Use 1 for enabling
> + the device with exclusive permissions set else 0.
>
> Example (K2G):
> -------------
> --
> 2.19.2
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-12 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 9:32 [PATCH v2 0/5] soc: ti: k3-am654: Allow for exclsive request of devices Lokesh Vutla
2019-02-23 9:32 ` [PATCH v2 1/5] firmware: ti_sci: (Dis)Allow for device exclusive permissions Lokesh Vutla
2019-02-23 9:32 ` [PATCH v2 2/5] dt-bindings: ti_sci_pm_domains: Add support for exclusive access Lokesh Vutla
2019-03-06 14:58 ` Nishanth Menon
2019-03-12 15:43 ` Rob Herring [this message]
2019-03-12 23:03 ` Nishanth Menon
2019-02-23 9:32 ` [PATCH v2 3/5] soc: ti: " Lokesh Vutla
2019-02-23 9:32 ` [PATCH v2 4/5] soc: ti: ti_sci_pm_domains: Switch to SPDX Licensing Lokesh Vutla
2019-02-23 9:32 ` [PATCH v2 5/5] arm64: dts: ti: k3-am654: Update the power domain cells 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=20190312154301.GA21389@bogus \
--to=robh@kernel.org \
--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=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
/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).