[PATCH] arm64: defconfig: Enable Qualcomm Command DB driver

[PATCH] arm64: defconfig: Enable Qualcomm Command DB driver

[Bjorn Andersson]

The Qualcomm Command DB driver seems to have been indirectly enabled by
the Qualcomm DRM driver and up until the introduction of '778279f4f5e4
("soc: qcom: cmd-db: allow loading as a module")' this resulted in the
driver "always" being builtin on arm64. But with the introduction of
said change it, and all other RPMH related drivers, becomes =m.

The immediate result is that the uart driver fails to probe, which
depending on userspace's dependency on the presence of /dev/console
might be fatal. For systems getting past this the default timeout of 0
seconds for probe deferral of many subsystems causes the system to be
completely useless.

So, make Command DB builtin.

Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
---
 arch/arm64/configs/defconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 5cfe3cf6f2ac..9e0f664461f4 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -930,6 +930,7 @@ CONFIG_RASPBERRYPI_POWER=y
 CONFIG_FSL_DPAA=y
 CONFIG_FSL_MC_DPIO=y
 CONFIG_QCOM_AOSS_QMP=y
+CONFIG_QCOM_COMMAND_DB=y
 CONFIG_QCOM_GENI_SE=y
 CONFIG_QCOM_RMTFS_MEM=m
 CONFIG_QCOM_RPMH=y
-- 
2.28.0

[PATCH] arm64: defconfig: Enable Qualcomm Command DB driver

[Bjorn Andersson]

The Qualcomm Command DB driver seems to have been indirectly enabled by
the Qualcomm DRM driver and up until the introduction of '778279f4f5e4
("soc: qcom: cmd-db: allow loading as a module")' this resulted in the
driver "always" being builtin on arm64. But with the introduction of
said change it, and all other RPMH related drivers, becomes =m.

The immediate result is that the uart driver fails to probe, which
depending on userspace's dependency on the presence of /dev/console
might be fatal. For systems getting past this the default timeout of 0
seconds for probe deferral of many subsystems causes the system to be
completely useless.

So, make Command DB builtin.

Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
---
 arch/arm64/configs/defconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 5cfe3cf6f2ac..9e0f664461f4 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -930,6 +930,7 @@ CONFIG_RASPBERRYPI_POWER=y
 CONFIG_FSL_DPAA=y
 CONFIG_FSL_MC_DPIO=y
 CONFIG_QCOM_AOSS_QMP=y
+CONFIG_QCOM_COMMAND_DB=y
 CONFIG_QCOM_GENI_SE=y
 CONFIG_QCOM_RMTFS_MEM=m
 CONFIG_QCOM_RPMH=y
-- 
2.28.0


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Re: [PATCH] arm64: defconfig: Enable Qualcomm Command DB driver

[Vinod Koul]

On 02-11-20, 17:08, Bjorn Andersson wrote:
> The Qualcomm Command DB driver seems to have been indirectly enabled by
> the Qualcomm DRM driver and up until the introduction of '778279f4f5e4
> ("soc: qcom: cmd-db: allow loading as a module")' this resulted in the
> driver "always" being builtin on arm64. But with the introduction of
> said change it, and all other RPMH related drivers, becomes =m.
> 
> The immediate result is that the uart driver fails to probe, which
> depending on userspace's dependency on the presence of /dev/console
> might be fatal. For systems getting past this the default timeout of 0
> seconds for probe deferral of many subsystems causes the system to be
> completely useless.
> 
> So, make Command DB builtin.

Reviewed-by: Vinod Koul <vkoul@kernel.org>

-- 
~Vinod

Re: [PATCH] arm64: defconfig: Enable Qualcomm Command DB driver

[Vinod Koul]

On 02-11-20, 17:08, Bjorn Andersson wrote:
> The Qualcomm Command DB driver seems to have been indirectly enabled by
> the Qualcomm DRM driver and up until the introduction of '778279f4f5e4
> ("soc: qcom: cmd-db: allow loading as a module")' this resulted in the
> driver "always" being builtin on arm64. But with the introduction of
> said change it, and all other RPMH related drivers, becomes =m.
> 
> The immediate result is that the uart driver fails to probe, which
> depending on userspace's dependency on the presence of /dev/console
> might be fatal. For systems getting past this the default timeout of 0
> seconds for probe deferral of many subsystems causes the system to be
> completely useless.
> 
> So, make Command DB builtin.

Reviewed-by: Vinod Koul <vkoul@kernel.org>

-- 
~Vinod

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel