Remove older ARM msm SoC support
Subsystems (3)
cover Remove older ARM msm SoC support
Over the past few years, the ARM msm SoC tree has picked up support for a handfull of SoCs. Each of these targets had a brief period of activity, and has since only received trivial fixes. Support has only been minimal, generally serial console, and possibly storage. None of these saw conversion to device tree, and they contain a lot of headers and other aspects that prevent use in the ARM multi-platform kernel.
Current activity on MSM seems to be focused on newer SoCs. These devices have the advantage of having dev-boards available, so hopefully there will be more community activity. There also seems to be effort into better DT and multi-platform support on these targets, but not the older ones.
This patch series removes support for the three older Qualcomm SoC
families: 7x00, 7x30, and 8x50.
If there is a serious desire to support any of these SoCs, patches that make them properly support DT, and multi-platform can begin by adding the necessary files back.
Note that because these patches remove a lot of lines of code, and the lengths exceed the size typically allowed on the mailing lists, I've generated the patches with the '-D' option to format-patch. I can send full patches on request, and I've also made the patches available at:
git://git.kernel.org/pub/scm/linux/kernel/git/davidb/linux-msm.git for-3.14/big-cleanup
David Brown (4):
ARM: msm: Remove unused board files
ARM: msm: Remove 7x00 support
ARM: msm: Remove 7x30 support
ARM: msm: Remove 8x50 support
arch/arm/mach-msm/Kconfig | 104 --- arch/arm/mach-msm/Makefile | 20 - arch/arm/mach-msm/board-halibut.c | 110 --- arch/arm/mach-msm/board-mahimahi.c | 88 -- arch/arm/mach-msm/board-msm7x30.c | 157 ---- arch/arm/mach-msm/board-qsd8x50.c | 213 ----- arch/arm/mach-msm/board-sapphire.c | 117 --- arch/arm/mach-msm/board-trout-gpio.c | 233 ----- arch/arm/mach-msm/board-trout-mmc.c | 185 ---- arch/arm/mach-msm/board-trout-panel.c | 292 ------- arch/arm/mach-msm/board-trout.c | 113 --- arch/arm/mach-msm/board-trout.h | 162 ---- arch/arm/mach-msm/clock-pcom.c | 177 ---- arch/arm/mach-msm/clock-pcom.h | 145 ---- arch/arm/mach-msm/devices-msm7x00.c | 480 ----------- arch/arm/mach-msm/devices-msm7x30.c | 246 ------ arch/arm/mach-msm/devices-qsd8x50.c | 388 --------- arch/arm/mach-msm/devices.h | 53 -- arch/arm/mach-msm/dma.c | 295 ------- arch/arm/mach-msm/gpiomux-8x50.c | 51 -- arch/arm/mach-msm/gpiomux-v1.h | 67 -- arch/arm/mach-msm/gpiomux.c | 111 --- arch/arm/mach-msm/gpiomux.h | 84 -- arch/arm/mach-msm/include/mach/entry-macro.S | 36 - arch/arm/mach-msm/include/mach/hardware.h | 18 - arch/arm/mach-msm/include/mach/irqs-7x00.h | 75 -- arch/arm/mach-msm/include/mach/irqs-7x30.h | 153 ---- arch/arm/mach-msm/include/mach/irqs-8x50.h | 88 -- arch/arm/mach-msm/include/mach/irqs.h | 37 - arch/arm/mach-msm/include/mach/msm_gpiomux.h | 38 - arch/arm/mach-msm/include/mach/msm_iomap-7x00.h | 108 --- arch/arm/mach-msm/include/mach/msm_iomap-7x30.h | 103 --- arch/arm/mach-msm/include/mach/msm_iomap-8x50.h | 125 --- arch/arm/mach-msm/include/mach/msm_iomap.h | 53 -- arch/arm/mach-msm/include/mach/msm_smd.h | 109 --- arch/arm/mach-msm/include/mach/sirc.h | 98 --- arch/arm/mach-msm/include/mach/vreg.h | 29 - arch/arm/mach-msm/io.c | 161 ---- arch/arm/mach-msm/irq-vic.c | 363 -------- arch/arm/mach-msm/irq.c | 151 ---- arch/arm/mach-msm/last_radio_log.c | 71 -- arch/arm/mach-msm/proc_comm.c | 129 --- arch/arm/mach-msm/proc_comm.h | 258 ------ arch/arm/mach-msm/sirc.c | 172 ---- arch/arm/mach-msm/smd.c | 1035 ----------------------- arch/arm/mach-msm/smd_debug.c | 311 ------- arch/arm/mach-msm/smd_private.h | 403 --------- arch/arm/mach-msm/vreg.c | 220 ----- 48 files changed, 8235 deletions(-) delete mode 100644 arch/arm/mach-msm/board-halibut.c delete mode 100644 arch/arm/mach-msm/board-mahimahi.c delete mode 100644 arch/arm/mach-msm/board-msm7x30.c delete mode 100644 arch/arm/mach-msm/board-qsd8x50.c delete mode 100644 arch/arm/mach-msm/board-sapphire.c delete mode 100644 arch/arm/mach-msm/board-trout-gpio.c delete mode 100644 arch/arm/mach-msm/board-trout-mmc.c delete mode 100644 arch/arm/mach-msm/board-trout-panel.c delete mode 100644 arch/arm/mach-msm/board-trout.c delete mode 100644 arch/arm/mach-msm/board-trout.h delete mode 100644 arch/arm/mach-msm/clock-pcom.c delete mode 100644 arch/arm/mach-msm/clock-pcom.h delete mode 100644 arch/arm/mach-msm/devices-msm7x00.c delete mode 100644 arch/arm/mach-msm/devices-msm7x30.c delete mode 100644 arch/arm/mach-msm/devices-qsd8x50.c delete mode 100644 arch/arm/mach-msm/devices.h delete mode 100644 arch/arm/mach-msm/dma.c delete mode 100644 arch/arm/mach-msm/gpiomux-8x50.c delete mode 100644 arch/arm/mach-msm/gpiomux-v1.h delete mode 100644 arch/arm/mach-msm/gpiomux.c delete mode 100644 arch/arm/mach-msm/gpiomux.h delete mode 100644 arch/arm/mach-msm/include/mach/entry-macro.S delete mode 100644 arch/arm/mach-msm/include/mach/hardware.h delete mode 100644 arch/arm/mach-msm/include/mach/irqs-7x00.h delete mode 100644 arch/arm/mach-msm/include/mach/irqs-7x30.h delete mode 100644 arch/arm/mach-msm/include/mach/irqs-8x50.h delete mode 100644 arch/arm/mach-msm/include/mach/irqs.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_gpiomux.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_iomap-7x00.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_iomap-7x30.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_iomap-8x50.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_iomap.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_smd.h delete mode 100644 arch/arm/mach-msm/include/mach/sirc.h delete mode 100644 arch/arm/mach-msm/include/mach/vreg.h delete mode 100644 arch/arm/mach-msm/io.c delete mode 100644 arch/arm/mach-msm/irq-vic.c delete mode 100644 arch/arm/mach-msm/irq.c delete mode 100644 arch/arm/mach-msm/last_radio_log.c delete mode 100644 arch/arm/mach-msm/proc_comm.c delete mode 100644 arch/arm/mach-msm/proc_comm.h delete mode 100644 arch/arm/mach-msm/sirc.c delete mode 100644 arch/arm/mach-msm/smd.c delete mode 100644 arch/arm/mach-msm/smd_debug.c delete mode 100644 arch/arm/mach-msm/smd_private.h delete mode 100644 arch/arm/mach-msm/vreg.c
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
PATCH 1/4 ARM: msm: Remove unused board files
These board files were added in 2010, and have never been compiled in the tree. If these targets were to be included, at this point, they would need to be done using device tree, so there is no reason to keep these files around.
---
Note that this patch was made with -D. I can send the full patch on request, and have also made the tree available at:
git://git.kernel.org/pub/scm/linux/kernel/git/davidb/linux-msm.git for-3.14/big-cleanup
arch/arm/mach-msm/board-mahimahi.c | 88 ---------------------------- arch/arm/mach-msm/board-sapphire.c | 117 ------------------------------------- 2 files changed, 205 deletions(-) delete mode 100644 arch/arm/mach-msm/board-mahimahi.c delete mode 100644 arch/arm/mach-msm/board-sapphire.c
arch/arm/mach-msm/board-mahimahi.c deleted +0 -0
arch/arm/mach-msm/board-sapphire.c deleted +0 -0
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
PATCH 2/4 ARM: msm: Remove 7x00 support
In reply to David BrownSupport for the MSM7x00 SoCs was added starting in 2008 based on code from Google's Android kernels. Platform support is fairly minimal, and there have primarily been trivial and cleanup changes to this code.
This code has not been converted to device tree, and is hindering supporting multi-platform on ARM. If someone wishes to continue support for this target, patches that provide devicetree and multi-platform support can start by re-adding these files.
---
Note that this patch was made with -D. I can send the full patch on request, and have also made the tree available at:
git://git.kernel.org/pub/scm/linux/kernel/git/davidb/linux-msm.git for-3.14/big-cleanup
arch/arm/mach-msm/Kconfig | 32 +- arch/arm/mach-msm/Makefile | 4 - arch/arm/mach-msm/board-halibut.c | 110 ------ arch/arm/mach-msm/board-trout-gpio.c | 233 ------------ arch/arm/mach-msm/board-trout-mmc.c | 185 --------- arch/arm/mach-msm/board-trout-panel.c | 292 -------------- arch/arm/mach-msm/board-trout.c | 113 ------ arch/arm/mach-msm/board-trout.h | 162 -------- arch/arm/mach-msm/devices-msm7x00.c | 480 ------------------------ arch/arm/mach-msm/include/mach/irqs-7x00.h | 75 ---- arch/arm/mach-msm/include/mach/msm_iomap-7x00.h | 108 ------ arch/arm/mach-msm/irq.c | 151 -------- 12 files changed, 1 insertion(+), 1944 deletions(-) delete mode 100644 arch/arm/mach-msm/board-halibut.c delete mode 100644 arch/arm/mach-msm/board-trout-gpio.c delete mode 100644 arch/arm/mach-msm/board-trout-mmc.c delete mode 100644 arch/arm/mach-msm/board-trout-panel.c delete mode 100644 arch/arm/mach-msm/board-trout.c delete mode 100644 arch/arm/mach-msm/board-trout.h delete mode 100644 arch/arm/mach-msm/devices-msm7x00.c delete mode 100644 arch/arm/mach-msm/include/mach/irqs-7x00.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_iomap-7x00.h delete mode 100644 arch/arm/mach-msm/irq.c
arch/arm/mach-msm/Kconfig +1 -31
@@ -5,19 +5,9 @@ comment "Qualcomm MSM SoC Type" choice prompt "Qualcomm MSM SoC Type" - default ARCH_MSM7X00A + default ARCH_MSM7X30 depends on !ARCH_MSM_DT -config ARCH_MSM7X00A - bool "MSM7x00A / MSM7x01A" - select ARCH_MSM_ARM11 - select CPU_V6 - select GPIO_MSM_V1 - select MACH_TROUT if !MACH_HALIBUT - select MSM_PROC_COMM - select MSM_SMD - select MSM_SMD_PKG3 - config ARCH_MSM7X30 bool "MSM7x30" select ARCH_MSM_SCORPION
@@ -70,9 +60,6 @@ config MSM_HAS_DEBUG_UART_HS config MSM_SOC_REV_A bool -config ARCH_MSM_ARM11 - bool - config ARCH_MSM_SCORPION bool
@@ -82,20 +69,6 @@ config MSM_VIC menu "Qualcomm MSM Board Type" depends on !ARCH_MSM_DT -config MACH_HALIBUT - depends on ARCH_MSM - depends on ARCH_MSM7X00A - bool "Halibut Board (QCT SURF7201A)" - help - Support for the Qualcomm SURF7201A eval board. - -config MACH_TROUT - depends on ARCH_MSM - depends on ARCH_MSM7X00A - bool "HTC Dream (aka trout)" - help - Support for the HTC Dream, T-Mobile G1, Android ADP1 devices. - config MACH_MSM7X30_SURF depends on ARCH_MSM7X30 bool "MSM7x30 SURF"
@@ -117,9 +90,6 @@ config MACH_QSD8X50A_ST1_5 endmenu -config MSM_SMD_PKG3 - bool - config MSM_PROC_COMM bool
arch/arm/mach-msm/Makefile +0 -4
@@ -3,7 +3,6 @@ obj-y += clock.o obj-$(CONFIG_MSM_VIC) += irq-vic.o -obj-$(CONFIG_ARCH_MSM7X00A) += irq.o obj-$(CONFIG_ARCH_QSD8X50) += sirc.o obj-$(CONFIG_MSM_PROC_COMM) += proc_comm.o clock-pcom.o vreg.o
@@ -21,9 +20,6 @@ CFLAGS_scm.o :=$(call as-instr,.arch_extension sec,-DREQUIRES_SEC=1) obj-$(CONFIG_HOTPLUG_CPU) += hotplug.o obj-$(CONFIG_SMP) += headsmp.o platsmp.o -obj-$(CONFIG_MACH_TROUT) += board-trout.o board-trout-gpio.o board-trout-mmc.o devices-msm7x00.o -obj-$(CONFIG_MACH_TROUT) += board-trout.o board-trout-gpio.o board-trout-mmc.o board-trout-panel.o devices-msm7x00.o -obj-$(CONFIG_MACH_HALIBUT) += board-halibut.o devices-msm7x00.o obj-$(CONFIG_ARCH_MSM7X30) += board-msm7x30.o devices-msm7x30.o obj-$(CONFIG_ARCH_QSD8X50) += board-qsd8x50.o devices-qsd8x50.o obj-$(CONFIG_ARCH_MSM_DT) += board-dt.o
arch/arm/mach-msm/board-halibut.c deleted +0 -0
arch/arm/mach-msm/board-trout-gpio.c deleted +0 -0
arch/arm/mach-msm/board-trout-mmc.c deleted +0 -0
arch/arm/mach-msm/board-trout-panel.c deleted +0 -0
arch/arm/mach-msm/board-trout.c deleted +0 -0
arch/arm/mach-msm/board-trout.h deleted +0 -0
arch/arm/mach-msm/devices-msm7x00.c deleted +0 -0
arch/arm/mach-msm/include/mach/irqs-7x00.h deleted +0 -0
arch/arm/mach-msm/include/mach/msm_iomap-7x00.h deleted +0 -0
arch/arm/mach-msm/irq.c deleted +0 -0
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
PATCH 3/4 ARM: msm: Remove 7x30 support
In reply to David BrownThe MSM7x30 SoC support was added in 2009 based on code from Google's Android kernels. Platform support is fairly minimal, and the only changes that have been made have been trivial and cleanup changes.
This code has not been converted to device tree, and is hindering supporting multiple-platform on ARM. If someone wishes to continue support for this target, patches that provide devicetree and multi-platform support can start by re-adding these files.
---
Note that this patch was made with -D. I can send the full patch on request, and have also made the tree available at:
git://git.kernel.org/pub/scm/linux/kernel/git/davidb/linux-msm.git for-3.14/big-cleanup
arch/arm/mach-msm/Kconfig | 19 +- arch/arm/mach-msm/Makefile | 2 - arch/arm/mach-msm/board-msm7x30.c | 157 --------------- arch/arm/mach-msm/devices-msm7x30.c | 246 ------------------------ arch/arm/mach-msm/include/mach/irqs-7x30.h | 153 --------------- arch/arm/mach-msm/include/mach/msm_iomap-7x30.h | 103 ---------- 6 files changed, 1 insertion(+), 679 deletions(-) delete mode 100644 arch/arm/mach-msm/board-msm7x30.c delete mode 100644 arch/arm/mach-msm/devices-msm7x30.c delete mode 100644 arch/arm/mach-msm/include/mach/irqs-7x30.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_iomap-7x30.h
arch/arm/mach-msm/Kconfig +1 -18
@@ -5,20 +5,9 @@ comment "Qualcomm MSM SoC Type" choice prompt "Qualcomm MSM SoC Type" - default ARCH_MSM7X30 + default ARCH_QSD8X50 depends on !ARCH_MSM_DT -config ARCH_MSM7X30 - bool "MSM7x30" - select ARCH_MSM_SCORPION - select CPU_V7 - select GPIO_MSM_V1 - select MACH_MSM7X30_SURF # if ! - select MSM_GPIOMUX - select MSM_PROC_COMM - select MSM_SMD - select MSM_VIC - config ARCH_QSD8X50 bool "QSD8X50" select ARCH_MSM_SCORPION
@@ -69,12 +58,6 @@ config MSM_VIC menu "Qualcomm MSM Board Type" depends on !ARCH_MSM_DT -config MACH_MSM7X30_SURF - depends on ARCH_MSM7X30 - bool "MSM7x30 SURF" - help - Support for the Qualcomm MSM7x30 SURF eval board. - config MACH_QSD8X50_SURF depends on ARCH_QSD8X50 bool "QSD8x50 SURF"
arch/arm/mach-msm/Makefile +0 -2
@@ -8,7 +8,6 @@ obj-$(CONFIG_ARCH_QSD8X50) += sirc.o obj-$(CONFIG_MSM_PROC_COMM) += proc_comm.o clock-pcom.o vreg.o obj-$(CONFIG_ARCH_MSM7X00A) += dma.o io.o -obj-$(CONFIG_ARCH_MSM7X30) += dma.o io.o obj-$(CONFIG_ARCH_QSD8X50) += dma.o io.o obj-$(CONFIG_MSM_SMD) += smd.o smd_debug.o
@@ -20,7 +19,6 @@ CFLAGS_scm.o :=$(call as-instr,.arch_extension sec,-DREQUIRES_SEC=1) obj-$(CONFIG_HOTPLUG_CPU) += hotplug.o obj-$(CONFIG_SMP) += headsmp.o platsmp.o -obj-$(CONFIG_ARCH_MSM7X30) += board-msm7x30.o devices-msm7x30.o obj-$(CONFIG_ARCH_QSD8X50) += board-qsd8x50.o devices-qsd8x50.o obj-$(CONFIG_ARCH_MSM_DT) += board-dt.o obj-$(CONFIG_MSM_GPIOMUX) += gpiomux.o
arch/arm/mach-msm/board-msm7x30.c deleted +0 -0
arch/arm/mach-msm/devices-msm7x30.c deleted +0 -0
arch/arm/mach-msm/include/mach/irqs-7x30.h deleted +0 -0
arch/arm/mach-msm/include/mach/msm_iomap-7x30.h deleted +0 -0
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
PATCH 4/4 ARM: msm: Remove 8x50 support
In reply to David BrownThe MSM8x50 SoC support was added in 2010 based on code from Google's Android kernels. Platform support is fairly minimal, and the only changes that have been made have been trivial and cleanup changes.
This code has not been converted to device tree, and is hindering support for the multi-platform kernel on ARM. If someone wishes to continue support for this target, patches that provide devicetree and multi-platform support can start by re-adding these files.
---
Note that this patch was made with -D. I can send the full patch on request, and have also made the tree available at:
git://git.kernel.org/pub/scm/linux/kernel/git/davidb/linux-msm.git for-3.14/big-cleanup
arch/arm/mach-msm/Kconfig | 57 -- arch/arm/mach-msm/Makefile | 14 - arch/arm/mach-msm/board-qsd8x50.c | 213 ----- arch/arm/mach-msm/clock-pcom.c | 177 ---- arch/arm/mach-msm/clock-pcom.h | 145 ---- arch/arm/mach-msm/devices-qsd8x50.c | 388 --------- arch/arm/mach-msm/devices.h | 53 -- arch/arm/mach-msm/dma.c | 295 ------- arch/arm/mach-msm/gpiomux-8x50.c | 51 -- arch/arm/mach-msm/gpiomux-v1.h | 67 -- arch/arm/mach-msm/gpiomux.c | 111 --- arch/arm/mach-msm/gpiomux.h | 84 -- arch/arm/mach-msm/include/mach/entry-macro.S | 36 - arch/arm/mach-msm/include/mach/hardware.h | 18 - arch/arm/mach-msm/include/mach/irqs-8x50.h | 88 -- arch/arm/mach-msm/include/mach/irqs.h | 37 - arch/arm/mach-msm/include/mach/msm_gpiomux.h | 38 - arch/arm/mach-msm/include/mach/msm_iomap-8x50.h | 125 --- arch/arm/mach-msm/include/mach/msm_iomap.h | 53 -- arch/arm/mach-msm/include/mach/msm_smd.h | 109 --- arch/arm/mach-msm/include/mach/sirc.h | 98 --- arch/arm/mach-msm/include/mach/vreg.h | 29 - arch/arm/mach-msm/io.c | 161 ---- arch/arm/mach-msm/irq-vic.c | 363 -------- arch/arm/mach-msm/last_radio_log.c | 71 -- arch/arm/mach-msm/proc_comm.c | 129 --- arch/arm/mach-msm/proc_comm.h | 258 ------ arch/arm/mach-msm/sirc.c | 172 ---- arch/arm/mach-msm/smd.c | 1035 ----------------------- arch/arm/mach-msm/smd_debug.c | 311 ------- arch/arm/mach-msm/smd_private.h | 403 --------- arch/arm/mach-msm/vreg.c | 220 ----- 32 files changed, 5409 deletions(-) delete mode 100644 arch/arm/mach-msm/board-qsd8x50.c delete mode 100644 arch/arm/mach-msm/clock-pcom.c delete mode 100644 arch/arm/mach-msm/clock-pcom.h delete mode 100644 arch/arm/mach-msm/devices-qsd8x50.c delete mode 100644 arch/arm/mach-msm/devices.h delete mode 100644 arch/arm/mach-msm/dma.c delete mode 100644 arch/arm/mach-msm/gpiomux-8x50.c delete mode 100644 arch/arm/mach-msm/gpiomux-v1.h delete mode 100644 arch/arm/mach-msm/gpiomux.c delete mode 100644 arch/arm/mach-msm/gpiomux.h delete mode 100644 arch/arm/mach-msm/include/mach/entry-macro.S delete mode 100644 arch/arm/mach-msm/include/mach/hardware.h delete mode 100644 arch/arm/mach-msm/include/mach/irqs-8x50.h delete mode 100644 arch/arm/mach-msm/include/mach/irqs.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_gpiomux.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_iomap-8x50.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_iomap.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_smd.h delete mode 100644 arch/arm/mach-msm/include/mach/sirc.h delete mode 100644 arch/arm/mach-msm/include/mach/vreg.h delete mode 100644 arch/arm/mach-msm/io.c delete mode 100644 arch/arm/mach-msm/irq-vic.c delete mode 100644 arch/arm/mach-msm/last_radio_log.c delete mode 100644 arch/arm/mach-msm/proc_comm.c delete mode 100644 arch/arm/mach-msm/proc_comm.h delete mode 100644 arch/arm/mach-msm/sirc.c delete mode 100644 arch/arm/mach-msm/smd.c delete mode 100644 arch/arm/mach-msm/smd_debug.c delete mode 100644 arch/arm/mach-msm/smd_private.h delete mode 100644 arch/arm/mach-msm/vreg.c
arch/arm/mach-msm/Kconfig +0 -57
@@ -3,24 +3,6 @@ if ARCH_MSM comment "Qualcomm MSM SoC Type" depends on ARCH_MSM_DT -choice - prompt "Qualcomm MSM SoC Type" - default ARCH_QSD8X50 - depends on !ARCH_MSM_DT - -config ARCH_QSD8X50 - bool "QSD8X50" - select ARCH_MSM_SCORPION - select CPU_V7 - select GPIO_MSM_V1 - select MACH_QSD8X50_SURF if !MACH_QSD8X50A_ST1_5 - select MSM_GPIOMUX - select MSM_PROC_COMM - select MSM_SMD - select MSM_VIC - -endchoice - config ARCH_MSM8X60 bool "MSM8X60" select ARM_GIC
@@ -46,45 +28,6 @@ config ARCH_MSM_DT config MSM_HAS_DEBUG_UART_HS bool -config MSM_SOC_REV_A - bool - -config ARCH_MSM_SCORPION - bool - -config MSM_VIC - bool - -menu "Qualcomm MSM Board Type" - depends on !ARCH_MSM_DT - -config MACH_QSD8X50_SURF - depends on ARCH_QSD8X50 - bool "QSD8x50 SURF" - help - Support for the Qualcomm QSD8x50 SURF eval board. - -config MACH_QSD8X50A_ST1_5 - depends on ARCH_QSD8X50 - bool "QSD8x50A ST1.5" - select MSM_SOC_REV_A - help - Support for the Qualcomm ST1.5. - -endmenu - -config MSM_PROC_COMM - bool - -config MSM_SMD - bool - -config MSM_GPIOMUX - bool - depends on !ARCH_MSM_DT - help - Support for MSM V1 TLMM GPIOMUX architecture. - config MSM_SCM bool endif
arch/arm/mach-msm/Makefile +0 -14
@@ -1,17 +1,6 @@ obj-y += timer.o obj-y += clock.o -obj-$(CONFIG_MSM_VIC) += irq-vic.o - -obj-$(CONFIG_ARCH_QSD8X50) += sirc.o - -obj-$(CONFIG_MSM_PROC_COMM) += proc_comm.o clock-pcom.o vreg.o - -obj-$(CONFIG_ARCH_MSM7X00A) += dma.o io.o -obj-$(CONFIG_ARCH_QSD8X50) += dma.o io.o - -obj-$(CONFIG_MSM_SMD) += smd.o smd_debug.o -obj-$(CONFIG_MSM_SMD) += last_radio_log.o obj-$(CONFIG_MSM_SCM) += scm.o scm-boot.o CFLAGS_scm.o :=$(call as-instr,.arch_extension sec,-DREQUIRES_SEC=1)
@@ -19,7 +8,4 @@ CFLAGS_scm.o :=$(call as-instr,.arch_extension sec,-DREQUIRES_SEC=1) obj-$(CONFIG_HOTPLUG_CPU) += hotplug.o obj-$(CONFIG_SMP) += headsmp.o platsmp.o -obj-$(CONFIG_ARCH_QSD8X50) += board-qsd8x50.o devices-qsd8x50.o obj-$(CONFIG_ARCH_MSM_DT) += board-dt.o -obj-$(CONFIG_MSM_GPIOMUX) += gpiomux.o -obj-$(CONFIG_ARCH_QSD8X50) += gpiomux-8x50.o
arch/arm/mach-msm/board-qsd8x50.c deleted +0 -0
arch/arm/mach-msm/clock-pcom.c deleted +0 -0
arch/arm/mach-msm/clock-pcom.h deleted +0 -0
arch/arm/mach-msm/devices-qsd8x50.c deleted +0 -0
arch/arm/mach-msm/devices.h deleted +0 -0
arch/arm/mach-msm/dma.c deleted +0 -0
arch/arm/mach-msm/gpiomux-8x50.c deleted +0 -0
arch/arm/mach-msm/gpiomux-v1.h deleted +0 -0
arch/arm/mach-msm/gpiomux.c deleted +0 -0
arch/arm/mach-msm/gpiomux.h deleted +0 -0
arch/arm/mach-msm/include/mach/entry-macro.S deleted +0 -0
arch/arm/mach-msm/include/mach/hardware.h deleted +0 -0
arch/arm/mach-msm/include/mach/irqs-8x50.h deleted +0 -0
arch/arm/mach-msm/include/mach/irqs.h deleted +0 -0
arch/arm/mach-msm/include/mach/msm_gpiomux.h deleted +0 -0
arch/arm/mach-msm/include/mach/msm_iomap-8x50.h deleted +0 -0
arch/arm/mach-msm/include/mach/msm_iomap.h deleted +0 -0
arch/arm/mach-msm/include/mach/msm_smd.h deleted +0 -0
arch/arm/mach-msm/include/mach/sirc.h deleted +0 -0
arch/arm/mach-msm/include/mach/vreg.h deleted +0 -0
arch/arm/mach-msm/io.c deleted +0 -0
arch/arm/mach-msm/irq-vic.c deleted +0 -0
arch/arm/mach-msm/last_radio_log.c deleted +0 -0
arch/arm/mach-msm/proc_comm.c deleted +0 -0
arch/arm/mach-msm/proc_comm.h deleted +0 -0
arch/arm/mach-msm/sirc.c deleted +0 -0
arch/arm/mach-msm/smd.c deleted +0 -0
arch/arm/mach-msm/smd_debug.c deleted +0 -0
arch/arm/mach-msm/smd_private.h deleted +0 -0
arch/arm/mach-msm/vreg.c deleted +0 -0
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
In reply to David BrownThat's not very nice .. You know there is a device connect with this that several of us have..
Quoted 163 lines · David Brown
Support for the MSM7x00 SoCs was added starting in 2008 based on code from Google's Android kernels. Platform support is fairly minimal, and there have primarily been trivial and cleanup changes to this code.
This code has not been converted to device tree, and is hindering supporting multi-platform on ARM. If someone wishes to continue support for this target, patches that provide devicetree and multi-platform support can start by re-adding these files.
Signed-off-by David Brown <[email protected]>---
Note that this patch was made with -D. I can send the full patch on request, and have also made the tree available at:
git://git.kernel.org/pub/scm/linux/kernel/git/davidb/linux-msm.gitfor-3.14/big-cleanuparch/arm/mach-msm/Kconfig | 32 +- arch/arm/mach-msm/Makefile | 4 - arch/arm/mach-msm/board-halibut.c | 110 ------ arch/arm/mach-msm/board-trout-gpio.c | 233 ------------ arch/arm/mach-msm/board-trout-mmc.c | 185 --------- arch/arm/mach-msm/board-trout-panel.c | 292 -------------- arch/arm/mach-msm/board-trout.c | 113 ------ arch/arm/mach-msm/board-trout.h | 162 -------- arch/arm/mach-msm/devices-msm7x00.c | 480 ------------------------ arch/arm/mach-msm/include/mach/irqs-7x00.h | 75 ---- arch/arm/mach-msm/include/mach/msm_iomap-7x00.h | 108 ------ arch/arm/mach-msm/irq.c | 151 -------- 12 files changed, 1 insertion(+), 1944 deletions(-) delete mode 100644 arch/arm/mach-msm/board-halibut.c delete mode 100644 arch/arm/mach-msm/board-trout-gpio.c delete mode 100644 arch/arm/mach-msm/board-trout-mmc.c delete mode 100644 arch/arm/mach-msm/board-trout-panel.c delete mode 100644 arch/arm/mach-msm/board-trout.c delete mode 100644 arch/arm/mach-msm/board-trout.h delete mode 100644 arch/arm/mach-msm/devices-msm7x00.c delete mode 100644 arch/arm/mach-msm/include/mach/irqs-7x00.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_iomap-7x00.h delete mode 100644 arch/arm/mach-msm/irq.carch/arm/mach-msm/Kconfig +1
-31@@ -5,19 +5,9 @@ comment "Qualcomm MSM SoC Type" choice prompt "Qualcomm MSM SoC Type" - default ARCH_MSM7X00A + default ARCH_MSM7X30 depends on !ARCH_MSM_DT -config ARCH_MSM7X00A - bool "MSM7x00A / MSM7x01A" - select ARCH_MSM_ARM11 - select CPU_V6 - select GPIO_MSM_V1 - select MACH_TROUT if !MACH_HALIBUT - select MSM_PROC_COMM - select MSM_SMD - select MSM_SMD_PKG3 - config ARCH_MSM7X30 bool "MSM7x30" select ARCH_MSM_SCORPION@@ -70,9 +60,6 @@ config MSM_HAS_DEBUG_UART_HS config MSM_SOC_REV_A bool -config ARCH_MSM_ARM11 - bool - config ARCH_MSM_SCORPION bool@@ -82,20 +69,6 @@ config MSM_VIC menu "Qualcomm MSM Board Type" depends on !ARCH_MSM_DT -config MACH_HALIBUT - depends on ARCH_MSM - depends on ARCH_MSM7X00A - bool "Halibut Board (QCT SURF7201A)" - help - Support for the Qualcomm SURF7201A eval board. - -config MACH_TROUT - depends on ARCH_MSM - depends on ARCH_MSM7X00A - bool "HTC Dream (aka trout)" - help - Support for the HTC Dream, T-Mobile G1, Android ADP1 devices. - config MACH_MSM7X30_SURF depends on ARCH_MSM7X30 bool "MSM7x30 SURF"@@ -117,9 +90,6 @@ config MACH_QSD8X50A_ST1_5 endmenu -config MSM_SMD_PKG3 - bool - config MSM_PROC_COMM boolarch/arm/mach-msm/Makefile +0
-4@@ -3,7 +3,6 @@ obj-y += clock.o obj-$(CONFIG_MSM_VIC) += irq-vic.o -obj-$(CONFIG_ARCH_MSM7X00A) += irq.o obj-$(CONFIG_ARCH_QSD8X50) += sirc.o obj-$(CONFIG_MSM_PROC_COMM) += proc_comm.o clock-pcom.o vreg.o@@ -21,9 +20,6 @@ CFLAGS_scm.o :=$(call as-instr,.arch_extension sec,-DREQUIRES_SEC=1) obj-$(CONFIG_HOTPLUG_CPU) += hotplug.o obj-$(CONFIG_SMP) += headsmp.o platsmp.o -obj-$(CONFIG_MACH_TROUT) += board-trout.o board-trout-gpio.o board-trout-mmc.o devices-msm7x00.o -obj-$(CONFIG_MACH_TROUT) += board-trout.o board-trout-gpio.o board-trout-mmc.o board-trout-panel.o devices-msm7x00.o -obj-$(CONFIG_MACH_HALIBUT) += board-halibut.o devices-msm7x00.o obj-$(CONFIG_ARCH_MSM7X30) += board-msm7x30.o devices-msm7x30.o obj-$(CONFIG_ARCH_QSD8X50) += board-qsd8x50.o devices-qsd8x50.o obj-$(CONFIG_ARCH_MSM_DT) += board-dt.oarch/arm/mach-msm/board-halibut.c deleted +0
-0arch/arm/mach-msm/board-trout-gpio.c deleted +0
-0arch/arm/mach-msm/board-trout-mmc.c deleted +0
-0arch/arm/mach-msm/board-trout-panel.c deleted +0
-0arch/arm/mach-msm/board-trout.c deleted +0
-0arch/arm/mach-msm/board-trout.h deleted +0
-0arch/arm/mach-msm/devices-msm7x00.c deleted +0
-0arch/arm/mach-msm/include/mach/irqs-7x00.h deleted +0
-0arch/arm/mach-msm/include/mach/msm_iomap-7x00.h deleted +0
-0arch/arm/mach-msm/irq.c deleted +0
-0Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
Daniel,
I would be very happy to take more code for the older Qualcomm chipset to enable full functionality for them, but it's been my impression that far from all that is needed to make it a useful platform is in the upstream kernel, and there's been no signs of more of it showing up at least in the last two years.
So we have a bit of a stalemate here -- the current Qualcomm team wants to avoid having to deal too much with the legacy platforms -- they are technically quite different from the current platforms and the divergence makes it hard to deal with supporting it all in a modern way without risking regressions. I tend to agree with them.
Just like omap split between omap1 and omap2plus, I think it's a time to create a mach-qcom instead, and move the modern (v7, most likely) platforms there -- enable them with device tree, modern framework infrastructure, etc. That way you can keep older platforms in mach-msm without risk of regressions, and they have a clean base to start on with their later platforms.
-Olof
Quoted 169 lines · Daniel Walker
That's not very nice .. You know there is a device connect with this that several of us have..
Quoted 163 lines · David Brown
Support for the MSM7x00 SoCs was added starting in 2008 based on code from Google's Android kernels. Platform support is fairly minimal, and there have primarily been trivial and cleanup changes to this code.
This code has not been converted to device tree, and is hindering supporting multi-platform on ARM. If someone wishes to continue support for this target, patches that provide devicetree and multi-platform support can start by re-adding these files.
Signed-off-by David Brown <[email protected]>---
Note that this patch was made with -D. I can send the full patch on request, and have also made the tree available at:
git://git.kernel.org/pub/scm/linux/kernel/git/davidb/linux-msm.gitfor-3.14/big-cleanuparch/arm/mach-msm/Kconfig | 32 +- arch/arm/mach-msm/Makefile | 4 - arch/arm/mach-msm/board-halibut.c | 110 ------ arch/arm/mach-msm/board-trout-gpio.c | 233 ------------ arch/arm/mach-msm/board-trout-mmc.c | 185 --------- arch/arm/mach-msm/board-trout-panel.c | 292 -------------- arch/arm/mach-msm/board-trout.c | 113 ------ arch/arm/mach-msm/board-trout.h | 162 -------- arch/arm/mach-msm/devices-msm7x00.c | 480 ------------------------ arch/arm/mach-msm/include/mach/irqs-7x00.h | 75 ---- arch/arm/mach-msm/include/mach/msm_iomap-7x00.h | 108 ------ arch/arm/mach-msm/irq.c | 151 -------- 12 files changed, 1 insertion(+), 1944 deletions(-) delete mode 100644 arch/arm/mach-msm/board-halibut.c delete mode 100644 arch/arm/mach-msm/board-trout-gpio.c delete mode 100644 arch/arm/mach-msm/board-trout-mmc.c delete mode 100644 arch/arm/mach-msm/board-trout-panel.c delete mode 100644 arch/arm/mach-msm/board-trout.c delete mode 100644 arch/arm/mach-msm/board-trout.h delete mode 100644 arch/arm/mach-msm/devices-msm7x00.c delete mode 100644 arch/arm/mach-msm/include/mach/irqs-7x00.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_iomap-7x00.h delete mode 100644 arch/arm/mach-msm/irq.carch/arm/mach-msm/Kconfig +1
-31@@ -5,19 +5,9 @@ comment "Qualcomm MSM SoC Type" choice prompt "Qualcomm MSM SoC Type" - default ARCH_MSM7X00A + default ARCH_MSM7X30 depends on !ARCH_MSM_DT -config ARCH_MSM7X00A - bool "MSM7x00A / MSM7x01A" - select ARCH_MSM_ARM11 - select CPU_V6 - select GPIO_MSM_V1 - select MACH_TROUT if !MACH_HALIBUT - select MSM_PROC_COMM - select MSM_SMD - select MSM_SMD_PKG3 - config ARCH_MSM7X30 bool "MSM7x30" select ARCH_MSM_SCORPION@@ -70,9 +60,6 @@ config MSM_HAS_DEBUG_UART_HS config MSM_SOC_REV_A bool -config ARCH_MSM_ARM11 - bool - config ARCH_MSM_SCORPION bool@@ -82,20 +69,6 @@ config MSM_VIC menu "Qualcomm MSM Board Type" depends on !ARCH_MSM_DT -config MACH_HALIBUT - depends on ARCH_MSM - depends on ARCH_MSM7X00A - bool "Halibut Board (QCT SURF7201A)" - help - Support for the Qualcomm SURF7201A eval board. - -config MACH_TROUT - depends on ARCH_MSM - depends on ARCH_MSM7X00A - bool "HTC Dream (aka trout)" - help - Support for the HTC Dream, T-Mobile G1, Android ADP1 devices. - config MACH_MSM7X30_SURF depends on ARCH_MSM7X30 bool "MSM7x30 SURF"@@ -117,9 +90,6 @@ config MACH_QSD8X50A_ST1_5 endmenu -config MSM_SMD_PKG3 - bool - config MSM_PROC_COMM boolarch/arm/mach-msm/Makefile +0
-4@@ -3,7 +3,6 @@ obj-y += clock.o obj-$(CONFIG_MSM_VIC) += irq-vic.o -obj-$(CONFIG_ARCH_MSM7X00A) += irq.o obj-$(CONFIG_ARCH_QSD8X50) += sirc.o obj-$(CONFIG_MSM_PROC_COMM) += proc_comm.o clock-pcom.o vreg.o@@ -21,9 +20,6 @@ CFLAGS_scm.o :=$(call as-instr,.arch_extension sec,-DREQUIRES_SEC=1) obj-$(CONFIG_HOTPLUG_CPU) += hotplug.o obj-$(CONFIG_SMP) += headsmp.o platsmp.o -obj-$(CONFIG_MACH_TROUT) += board-trout.o board-trout-gpio.o board-trout-mmc.o devices-msm7x00.o -obj-$(CONFIG_MACH_TROUT) += board-trout.o board-trout-gpio.o board-trout-mmc.o board-trout-panel.o devices-msm7x00.o -obj-$(CONFIG_MACH_HALIBUT) += board-halibut.o devices-msm7x00.o obj-$(CONFIG_ARCH_MSM7X30) += board-msm7x30.o devices-msm7x30.o obj-$(CONFIG_ARCH_QSD8X50) += board-qsd8x50.o devices-qsd8x50.o obj-$(CONFIG_ARCH_MSM_DT) += board-dt.oarch/arm/mach-msm/board-halibut.c deleted +0
-0arch/arm/mach-msm/board-trout-gpio.c deleted +0
-0arch/arm/mach-msm/board-trout-mmc.c deleted +0
-0arch/arm/mach-msm/board-trout-panel.c deleted +0
-0arch/arm/mach-msm/board-trout.c deleted +0
-0arch/arm/mach-msm/board-trout.h deleted +0
-0arch/arm/mach-msm/devices-msm7x00.c deleted +0
-0arch/arm/mach-msm/include/mach/irqs-7x00.h deleted +0
-0arch/arm/mach-msm/include/mach/msm_iomap-7x00.h deleted +0
-0arch/arm/mach-msm/irq.c deleted +0
-1--The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
Quoted 7 lines · Olof Johansson
Daniel,
I would be very happy to take more code for the older Qualcomm chipset to enable full functionality for them, but it's been my impression that far from all that is needed to make it a useful platform is in the upstream kernel, and there's been no signs of more of it showing up at least in the last two years.
Some of the platform code he's removing is not compiled right now. I would have liked to make it compile, but I don't care that much (and they don't either) ..
Quoted 5 lines
So we have a bit of a stalemate here -- the current Qualcomm team wants to avoid having to deal too much with the legacy platforms -- they are technically quite different from the current platforms and the divergence makes it hard to deal with supporting it all in a modern way without risking regressions. I tend to agree with them.
Oh what a sob story .. They can't claim to maintain msm except for the parts they don't like that much, thats not how it works. If you have a technical reason why you think hard to maintain code is "hard to deal with", please put that forth .
If they want they can start submitting their patches to me, and I can deal with their "hard to deal with" stuff..
Quoted 6 lines
Just like omap split between omap1 and omap2plus, I think it's a time to create a mach-qcom instead, and move the modern (v7, most likely) platforms there -- enable them with device tree, modern framework infrastructure, etc. That way you can keep older platforms in mach-msm without risk of regressions, and they have a clean base to start on with their later platforms.
Personally I think splitting mach- stuff isn't very useful or interesting.. There's just no technical reason for it, for example x86 and x86_64 was a win from my perspective , there's a lot more reason to keep similar things together than to split things up.
The whole risking regressions, do you have proof of why you think that's happening ? The inverse seems more likely..
Daniel
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
Quoted 4 lines · Daniel Walker
Personally I think splitting mach- stuff isn't very useful or interesting.. There's just no technical reason for it, for example x86 and
x86_64was a win from my perspective , there's a lot more reason to keep similar things together than to split things up.
There are definitely valid technical reasons for it; the old and new platforms share no code, and the legacy platforms are unlikely to be updated to modern infrastructure anytime soon. Other platforms are managed in similar manners, such as OMAP, imx/mxs, etc.
-Olof
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
Quoted 11 lines · Olof Johansson
Quoted 4 lines · Daniel Walker
Personally I think splitting mach- stuff isn't very useful or interesting.. There's just no technical reason for it, for example x86 and
x86_64was a win from my perspective , there's a lot more reason to keep similar things together than to split things up.There are definitely valid technical reasons for it; the old and new platforms share no code, and the legacy platforms are unlikely to be updated to modern infrastructure anytime soon. Other platforms are managed in similar manners, such as OMAP, imx/mxs, etc.
Yeah there are still few valid reasons to have separate mach directories.
The main reason why mach-omap2 was originally set up separately from mach-omap1 was because the IO space was different. And we could not properly deal with that until CONFIG_ARM_PATCH_PHYS_VIRT few years ago.
So we placed the shared code into plat-omap, which worked OK but is not really needed any longer with device tree. We have only dmtimer and legacy DMA code left in plat-omap pretty much. And those will be moved to live under drivers/.
Even with most issues fixed, it still does not not make sense to merge mach-omap1 and mach-omap2. For example, even if somebody wanted to do it as a hobby project, we'd have to compile things with v4 or v5 flags, which won't work properly for SMP cores at least :)
Regards,
Tony
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
In reply to Olof JohanssonQuoted 11 lines · Olof Johansson
Quoted 4 lines · Daniel Walker
Personally I think splitting mach- stuff isn't very useful or interesting.. There's just no technical reason for it, for example x86 and
x86_64was a win from my perspective , there's a lot more reason to keep similar things together than to split things up.There are definitely valid technical reasons for it; the old and new platforms share no code, and the legacy platforms are unlikely to be updated to modern infrastructure anytime soon. Other platforms are managed in similar manners, such as OMAP, imx/mxs, etc.
Are you speaking from a meta perspective , or you have specific example in msm code ?
Daniel
Re: [PATCH 3/4] ARM: msm: Remove 7x30 supporty
In reply to David BrownWhy wouldn't you just update it to use the device tree ? There are lots of phones our there using 7x30 ..
This is one that Qualcomm specifically upstreamed, so what was the point of upstreaming it ?
Quoted 103 lines · David Brown
The MSM7x30 SoC support was added in 2009 based on code from Google's Android kernels. Platform support is fairly minimal, and the only changes that have been made have been trivial and cleanup changes.
This code has not been converted to device tree, and is hindering supporting multiple-platform on ARM. If someone wishes to continue support for this target, patches that provide devicetree and multi-platform support can start by re-adding these files.
Signed-off-by David Brown <[email protected]>---
Note that this patch was made with -D. I can send the full patch on request, and have also made the tree available at:
git://git.kernel.org/pub/scm/linux/kernel/git/davidb/linux-msm.gitfor-3.14/big-cleanuparch/arm/mach-msm/Kconfig | 19 +- arch/arm/mach-msm/Makefile | 2 - arch/arm/mach-msm/board-msm7x30.c | 157 --------------- arch/arm/mach-msm/devices-msm7x30.c | 246 ------------------------ arch/arm/mach-msm/include/mach/irqs-7x30.h | 153 --------------- arch/arm/mach-msm/include/mach/msm_iomap-7x30.h | 103 ---------- 6 files changed, 1 insertion(+), 679 deletions(-) delete mode 100644 arch/arm/mach-msm/board-msm7x30.c delete mode 100644 arch/arm/mach-msm/devices-msm7x30.c delete mode 100644 arch/arm/mach-msm/include/mach/irqs-7x30.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_iomap-7x30.harch/arm/mach-msm/Kconfig +1
-18@@ -5,20 +5,9 @@ comment "Qualcomm MSM SoC Type" choice prompt "Qualcomm MSM SoC Type" - default ARCH_MSM7X30 + default ARCH_QSD8X50 depends on !ARCH_MSM_DT -config ARCH_MSM7X30 - bool "MSM7x30" - select ARCH_MSM_SCORPION - select CPU_V7 - select GPIO_MSM_V1 - select MACH_MSM7X30_SURF # if ! - select MSM_GPIOMUX - select MSM_PROC_COMM - select MSM_SMD - select MSM_VIC - config ARCH_QSD8X50 bool "QSD8X50" select ARCH_MSM_SCORPION@@ -69,12 +58,6 @@ config MSM_VIC menu "Qualcomm MSM Board Type" depends on !ARCH_MSM_DT -config MACH_MSM7X30_SURF - depends on ARCH_MSM7X30 - bool "MSM7x30 SURF" - help - Support for the Qualcomm MSM7x30 SURF eval board. - config MACH_QSD8X50_SURF depends on ARCH_QSD8X50 bool "QSD8x50 SURF"arch/arm/mach-msm/Makefile +0
-2@@ -8,7 +8,6 @@ obj-$(CONFIG_ARCH_QSD8X50) += sirc.o obj-$(CONFIG_MSM_PROC_COMM) += proc_comm.o clock-pcom.o vreg.o obj-$(CONFIG_ARCH_MSM7X00A) += dma.o io.o -obj-$(CONFIG_ARCH_MSM7X30) += dma.o io.o obj-$(CONFIG_ARCH_QSD8X50) += dma.o io.o obj-$(CONFIG_MSM_SMD) += smd.o smd_debug.o@@ -20,7 +19,6 @@ CFLAGS_scm.o :=$(call as-instr,.arch_extension sec,-DREQUIRES_SEC=1) obj-$(CONFIG_HOTPLUG_CPU) += hotplug.o obj-$(CONFIG_SMP) += headsmp.o platsmp.o -obj-$(CONFIG_ARCH_MSM7X30) += board-msm7x30.o devices-msm7x30.o obj-$(CONFIG_ARCH_QSD8X50) += board-qsd8x50.o devices-qsd8x50.o obj-$(CONFIG_ARCH_MSM_DT) += board-dt.o obj-$(CONFIG_MSM_GPIOMUX) += gpiomux.oarch/arm/mach-msm/board-msm7x30.c deleted +0
-0arch/arm/mach-msm/devices-msm7x30.c deleted +0
-0arch/arm/mach-msm/include/mach/irqs-7x30.h deleted +0
-0arch/arm/mach-msm/include/mach/msm_iomap-7x30.h deleted +0
-0Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
Re: [PATCH 4/4] ARM: msm: Remove 8x50 support
In reply to David BrownIsn't this the Nexus one platform ? Same as the last one , why don't you just update it to use the device tree? This doesn't seem like it would be all that difficult.
Quoted 279 lines · David Brown
The MSM8x50 SoC support was added in 2010 based on code from Google's Android kernels. Platform support is fairly minimal, and the only changes that have been made have been trivial and cleanup changes.
This code has not been converted to device tree, and is hindering support for the multi-platform kernel on ARM. If someone wishes to continue support for this target, patches that provide devicetree and multi-platform support can start by re-adding these files.
Signed-off-by David Brown <[email protected]>---
Note that this patch was made with -D. I can send the full patch on request, and have also made the tree available at:
git://git.kernel.org/pub/scm/linux/kernel/git/davidb/linux-msm.gitfor-3.14/big-cleanuparch/arm/mach-msm/Kconfig | 57 -- arch/arm/mach-msm/Makefile | 14 - arch/arm/mach-msm/board-qsd8x50.c | 213 ----- arch/arm/mach-msm/clock-pcom.c | 177 ---- arch/arm/mach-msm/clock-pcom.h | 145 ---- arch/arm/mach-msm/devices-qsd8x50.c | 388 --------- arch/arm/mach-msm/devices.h | 53 -- arch/arm/mach-msm/dma.c | 295 ------- arch/arm/mach-msm/gpiomux-8x50.c | 51 -- arch/arm/mach-msm/gpiomux-v1.h | 67 -- arch/arm/mach-msm/gpiomux.c | 111 --- arch/arm/mach-msm/gpiomux.h | 84 -- arch/arm/mach-msm/include/mach/entry-macro.S | 36 - arch/arm/mach-msm/include/mach/hardware.h | 18 - arch/arm/mach-msm/include/mach/irqs-8x50.h | 88 -- arch/arm/mach-msm/include/mach/irqs.h | 37 - arch/arm/mach-msm/include/mach/msm_gpiomux.h | 38 - arch/arm/mach-msm/include/mach/msm_iomap-8x50.h | 125 --- arch/arm/mach-msm/include/mach/msm_iomap.h | 53 -- arch/arm/mach-msm/include/mach/msm_smd.h | 109 --- arch/arm/mach-msm/include/mach/sirc.h | 98 --- arch/arm/mach-msm/include/mach/vreg.h | 29 - arch/arm/mach-msm/io.c | 161 ---- arch/arm/mach-msm/irq-vic.c | 363 -------- arch/arm/mach-msm/last_radio_log.c | 71 -- arch/arm/mach-msm/proc_comm.c | 129 --- arch/arm/mach-msm/proc_comm.h | 258 ------ arch/arm/mach-msm/sirc.c | 172 ---- arch/arm/mach-msm/smd.c | 1035 ----------------------- arch/arm/mach-msm/smd_debug.c | 311 ------- arch/arm/mach-msm/smd_private.h | 403 --------- arch/arm/mach-msm/vreg.c | 220 ----- 32 files changed, 5409 deletions(-) delete mode 100644 arch/arm/mach-msm/board-qsd8x50.c delete mode 100644 arch/arm/mach-msm/clock-pcom.c delete mode 100644 arch/arm/mach-msm/clock-pcom.h delete mode 100644 arch/arm/mach-msm/devices-qsd8x50.c delete mode 100644 arch/arm/mach-msm/devices.h delete mode 100644 arch/arm/mach-msm/dma.c delete mode 100644 arch/arm/mach-msm/gpiomux-8x50.c delete mode 100644 arch/arm/mach-msm/gpiomux-v1.h delete mode 100644 arch/arm/mach-msm/gpiomux.c delete mode 100644 arch/arm/mach-msm/gpiomux.h delete mode 100644 arch/arm/mach-msm/include/mach/entry-macro.S delete mode 100644 arch/arm/mach-msm/include/mach/hardware.h delete mode 100644 arch/arm/mach-msm/include/mach/irqs-8x50.h delete mode 100644 arch/arm/mach-msm/include/mach/irqs.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_gpiomux.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_iomap-8x50.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_iomap.h delete mode 100644 arch/arm/mach-msm/include/mach/msm_smd.h delete mode 100644 arch/arm/mach-msm/include/mach/sirc.h delete mode 100644 arch/arm/mach-msm/include/mach/vreg.h delete mode 100644 arch/arm/mach-msm/io.c delete mode 100644 arch/arm/mach-msm/irq-vic.c delete mode 100644 arch/arm/mach-msm/last_radio_log.c delete mode 100644 arch/arm/mach-msm/proc_comm.c delete mode 100644 arch/arm/mach-msm/proc_comm.h delete mode 100644 arch/arm/mach-msm/sirc.c delete mode 100644 arch/arm/mach-msm/smd.c delete mode 100644 arch/arm/mach-msm/smd_debug.c delete mode 100644 arch/arm/mach-msm/smd_private.h delete mode 100644 arch/arm/mach-msm/vreg.carch/arm/mach-msm/Kconfig +0
-57@@ -3,24 +3,6 @@ if ARCH_MSM comment "Qualcomm MSM SoC Type" depends on ARCH_MSM_DT -choice - prompt "Qualcomm MSM SoC Type" - default ARCH_QSD8X50 - depends on !ARCH_MSM_DT - -config ARCH_QSD8X50 - bool "QSD8X50" - select ARCH_MSM_SCORPION - select CPU_V7 - select GPIO_MSM_V1 - select MACH_QSD8X50_SURF if !MACH_QSD8X50A_ST1_5 - select MSM_GPIOMUX - select MSM_PROC_COMM - select MSM_SMD - select MSM_VIC - -endchoice - config ARCH_MSM8X60 bool "MSM8X60" select ARM_GIC@@ -46,45 +28,6 @@ config ARCH_MSM_DT config MSM_HAS_DEBUG_UART_HS bool -config MSM_SOC_REV_A - bool - -config ARCH_MSM_SCORPION - bool - -config MSM_VIC - bool - -menu "Qualcomm MSM Board Type" - depends on !ARCH_MSM_DT - -config MACH_QSD8X50_SURF - depends on ARCH_QSD8X50 - bool "QSD8x50 SURF" - help - Support for the Qualcomm QSD8x50 SURF eval board. - -config MACH_QSD8X50A_ST1_5 - depends on ARCH_QSD8X50 - bool "QSD8x50A ST1.5" - select MSM_SOC_REV_A - help - Support for the Qualcomm ST1.5. - -endmenu - -config MSM_PROC_COMM - bool - -config MSM_SMD - bool - -config MSM_GPIOMUX - bool - depends on !ARCH_MSM_DT - help - Support for MSM V1 TLMM GPIOMUX architecture. - config MSM_SCM bool endifarch/arm/mach-msm/Makefile +0
-14@@ -1,17 +1,6 @@ obj-y += timer.o obj-y += clock.o -obj-$(CONFIG_MSM_VIC) += irq-vic.o - -obj-$(CONFIG_ARCH_QSD8X50) += sirc.o - -obj-$(CONFIG_MSM_PROC_COMM) += proc_comm.o clock-pcom.o vreg.o - -obj-$(CONFIG_ARCH_MSM7X00A) += dma.o io.o -obj-$(CONFIG_ARCH_QSD8X50) += dma.o io.o - -obj-$(CONFIG_MSM_SMD) += smd.o smd_debug.o -obj-$(CONFIG_MSM_SMD) += last_radio_log.o obj-$(CONFIG_MSM_SCM) += scm.o scm-boot.o CFLAGS_scm.o :=$(call as-instr,.arch_extension sec,-DREQUIRES_SEC=1)@@ -19,7 +8,4 @@ CFLAGS_scm.o :=$(call as-instr,.arch_extension sec,-DREQUIRES_SEC=1) obj-$(CONFIG_HOTPLUG_CPU) += hotplug.o obj-$(CONFIG_SMP) += headsmp.o platsmp.o -obj-$(CONFIG_ARCH_QSD8X50) += board-qsd8x50.o devices-qsd8x50.o obj-$(CONFIG_ARCH_MSM_DT) += board-dt.o -obj-$(CONFIG_MSM_GPIOMUX) += gpiomux.o -obj-$(CONFIG_ARCH_QSD8X50) += gpiomux-8x50.oarch/arm/mach-msm/board-qsd8x50.c deleted +0
-0arch/arm/mach-msm/clock-pcom.c deleted +0
-0arch/arm/mach-msm/clock-pcom.h deleted +0
-0arch/arm/mach-msm/devices-qsd8x50.c deleted +0
-0arch/arm/mach-msm/devices.h deleted +0
-0arch/arm/mach-msm/dma.c deleted +0
-0arch/arm/mach-msm/gpiomux-8x50.c deleted +0
-0arch/arm/mach-msm/gpiomux-v1.h deleted +0
-0arch/arm/mach-msm/gpiomux.c deleted +0
-0arch/arm/mach-msm/gpiomux.h deleted +0
-0arch/arm/mach-msm/include/mach/entry-macro.S deleted +0
-0arch/arm/mach-msm/include/mach/hardware.h deleted +0
-0arch/arm/mach-msm/include/mach/irqs-8x50.h deleted +0
-0arch/arm/mach-msm/include/mach/irqs.h deleted +0
-0arch/arm/mach-msm/include/mach/msm_gpiomux.h deleted +0
-0arch/arm/mach-msm/include/mach/msm_iomap-8x50.h deleted +0
-0arch/arm/mach-msm/include/mach/msm_iomap.h deleted +0
-0arch/arm/mach-msm/include/mach/msm_smd.h deleted +0
-0arch/arm/mach-msm/include/mach/sirc.h deleted +0
-0arch/arm/mach-msm/include/mach/vreg.h deleted +0
-0arch/arm/mach-msm/io.c deleted +0
-0arch/arm/mach-msm/irq-vic.c deleted +0
-0arch/arm/mach-msm/last_radio_log.c deleted +0
-0arch/arm/mach-msm/proc_comm.c deleted +0
-0arch/arm/mach-msm/proc_comm.h deleted +0
-0arch/arm/mach-msm/sirc.c deleted +0
-0arch/arm/mach-msm/smd.c deleted +0
-0arch/arm/mach-msm/smd_debug.c deleted +0
-0arch/arm/mach-msm/smd_private.h deleted +0
-0arch/arm/mach-msm/vreg.c deleted +0
-0Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
Re: [PATCH 3/4] ARM: msm: Remove 7x30 supporty
In reply to Daniel WalkerQuoted 5 lines · Daniel Walker
Why wouldn't you just update it to use the device tree ? There are lots of phones our there using 7x30 ..
This is one that Qualcomm specifically upstreamed, so what was the point of upstreaming it ?
Things like this happen a lot: you start with great ambitions, then real life takes over and everybody who was once working on it has moved on to other projects before the code actually works.
We have the policy to let new code for incomplete platforms into the tree very liberally, but the flip side is that we have to remove them as swiftly if progress stops. Note that this is completely different from most of the older platforms like the StrongARM based machines that are way more outdated but are actually working just fine and getting fixed when they don't.
The MSM platform is currently a mess with most SoCs broken most of the time. I definitely agree with David's approach of removing the ones that are not being worked on and finally getting the newer ones to work properly, and on the same level as the other platforms.
Once that work is complete, adding back support for the older SoCs should become much easier if anyone is still interested, since the required changes (multiplatform, DT, ...) are targetted at reducing the effort of maintaining platforms.
Arnd
Re: [PATCH 4/4] ARM: msm: Remove 8x50 support
In reply to Daniel WalkerQuoted 3 lines · Daniel Walker
Isn't this the Nexus one platform ? Same as the last one , why don't you just update it to use the device tree? This doesn't seem like it would be all that difficult.
Please don't top-post.
Quoted 6 lines · David Brown
Quoted 5 lines
This code has not been converted to device tree, and is hindering support for the multi-platform kernel on ARM. If someone wishes to continue support for this target, patches that provide devicetree and multi-platform support can start by re-adding these files.
^ Here is your answer.
While I'd definitely love to see support for the Nexus One upstream, it is evident that nobody has been working on this for a long time.
Arnd
Re: [PATCH 4/4] ARM: msm: Remove 8x50 support
Quoted 6 lines · Arnd Bergmann
Quoted 3 lines · Daniel Walker
Isn't this the Nexus one platform ? Same as the last one , why don't you just update it to use the device tree? This doesn't seem like it would be all that difficult.
Please don't top-post.
Seriously ? I was responding to the whole comment, don't be so pedantic ..
Quoted 8 lines
Quoted 7 lines · David Brown
Quoted 5 lines
This code has not been converted to device tree, and is hindering support for the multi-platform kernel on ARM. If someone wishes to continue support for this target, patches that provide devicetree and multi-platform support can start by re-adding these files.
Quoted 5 lines
^ Here is your answer.
While I'd definitely love to see support for the Nexus One upstream, it is evident that nobody has been working on this for a long time.
I have a device with this chip in it .. I would like that device not to disappear from Linux .. Doing this puts an un-do burden on users who would like to see this support go in, but if it's removed like this that will never happen. No one has an much information on these chips as Qualcomm .. It's not realistic that any user would be able to do a lot without their support.. By allowing them to remove code for these device it effectively ends and chance of them have more code support added.. Yet the devices exist in mass amounts.
To be honest your not an MSM maintainer, are there are political issue related to this.. This isn't particularly technical because converting these relatively simple platform to the device tree shouldn't be all that difficult. To me Your involvement is puzzling .. Myself and my co-maintainers need to be the ones discussing this..
G1 code is also getting removed in this series, and the code for this creates a usable device .. The problem here is that you really can't start randomly removing support for platforms that people have and want them to continue working. We have a process for that, and typically user objections weight heavily in that process (read, feature-removal-schedule.txt)
Daniel
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
In reply to Olof JohanssonQuoted 11 lines · Olof Johansson
I would be very happy to take more code for the older Qualcomm chipset to enable full functionality for them, but it's been my impression that far from all that is needed to make it a useful platform is in the upstream kernel, and there's been no signs of more of it showing up at least in the last two years.
So we have a bit of a stalemate here -- the current Qualcomm team wants to avoid having to deal too much with the legacy platforms -- they are technically quite different from the current platforms and the divergence makes it hard to deal with supporting it all in a modern way without risking regressions. I tend to agree with them.
As do I.
Quoted 6 lines
Just like omap split between omap1 and omap2plus, I think it's a time to create a mach-qcom instead, and move the modern (v7, most likely) platforms there -- enable them with device tree, modern framework infrastructure, etc. That way you can keep older platforms in mach-msm without risk of regressions, and they have a clean base to start on with their later platforms.
I think this split approach is a good compromise.
If the maintainers of the current older platforms wish to bring them up to modern frameworks, we can consider combining again. If not, they the older platforms will take the same path as the rest of the older platforms that slowly fade away.
Kevin
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
Quoted 23 lines · Kevin Hilman
Quoted 11 lines · Olof Johansson
I would be very happy to take more code for the older Qualcomm chipset to enable full functionality for them, but it's been my impression that far from all that is needed to make it a useful platform is in the upstream kernel, and there's been no signs of more of it showing up at least in the last two years.
So we have a bit of a stalemate here -- the current Qualcomm team wants to avoid having to deal too much with the legacy platforms -- they are technically quite different from the current platforms and the divergence makes it hard to deal with supporting it all in a modern way without risking regressions. I tend to agree with them.
As do I.
Quoted 6 lines
Just like omap split between omap1 and omap2plus, I think it's a time to create a mach-qcom instead, and move the modern (v7, most likely) platforms there -- enable them with device tree, modern framework infrastructure, etc. That way you can keep older platforms in mach-msm without risk of regressions, and they have a clean base to start on with their later platforms.
Quoted 7 lines
I think this split approach is a good compromise.
If the maintainers of the current older platforms wish to bring them up to modern frameworks, we can consider combining again. If not, they the older platforms will take the same path as the rest of the older platforms that slowly fade away.
So the current users of those platforms are, what SOL ?
Daniel
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
Quoted 1 line · Daniel Walker
So the current users of those platforms are, what SOL ?
What users? Show me one.
-Olof
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
Quoted 6 lines · Olof Johansson
Quoted 1 line · Daniel Walker
So the current users of those platforms are, what SOL ?
What users? Show me one.
What am I chop liver ?
Daniel
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
Quoted 8 lines · Daniel Walker
Quoted 5 lines · Olof Johansson
Quoted 1 line · Daniel Walker
So the current users of those platforms are, what SOL ?
What users? Show me one.
What am I chop liver ?
Ah, right. So, what platforms do you currently rely on mainline support for? Please be precise so we can figure out what needs to be kept and not.
-Olof
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
Quoted 6 lines · Olof Johansson
Quoted 5 lines · Daniel Walker
Quoted 4 lines · Olof Johansson
Quoted 1 line · Daniel Walker
So the current users of those platforms are, what SOL ?
Quoted 7 lines
Quoted 3 lines
Quoted 1 line
What users? Show me one.
What am I chop liver ?
Ah, right. So, what platforms do you currently rely on mainline support for? Please be precise so we can figure out what needs to be kept and not.
The only one I don't have is 7x30, as I said in prior emails.
Daniel
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
Quoted 9 lines · Daniel Walker
Quoted 8 lines · Olof Johansson
Quoted 7 lines · Daniel Walker
Quoted 5 lines · Olof Johansson
Quoted 1 line · Daniel Walker
So the current users of those platforms are, what SOL ?
What users? Show me one.
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
What am I chop liver ?
Ah, right. So, what platforms do you currently rely on mainline support for? Please be precise so we can figure out what needs to be kept and not.
The only one I don't have is 7x30, as I said in prior emails.
That's not actually what I asked. Which ones of them do you rely on mainline support for?
-Olof
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
Quoted 12 lines · Olof Johansson
Quoted 11 lines · Daniel Walker
Quoted 10 lines · Olof Johansson
Quoted 8 lines · Daniel Walker
Quoted 5 lines · Olof Johansson
Quoted 1 line · Daniel Walker
So the current users of those platforms are, what SOL ?
What users? Show me one.
What am I chop liver ?
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
Ah, right. So, what platforms do you currently rely on mainline support for? Please be precise so we can figure out what needs to be kept and not.
The only one I don't have is 7x30, as I said in prior emails.
That's not actually what I asked. Which ones of them do you rely on mainline support for?
I rely on mainline support for 8x50 and G1 trout. This is starting to feel like an interogation .. The only reason I'm tolerating this is because I know you'll make some attempt to accept these patches over my already explicit objections.
Daniel
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
In reply to Daniel WalkerQuoted 26 lines · Daniel Walker
Quoted 25 lines · Kevin Hilman
Quoted 11 lines · Olof Johansson
I would be very happy to take more code for the older Qualcomm chipset to enable full functionality for them, but it's been my impression that far from all that is needed to make it a useful platform is in the upstream kernel, and there's been no signs of more of it showing up at least in the last two years.
So we have a bit of a stalemate here -- the current Qualcomm team wants to avoid having to deal too much with the legacy platforms -- they are technically quite different from the current platforms and the divergence makes it hard to deal with supporting it all in a modern way without risking regressions. I tend to agree with them.
As do I.
Quoted 6 lines
Just like omap split between omap1 and omap2plus, I think it's a time to create a mach-qcom instead, and move the modern (v7, most likely) platforms there -- enable them with device tree, modern framework infrastructure, etc. That way you can keep older platforms in mach-msm without risk of regressions, and they have a clean base to start on with their later platforms.
I think this split approach is a good compromise.
Quoted 7 lines
Quoted 5 lines
If the maintainers of the current older platforms wish to bring them up to modern frameworks, we can consider combining again. If not, they the older platforms will take the same path as the rest of the older platforms that slowly fade away.
So the current users of those platforms are, what SOL ?
No. The idea behind splitting them is to allow current platforms with active maintainers to progress without being held back. The older platforms can stay and have an opportunity to modernize.
The kernel is a moving target, without some minimal effort to keep platforms up to date, the effort to continue to maintain/modernize them can become more of a pain than it's worth. If maintainers of these older platforms are willing to put in the work, nobody will be SOL. If nobody shows interest in modernizing these older platforms (which seems to be the case based on the last couple years), then it is reasonable IMO for them to fade away slowly.
Kevin
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
Quoted 7 lines · Kevin Hilman
Daniel Walker <[email protected]> writes:
No. The idea behind splitting them is to allow current platforms with active maintainers to progress without being held back. The older platforms can stay and have an opportunity to modernize.
Quoted 7 lines
The kernel is a moving target, without some minimal effort to keep platforms up to date, the effort to continue to maintain/modernize them can become more of a pain than it's worth. If maintainers of these older platforms are willing to put in the work, nobody will be SOL. If nobody shows interest in modernizing these older platforms (which seems to be the case based on the last couple years), then it is reasonable IMO for them to fade away slowly.
According to a prior email Tony suggested that OMAP was split for purely technical reasons.. If code is shared in some way , or has synergies, and there's no technical reason to split a sub-architecture, then to me there's no win in splitting things.. It's just more directories, more confusion etc.. The confusion would come from someone wanting to find the code related to a platform, but woops there's a bunch of directories, or code flow and how the sub-architecture is strung together .. Personally I found OMAP very confusing in that regard.
ARM and the sub-architectures is already confusing I don't think we need to start compounding the problem by allowing random whatever-you-want sub-directories from every sub-architecture.
Daniel
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
Quoted 17 lines · Daniel Walker
Quoted 7 lines · Kevin Hilman
Daniel Walker <[email protected]> writes:
No. The idea behind splitting them is to allow current platforms with active maintainers to progress without being held back. The older platforms can stay and have an opportunity to modernize.
Quoted 7 lines
The kernel is a moving target, without some minimal effort to keep platforms up to date, the effort to continue to maintain/modernize them can become more of a pain than it's worth. If maintainers of these older platforms are willing to put in the work, nobody will be SOL. If nobody shows interest in modernizing these older platforms (which seems to be the case based on the last couple years), then it is reasonable IMO for them to fade away slowly.
Quoted 4 lines
According to a prior email Tony suggested that OMAP was split for purely technical reasons.. If code is shared in some way , or has synergies, and there's no technical reason to split a sub-architecture, then to me there's no win in splitting things..
The wins have already been well described in this thread in terms of maintenance of newer platforms using modern kernel infrastructure.
Quoted 9 lines
It's just more directories, more confusion etc.. The confusion would come from someone wanting to find the code related to a platform, but woops there's a bunch of directories, or code flow and how the sub-architecture is strung together .. Personally I found OMAP very confusing in that regard.
ARM and the sub-architectures is already confusing I don't think we need to start compounding the problem by allowing random whatever-you-want sub-directories from every sub-architecture.
Randomness is quite a bit of an exaggeration of what's been proposed here.
These decisions are made on a case-by-case basis and is this case is being done for ease of maintainence for newer platforms, which may not be a "technical reason" for you, but is important for overall maintenance of arm-soc.
If we do this split, you are more than welcome to demonstrate the commonality by modernizing mach-msm, combining it with mach-qcom, removing mach-msm, and then removing all the "confusion."
Kevin
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
In reply to Daniel WalkerQuoted 3 lines · Daniel Walker
ARM and the sub-architectures is already confusing I don't think we need to start compounding the problem by allowing random whatever-you-want sub-directories from every sub-architecture.
Confusing?
I'm not sure about that. It's actually really simple from my perspective:
arch/arm - the ARM 32-bit architecture
arch/arm/mach-* - support for a single SoC or a group of similar SoCs
arch/arm/plat-* - common support for a set of dissimilar SoCs which want
to share code between themselves
How is that confusing?
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
In reply to Kevin HilmanQuoted 19 lines · Kevin Hilman
Quoted 17 lines · Daniel Walker
Quoted 14 lines · Kevin Hilman
Daniel Walker <[email protected]> writes:
No. The idea behind splitting them is to allow current platforms with active maintainers to progress without being held back. The older platforms can stay and have an opportunity to modernize.
The kernel is a moving target, without some minimal effort to keep platforms up to date, the effort to continue to maintain/modernize them can become more of a pain than it's worth. If maintainers of these older platforms are willing to put in the work, nobody will be SOL. If nobody shows interest in modernizing these older platforms (which seems to be the case based on the last couple years), then it is reasonable IMO for them to fade away slowly.
Quoted 7 lines
Quoted 4 lines
According to a prior email Tony suggested that OMAP was split for purely technical reasons.. If code is shared in some way , or has synergies, and there's no technical reason to split a sub-architecture, then to me there's no win in splitting things..
The wins have already been well described in this thread in terms of maintenance of newer platforms using modern kernel infrastructure.
That's not very concrete .. Can you be specific, and what platforms are we talking about?
Quoted 6 lines
Quoted 6 lines
It's just more directories, more confusion etc.. The confusion would come from someone wanting to find the code related to a platform, but woops there's a bunch of directories, or code flow and how the sub-architecture is strung together .. Personally I found OMAP very confusing in that regard.
Quoted 6 lines
Quoted 3 lines
ARM and the sub-architectures is already confusing I don't think we need to start compounding the problem by allowing random whatever-you-want sub-directories from every sub-architecture.
Randomness is quite a bit of an exaggeration of what's been proposed here.
No one has proposed anything, as far as I can tell.
Quoted 4 lines
These decisions are made on a case-by-case basis and is this case is being done for ease of maintainence for newer platforms, which may not be a "technical reason" for you, but is important for overall maintenance of arm-soc.
Who's making this decision ? If there's some reason why maintenance is easier , can you explain it ? That's typically how we make decisions in this community there needs to be a clear reason to do something.
Quoted 3 lines
If we do this split, you are more than welcome to demonstrate the commonality by modernizing mach-msm, combining it with mach-qcom, removing mach-msm, and then removing all the "confusion."
Thanks, why not get it right the first time..
Daniel
Re: [PATCH 2/4] ARM: msm: Remove 7x00 support
In reply to Russell King - ARM LinuxQuoted 9 lines · Russell King - ARM Linux
Quoted 3 lines · Daniel Walker
ARM and the sub-architectures is already confusing I don't think we need to start compounding the problem by allowing random whatever-you-want sub-directories from every sub-architecture.
Confusing?
I'm not sure about that. It's actually really simple from my perspective:
Quoted 9 lines
arch/arm- the ARM 32-bit architecture
arch/arm/mach-*- support for a single SoC or a group of similar SoCs
arch/arm/plat-*- common support for a set of dissimilar SoCs which want
to share code between themselvesHow is that confusing?
It's the relationship between the arch/arm/mach-* and the arch/arm/plat-* and which ones connect with each other etc, and how the connection was actually done..
For me as a developer I found it confusing vs something that was fully integrated.
Daniel