From: Bjorn Andersson <bjorn.andersson@sonymobile.com>
To: Andy Gross <agross@codeaurora.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <pawel.moll@arm.com>, Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-soc@vger.kernel.org
Subject: [PATCH v2 0/5] Qualcomm Shared Memory State Machines
Date: Thu, 24 Sep 2015 18:24:58 -0700 [thread overview]
Message-ID: <1443144303-21020-1-git-send-email-bjorn.andersson@sonymobile.com> (raw)
This series implements the two different mechanisms for propagating single bit
state information, used on the various Qualcomm platforms.
The system was traditionally used by the modem and application processor to
convey information about boot progress, power states, error handling and so on.
This was implemented as SMSM, with status bits representing a single local
state.
As the complexity of the SoC grew the state bits array grew and the need for
targeting specific state information at specific remote processors appeared.
SMP2P solves this by having separate shared memory regions per processor-pair.
This state information is e.g. used to convey progress and status of remote
firmware loading. Individual bits maps to various stages of the boot and error
states.
Changed since v1:
- The series moved away from representing outgoing bits as gpios
Bjorn Andersson (5):
dt-binding: soc: qcom: Add Qualcomm SMSM device tree documentation
dt-binding: soc: qcom: Introduce qcom,smp2p binding documentation
soc: qcom: Introduce common SMEM state machine code
soc: qcom: smsm: Add driver for Qualcomm SMSM
soc: qcom: smp2p: Qualcomm Shared Memory Point to Point
.../devicetree/bindings/soc/qcom/qcom,smp2p.txt | 104 ++++
.../devicetree/bindings/soc/qcom/qcom,smsm.txt | 104 ++++
drivers/soc/qcom/Kconfig | 19 +
drivers/soc/qcom/Makefile | 3 +
drivers/soc/qcom/smem_state.c | 201 +++++++
drivers/soc/qcom/smp2p.c | 578 +++++++++++++++++++
drivers/soc/qcom/smsm.c | 625 +++++++++++++++++++++
include/linux/soc/qcom/smem_state.h | 18 +
8 files changed, 1652 insertions(+)
create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,smp2p.txt
create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,smsm.txt
create mode 100644 drivers/soc/qcom/smem_state.c
create mode 100644 drivers/soc/qcom/smp2p.c
create mode 100644 drivers/soc/qcom/smsm.c
create mode 100644 include/linux/soc/qcom/smem_state.h
--
1.8.2.2
next reply other threads:[~2015-09-25 1:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 1:24 Bjorn Andersson [this message]
2015-09-25 1:24 ` [PATCH v2 1/5] dt-binding: soc: qcom: Add Qualcomm SMSM device tree documentation Bjorn Andersson
2015-09-25 1:25 ` [PATCH v2 2/5] dt-binding: soc: qcom: Introduce qcom,smp2p binding documentation Bjorn Andersson
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=1443144303-21020-1-git-send-email-bjorn.andersson@sonymobile.com \
--to=bjorn.andersson@sonymobile.com \
--cc=agross@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
/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).