From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Loic Poulain <loic.poulain@linaro.org>
Cc: catalin.marinas@arm.com, will@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] arm64: Add qcom Kconfig fragment
Date: Thu, 26 Dec 2019 22:39:15 -0800 [thread overview]
Message-ID: <20191227063915.GI1908628@ripper> (raw)
In-Reply-To: <1576850160-1564-1-git-send-email-loic.poulain@linaro.org>
On Fri 20 Dec 05:56 PST 2019, Loic Poulain wrote:
> Add qcom Kconfig fragment which enables the appropriate symbols for
> support of Qualcomm based boards, like the 'popular' dragonboards.
> This permits to fully support the boards upstream without having to
> rely on downstream deconfig changes.
>
> This patch has been tested with Dragonboard-410c and Dragonboard-820c.
>
As Catalin said, this should be added to the generic defconfig. I have a
few of these queued up already for v5.6 in linux-next, but please do
send me additional patches and I'll include them in the qcom/defconfig
branch.
> qcom.config fragment has been generated with ./script/diffconfig
>
> Signed-off-by: Loic Poulain <loic.poulain@linaro.org>
> ---
> arch/arm64/configs/qcom.config | 57 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 57 insertions(+)
> create mode 100644 arch/arm64/configs/qcom.config
>
> diff --git a/arch/arm64/configs/qcom.config b/arch/arm64/configs/qcom.config
> new file mode 100644
> index 0000000..9358df8
> --- /dev/null
> +++ b/arch/arm64/configs/qcom.config
> @@ -0,0 +1,57 @@
> +CONFIG_ARM_QCOM_CPUFREQ_HW=y
> +CONFIG_BT_HCIUART_3WIRE=y
> +CONFIG_BT_HCIUART_QCA=y
> +CONFIG_BT_HCIUART_RTL=y
> +CONFIG_CRYPTO_DEV_QCOM_RNG=y
=m
> +CONFIG_EXTCON_QCOM_SPMI_MISC=y
> +CONFIG_INTERCONNECT=y
> +CONFIG_MFD_QCOM_RPM=y
This is for 32-bit targets.
> +CONFIG_PHY_QCOM_PCIE2=y
=m
> +CONFIG_PHY_QCOM_QMP=y
=m
> +CONFIG_PHY_QCOM_QUSB2=y
=m
> +CONFIG_PHY_QCOM_UFS=y
I recently proposed a patch to add 8996 UFS support to the common QMP
driver, so hopefully we can get that merged for v5.6 instead.
> +CONFIG_PM8916_WATCHDOG=y
=m
> +CONFIG_POWER_RESET_QCOM_PON=y
=m
> +CONFIG_QCOM_APR=m
> +CONFIG_QCOM_FASTRPC=y
=m
> +CONFIG_QCOM_RMTFS_MEM=m
> +CONFIG_QCOM_RPMHPD=y
> +CONFIG_QCOM_RPMPD=y
> +CONFIG_QCOM_SOCINFO=m
> +CONFIG_QCOM_WCNSS_CTRL=m
> +CONFIG_QCOM_WCNSS_PIL=m
> +CONFIG_SCSI_UFS_QCOM=y
=m
> +CONFIG_SND_SOC_CROS_EC_CODEC=m
> +CONFIG_SND_SOC_MAX98927=m
> +CONFIG_SND_SOC_MSM8916_WCD_ANALOG=m
> +CONFIG_SND_SOC_MSM8916_WCD_DIGITAL=m
> +CONFIG_VIDEO_QCOM_CAMSS=m
> +CONFIG_VIDEO_QCOM_VENUS=m
> +CONFIG_WCN36XX=m
> +CONFIG_BT_QCA=m
> +CONFIG_BT_QCOMSMD=m
> +CONFIG_INTERCONNECT_QCOM=y
> +CONFIG_INTERCONNECT_QCOM_MSM8974=y
> +CONFIG_INTERCONNECT_QCOM_QCS404=y
> +CONFIG_INTERCONNECT_QCOM_SDM845=y
> +CONFIG_INTERCONNECT_QCOM_SMD_RPM=y
Selected as needed by previous options.
> +CONFIG_PHY_QCOM_UFS_14NM=y
Follows CONFIG_PHY_QCOM_UFS, and should be replaced by
CONFIG_PHY_QCOM_QMP
> +CONFIG_QCOM_CLK_RPM=y
> +CONFIG_REGULATOR_QCOM_RPM=y
These two are for 32-bit targets.
Regards,
Bjorn
> +CONFIG_SND_COMPRESS_OFFLOAD=y
> +CONFIG_SND_SOC_COMPRESS=y
> +CONFIG_SND_SOC_MSM8996=m
> +CONFIG_SND_SOC_QCOM_COMMON=m
> +CONFIG_SND_SOC_QDSP6=m
> +CONFIG_SND_SOC_QDSP6_ADM=m
> +CONFIG_SND_SOC_QDSP6_AFE=m
> +CONFIG_SND_SOC_QDSP6_AFE_DAI=m
> +CONFIG_SND_SOC_QDSP6_ASM=m
> +CONFIG_SND_SOC_QDSP6_ASM_DAI=m
> +CONFIG_SND_SOC_QDSP6_COMMON=m
> +CONFIG_SND_SOC_QDSP6_CORE=m
> +CONFIG_SND_SOC_QDSP6_ROUTING=m
> +CONFIG_SND_SOC_RT5663=m
> +CONFIG_SND_SOC_SDM845=m
> +CONFIG_VIDEOBUF2_DMA_SG=m
> +CONFIG_WCN36XX_DEBUGFS=y
> --
> 2.7.4
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-12-27 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 13:56 [PATCH] arm64: Add qcom Kconfig fragment Loic Poulain
2019-12-20 18:01 ` Catalin Marinas
2019-12-20 19:14 ` Brian Masney
2019-12-27 6:39 ` Bjorn Andersson [this message]
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=20191227063915.GI1908628@ripper \
--to=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=will@kernel.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).