From: Nishanth Menon <nm@ti.com>
To: Lokesh Vutla <lokeshvutla@ti.com>
Cc: Device Tree Mailing List <devicetree@vger.kernel.org>,
Sekhar Nori <nsekhar@ti.com>, Tero Kristo <t-kristo@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 0/5] soc: ti: k3: Allow for exclusive and shared device requests
Date: Tue, 23 Jul 2019 06:42:13 -0500 [thread overview]
Message-ID: <20190723114213.ogypuwcp3mw3vmcn@kahuna> (raw)
In-Reply-To: <20190722050757.29893-1-lokeshvutla@ti.com>
On 10:37-20190722, Lokesh Vutla wrote:
> Sysfw provides an option for requesting exclusive access for a
> device using the flags MSG_FLAG_DEVICE_EXCLUSIVE. If this flag is
> not used, the device is meant to be shared across hosts. Once a device
> is requested from a host with this flag set, any request to this
> device from a different host will be nacked by sysfw.
>
> Current tisci firmware and pm drivers always requests for device with
> exclusive permissions set. But this is not be true for certain devices
> that are expcted to be shared across different host contexts.
> So add support for getting the shared or exclusive permissions from DT
> and request firmware accordingly.
>
> Changes since v3: https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=103447
> - Rebased on top of v5.3-rc1
> - Updated power-domain cells for j721e.
> - Mark the console uart as shared in am65x-base-board
> - Added Reviewed-by from Rob
[...]
Looks good to me.
Reviewed-by: Nishanth Menon <nm@ti.com>
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2019-07-23 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 5:07 [PATCH v4 0/5] soc: ti: k3: Allow for exclusive and shared device requests Lokesh Vutla
2019-07-22 5:07 ` [PATCH v4 1/5] firmware: ti_sci: Allow for device shared and exclusive requests Lokesh Vutla
2019-07-22 5:07 ` [PATCH v4 2/5] dt-bindings: ti_sci_pm_domains: Add support for exclusive and shared access Lokesh Vutla
2019-07-22 5:07 ` [PATCH v4 3/5] soc: ti: " Lokesh Vutla
2019-07-22 5:07 ` [PATCH v4 4/5] arm64: dts: ti: k3-am654: Update the power domain cells Lokesh Vutla
2019-07-22 5:07 ` [PATCH v4 5/5] arm64: dts: ti: k3-j721e: " Lokesh Vutla
2019-07-22 5:11 ` [PATCH v4 0/5] soc: ti: k3: Allow for exclusive and shared device requests Lokesh Vutla
2019-07-23 11:42 ` Nishanth Menon [this message]
2019-07-25 17:39 ` santosh.shilimkar
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=20190723114213.ogypuwcp3mw3vmcn@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+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).