LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Jordan Crouse <jcrouse@codeaurora.org> To: Vikash Garodia <vgarodia@codeaurora.org> Cc: hverkuil@xs4all.nl, mchehab@kernel.org, andy.gross@linaro.org, bjorn.andersson@linaro.org, stanimir.varbanov@linaro.org, linux-media@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org, acourbot@google.com Subject: Re: [PATCH 2/4] media: venus: add a routine to reset ARM9 Date: Thu, 17 May 2018 09:57:38 -0600 [thread overview] Message-ID: <20180517155737.GI4995@jcrouse-lnx.qualcomm.com> (raw) In-Reply-To: <1526556740-25494-3-git-send-email-vgarodia@codeaurora.org> On Thu, May 17, 2018 at 05:02:18PM +0530, Vikash Garodia wrote: > Add a new routine to reset the ARM9 and brings it > out of reset. This is in preparation to add PIL > functionality in venus driver. > > Signed-off-by: Vikash Garodia <vgarodia@codeaurora.org> > --- > drivers/media/platform/qcom/venus/firmware.c | 26 ++++++++++++++++++++++++ > drivers/media/platform/qcom/venus/firmware.h | 1 + > drivers/media/platform/qcom/venus/hfi_venus_io.h | 5 +++++ > 3 files changed, 32 insertions(+) > > diff --git a/drivers/media/platform/qcom/venus/firmware.c b/drivers/media/platform/qcom/venus/firmware.c > index c4a5778..8f25375 100644 > --- a/drivers/media/platform/qcom/venus/firmware.c > +++ b/drivers/media/platform/qcom/venus/firmware.c > @@ -14,6 +14,7 @@ > > #include <linux/device.h> > #include <linux/firmware.h> > +#include <linux/delay.h> > #include <linux/kernel.h> > #include <linux/io.h> > #include <linux/of.h> > @@ -22,11 +23,36 @@ > #include <linux/sizes.h> > #include <linux/soc/qcom/mdt_loader.h> > > +#include "core.h" > #include "firmware.h" > +#include "hfi_venus_io.h" > > #define VENUS_PAS_ID 9 > #define VENUS_FW_MEM_SIZE (6 * SZ_1M) > > +void venus_reset_hw(struct venus_core *core) > +{ > + void __iomem *reg_base = core->base; > + > + writel(0, reg_base + WRAPPER_FW_START_ADDR); > + writel(VENUS_FW_MEM_SIZE, reg_base + WRAPPER_FW_END_ADDR); > + writel(0, reg_base + WRAPPER_CPA_START_ADDR); > + writel(VENUS_FW_MEM_SIZE, reg_base + WRAPPER_CPA_END_ADDR); > + writel(0x0, reg_base + WRAPPER_CPU_CGC_DIS); > + writel(0x0, reg_base + WRAPPER_CPU_CLOCK_CONFIG); If you are going to have a bunch of writel() functions followed by a barrier it wouldn't hurt to use writel_relaxed() instead. Jordan > + /* Make sure all register writes are committed. */ > + mb(); > + > + /* > + * Need to wait 10 cycles of internal clocks before bringing ARM9 > + * out of reset. > + */ > + udelay(1); > + > + /* Bring Arm9 out of reset */ > + writel_relaxed(0, reg_base + WRAPPER_A9SS_SW_RESET); > +} > int venus_boot(struct device *dev, const char *fwname) > { > const struct firmware *mdt; > diff --git a/drivers/media/platform/qcom/venus/firmware.h b/drivers/media/platform/qcom/venus/firmware.h > index 428efb5..d56f5b2 100644 > --- a/drivers/media/platform/qcom/venus/firmware.h > +++ b/drivers/media/platform/qcom/venus/firmware.h > @@ -18,5 +18,6 @@ > > int venus_boot(struct device *dev, const char *fwname); > int venus_shutdown(struct device *dev); > +void venus_reset_hw(struct venus_core *core); > > #endif > diff --git a/drivers/media/platform/qcom/venus/hfi_venus_io.h b/drivers/media/platform/qcom/venus/hfi_venus_io.h > index 76f4793..39afa5d 100644 > --- a/drivers/media/platform/qcom/venus/hfi_venus_io.h > +++ b/drivers/media/platform/qcom/venus/hfi_venus_io.h > @@ -109,6 +109,11 @@ > #define WRAPPER_CPU_CGC_DIS (WRAPPER_BASE + 0x2010) > #define WRAPPER_CPU_STATUS (WRAPPER_BASE + 0x2014) > #define WRAPPER_SW_RESET (WRAPPER_BASE + 0x3000) > +#define WRAPPER_CPA_START_ADDR (WRAPPER_BASE + 0x1020) > +#define WRAPPER_CPA_END_ADDR (WRAPPER_BASE + 0x1024) > +#define WRAPPER_FW_START_ADDR (WRAPPER_BASE + 0x1028) > +#define WRAPPER_FW_END_ADDR (WRAPPER_BASE + 0x102C) > +#define WRAPPER_A9SS_SW_RESET (WRAPPER_BASE + 0x3000) > > /* Venus 4xx */ > #define WRAPPER_VCODEC0_MMCC_POWER_STATUS (WRAPPER_BASE + 0x90) -- The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2018-05-17 15:57 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-17 11:32 [PATCH 0/4] Venus updates - PIL Vikash Garodia 2018-05-17 11:32 ` [PATCH 1/4] soc: qcom: mdt_loader: Add check to make scm calls Vikash Garodia 2018-05-17 15:50 ` Jordan Crouse 2018-05-18 5:28 ` Bjorn Andersson 2018-05-18 7:18 ` Vikash Garodia 2018-05-17 11:32 ` [PATCH 2/4] media: venus: add a routine to reset ARM9 Vikash Garodia 2018-05-17 15:57 ` Jordan Crouse [this message] 2018-05-17 11:32 ` [PATCH 3/4] venus: add check to make scm calls Vikash Garodia 2018-05-22 13:04 ` Stanimir Varbanov 2018-05-22 19:50 ` Jordan Crouse 2018-05-22 20:57 ` Stanimir Varbanov 2018-05-23 5:30 ` Vikash Garodia 2018-05-17 11:32 ` [PATCH 4/4] media: venus: add PIL support Vikash Garodia 2018-05-18 0:40 ` Trilok Soni 2018-05-18 12:20 ` Vikash Garodia 2018-05-22 13:02 ` Stanimir Varbanov 2018-05-22 15:52 ` Stanimir Varbanov 2018-06-01 6:53 ` Vikash Garodia
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=20180517155737.GI4995@jcrouse-lnx.qualcomm.com \ --to=jcrouse@codeaurora.org \ --cc=acourbot@google.com \ --cc=andy.gross@linaro.org \ --cc=bjorn.andersson@linaro.org \ --cc=hverkuil@xs4all.nl \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-media@vger.kernel.org \ --cc=linux-soc@vger.kernel.org \ --cc=mchehab@kernel.org \ --cc=stanimir.varbanov@linaro.org \ --cc=vgarodia@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: linkBe 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).