From: "Arnd Bergmann" <arnd@arndb.de>
To: "Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Peter Griffin" <peter.griffin@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
krzysztof.kozlowski+dt@linaro.org,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
andi.shyti@kernel.org, "Alim Akhtar" <alim.akhtar@samsung.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
"Sylwester Nawrocki" <s.nawrocki@samsung.com>,
"Tomasz Figa" <tomasz.figa@gmail.com>,
"Chanwoo Choi" <cw00.choi@samsung.com>,
"Sam Protsenko" <semen.protsenko@linaro.org>
Cc: "André Draszik" <andre.draszik@linaro.org>,
saravanak@google.com,
"William McVicker" <willmcvicker@google.com>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH 12/13] arm64: defconfig: sync with savedefconfig
Date: Thu, 14 Dec 2023 13:08:08 +0100 [thread overview]
Message-ID: <1153987b-a818-454a-a292-57f2b3898771@app.fastmail.com> (raw)
In-Reply-To: <20231214105243.3707730-13-tudor.ambarus@linaro.org>
On Thu, Dec 14, 2023, at 11:52, Tudor Ambarus wrote:
> Sync the defconfig with savedefconfig as config options
> change/move over time.
>
> Generated with the following commands:
> make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- defconfig
> make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- savedefconfig
> cp defconfig arch/arm64/configs/defconfig
>
> Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
> ---
> arch/arm64/configs/defconfig | 144 +++++++++++++----------------------
> 1 file changed, 55 insertions(+), 89 deletions(-)
I usually ask for defconfig changes to be merged when someone just
adds a single line per patch, but a 144 line change is clearly too
big, please split this up.
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index b60aa1f89343..09fb467303ba 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -30,6 +30,8 @@ CONFIG_SCHED_AUTOGROUP=y
> CONFIG_BLK_DEV_INITRD=y
> CONFIG_KALLSYMS_ALL=y
> CONFIG_PROFILING=y
> +CONFIG_KEXEC_FILE=y
> +CONFIG_CRASH_DUMP=y
> CONFIG_ARCH_ACTIONS=y
> CONFIG_ARCH_SUNXI=y
> CONFIG_ARCH_ALPINE=y
> @@ -77,9 +79,6 @@ CONFIG_ARM64_VA_BITS_48=y
> CONFIG_SCHED_MC=y
> CONFIG_SCHED_SMT=y
> CONFIG_NUMA=y
> -CONFIG_KEXEC=y
> -CONFIG_KEXEC_FILE=y
> -CONFIG_CRASH_DUMP=y
> CONFIG_XEN=y
> CONFIG_COMPAT=y
> CONFIG_RANDOMIZE_BASE=y
These two hunks seem to go together, but it needs an explanation
why you are removing CONFIG_KEXEC.
> @@ -119,7 +118,6 @@ CONFIG_KVM=y
> CONFIG_JUMP_LABEL=y
> CONFIG_MODULES=y
> CONFIG_MODULE_UNLOAD=y
> -CONFIG_IOSCHED_BFQ=y
> # CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
> # CONFIG_COMPAT_BRK is not set
> CONFIG_MEMORY_HOTPLUG=y
No, I definitely want CONFIG_IOSCHED_BFQ=y, it is essential
for performance on certain classes of machines. It would
be better to drop the 'imply IOSCHED_BFQ' in two Kconfig
files.
> @@ -129,8 +127,6 @@ CONFIG_MEMORY_FAILURE=y
> CONFIG_TRANSPARENT_HUGEPAGE=y
> CONFIG_NET=y
> CONFIG_PACKET=y
> -CONFIG_UNIX=y
> -CONFIG_INET=y
> CONFIG_IP_MULTICAST=y
> CONFIG_IP_PNP=y
> CONFIG_IP_PNP_DHCP=y
These also seem kind of essential for almost any machine,
I assume you are doing something wrong here.
> @@ -180,8 +176,6 @@ CONFIG_NET_ACT_GATE=m
> CONFIG_QRTR_SMD=m
> CONFIG_QRTR_TUN=m
> CONFIG_CAN=m
> -CONFIG_CAN_M_CAN=m
> -CONFIG_CAN_M_CAN_PLATFORM=m
> CONFIG_BT=m
> CONFIG_BT_HIDP=m
> # CONFIG_BT_LE is not set
> @@ -384,6 +372,8 @@ CONFIG_DP83869_PHY=m
> CONFIG_DP83TD510_PHY=y
> CONFIG_VITESSE_PHY=y
> CONFIG_CAN_FLEXCAN=m
> +CONFIG_CAN_M_CAN=m
> +CONFIG_CAN_M_CAN_PLATFORM=m
> CONFIG_CAN_RCAR=m
> CONFIG_CAN_RCAR_CANFD=m
> CONFIG_CAN_MCP251XFD=m
These just get moved around in the file, please don't
mix those changes with other changes that change the behavior.
> @@ -215,27 +209,27 @@ CONFIG_PCI_PASID=y
> CONFIG_HOTPLUG_PCI=y
> CONFIG_HOTPLUG_PCI_ACPI=y
> CONFIG_PCI_AARDVARK=y
> -CONFIG_PCI_TEGRA=y
> -CONFIG_PCIE_RCAR_HOST=y
> -CONFIG_PCIE_RCAR_EP=y
> -CONFIG_PCI_HOST_GENERIC=y
> -CONFIG_PCI_XGENE=y
> CONFIG_PCIE_ALTERA=y
> CONFIG_PCIE_ALTERA_MSI=y
> +CONFIG_PCIE_BRCMSTB=m
> CONFIG_PCI_HOST_THUNDER_PEM=y
> CONFIG_PCI_HOST_THUNDER_ECAM=y
> -CONFIG_PCIE_ROCKCHIP_HOST=m
> +CONFIG_PCI_HOST_GENERIC=y
> CONFIG_PCIE_MEDIATEK_GEN3=m
> -CONFIG_PCIE_BRCMSTB=m
> +CONFIG_PCI_TEGRA=y
> +CONFIG_PCIE_RCAR_HOST=y
> +CONFIG_PCIE_RCAR_EP=y
> +CONFIG_PCIE_ROCKCHIP_HOST=m
> +CONFIG_PCI_XGENE=y
> CONFIG_PCI_IMX6_HOST=y
> CONFIG_PCI_LAYERSCAPE=y
> CONFIG_PCI_HISI=y
> -CONFIG_PCIE_QCOM=y
> -CONFIG_PCIE_ARMADA_8K=y
> -CONFIG_PCIE_ROCKCHIP_DW_HOST=y
> CONFIG_PCIE_KIRIN=y
> CONFIG_PCIE_HISI_STB=y
> +CONFIG_PCIE_ARMADA_8K=y
> CONFIG_PCIE_TEGRA194_HOST=m
> +CONFIG_PCIE_QCOM=y
> +CONFIG_PCIE_ROCKCHIP_DW_HOST=y
> CONFIG_PCIE_VISCONTI_HOST=y
> CONFIG_PCIE_LAYERSCAPE_GEN4=y
> CONFIG_PCI_ENDPOINT=y
Same here
> @@ -247,14 +241,12 @@ CONFIG_FW_LOADER_USER_HELPER=y
> CONFIG_HISILICON_LPC=y
> CONFIG_TEGRA_ACONNECT=m
> CONFIG_MHI_BUS_PCI_GENERIC=m
> -CONFIG_ARM_SCMI_PROTOCOL=y
> CONFIG_ARM_SCPI_PROTOCOL=y
> CONFIG_RASPBERRYPI_FIRMWARE=y
> CONFIG_INTEL_STRATIX10_SERVICE=y
> @@ -1185,7 +1168,6 @@ CONFIG_CROS_EC_RPMSG=m
> CONFIG_CROS_EC_SPI=y
> CONFIG_CROS_EC_CHARDEV=m
> CONFIG_COMMON_CLK_RK808=y
> -CONFIG_COMMON_CLK_SCMI=y
> CONFIG_COMMON_CLK_SCPI=y
> CONFIG_COMMON_CLK_CS2000_CP=y
> CONFIG_COMMON_CLK_FSL_SAI=y
This was caused by commit 9e4e24414cc6 ("arm64:
introduce STM32 family on Armv8 architecture"),
which selects ARM_SCMI_PROTOCOL and COMMON_CLK_SCMI.
I think we should instead revert those and enable
them in the defconfig for consistency with the other
platforms that need the same driver.
> CONFIG_INTEL_STRATIX10_RSU=m
> CONFIG_EFI_CAPSULE_LOADER=y
> CONFIG_IMX_SCU=y
> -CONFIG_IMX_SCU_PD=y
> CONFIG_GNSS=m
> CONFIG_GNSS_MTK_SERIAL=m
> CONFIG_MTD=y
> @@ -276,15 +268,12 @@ CONFIG_MTD_NAND_FSL_IFC=y
> CONFIG_MTD_NAND_QCOM=y
> CONFIG_MTD_SPI_NOR=y
> CONFIG_MTD_UBI=m
> -CONFIG_UBIFS_FS=m
> CONFIG_BLK_DEV_LOOP=y
> CONFIG_BLK_DEV_NBD=m
> CONFIG_VIRTIO_BLK=y
> CONFIG_BLK_DEV_NVME=m
> CONFIG_QCOM_COINCELL=m
> CONFIG_QCOM_FASTRPC=m
> -CONFIG_BATTERY_QCOM_BATTMGR=m
> -CONFIG_UCSI_PMIC_GLINK=m
> CONFIG_SRAM=y
> CONFIG_PCI_ENDPOINT_TEST=m
> CONFIG_EEPROM_AT24=m
Again, just moved around.
> @@ -308,7 +297,6 @@ CONFIG_AHCI_XGENE=y
> CONFIG_AHCI_QORIQ=y
> CONFIG_SATA_SIL24=y
> CONFIG_SATA_RCAR=y
> -CONFIG_PATA_PLATFORM=y
> CONFIG_PATA_OF_PLATFORM=y
> CONFIG_MD=y
> CONFIG_BLK_DEV_MD=m
For the ones that got removed for a good and trivial reason,
you can probably combine the patches and just list what
happened.
> @@ -635,7 +625,7 @@ CONFIG_GPIO_PCA953X_IRQ=y
> CONFIG_GPIO_BD9571MWV=m
> CONFIG_GPIO_MAX77620=y
> CONFIG_GPIO_SL28CPLD=m
> -CONFIG_GPIO_SYSCON=y
Apparently caused by GPIO_SAMA5D2_PIOBU, please change that
to 'depends on'.
> @@ -856,7 +843,6 @@ CONFIG_DRM_LONTIUM_LT9611UXC=m
> CONFIG_DRM_ITE_IT66121=m
> CONFIG_DRM_NWL_MIPI_DSI=m
> CONFIG_DRM_PARADE_PS8640=m
> -CONFIG_DRM_SAMSUNG_DSIM=m
> CONFIG_DRM_SII902X=m
> CONFIG_DRM_SIMPLE_BRIDGE=m
> CONFIG_DRM_THINE_THC63LVD1024=m
DRM_EXYNOS_DSI should probably depend on this rather than
selecting it.
> @@ -1203,18 +1185,6 @@ CONFIG_CLK_IMX8QXP=y
> CONFIG_CLK_IMX8ULP=y
> CONFIG_CLK_IMX93=y
> CONFIG_TI_SCI_CLK=y
> -CONFIG_COMMON_CLK_MT8192_AUDSYS=y
> -CONFIG_COMMON_CLK_MT8192_CAMSYS=y
> -CONFIG_COMMON_CLK_MT8192_IMGSYS=y
> -CONFIG_COMMON_CLK_MT8192_IMP_IIC_WRAP=y
> -CONFIG_COMMON_CLK_MT8192_IPESYS=y
> -CONFIG_COMMON_CLK_MT8192_MDPSYS=y
> -CONFIG_COMMON_CLK_MT8192_MFGCFG=y
> -CONFIG_COMMON_CLK_MT8192_MMSYS=y
> -CONFIG_COMMON_CLK_MT8192_MSDC=y
> -CONFIG_COMMON_CLK_MT8192_SCP_ADSP=y
> -CONFIG_COMMON_CLK_MT8192_VDECSYS=y
> -CONFIG_COMMON_CLK_MT8192_VENCSYS=y
> CONFIG_COMMON_CLK_QCOM=y
> CONFIG_QCOM_A53PLL=y
> CONFIG_QCOM_CLK_APCS_MSM8916=y
These looks legitimate
> @@ -1275,7 +1244,6 @@ CONFIG_TEGRA186_TIMER=y
> CONFIG_RENESAS_OSTM=y
> CONFIG_ARM_MHU=y
> CONFIG_IMX_MBOX=y
> -CONFIG_OMAP2PLUS_MBOX=m
> CONFIG_PLATFORM_MHU=y
> CONFIG_BCM2835_MBOX=y
> CONFIG_QCOM_APCS_IPC=y
Again we have a mix of select and depends:
drivers/remoteproc/Kconfig: select OMAP2PLUS_MBOX
drivers/remoteproc/Kconfig: select OMAP2PLUS_MBOX
drivers/remoteproc/Kconfig: select OMAP2PLUS_MBOX
drivers/soc/ti/Kconfig: depends on OMAP2PLUS_MBOX
We probably want the latter for all of them.
> @@ -1462,7 +1431,6 @@ CONFIG_PHY_J721E_WIZ=m
> CONFIG_ARM_CCI_PMU=m
> CONFIG_ARM_CCN=m
> CONFIG_ARM_CMN=m
> -CONFIG_ARM_CORESIGHT_PMU_ARCH_SYSTEM_PMU=m
> CONFIG_ARM_SMMU_V3_PMU=m
> CONFIG_ARM_DSU_PMU=m
> CONFIG_FSL_IMX8_DDR_PMU=m
> @@ -1471,6 +1439,7 @@ CONFIG_QCOM_L3_PMU=y
> CONFIG_ARM_SPE_PMU=m
> CONFIG_ARM_DMC620_PMU=m
> CONFIG_HISI_PMU=y
> +CONFIG_ARM_CORESIGHT_PMU_ARCH_SYSTEM_PMU=m
> CONFIG_MESON_DDR_PMU=m
> CONFIG_NVMEM_LAYOUT_SL28_VPD=m
> CONFIG_NVMEM_IMX_OCOTP=y
Just moved
> @@ -1498,10 +1467,8 @@ CONFIG_TEE=y
> CONFIG_OPTEE=y
> CONFIG_MUX_GPIO=m
> CONFIG_MUX_MMIO=y
> -CONFIG_SLIMBUS=m
> CONFIG_SLIM_QCOM_CTRL=m
Please fix SOUNDWIRE_QCOM to no longer 'imply SLIMBUS'.
> CONFIG_SLIM_QCOM_NGD_CTRL=m
> -CONFIG_INTERCONNECT=y
> CONFIG_INTERCONNECT_IMX=y
> CONFIG_INTERCONNECT_IMX8MM=m
> CONFIG_INTERCONNECT_IMX8MN=m
I think the problem here are some Tegra device drivers that
incorrectly 'select INTERCONNECT' rather than using the
'depends on' that every other interconnect driver has.
Please fix those instead.
> @@ -1544,8 +1511,8 @@ CONFIG_OVERLAY_FS=m
> CONFIG_VFAT_FS=y
> CONFIG_TMPFS_POSIX_ACL=y
> CONFIG_HUGETLBFS=y
> -CONFIG_CONFIGFS_FS=y
> CONFIG_EFIVAR_FS=y
For CONFIG_CONFIGFS_FS, we have a mix of 'depends on' and 'select'
in the Kconfig options that use it. Before you remove this here,
let's discuss with all the users which of the two should actually
be used and then change them to be consistent.
> @@ -1593,7 +1560,6 @@ CONFIG_DEBUG_INFO_REDUCED=y
> CONFIG_MAGIC_SYSRQ=y
> CONFIG_DEBUG_FS=y
> # CONFIG_SCHED_DEBUG is not set
> -# CONFIG_DEBUG_PREEMPT is not set
> # CONFIG_FTRACE is not set
> CONFIG_CORESIGHT=m
> CONFIG_CORESIGHT_LINK_AND_SINK_TMC=m
These looks sensible. Can you do the same thing for
arch/arm/configs/* in a combined patch?
Arnd
next prev parent reply other threads:[~2023-12-14 12:08 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 10:52 [PATCH 00/13] GS101 Oriole: CMU_PERIC0 support and USI updates Tudor Ambarus
2023-12-14 10:52 ` [PATCH 01/13] dt-bindings: clock: google,gs101: fix CMU_TOP gate clock names Tudor Ambarus
2023-12-14 15:07 ` Sam Protsenko
2023-12-14 15:16 ` Tudor Ambarus
2023-12-14 15:22 ` Sam Protsenko
2023-12-14 16:04 ` Peter Griffin
2023-12-15 8:13 ` Krzysztof Kozlowski
2023-12-15 10:23 ` Tudor Ambarus
2023-12-15 19:24 ` Krzysztof Kozlowski
2023-12-15 19:25 ` Krzysztof Kozlowski
2023-12-18 6:50 ` Tudor Ambarus
2023-12-14 10:52 ` [PATCH 02/13] dt-bindings: clock: google,gs101-clock: add PERIC0 clock management unit Tudor Ambarus
2023-12-14 15:12 ` Sam Protsenko
2023-12-20 15:07 ` Rob Herring
2023-12-21 7:20 ` Tudor Ambarus
2023-12-22 17:56 ` Peter Griffin
2023-12-27 12:38 ` Tudor Ambarus
2023-12-28 7:30 ` Krzysztof Kozlowski
2023-12-28 7:49 ` Tudor Ambarus
2023-12-14 10:52 ` [PATCH 03/13] dt-bindings: i2c: exynos5: add google,gs101-hsi2c compatible Tudor Ambarus
2023-12-14 13:06 ` Wolfram Sang
2023-12-14 15:12 ` Sam Protsenko
2023-12-15 19:42 ` Rob Herring
2023-12-14 10:52 ` [PATCH 04/13] dt-bindings: serial: samsung: gs101: make reg-io-width required property Tudor Ambarus
2023-12-14 15:14 ` Sam Protsenko
2023-12-15 7:58 ` Krzysztof Kozlowski
2023-12-14 10:52 ` [PATCH 05/13] tty: serial: samsung: add gs101 earlycon support Tudor Ambarus
2023-12-14 12:01 ` Arnd Bergmann
2023-12-14 13:52 ` Tudor Ambarus
2023-12-14 14:19 ` Arnd Bergmann
2023-12-14 14:31 ` Tudor Ambarus
2023-12-15 8:01 ` Krzysztof Kozlowski
2023-12-21 7:41 ` Tudor Ambarus
2023-12-14 10:52 ` [PATCH 06/13] clk: samsung: gs101: add support for cmu_peric0 Tudor Ambarus
2023-12-14 10:52 ` [PATCH 07/13] clk: samsung: gs101: mark PERIC0 IP TOP gate clock as critical Tudor Ambarus
2023-12-14 15:37 ` Sam Protsenko
2023-12-14 16:01 ` Tudor Ambarus
2023-12-14 16:09 ` Sam Protsenko
2023-12-14 16:15 ` Tudor Ambarus
2023-12-14 16:43 ` Sam Protsenko
2023-12-19 16:47 ` Tudor Ambarus
2023-12-19 17:31 ` Sam Protsenko
2023-12-20 14:22 ` Tudor Ambarus
2023-12-20 15:12 ` Sam Protsenko
2023-12-14 10:52 ` [PATCH 08/13] arm64: dts: exynos: gs101: enable cmu-peric0 clock controller Tudor Ambarus
2023-12-14 15:39 ` Sam Protsenko
2023-12-15 8:02 ` Krzysztof Kozlowski
2023-12-14 10:52 ` [PATCH 09/13] arm64: dts: exynos: gs101: update USI UART to use peric0 clocks Tudor Ambarus
2023-12-14 15:42 ` Sam Protsenko
2023-12-14 10:52 ` [PATCH 10/13] arm64: dts: exynos: gs101: define USI8 with I2C configuration Tudor Ambarus
2023-12-14 15:51 ` Sam Protsenko
2023-12-15 8:04 ` Krzysztof Kozlowski
2023-12-14 10:52 ` [PATCH 11/13] arm64: dts: exynos: gs101: enable eeprom on gs101-oriole Tudor Ambarus
2023-12-14 15:55 ` Sam Protsenko
2023-12-15 8:07 ` Krzysztof Kozlowski
2023-12-14 10:52 ` [PATCH 12/13] arm64: defconfig: sync with savedefconfig Tudor Ambarus
2023-12-14 12:08 ` Arnd Bergmann [this message]
2023-12-14 13:19 ` Krzysztof Kozlowski
2023-12-14 14:09 ` Tudor Ambarus
2023-12-14 10:52 ` [PATCH 13/13] arm64: defconfig: make at24 eeprom builtin Tudor Ambarus
2023-12-14 13:20 ` Krzysztof Kozlowski
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=1153987b-a818-454a-a292-57f2b3898771@app.fastmail.com \
--to=arnd@arndb.de \
--cc=alim.akhtar@samsung.com \
--cc=andi.shyti@kernel.org \
--cc=andre.draszik@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peter.griffin@linaro.org \
--cc=robh+dt@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=saravanak@google.com \
--cc=sboyd@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=tomasz.figa@gmail.com \
--cc=tudor.ambarus@linaro.org \
--cc=will@kernel.org \
--cc=willmcvicker@google.com \
/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