From: Chris Lew <quic_clew@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Mark Brown <broonie@kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>
Subject: Re: [PATCH 2/2] remoteproc: qcom: select AUXILIARY_BUS
Date: Wed, 26 Jun 2024 14:26:12 -0700 [thread overview]
Message-ID: <30fd5a0f-d71e-4bcb-ac33-0a6f9bef2029@quicinc.com> (raw)
In-Reply-To: <20240626-qcom-pd-mapper-fix-deps-v1-2-644678dc4663@linaro.org>
On 6/26/2024 12:12 PM, Dmitry Baryshkov wrote:
> The QCOM_PD_MAPPER implementation made Qualcomm remoteproc drivers use
> auxiliary bus for the pd-mapper subdevice. Add necessary dependency.
>
> Reported-by: Mark Brown <broonie@kernel.org>
> Fixes: 5b9f51b200dc ("remoteproc: qcom: enable in-kernel PD mapper")
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> drivers/remoteproc/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig
> index 48845dc8fa85..dda2ada215b7 100644
> --- a/drivers/remoteproc/Kconfig
> +++ b/drivers/remoteproc/Kconfig
> @@ -166,6 +166,7 @@ config QCOM_PIL_INFO
>
> config QCOM_RPROC_COMMON
> tristate
> + select AUXILIARY_BUS
>
> config QCOM_Q6V5_COMMON
> tristate
>
Reviewed-by: Chris Lew <quic_clew@quicinc.com>
next prev parent reply other threads:[~2024-06-26 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 19:12 [PATCH 0/2] qcom: fix missing dependencies for the QCOM_PD_MAPPER Dmitry Baryshkov
2024-06-26 19:12 ` [PATCH 1/2] soc: qcom: add missing pd-mapper dependencies Dmitry Baryshkov
2024-06-26 21:26 ` Chris Lew
2024-06-26 19:12 ` [PATCH 2/2] remoteproc: qcom: select AUXILIARY_BUS Dmitry Baryshkov
2024-06-26 21:26 ` Chris Lew [this message]
2024-07-03 3:37 ` (subset) [PATCH 0/2] qcom: fix missing dependencies for the QCOM_PD_MAPPER 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=30fd5a0f-d71e-4bcb-ac33-0a6f9bef2029@quicinc.com \
--to=quic_clew@quicinc.com \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.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
all inboxes | Powered by JetHome®