Further code removal after Arnd's latest cleanup
Subsystems (25)
cover Further code removal after Arnd's latest cleanup
Dear Arnd,
you have shared some further clean-up activities in linux-next (see the specific commits mentioned in the patches for details). This allows us to clean up even more code in the repository.
Please pick these patches on top of the commits mentioned in the corresponding patches (I assume that it is your soc-next tree?).
Best regards,
Lukas
Lukas Bulwahn (4):
ARM: s3c: remove obsolete s3c-cpu-freq header
ARM: pxa: remove further dead code after pxa93 support removal
usb: remove OMAP USB Device Controller and OHCI support for OMAP1/2
chips
ARM: debug: remove references in DEBUG_UART_8250_SHIFT to removed
configs
arch/arm/Kconfig.debug | 3 +- arch/arm/mach-omap1/board-osk.c | 5 - arch/arm/mach-omap1/omap-dma.c | 455 ---- arch/arm/mach-omap1/usb.c | 67 - arch/arm/mach-omap1/usb.h | 4 - drivers/usb/gadget/udc/Kconfig | 15 - drivers/usb/gadget/udc/Makefile | 1 - drivers/usb/gadget/udc/omap_udc.c | 3001 ---------------------- drivers/usb/gadget/udc/omap_udc.h | 207 -- drivers/usb/host/Kconfig | 8 - drivers/usb/host/Makefile | 1 - drivers/usb/host/ohci-omap.c | 435 ---- include/linux/omap-dma.h | 28 - include/linux/soc/pxa/cpu.h | 47 - include/linux/soc/samsung/s3c-cpu-freq.h | 145 -- 15 files changed, 1 insertion(+), 4421 deletions(-) delete mode 100644 drivers/usb/gadget/udc/omap_udc.c delete mode 100644 drivers/usb/gadget/udc/omap_udc.h delete mode 100644 drivers/usb/host/ohci-omap.c delete mode 100644 include/linux/soc/samsung/s3c-cpu-freq.h
Signature · 7 lines
2.17.1 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
PATCH 1/4 ARM: s3c: remove obsolete s3c-cpu-freq header
The s3c-cpu-freq header was previously included by:
./arch/arm/mach-s3c/mach-bast.c
./arch/arm/mach-s3c/mach-osiris-dvs.c
./arch/arm/mach-s3c/mach-osiris.c
./include/linux/soc/samsung/s3c-cpufreq-core.h
Commit a4946a153cb9 ("ARM: s3c: remove all s3c24xx support") removes the files in ./arch/arm/mach-s3c/; commit daf0ee583fc7 ("cpufreq: remove s3c24xx drivers") removes the file s3c-cpufreq-core.h.
Remove this obsolete header file.
This issue was identified, as s3c-cpu-freq.h referred to the removed config ARM_S3C_CPUFREQ.
--- include/linux/soc/samsung/s3c-cpu-freq.h | 145 ----------------------- 1 file changed, 145 deletions(-) delete mode 100644 include/linux/soc/samsung/s3c-cpu-freq.h
include/linux/soc/samsung/s3c-cpu-freq.h deleted +0 -145
@@ -1,145 +0,0 @@ -/* SPDX-License-Identifier: GPL-2.0 */ -/* -* Copyright (c) 2006-2007 Simtec Electronics -* http://armlinux.simtec.co.uk/ -* Ben Dooks <[email protected]> -* -* S3C CPU frequency scaling support - driver and board -*/ -#ifndef __LINUX_SOC_SAMSUNG_S3C_CPU_FREQ_H -#define __LINUX_SOC_SAMSUNG_S3C_CPU_FREQ_H - -#include <linux/cpufreq.h> - -struct s3c_cpufreq_info ; -struct s3c_cpufreq_board ; -struct s3c_iotimings ; - -/** -* struct s3c_freq - frequency information (mainly for core drivers) -* @fclk: The FCLK frequency in Hz. -* @armclk: The ARMCLK frequency in Hz. -* @hclk_tns: HCLK cycle time in 10ths of nano-seconds. -* @hclk: The HCLK frequency in Hz. -* @pclk: The PCLK frequency in Hz. -* -* This contains the frequency information about the current configuration -* mainly for the core drivers to ensure we do not end up passing about -* a large number of parameters. -* -* The @hclk_tns field is a useful cache for the parts of the drivers that -* need to calculate IO timings and suchlike. -*/ -struct s3c_freq { -unsigned long fclk; -unsigned long armclk; -unsigned long hclk_tns;/* in 10ths of ns */ -unsigned long hclk; -unsigned long pclk; -}; - -/** -* struct s3c_cpufreq_freqs - s3c cpufreq notification information. -* @freqs: The cpufreq setting information. -* @old: The old clock settings. -* @new: The new clock settings. -* @pll_changing: Set if the PLL is changing. -* -* Wrapper 'struct cpufreq_freqs' so that any drivers receiving the -* notification can use this information that is not provided by just -* having the core frequency alone. -* -* The pll_changing flag is used to indicate if the PLL itself is -* being set during this change. This is important as the clocks -* will temporarily be set to the XTAL clock during this time, so -* drivers may want to close down their output during this time. -* -* Note, this is not being used by any current drivers and therefore -* may be removed in the future. -*/ -struct s3c_cpufreq_freqs { -struct cpufreq_freqs freqs; -struct s3c_freq old; -struct s3c_freq new; - -unsigned int pll_changing:1 ; -}; - -#define to_s3c_cpufreq (_cf) container_of(_cf, struct s3c_cpufreq_freqs, freqs) - -/** -* struct s3c_clkdivs - clock divisor information -* @p_divisor: Divisor from FCLK to PCLK. -* @h_divisor: Divisor from FCLK to HCLK. -* @arm_divisor: Divisor from FCLK to ARMCLK (not all CPUs). -* @dvs: Non-zero if using DVS mode for ARMCLK. -* -* Divisor settings for the core clocks. -*/ -struct s3c_clkdivs { -int p_divisor; -int h_divisor; -int arm_divisor; -unsigned char dvs; -}; - -#define PLLVAL (_m, _p, _s) (((_m) << 12) | ((_p) << 4) | (_s)) - -/** -* struct s3c_pllval - PLL value entry. -* @freq: The frequency for this entry in Hz. -* @pll_reg: The PLL register setting for this PLL value. -*/ -struct s3c_pllval { -unsigned long freq; -unsigned long pll_reg; -}; - -/** -* struct s3c_cpufreq_board - per-board cpu frequency informatin -* @refresh: The SDRAM refresh period in nanoseconds. -* @auto_io: Set if the IO timing settings should be generated from the -* initialisation time hardware registers. -* @need_io: Set if the board has external IO on any of the chipselect -* lines that will require the hardware timing registers to be -* updated on a clock change. -* @max: The maxium frequency limits for the system. Any field that -* is left at zero will use the CPU's settings. -* -* This contains the board specific settings that affect how the CPU -* drivers chose settings. These include the memory refresh and IO -* timing information. -* -* Registration depends on the driver being used, the ARMCLK only -* implementation does not currently need this but the older style -* driver requires this to be available. -*/ -struct s3c_cpufreq_board { -unsigned int refresh; -unsigned int auto_io:1 ;/* automatically init io timings. */ -unsigned int need_io:1 ;/* set if needs io timing support. */ - -/* any non-zero field in here is taken as an upper limit. */ -struct s3c_freq max;/* frequency limits */ -}; - -/* Things depending on frequency scaling. */ -#ifdef CONFIG_ARM_S3C_CPUFREQ -#define __init_or_cpufreq -#else -#define __init_or_cpufreq __init -#endif - -/* Board functions */ - -#ifdef CONFIG_ARM_S3C_CPUFREQ -extern int s3c_cpufreq_setboard (struct s3c_cpufreq_board *board); -#else - -static inline int s3c_cpufreq_setboard (struct s3c_cpufreq_board *board) -{ -return 0 ; -} -#endif /* CONFIG_ARM_S3C_CPUFREQ */ - -#endif
Signature · 7 lines
2.17.1 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH 1/4] ARM: s3c: remove obsolete s3c-cpu-freq header
Quoted 13 lines · Lukas Bulwahn
The s3c-cpu-freq header was previously included by:
./arch/arm/mach-s3c/mach-bast.c
./arch/arm/mach-s3c/mach-osiris-dvs.c
./arch/arm/mach-s3c/mach-osiris.c
./include/linux/soc/samsung/s3c-cpufreq-core.hCommit
a4946a153cb9("ARM: s3c: remove all s3c24xx support") removes the files in./arch/arm/mach-s3c/; commitdaf0ee583fc7("cpufreq: remove s3c24xx drivers") removes the files3c-cpufreq-core.h.Remove this obsolete header file.
Quoted 7 lines
This issue was identified, as
s3c-cpu-freq.hreferred to the removed configARM_S3C_CPUFREQ.Signed-off-by Lukas Bulwahn <[email protected]>--- include/linux/soc/samsung/s3c-cpu-freq.h | 145 ----------------------- 1 file changed, 145 deletions(-)
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
PATCH 2/4 ARM: pxa: remove further dead code after pxa93 support removal
In reply to Lukas BulwahnCommit 150ccb6f9a89 ("ARM: pxa: remove pxa93x support") removes configs CPU_PXA930 and CPU_PXA935 and uses of cpu_is_pxa93x() and cpu_is_pxa935().
Remove some further dead code in ./include/linux/soc/pxa/cpu.h on top of that commit above.
--- include/linux/soc/pxa/cpu.h | 47 ------------------------------------- 1 file changed, 47 deletions(-)
include/linux/soc/pxa/cpu.h +0 -47
@@ -126,26 +126,6 @@#define __cpu_is_pxa320 (id) (0)#endif -#ifdef CONFIG_CPU_PXA930 -#define __cpu_is_pxa930 (id) \ - ({ \ - unsigned int _id = (id) >> 4 & 0xfff; \ - _id == 0x683; \ - }) -#else -#define __cpu_is_pxa930 (id) (0) -#endif - -#ifdef CONFIG_CPU_PXA935 -#define __cpu_is_pxa935 (id) \ - ({ \ - unsigned int _id = (id) >> 4 & 0xfff; \ - _id == 0x693; \ - }) -#else -#define __cpu_is_pxa935 (id) (0) -#endif -#define cpu_is_pxa210 () \ ({ \ __cpu_is_pxa210(read_cpuid_id()); \
@@ -186,18 +166,6 @@__cpu_is_pxa320 (read_cpuid_id ()); \ }) -#define cpu_is_pxa930 () \ - ({ \ - __cpu_is_pxa930(read_cpuid_id()); \ - }) - -#define cpu_is_pxa935 () \ - ({ \ - __cpu_is_pxa935(read_cpuid_id()); \ - }) - - -/* * CPUID Core Generation Bit * <= 0x2 for pxa21x/pxa25x/pxa26x/pxa27x
@@ -224,16 +192,6 @@#define __cpu_is_pxa3xx (id) (0)#endif -#if defined(CONFIG_CPU_PXA930 ) || defined(CONFIG_CPU_PXA935 ) -#define __cpu_is_pxa93x (id) \ - ({ \ - __cpu_is_pxa930(id) \ - || __cpu_is_pxa935(id); \ - }) -#else -#define __cpu_is_pxa93x (id) (0) -#endif -#define cpu_is_pxa2xx () \ ({ \ __cpu_is_pxa2xx(read_cpuid_id()); \
@@ -244,9 +202,4 @@__cpu_is_pxa3xx (read_cpuid_id ()); \ }) -#define cpu_is_pxa93x () \ - ({ \ - __cpu_is_pxa93x(read_cpuid_id()); \ - }) -#endif
Signature · 7 lines
2.17.1 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Arnd Bergmann
maintainerRe: [PATCH 2/4] ARM: pxa: remove further dead code after pxa93 support removal
Quoted 7 lines · Lukas Bulwahn
Commit
150ccb6f9a89("ARM: pxa: remove pxa93x support") removes configsCPU_PXA930andCPU_PXA935and uses ofcpu_is_pxa93x()andcpu_is_pxa935().Remove some further dead code in
./include/linux/soc/pxa/cpu.hon top of that commit above.Signed-off-by Lukas Bulwahn <[email protected]>
I had this in an earlier version and ended up leaving this bit in when I reworked the series to not drop support for PXA310 and PXA320.
You are probably right that we should not reference the removed Kconfig symbols, but I see that this causes a regression unless I also bring back the change to
drivers/mmc/host/pxamci.c: || cpu_is_pxa935())
Arnd
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH 2/4] ARM: pxa: remove further dead code after pxa93 support removal
Quoted 10 lines · Arnd Bergmann
Quoted 7 lines · Lukas Bulwahn
Commit
150ccb6f9a89("ARM: pxa: remove pxa93x support") removes configsCPU_PXA930andCPU_PXA935and uses ofcpu_is_pxa93x()andcpu_is_pxa935().Remove some further dead code in
./include/linux/soc/pxa/cpu.hon top of that commit above.Signed-off-by Lukas Bulwahn <[email protected]>
Quoted 9 lines
I had this in an earlier version and ended up leaving this bit in when I reworked the series to not drop support for PXA310 and PXA320.
You are probably right that we should not reference the removed
Kconfigsymbols, but I see that this causes a regression unless I also bring back the change to
drivers/mmc/host/pxamci.c: ||cpu_is_pxa935())
Thanks for the insights of your previous attempt. In my janitorial work, I am just triggered by references to removed configs and hardly have the resources to test all the various arm pxa configs. Let us keep it as is for now, and see once your clean-up has settled in mainline, if we find a good suitable further cleanup patch on these code parts here then.
Lukas
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Arnd Bergmann
maintainerRe: [PATCH 2/4] ARM: pxa: remove further dead code after pxa93 support removal
Quoted 21 lines · Lukas Bulwahn
Quoted 10 lines · Arnd Bergmann
Quoted 7 lines · Lukas Bulwahn
Commit
150ccb6f9a89("ARM: pxa: remove pxa93x support") removes configsCPU_PXA930andCPU_PXA935and uses ofcpu_is_pxa93x()andcpu_is_pxa935().Remove some further dead code in
./include/linux/soc/pxa/cpu.hon top of that commit above.Signed-off-by Lukas Bulwahn <[email protected]>Quoted 9 lines
I had this in an earlier version and ended up leaving this bit in when I reworked the series to not drop support for PXA310 and PXA320.
You are probably right that we should not reference the removed
Kconfigsymbols, but I see that this causes a regression unless I also bring back the change to
drivers/mmc/host/pxamci.c: ||cpu_is_pxa935())
Quoted 6 lines
Thanks for the insights of your previous attempt. In my janitorial work, I am just triggered by references to removed configs and hardly have the resources to test all the various arm pxa configs. Let us keep it as is for now, and see once your clean-up has settled in mainline, if we find a good suitable further cleanup patch on these code parts here then.
Sounds good, thanks.
It's very helpful to have you checks trigger on my modified patches as that shows what I have missed in the updates, as well as showing that the initial step I had done did not contain such mistakes.
The procedure I used to create my series was to remove all the boards marked as 'depends on UNUSED_BOARD_FILES' and then recursively remove orphaned header Kconfig symbols, header files.
There is another related set of patches that started looking into, which is for device drivers that
- register a platform_driver, i2c_driver or spi_driver
- have no support of probing from DT or ACPI
- have no remaining device registration in tree
See below for the list that I came up with. I only annotated the drivers at this point, as these are slightly more controversial than the files that are clearly dead code based on existing Kconfig dependencies etc.
If you're interested in helping out with these, feel free to take anything from this list and send patches directly to the subsystem maintainers.
Arnd
---
commit 853e389693ce4da709641cbeb46a8f405d92287a
Author: Arnd Bergmann <[email protected]> Date: Fri Oct 14 16:20:09 2022 +0200
depends-on-unused
arch/x86/Kconfig +1 -0
@@ -735,6 +735,7 @@ config X86_SUPPORTS_MEMORY_FAILURE config STA2X11 bool "STA2X11 Companion Chip Support" depends on X86_32_NON_STANDARD && PCI + depends on UNUSED select SWIOTLB select MFD_STA2X11 select GPIOLIB
drivers/iio/light/Kconfig +1 -0
@@ -305,6 +305,7 @@ config RPR0521 config SENSORS_LM3533 tristate "LM3533 ambient light sensor" depends on MFD_LM3533 + depends on UNUSED help If you say yes here you get support for the ambient light sensor interface on National Semiconductor / TI LM3533 Lighting Power
drivers/input/keyboard/Kconfig +2 -0
@@ -30,6 +30,7 @@ config KEYBOARD_ADC config KEYBOARD_ADP5520 tristate "Keypad Support for ADP5520 PMIC" depends on PMIC_ADP5520 + depends on UNUSED help This option enables support for the keypad scan matrix on Analog Devices ADP5520 PMICs.
@@ -53,6 +54,7 @@ config KEYBOARD_ADP5588 config KEYBOARD_ADP5589 tristate "ADP5585/ADP5589 I2C QWERTY Keypad and IO Expander" depends on I2C + depends on UNUSED help Say Y here if you want to use a ADP5585/ADP5589 attached to your system I2C bus.
drivers/input/misc/Kconfig +1 -0
@@ -45,6 +45,7 @@ config INPUT_AB8500_PONKEY config INPUT_AD714X tristate "Analog Devices AD714x Capacitance Touch Sensor" + depends on UNUSED help Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
drivers/input/touchscreen/Kconfig +1 -0
@@ -46,6 +46,7 @@ config TOUCHSCREEN_ADS7846 config TOUCHSCREEN_AD7877 tristate "AD7877 based touchscreens" depends on SPI_MASTER + depends on UNUSED help Say Y here if you have a touchscreen interface using the AD7877 controller, and your board-specific initialization
drivers/media/pci/sta2x11/Kconfig +1 -0
@@ -3,6 +3,7 @@ config STA2X11_VIP tristate "STA2X11 VIP Video For Linux" depends on PCI && VIDEO_DEV && I2C depends on STA2X11 || COMPILE_TEST + depends on UNUSED select GPIOLIB if MEDIA_SUBDRV_AUTOSELECT select VIDEO_ADV7180 if MEDIA_SUBDRV_AUTOSELECT select VIDEOBUF2_DMA_CONTIG
drivers/media/platform/samsung/s3c-camif/Kconfig +1 -0
@@ -4,6 +4,7 @@ config VIDEO_S3C_CAMIF depends on V4L_PLATFORM_DRIVERS depends on VIDEO_DEV && I2C && PM depends on ARCH_S3C64XX || COMPILE_TEST + depends on UNUSED select MEDIA_CONTROLLER select VIDEO_V4L2_SUBDEV_API select VIDEOBUF2_DMA_CONTIG
drivers/media/radio/Kconfig +1 -0
@@ -144,6 +144,7 @@ config RADIO_TIMBERDALE config RADIO_WL1273 tristate "Texas Instruments WL1273 I2C FM Radio" depends on I2C + depends on UNUSED select MFD_CORE select MFD_WL1273_CORE select FW_LOADER
drivers/mfd/Kconfig +12 -0
@@ -104,6 +104,7 @@ config MFD_AS3722 config PMIC_ADP5520 bool "Analog Devices ADP5520/01 MFD PMIC Core Support" depends on I2C=y + depends on UNUSED help Say yes here to add support for Analog Devices ADP5520 and ADP5501, Multifunction Power Management IC. This includes
@@ -116,6 +117,7 @@ config MFD_AAT2870_CORE select MFD_CORE depends on I2C=y depends on GPIOLIB || COMPILE_TEST + depends on UNUSED help If you say yes here you get support for the AAT2870. This driver provides common support for accessing the device,
@@ -303,6 +305,7 @@ config MFD_CS47L92 config PMIC_DA903X bool "Dialog Semiconductor DA9030/DA9034 PMIC Support" depends on I2C=y + depends on UNUSED help Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
@@ -988,6 +991,7 @@ config MFD_OCELOT config EZX_PCAP bool "Motorola EZXPCAP Support" depends on SPI_MASTER + depends on UNUSED help This enables the PCAP ASIC present on EZX Phones. This is needed for MMC, TouchScreen, Sound, USB, etc..
@@ -1040,6 +1044,7 @@ config MFD_RETU config MFD_PCF50633 tristate "NXP PCF50633" + depends on UNUSED depends on I2C select REGMAP_I2C help
@@ -1164,6 +1169,7 @@ config MFD_RT5120 config MFD_RC5T583 bool "Ricoh RC5T583 Power Management system device" depends on I2C=y + depends on UNUSED select MFD_CORE select REGMAP_I2C help
@@ -1225,6 +1231,7 @@ config MFD_SEC_CORE config MFD_SI476X_CORE tristate "Silicon Laboratories 4761/64/68 AM/FM radio." depends on I2C + depends on UNUSED select MFD_CORE select REGMAP_I2C help
@@ -1387,6 +1394,7 @@ endmenu config MFD_STA2X11 bool "STMicroelectronics STA2X11" depends on STA2X11 + depends on UNUSED select MFD_CORE select REGMAP_MMIO
@@ -1431,6 +1439,7 @@ config MFD_LP3943 config MFD_LP8788 bool "TI LP8788 Power Management Unit Driver" depends on I2C=y + depends on UNUSED select MFD_CORE select REGMAP_I2C select IRQ_DOMAIN
@@ -1723,6 +1732,7 @@ config MENELAUS config MFD_WL1273_CORE tristate "TI WL1273 FM radio" depends on I2C + depends on UNUSED select MFD_CORE default n help
@@ -1732,6 +1742,7 @@ config MFD_WL1273_CORE config MFD_LM3533 tristate "TI/National Semiconductor LM3533 Lighting Power chip" + depends on UNUSED depends on I2C select MFD_CORE select REGMAP_I2C
@@ -1850,6 +1861,7 @@ config MFD_WM8400 bool "Wolfson Microelectronics WM8400" select MFD_CORE depends on I2C=y + depends on UNUSED select REGMAP_I2C help Support for the Wolfson Microelecronics WM8400 PMIC and audio
drivers/misc/Kconfig +2 -0
@@ -352,6 +352,7 @@ config SENSORS_TSL2550 config SENSORS_BH1770 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor" depends on I2C + depends on UNUSED help Say Y here if you want to build a driver for BH1770GLC (ROHM) or SFH7770 (Osram) combined ambient light and proximity sensor chip.
@@ -362,6 +363,7 @@ config SENSORS_BH1770 config SENSORS_APDS990X tristate "APDS990X combined als and proximity sensors" depends on I2C + depends on UNUSED help Say Y here if you want to build a driver for Avago APDS990x combined ambient light and proximity sensor chip.
drivers/misc/ti-st/Kconfig +1 -0
@@ -8,6 +8,7 @@ config TI_ST tristate "Shared transport core driver" depends on NET && TTY depends on GPIOLIB || COMPILE_TEST + depends on UNUSED select FW_LOADER help This enables the shared transport core driver for TI
drivers/net/ethernet/Kconfig +1 -0
@@ -111,6 +111,7 @@ config KORINA config LANTIQ_ETOP tristate "Lantiq SoC ETOP driver" depends on SOC_TYPE_XWAY + depends on UNUSED help Support for the MII0 inside the Lantiq SoC
drivers/net/ethernet/wiznet/Kconfig +1 -0
@@ -33,6 +33,7 @@ config WIZNET_W5100 config WIZNET_W5300 tristate "WIZnet W5300 Ethernet support" depends on HAS_IOMEM + depends on UNUSED help Support for WIZnet W5300 chips.
drivers/net/wireless/marvell/libertas/Kconfig +1 -0
@@ -30,6 +30,7 @@ config LIBERTAS_SDIO config LIBERTAS_SPI tristate "Marvell Libertas 8686 SPI 802.11b/g cards" depends on LIBERTAS && SPI + depends on UNUSED help A driver for Marvell Libertas 8686 SPI devices.
drivers/power/supply/Kconfig +1 -0
@@ -281,6 +281,7 @@ config BATTERY_BQ27XXX_DT_UPDATES_NVM config BATTERY_DA9030 tristate "DA9030 battery driver" + depends on UNUSED depends on PMIC_DA903X help Say Y here to enable support for batteries charger integrated into
drivers/regulator/Kconfig +2 -0
@@ -463,6 +463,7 @@ config REGULATOR_LOCHNAGAR config REGULATOR_LP3971 tristate "National Semiconductors LP3971 PMIC regulator driver" + depends on UNUSED depends on I2C help Say Y here to support the voltage regulators and convertors
@@ -470,6 +471,7 @@ config REGULATOR_LP3971 config REGULATOR_LP3972 tristate "National Semiconductors LP3972 PMIC regulator driver" + depends on UNUSED depends on I2C help Say Y here to support the voltage regulators and convertors
drivers/spi/Kconfig +1 -0
@@ -1157,6 +1157,7 @@ config SPI_LOOPBACK_TEST config SPI_TLE62X0 tristate "Infineon TLE62X0 (for power switching)" depends on SYSFS + depends on UNUSED help SPI driver for Infineon TLE62X0 series line driver chips, such as the TLE6220, TLE6230 and TLE6240. This provides a
drivers/staging/media/omap4iss/Kconfig +1 -0
@@ -4,6 +4,7 @@ config VIDEO_OMAP4 tristate "OMAP 4 Camera support" depends on VIDEO_DEV && I2C depends on ARCH_OMAP4 || COMPILE_TEST + depends on UNUSED select MEDIA_CONTROLLER select VIDEO_V4L2_SUBDEV_API select MFD_SYSCON
drivers/tty/serial/Kconfig +1 -0
@@ -316,6 +316,7 @@ config SERIAL_TEGRA_TCU_CONSOLE config SERIAL_MAX3100 tristate "MAX3100 support" depends on SPI + depends on UNUSED select SERIAL_CORE help MAX3100 chip support
drivers/usb/gadget/udc/Kconfig +2 -0
@@ -209,6 +209,7 @@ config USB_PXA27X config USB_MV_UDC tristate "Marvell USB2.0 Device Controller" depends on HAS_DMA + depends on UNUSED help Marvell Socs (including PXA and MMP series) include a high speed USB2.0 OTG controller, which can be configured as high speed or
@@ -217,6 +218,7 @@ config USB_MV_UDC config USB_MV_U3D depends on HAS_DMA tristate "MARVELL PXA2128 USB 3.0 controller" + depends on UNUSED help MARVELL PXA2128 Processor series include a super speed USB3.0 device controller, which support super speed USB peripheral.
drivers/usb/host/Kconfig +2 -1
@@ -368,7 +368,7 @@ config USB_ISP116X_HCD config USB_ISP1362_HCD tristate "ISP1362 HCD support" depends on HAS_IOMEM - depends on COMPILE_TEST # nothing uses this + depends on UNUSED # nothing uses this help Supports the Philips ISP1362 chip as a host controller
@@ -654,6 +654,7 @@ config USB_U132_HCD config USB_SL811_HCD tristate "SL811HS HCD support" depends on HAS_IOMEM + depends on UNUSED help The SL811HS is a single-port USB controller that supports either host side or peripheral side roles. Enable this option if your
drivers/usb/phy/Kconfig +1 -0
@@ -130,6 +130,7 @@ config USB_MV_OTG tristate "Marvell USB OTG support" depends on USB_EHCI_MV && USB_MV_UDC && PM && USB_OTG depends on USB_GADGET || !USB_GADGET # if USB_GADGET=m, this can't be 'y' + depends on UNUSED select USB_PHY help Say Y here if you want to build Marvell USB OTG transceiver
drivers/video/fbdev/Kconfig +3 -0
@@ -1770,6 +1770,7 @@ config FB_PXA168 tristate "PXA168/910 LCD framebuffer support" depends on FB && HAVE_CLK && HAS_IOMEM depends on CPU_PXA168 || CPU_PXA910 || COMPILE_TEST + depends on UNUSED select FB_CFB_FILLRECT select FB_CFB_COPYAREA select FB_CFB_IMAGEBLIT
@@ -2003,6 +2004,7 @@ config FB_DA8XX tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support" depends on FB && HAVE_CLK && HAS_IOMEM depends on ARCH_DAVINCI_DA8XX || SOC_AM33XX || COMPILE_TEST + depends on UNUSED select FB_CFB_FILLRECT select FB_CFB_COPYAREA select FB_CFB_IMAGEBLIT
@@ -2128,6 +2130,7 @@ config FB_PRE_INIT_FB config FB_MX3 tristate "MX3 Framebuffer support" depends on FB && MX3_IPU + depends on UNUSED select BACKLIGHT_CLASS_DEVICE select FB_CFB_FILLRECT select FB_CFB_COPYAREA
drivers/video/fbdev/mmp/fb/Kconfig +1 -0
@@ -2,6 +2,7 @@ config MMP_FB tristate "fb driver for Marvell MMP Display Subsystem" depends on FB + depends on UNUSED select FB_CFB_FILLRECT select FB_CFB_COPYAREA select FB_CFB_IMAGEBLIT
sound/spi/Kconfig +1 -0
@@ -13,6 +13,7 @@ if SND_SPI config SND_AT73C213 tristate "Atmel AT73C213 DAC driver" depends on ATMEL_SSC + depends on UNUSED select SND_PCM help Say Y here if you want to use the Atmel AT73C213 external DAC. This
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
PATCH 3/4 usb: remove OMAP USB Device Controller and OHCI support for OMAP1/2 chips
In reply to Lukas BulwahnCommit 0fee2eac5c2b ("usb: phy: remove phy-isp1301-omap driver") removes the Philips ISP1301 with OMAP OTG driver and its corresponding config ISP1301_OMAP. The drivers, OMAP USB Device Controller and OHCI support for OMAP1/2 chips, with corresponding configs, USB_OMAP and USB_OHCI_HCD_OMAP1, need this removed driver (see "depends on ISP1301_OMAP") to build.
Remove those two drivers.
With the config USB_OMAP removed in this commit, remove some further code in the omap-dma header and mach-omap1 architecture code.
--- arch/arm/mach-omap1/board-osk.c | 5 - arch/arm/mach-omap1/omap-dma.c | 455 ----- arch/arm/mach-omap1/usb.c | 67 - arch/arm/mach-omap1/usb.h | 4 - drivers/usb/gadget/udc/Kconfig | 15 - drivers/usb/gadget/udc/Makefile | 1 - drivers/usb/gadget/udc/omap_udc.c | 3001 ----------------------------- drivers/usb/gadget/udc/omap_udc.h | 207 -- drivers/usb/host/Kconfig | 8 - drivers/usb/host/Makefile | 1 - drivers/usb/host/ohci-omap.c | 435 ----- include/linux/omap-dma.h | 28 - 12 files changed, 4227 deletions(-) delete mode 100644 drivers/usb/gadget/udc/omap_udc.c delete mode 100644 drivers/usb/gadget/udc/omap_udc.h delete mode 100644 drivers/usb/host/ohci-omap.c
arch/arm/mach-omap1/board-osk.c +0 -5
@@ -328,14 +328,9 @@ static struct omap_usb_config osk_usb_config __initdata = {* be used, with a NONSTANDARD gender-bending cable/dongle, as * a peripheral. */ -#if IS_ENABLED (CONFIG_USB_OMAP ) - .register_dev = 1, - .hmc_mode = 0, -#else .register_host = 1, .hmc_mode = 16, .rwc = 1, -#endif .pins[0] = 2, };
arch/arm/mach-omap1/omap-dma.c +0 -455
467 lines not on this page · raw message
arch/arm/mach-omap1/usb.c +0 -67
89 lines not on this page · raw message
arch/arm/mach-omap1/usb.h +0 -4
@@ -6,11 +6,7 @@#include <linux/platform_data/usb-omap1.h> #include <linux/soc/ti/omap1-usb.h> -#if IS_ENABLED (CONFIG_USB_OMAP ) -#define is_usb0_device (config) 1 -#else #define is_usb0_device (config) 0 -#endif #if IS_ENABLED (CONFIG_USB_SUPPORT )void omap1_usb_init (struct omap_usb_config *pdata);
drivers/usb/gadget/udc/Kconfig +0 -15
@@ -115,21 +115,6 @@ config USB_GR_UDC Select this to support Aeroflex Gaisler GRUSBDC cores from the GRLIB VHDL IP core library. -config USB_OMAP - tristate "OMAP USB Device Controller" - depends on ARCH_OMAP1 - depends on ISP1301_OMAP - help - Many Texas Instruments OMAP processors have flexible full - speed USB device controllers, with support for up to 30 - endpoints (plus endpoint zero). This driver supports the - controller in the OMAP 1611, and should work with controllers - in other OMAP processors too, given minor tweaks. - - Say "y" to link the driver statically, or "m" to build a - dynamically linked module called "omap_udc" and force all - gadget drivers to also be dynamically linked. - config USB_PXA25X tristate "PXA 25x or IXP 4xx" depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
drivers/usb/gadget/udc/Makefile +0 -1
@@ -16,7 +16,6 @@ obj-$(CONFIG_USB_AMD5536UDC) += amd5536udc_pci.o obj-$(CONFIG_USB_PXA25X) += pxa25x_udc.o obj-$(CONFIG_USB_PXA27X) += pxa27x_udc.o obj-$(CONFIG_USB_GOKU) += goku_udc.o -obj-$(CONFIG_USB_OMAP) += omap_udc.o obj-$(CONFIG_USB_AT91) += at91_udc.o obj-$(CONFIG_USB_ATMEL_USBA) += atmel_usba_udc.o obj-$(CONFIG_USB_BCM63XX_UDC) += bcm63xx_udc.o
drivers/usb/gadget/udc/omap_udc.c deleted +0 -3001
2,391 lines not on this page · raw message
drivers/usb/gadget/udc/omap_udc.h deleted +0 -207
207 lines not on this page · raw message
drivers/usb/host/ohci-omap.c deleted +0 -435
435 lines not on this page · raw message
The rest of this diff is not shown. View the raw message.
Signature · 1 line
2.17.1
Part of the diff is not shown here. View the raw message.
Arnd Bergmann
maintainerRe: [PATCH 3/4] usb: remove OMAP USB Device Controller and OHCI support for OMAP1/2 chips
Quoted 6 lines · Lukas Bulwahn
Commit
0fee2eac5c2b("usb: phy: remove phy-isp1301-omap driver") removes the Philips ISP1301 with OMAP OTG driver and its corresponding configISP1301_OMAP. The drivers, OMAP USB Device Controller and OHCI support for OMAP1/2 chips, with corresponding configs,USB_OMAPandUSB_OHCI_HCD_OMAP1, need this removed driver (see "depends onISP1301_OMAP") to build.
Quoted 6 lines
Remove those two drivers.
With the config
USB_OMAPremoved in this commit, remove some further code in the omap-dma header and mach-omap1 architecture code.Signed-off-by Lukas Bulwahn <[email protected]>
This would be a great cleanup because of the simplications of the omap-dma code. I had previously looked at it and concluded that the driver is still in use though, and I think my mistake was just in the Kconfig part of this patch:
commit c32fd10914a314dd96c5d24030200070c84df5f1
Author: Arnd Bergmann <[email protected]> Date: Thu Sep 29 15:38:56 2022 +0200
ARM: omap1: remove unused board files
All board support that was marked as 'unused' earlier can now be removed, leaving the five machines that that still had someone using them in 2022, or that are supported in qemu.
drivers/usb/gadget/udc/Kconfig +1 -1
@@ -118,7 +118,7 @@ config USB_GR_UDC config USB_OMAP tristate "OMAP USB Device Controller" depends on ARCH_OMAP1 - depends on ISP1301_OMAP || !(MACH_OMAP_H2 || MACH_OMAP_H3) + depends on ISP1301_OMAP help Many Texas Instruments OMAP processors have flexible full speed USB device controllers, with support for up to 30
drivers/usb/host/Kconfig +1 -1
@@ -409,7 +409,7 @@ if USB_OHCI_HCD config USB_OHCI_HCD_OMAP1 tristate "OHCI support for OMAP1/2 chips" depends on ARCH_OMAP1 - depends on ISP1301_OMAP || !(MACH_OMAP_H2 || MACH_OMAP_H3) + depends on ISP1301_OMAP default y help Enables support for the OHCI controller on OMAP1/2 chips.
Instead of changing this to 'depends on ISP1301_OMAP', the line probably should just be dropped entirely.
Arnd
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH 3/4] usb: remove OMAP USB Device Controller and OHCI support for OMAP1/2 chips
Quoted 64 lines · Arnd Bergmann
Quoted 6 lines · Lukas Bulwahn
Commit
0fee2eac5c2b("usb: phy: remove phy-isp1301-omap driver") removes the Philips ISP1301 with OMAP OTG driver and its corresponding configISP1301_OMAP. The drivers, OMAP USB Device Controller and OHCI support for OMAP1/2 chips, with corresponding configs,USB_OMAPandUSB_OHCI_HCD_OMAP1, need this removed driver (see "depends onISP1301_OMAP") to build.Quoted 6 lines
Remove those two drivers.
With the config
USB_OMAPremoved in this commit, remove some further code in the omap-dma header and mach-omap1 architecture code.Signed-off-by Lukas Bulwahn <[email protected]>This would be a great cleanup because of the simplications of the omap-dma code. I had previously looked at it and concluded that the driver is still in use though, and I think my mistake was just in the
Kconfigpart of this patch:commit
c32fd10914a314dd96c5d24030200070c84df5f1Author: Arnd Bergmann <[email protected]> Date: Thu Sep 29 15:38:56 2022 +0200ARM: omap1: remove unused board files
All board support that was marked as 'unused' earlier can now be removed, leaving the five machines that that still had someone using them in 2022, or that are supported in qemu.
Cc Aaro Koskinen <[email protected]>Cc Janusz Krzysztofik <[email protected]>Cc Tony Lindgren <[email protected]>Signed-off-by Arnd Bergmann <[email protected]>drivers/usb/gadget/udc/Kconfig +1
-1@@ -118,7 +118,7 @@ config USB_GR_UDC config USB_OMAP tristate "OMAP USB Device Controller" depends on ARCH_OMAP1 - depends on ISP1301_OMAP || !(MACH_OMAP_H2 || MACH_OMAP_H3) + depends on ISP1301_OMAP help Many Texas Instruments OMAP processors have flexible full speed USB device controllers, with support for up to 30drivers/usb/host/Kconfig +1
-1@@ -409,7 +409,7 @@ if USB_OHCI_HCD config USB_OHCI_HCD_OMAP1 tristate "OHCI support for OMAP1/2 chips" depends on ARCH_OMAP1 - depends on ISP1301_OMAP || !(MACH_OMAP_H2 || MACH_OMAP_H3) + depends on ISP1301_OMAP default y help Enables support for the OHCI controller on OMAP1/2 chips.
Quoted 3 lines
Instead of changing this to 'depends on
ISP1301_OMAP', the line probably should just be dropped entirely.
I see. Yes, probably, !(MACH_OMAP_H2 || MACH_OMAP_H3) is really in the current state of the repository "always true", and hence this dependency "depends on ISP1301_OMAP || !(MACH_OMAP_H2 || MACH_OMAP_H3)" is always independent of ISP1301_OMAP.
Are you going to fix up your commit "ARM: omap1: remove unused board files" with this change?
Please ignore this patch then; patch 1 and 4 still seem good to pick, though.
Lukas
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Arnd Bergmann
maintainerRe: [PATCH 3/4] usb: remove OMAP USB Device Controller and OHCI support for OMAP1/2 chips
Quoted 11 lines · Lukas Bulwahn
On Thu, Jan 12, 2023 at 10:03 AM Arnd Bergmann <[email protected]> wrote:
I see. Yes, probably, !(MACH_OMAP_H2 ||
MACH_OMAP_H3) is really in the current state of the repository "always true", and hence this dependency "depends onISP1301_OMAP|| !(MACH_OMAP_H2 ||MACH_OMAP_H3)" is always independent ofISP1301_OMAP.Are you going to fix up your commit "ARM: omap1: remove unused board files" with this change?
Please ignore this patch then; patch 1 and 4 still seem good to pick, though.
Done, I've applied those two and fixed up the other patch.
Thanks a lot for your series!
Arnd
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Tony Lindgren
reviewerRe: [PATCH 3/4] usb: remove OMAP USB Device Controller and OHCI support for OMAP1/2 chips
In reply to Arnd BergmannQuoted 12 lines · Arnd Bergmann
Quoted 11 lines · Lukas Bulwahn
Commit
0fee2eac5c2b("usb: phy: remove phy-isp1301-omap driver") removes the Philips ISP1301 with OMAP OTG driver and its corresponding configISP1301_OMAP. The drivers, OMAP USB Device Controller and OHCI support for OMAP1/2 chips, with corresponding configs,USB_OMAPandUSB_OHCI_HCD_OMAP1, need this removed driver (see "depends onISP1301_OMAP") to build.Remove those two drivers.
With the config
USB_OMAPremoved in this commit, remove some further code in the omap-dma header and mach-omap1 architecture code.
Quoted 6 lines
Quoted 1 line
Signed-off-by Lukas Bulwahn <[email protected]>This would be a great cleanup because of the simplications of the omap-dma code. I had previously looked at it and concluded that the driver is still in use though, and I think my mistake was just in the
Kconfigpart of this patch:
It sure would be nice to drop the old custom dma api in omap-dma.c while keeping the dma.c in arch/arm/mach-omap1.
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Arnd Bergmann
maintainerRe: [PATCH 3/4] usb: remove OMAP USB Device Controller and OHCI support for OMAP1/2 chips
Quoted 15 lines · Tony Lindgren
Quoted 14 lines · Arnd Bergmann
Quoted 12 lines · Lukas Bulwahn
Commit
0fee2eac5c2b("usb: phy: remove phy-isp1301-omap driver") removes the Philips ISP1301 with OMAP OTG driver and its corresponding configISP1301_OMAP. The drivers, OMAP USB Device Controller and OHCI support for OMAP1/2 chips, with corresponding configs,USB_OMAPandUSB_OHCI_HCD_OMAP1, need this removed driver (see "depends onISP1301_OMAP") to build.Remove those two drivers.
With the config
USB_OMAPremoved in this commit, remove some further code in the omap-dma header and mach-omap1 architecture code.Signed-off-by Lukas Bulwahn <[email protected]>
Quoted 7 lines
Quoted 4 lines
This would be a great cleanup because of the simplications of the omap-dma code. I had previously looked at it and concluded that the driver is still in use though, and I think my mistake was just in the
Kconfigpart of this patch:It sure would be nice to drop the old custom dma api in
omap-dma.cwhile keeping thedma.cinarch/arm/mach-omap1.
I see that four out of the five remaining board files still use omap_udc, which is the only remaining user of the custom DMA interface. What I had not noticed earlier is that DMA support in that driver is actually optional, though it's hardwired to be enabled.
So if we want to kill off the old DMA stuff there is actually a choice between either making omap_udc PIO-only or converting it to use the standard dmaengine interface.
Arnd
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Aaro Koskinen
maintainerRe: [PATCH 3/4] usb: remove OMAP USB Device Controller and OHCI support for OMAP1/2 chips
Hi,
Quoted 30 lines · Arnd Bergmann
Quoted 15 lines · Tony Lindgren
Quoted 14 lines · Arnd Bergmann
Quoted 12 lines · Lukas Bulwahn
Commit
0fee2eac5c2b("usb: phy: remove phy-isp1301-omap driver") removes the Philips ISP1301 with OMAP OTG driver and its corresponding configISP1301_OMAP. The drivers, OMAP USB Device Controller and OHCI support for OMAP1/2 chips, with corresponding configs,USB_OMAPandUSB_OHCI_HCD_OMAP1, need this removed driver (see "depends onISP1301_OMAP") to build.Remove those two drivers.
With the config
USB_OMAPremoved in this commit, remove some further code in the omap-dma header and mach-omap1 architecture code.Signed-off-by Lukas Bulwahn <[email protected]>Quoted 7 lines
Quoted 4 lines
This would be a great cleanup because of the simplications of the omap-dma code. I had previously looked at it and concluded that the driver is still in use though, and I think my mistake was just in the
Kconfigpart of this patch:It sure would be nice to drop the old custom dma api in
omap-dma.cwhile keeping thedma.cinarch/arm/mach-omap1.I see that four out of the five remaining board files still use
omap_udc, which is the only remaining user of the custom DMA interface. What I had not noticed earlier is that DMA support in that driver is actually optional, though it's hardwired to be enabled.
Quoted 3 lines
So if we want to kill off the old DMA stuff there is actually a choice between either making
omap_udcPIO-only or converting it to use the standard dmaengine interface.
I use this driver on Palm TE and 770, and without it those boards would be useless for my use cases. Also DMA doubles the throughput, probably also power usage is smaller.
A.
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Arnd Bergmann
maintainerRe: [PATCH 3/4] usb: remove OMAP USB Device Controller and OHCI support for OMAP1/2 chips
Quoted 10 lines · Aaro Koskinen
Quoted 5 lines · Arnd Bergmann
On Thu, Jan 12, 2023, at 10:53, Tony Lindgren wrote:
So if we want to kill off the old DMA stuff there is actually a choice between either making
omap_udcPIO-only or converting it to use the standard dmaengine interface.I use this driver on Palm TE and 770, and without it those boards would be useless for my use cases. Also DMA doubles the throughput, probably also power usage is smaller.
Ok, if the performance is important, converting to dmaengine is probably best. Do you know if this is just a straightforward replacement of the function calls, or are there technical reasons why it's not using the dmaengine interface yet?
Arnd
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Tony Lindgren
reviewerRe: [PATCH 3/4] usb: remove OMAP USB Device Controller and OHCI support for OMAP1/2 chips
Quoted 8 lines · Arnd Bergmann
Quoted 7 lines · Aaro Koskinen
Quoted 5 lines · Arnd Bergmann
On Thu, Jan 12, 2023, at 10:53, Tony Lindgren wrote:
So if we want to kill off the old DMA stuff there is actually a choice between either making
omap_udcPIO-only or converting it to use the standard dmaengine interface.
Quoted 8 lines
Quoted 3 lines
I use this driver on Palm TE and 770, and without it those boards would be useless for my use cases. Also DMA doubles the throughput, probably also power usage is smaller.
Ok, if the performance is important, converting to dmaengine is probably best. Do you know if this is just a straightforward replacement of the function calls, or are there technical reasons why it's not using the dmaengine interface yet?
Yes I agree dmaengine is the best solution. Seems like this is the last driver using the old api that never got updated probably because it's not used on the newer SoCs.
I don't think there are any technical reasons to not use dmaengine here.
FYI, the last blocker for dmaengine use was for drivers using port_window that got added with the drivers/usb/musb/tusb6010_omap.c dmaengine conversion a few years back.
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
PATCH 4/4 ARM: debug: remove references in DEBUG_UART_8250_SHIFT to removed configs
In reply to Lukas BulwahnCommit 67d3928c3df5 ("ARM: omap1: remove unused board files") removes configs DEBUG_OMAP7XXUART{1,2,3}.
The config DEBUG_UART_8250_SHIFT still refers to those removed configs.
Remove those obsolete references.
--- arch/arm/Kconfig.debug | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
arch/arm/Kconfig.debug +1 -2
@@ -1778,8 +1778,7 @@ config DEBUG_UART_8250_SHIFT int "Register offset shift for the 8250 debug UART" depends on DEBUG_LL_UART_8250 || DEBUG_UART_8250 default 0 if DEBUG_FOOTBRIDGE_COM1 || DEBUG_BCM_5301X || \ - DEBUG_BCM_HR2 || DEBUG_OMAP7XXUART1 || DEBUG_OMAP7XXUART2 || \ - DEBUG_OMAP7XXUART3 + DEBUG_BCM_HR2 default 3 if DEBUG_MSTARV7_PMUART default 2
Signature · 1 line
2.17.1