From: santosh.shilimkar@oracle.com
To: Lokesh Vutla <lokeshvutla@ti.com>, 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 v4 0/5] soc: ti: k3: Allow for exclusive and shared device requests
Date: Thu, 25 Jul 2019 10:39:23 -0700 [thread overview]
Message-ID: <d549d2e9-c375-2c46-e4bc-e3a572c90f11@oracle.com> (raw)
In-Reply-To: <20190722050757.29893-1-lokeshvutla@ti.com>
On 7/21/19 10:07 PM, 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
>
> Lokesh Vutla (5):
> firmware: ti_sci: Allow for device shared and exclusive requests
> dt-bindings: ti_sci_pm_domains: Add support for exclusive and shared
> access
> soc: ti: ti_sci_pm_domains: Add support for exclusive and shared
> access
> arm64: dts: ti: k3-am654: Update the power domain cells
> arm64: dts: ti: k3-j721e: Update the power domain cells
>
> .../bindings/soc/ti/sci-pm-domain.txt | 11 ++++-
> MAINTAINERS | 1 +
> arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 44 +++++++++---------
> arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi | 10 ++---
> arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 6 +--
> arch/arm64/boot/dts/ti/k3-am65.dtsi | 1 +
> .../arm64/boot/dts/ti/k3-am654-base-board.dts | 1 +
> .../dts/ti/k3-j721e-common-proc-board.dts | 4 ++
> arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 20 ++++-----
> .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 6 +--
> arch/arm64/boot/dts/ti/k3-j721e.dtsi | 1 +
> drivers/firmware/ti_sci.c | 45 ++++++++++++++++++-
> drivers/soc/ti/ti_sci_pm_domains.c | 23 +++++++++-
> include/dt-bindings/soc/ti,sci_pm_domain.h | 9 ++++
> include/linux/soc/ti/ti_sci_protocol.h | 3 ++
> 15 files changed, 136 insertions(+), 49 deletions(-)
> create mode 100644 include/dt-bindings/soc/ti,sci_pm_domain.h
>
Please split this patch series so that drivers and arch, dts patches
can be queued by respective trees.
Regards,
Santosh
prev parent reply other threads:[~2019-07-25 17:39 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
2019-07-25 17:39 ` santosh.shilimkar [this message]
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=d549d2e9-c375-2c46-e4bc-e3a572c90f11@oracle.com \
--to=santosh.shilimkar@oracle.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 \
--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).