From: Lokesh Vutla <lokeshvutla@ti.com>
To: Nishanth Menon <nm@ti.com>, Tero Kristo <t-kristo@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 3/5] soc: ti: ti_sci_pm_domains: Add support for exclusive and shared access
Date: Wed, 5 Jun 2019 11:14:22 +0530 [thread overview]
Message-ID: <b6f005da-3c0a-ce73-79f0-eaa19c7da92c@ti.com> (raw)
In-Reply-To: <20190410053728.17374-4-lokeshvutla@ti.com>
Santosh,
On 10/04/19 11:07 AM, 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.
>
> For keeping the DT backward compatibility intact, defaulting the
> device permissions to set the exclusive flag set. In this case the
> power-domain-cells is 1.
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Any chance you can pick this patch? Tero is waiting for you to pick it up so
that dts changes can be pulled. Or can you ack it so that Tero can pick the
entire series?
Thanks and regards,
Lokesh
next prev parent reply other threads:[~2019-06-05 5:44 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
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 [this message]
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=b6f005da-3c0a-ce73-79f0-eaa19c7da92c@ti.com \
--to=lokeshvutla@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--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).