From: Avaneesh Kumar Dwivedi <akdwived@codeaurora.org>
To: bjorn.andersson@linaro.org
Cc: sboyd@codeaurora.org, agross@codeaurora.org,
linux-arm-msm@vger.kernel.org,
Avaneesh Kumar Dwivedi <akdwived@codeaurora.org>
Subject: [PATCH v4 01/10] remoteproc: qcom: Add and initialize private data for hexagon dsp.
Date: Wed, 16 Nov 2016 22:31:27 +0530 [thread overview]
Message-ID: <1479315696-15490-2-git-send-email-akdwived@codeaurora.org> (raw)
In-Reply-To: <1479315696-15490-1-git-send-email-akdwived@codeaurora.org>
Embed resources specific to version of hexagon chip in device
structure to avoid conditional check for manipulation of those
resources in driver code.
Signed-off-by: Avaneesh Kumar Dwivedi <akdwived@codeaurora.org>
---
.../devicetree/bindings/remoteproc/qcom,q6v5.txt | 1 +
drivers/remoteproc/qcom_q6v5_pil.c | 48 +++++++++++++++++++++-
2 files changed, 47 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt b/Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt
index 57cb49e..cbc165c 100644
--- a/Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt
+++ b/Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt
@@ -8,6 +8,7 @@ on the Qualcomm Hexagon core.
Value type: <string>
Definition: must be one of:
"qcom,q6v5-pil"
+ "qcom,q6v56-pil"
- reg:
Usage: required
diff --git a/drivers/remoteproc/qcom_q6v5_pil.c b/drivers/remoteproc/qcom_q6v5_pil.c
index 2e0caaa..7660012 100644
--- a/drivers/remoteproc/qcom_q6v5_pil.c
+++ b/drivers/remoteproc/qcom_q6v5_pil.c
@@ -30,13 +30,14 @@
#include <linux/reset.h>
#include <linux/soc/qcom/smem.h>
#include <linux/soc/qcom/smem_state.h>
+#include <linux/of_device.h>
#include "remoteproc_internal.h"
#include "qcom_mdt_loader.h"
#include <linux/qcom_scm.h>
-#define MBA_FIRMWARE_NAME "mba.b00"
+#define MBA_FIRMWARE_NAME "mba.b00"
#define MPSS_FIRMWARE_NAME "modem.mdt"
#define MPSS_CRASH_REASON_SMEM 421
@@ -93,6 +94,23 @@
#define QDSS_BHS_ON BIT(21)
#define QDSS_LDO_BYP BIT(22)
+struct q6_rproc_res {
+ char *q6_mba_image;
+ int (*q6_reset_init)(void *q, void *p);
+ char **proxy_reg_string;
+ char **active_reg_string;
+ int **proxy_voltage_load;
+ int **active_voltage_load;
+ char **proxy_clk_string;
+ char **active_clk_string;
+};
+
+struct reg_info {
+ struct regulator *reg;
+ int uV;
+ int uA;
+};
+
struct q6v5 {
struct device *dev;
struct rproc *rproc;
@@ -890,8 +908,34 @@ static int q6v5_remove(struct platform_device *pdev)
return 0;
}
+static char *proxy_q6v56_regulator_namestr[] = {"mx", "cx", "pll", NULL};
+static int proxy_q6v56_voltage_load[3][2] = { {1050000, 0}, {0, 100000},
+ {0, 100000} };
+static char *proxy_q6v56_clk_namestr[] = {"xo", "pnoc", "qdss", NULL};
+static char *active_q6v56_clk_namestr[] = {"iface", "bus", "mem",
+ "gpll0_mss_clk", "snoc_axi_clk", "mnoc_axi_clk", NULL};
+
+static const struct q6_rproc_res q6v56_res = {
+ .q6_reset_init = NULL,
+ .q6_mba_image = "mba.mbn",
+ .proxy_reg_string = proxy_q6v56_regulator_namestr,
+ .active_reg_string = NULL,
+ .proxy_voltage_load = (int **)proxy_q6v56_voltage_load,
+ .active_voltage_load = NULL,
+ .proxy_clk_string = proxy_q6v56_clk_namestr,
+ .active_clk_string = active_q6v56_clk_namestr,
+};
+
+static const struct q6_rproc_res q6v5_res = {
+ .q6_reset_init = NULL,
+ .q6_mba_image = "mba.mbn",
+ .proxy_reg_string = proxy_q6v56_regulator_namestr,
+ .proxy_voltage_load = (int **)proxy_q6v56_voltage_load,
+};
+
static const struct of_device_id q6v5_of_match[] = {
- { .compatible = "qcom,q6v5-pil", },
+ { .compatible = "qcom,q6v5-pil", .data = &q6v5_res},
+ { .compatible = "qcom,q6v56-pil", .data = &q6v56_res},
{ },
};
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2016-11-16 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 17:01 [PATCH v4 00/10]remoteproc: qcom: Add support to hexagon q6v56 in qcom hexagon rproc driver Avaneesh Kumar Dwivedi
2016-11-16 17:01 ` Avaneesh Kumar Dwivedi [this message]
2016-11-16 17:01 ` [PATCH v4 02/10] remoteproc: qcom: Initialize MSS reset control handle Avaneesh Kumar Dwivedi
2016-11-16 17:01 ` [PATCH v4 03/10] remoteproc: qcom: Initialize clock and regulator handle with private data Avaneesh Kumar Dwivedi
2016-11-16 17:01 ` [PATCH v4 04/10] remoteproc: qcom: Modify regulator enable and disable interface Avaneesh Kumar Dwivedi
2016-11-16 17:01 ` [PATCH v4 05/10] remoteproc: qcom: Separate out regulator disable routine in two Avaneesh Kumar Dwivedi
2016-11-16 17:01 ` [PATCH v4 06/10] remoteproc: qcom: Modify clock enable and disable routine Avaneesh Kumar Dwivedi
2016-11-16 17:01 ` [PATCH v4 07/10] remoteproc: qcom: Add new routine for mss restart programming Avaneesh Kumar Dwivedi
2016-11-16 17:01 ` [PATCH v4 08/10] remoteproc: qcom: Modify reset sequence for hexagon to support q6v56 Avaneesh Kumar Dwivedi
2016-11-16 17:01 ` [PATCH v4 09/10] remoteproc: qcom: Modify stop routine for q6v56 specific step Avaneesh Kumar Dwivedi
2016-11-16 17:01 ` [PATCH v4 10/10] remoteproc: qcom: Adding required initialization for q6v5 hexagon Avaneesh Kumar Dwivedi
2016-11-16 23:03 ` [PATCH v4 00/10]remoteproc: qcom: Add support to hexagon q6v56 in qcom hexagon rproc driver Stephen Boyd
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=1479315696-15490-2-git-send-email-akdwived@codeaurora.org \
--to=akdwived@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=bjorn.andersson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.