From: Sibi Sankar <sibis@codeaurora.org>
To: bjorn.andersson@linaro.org
Cc: agross@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, swboyd@chromium.org,
manivannan.sadhasivam@linaro.org,
Sibi Sankar <sibis@codeaurora.org>
Subject: [PATCH v4 0/2] soc: qcom: aoss: Expose send for generic usecase
Date: Wed, 9 Jun 2021 16:48:50 +0530 [thread overview]
Message-ID: <1623237532-20829-1-git-send-email-sibis@codeaurora.org> (raw)
The patch series exposes functions to enable drivers to send their own
messages to AOSS (Always on Subsystem). It also adds a debugfs node for
qmp so messages can be sent to aoss for debugging and testing purposes.
V4:
* Fix compilation error due to missing qmp_put
* Minor typos [s/tarcks/tracks]
V3:
* Remove devm memory allocation
* Use refcount for qmp handle
* Update qmp_get/qmp_put/qmp_remove function with refcount logic
Deepak Kumar Singh (2):
soc: qcom: aoss: Expose send for generic usecase
soc: qcom: aoss: Add debugfs entry
drivers/soc/qcom/qcom_aoss.c | 109 ++++++++++++++++++++++++++++++++++++-
include/linux/soc/qcom/qcom_aoss.h | 36 ++++++++++++
2 files changed, 143 insertions(+), 2 deletions(-)
create mode 100644 include/linux/soc/qcom/qcom_aoss.h
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2021-06-09 11:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 11:18 Sibi Sankar [this message]
2021-06-09 11:18 ` [PATCH v4 1/2] soc: qcom: aoss: Expose send for generic usecase Sibi Sankar
2021-07-21 6:37 ` Stephen Boyd
2021-07-23 9:51 ` Deepak Kumar Singh
2021-07-23 19:28 ` Stephen Boyd
2021-06-09 11:18 ` [PATCH v4 2/2] soc: qcom: aoss: Add debugfs entry Sibi Sankar
2021-08-04 19:06 ` Bjorn Andersson
2021-06-14 10:21 [PATCH V4 0/2] soc: qcom: aoss: Expose send for generic usecase Deepak Kumar Singh
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=1623237532-20829-1-git-send-email-sibis@codeaurora.org \
--to=sibis@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=swboyd@chromium.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).