From: Rob Clark <robdclark@gmail.com>
To: dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org
Cc: Stephen Boyd <sboyd@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@sonymobile.com>
Subject: [PATCH 0/5] qcom-scm fixes and support for OCMEM
Date: Mon, 5 Oct 2015 10:22:06 -0400 [thread overview]
Message-ID: <1444054931-2147-1-git-send-email-robdclark@gmail.com> (raw)
Split out the restore-secure-config part from the ocmem lock/unlock,
and updates to address review comments.
Rob Clark (5):
qcom-scm: fix endianess issue in __qcom_scm_is_call_available
qcom-scm: fix header compile errors
qcom-scm: add missing prototype for qcom_scm_is_available()
qcom-scm: add support to restore secure config
qcom-scm: add OCMEM lock/unlock interface
drivers/firmware/qcom_scm-32.c | 60 ++++++++++++++++++++++++++++++++++++--
drivers/firmware/qcom_scm-64.c | 16 +++++++++++
drivers/firmware/qcom_scm.c | 65 ++++++++++++++++++++++++++++++++++++++++--
drivers/firmware/qcom_scm.h | 12 ++++++++
include/linux/qcom_scm.h | 16 +++++++++--
5 files changed, 162 insertions(+), 7 deletions(-)
--
2.4.3
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-10-05 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 14:22 Rob Clark [this message]
2015-10-05 14:22 ` [PATCH 1/5] qcom-scm: fix endianess issue in __qcom_scm_is_call_available Rob Clark
2015-10-05 14:22 ` [PATCH 2/5] qcom-scm: fix header compile errors Rob Clark
2015-10-05 14:22 ` [PATCH 3/5] qcom-scm: add missing prototype for qcom_scm_is_available() Rob Clark
2015-10-05 14:22 ` [PATCH 4/5] qcom-scm: add support to restore secure config Rob Clark
2015-10-05 14:29 ` Rob Clark
2015-10-06 23:48 ` [PATCH] " Rob Clark
2015-10-05 14:22 ` [PATCH 5/5] qcom-scm: add OCMEM lock/unlock interface Rob Clark
2015-10-05 15:41 ` Rob Clark
2015-10-06 23:49 ` [PATCH] " Rob Clark
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=1444054931-2147-1-git-send-email-robdclark@gmail.com \
--to=robdclark@gmail.com \
--cc=bjorn.andersson@sonymobile.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=sboyd@codeaurora.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).