From: Nishanth Menon <nm@ti.com>
To: Rob Herring <robh@kernel.org>
Cc: Device Tree Mailing List <devicetree@vger.kernel.org>,
Lokesh Vutla <lokeshvutla@ti.com>, 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 18:03:17 -0500 [thread overview]
Message-ID: <20190312230317.bzq3hxonqil7xpyj@kahuna> (raw)
In-Reply-To: <20190312154301.GA21389@bogus>
On 10:43-20190312, Rob Herring wrote:
> 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.
Rob,
I wonder if it is better to represent this as exclusive power domain or
shared power domain - because that is what the firmware in effect makes
OS think the hardware is? Two power domain nodes in dts, instead of
introducing property as part of cells?
Device may belong to a shared domain or an exclusive domain depending on
the SoC variations.
--
Regards,
Nishanth Menon
_______________________________________________
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-13 11:33 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
2019-03-12 23:03 ` Nishanth Menon [this message]
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=20190312230317.bzq3hxonqil7xpyj@kahuna \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lokeshvutla@ti.com \
--cc=nsekhar@ti.com \
--cc=robh@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