Skip to contentSkip to conversation

Kconfig: Great White Handkerchief going round

PATCH Applied Enrico Weigelt, metux IT consult 7 participants 123 messages Mar 11, 2019 – Apr 29, 2019 Page 2 of 2

Subsystems (245)
lore
Share & tools
lore
#79 lore raw

PATCH 74/114 drivers: md: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/md/Kconfig                 | 236 ++++++++++++++++++-------------------
 drivers/md/persistent-data/Kconfig |  15 ++-
 2 files changed, 125 insertions(+), 126 deletions(-)
drivers/md/Kconfig +118 -118
index 2557f19..e7e1596 100644
@@ -37,9 +37,9 @@ config MD_AUTODETECT
 	default y
 	---help---
 	  If you say Y here, then the kernel will try to autodetect raid
-	  arrays as part of its boot process. 
+	  arrays as part of its boot process.
 
-	  If you don't use raid and say Y, this autodetection can cause 
+	  If you don't use raid and say Y, this autodetection can cause
 	  a several-second delay in the boot time due to various
 	  synchronisation steps that are part of this step.
 
@@ -183,15 +183,15 @@ config MD_CLUSTER
 	depends on DLM
 	default n
 	---help---
-	Clustering support for MD devices. This enables locking and
-	synchronization across multiple systems on the cluster, so all
-	nodes in the cluster can access the MD devices simultaneously.
+	  Clustering support for MD devices. This enables locking and
+	  synchronization across multiple systems on the cluster, so all
+	  nodes in the cluster can access the MD devices simultaneously.
 
-	This brings the redundancy (and uptime) of RAID levels across the
-	nodes of the cluster. Currently, it can work with raid1 and raid10
-	(limited support).
+	  This brings the redundancy (and uptime) of RAID levels across the
+	  nodes of the cluster. Currently, it can work with raid1 and raid10
+	  (limited support).
 
-	If unsure, say N.
+	  If unsure, say N.
 
 source "drivers/md/bcache/Kconfig"
 
@@ -224,44 +224,44 @@ config DM_DEBUG
 	  If unsure, say N.
 
 config DM_BUFIO
-       tristate
-       depends on BLK_DEV_DM
-       ---help---
-	 This interface allows you to do buffered I/O on a device and acts
-	 as a cache, holding recently-read blocks in memory and performing
-	 delayed writes.
+	tristate
+	depends on BLK_DEV_DM
+	---help---
+	  This interface allows you to do buffered I/O on a device and acts
+	  as a cache, holding recently-read blocks in memory and performing
+	  delayed writes.
 
 config DM_DEBUG_BLOCK_MANAGER_LOCKING
-       bool "Block manager locking"
-       depends on DM_BUFIO
-       ---help---
-	 Block manager locking can catch various metadata corruption issues.
+	bool "Block manager locking"
+	depends on DM_BUFIO
+	---help---
+	  Block manager locking can catch various metadata corruption issues.
 
-	 If unsure, say N.
+	  If unsure, say N.
 
 config DM_DEBUG_BLOCK_STACK_TRACING
-       bool "Keep stack trace of persistent data block lock holders"
-       depends on STACKTRACE_SUPPORT && DM_DEBUG_BLOCK_MANAGER_LOCKING
-       select STACKTRACE
-       ---help---
-	 Enable this for messages that may help debug problems with the
-	 block manager locking used by thin provisioning and caching.
+	bool "Keep stack trace of persistent data block lock holders"
+	depends on STACKTRACE_SUPPORT && DM_DEBUG_BLOCK_MANAGER_LOCKING
+	select STACKTRACE
+	---help---
+	  Enable this for messages that may help debug problems with the
+	  block manager locking used by thin provisioning and caching.
 
-	 If unsure, say N.
+	  If unsure, say N.
 
 config DM_BIO_PRISON
-       tristate
-       depends on BLK_DEV_DM
-       ---help---
-	 Some bio locking schemes used by other device-mapper targets
-	 including thin provisioning.
+	tristate
+	depends on BLK_DEV_DM
+	---help---
+	  Some bio locking schemes used by other device-mapper targets
+	  including thin provisioning.
 
 source "drivers/md/persistent-data/Kconfig"
 
 config DM_UNSTRIPED
-       tristate "Unstriped target"
-       depends on BLK_DEV_DM
-       ---help---
+	tristate "Unstriped target"
+	depends on BLK_DEV_DM
+	---help---
 	  Unstripes I/O so it is issued solely on a single drive in a HW
 	  RAID0 or dm-striped target.
 
@@ -284,73 +284,73 @@ config DM_CRYPT
 	  If unsure, say N.
 
 config DM_SNAPSHOT
-       tristate "Snapshot target"
-       depends on BLK_DEV_DM
-       select DM_BUFIO
-       ---help---
-         Allow volume managers to take writable snapshots of a device.
+	tristate "Snapshot target"
+	depends on BLK_DEV_DM
+	select DM_BUFIO
+	---help---
+	  Allow volume managers to take writable snapshots of a device.
 
 config DM_THIN_PROVISIONING
-       tristate "Thin provisioning target"
-       depends on BLK_DEV_DM
-       select DM_PERSISTENT_DATA
-       select DM_BIO_PRISON
-       ---help---
-         Provides thin provisioning and snapshots that share a data store.
+	tristate "Thin provisioning target"
+	depends on BLK_DEV_DM
+	select DM_PERSISTENT_DATA
+	select DM_BIO_PRISON
+	---help---
+	  Provides thin provisioning and snapshots that share a data store.
 
 config DM_CACHE
-       tristate "Cache target (EXPERIMENTAL)"
-       depends on BLK_DEV_DM
-       default n
-       select DM_PERSISTENT_DATA
-       select DM_BIO_PRISON
-       ---help---
-         dm-cache attempts to improve performance of a block device by
-         moving frequently used data to a smaller, higher performance
-         device.  Different 'policy' plugins can be used to change the
-         algorithms used to select which blocks are promoted, demoted,
-         cleaned etc.  It supports writeback and writethrough modes.
+	tristate "Cache target (EXPERIMENTAL)"
+	depends on BLK_DEV_DM
+	default n
+	select DM_PERSISTENT_DATA
+	select DM_BIO_PRISON
+	---help---
+	  dm-cache attempts to improve performance of a block device by
+	  moving frequently used data to a smaller, higher performance
+	  device.  Different 'policy' plugins can be used to change the
+	  algorithms used to select which blocks are promoted, demoted,
+	  cleaned etc.  It supports writeback and writethrough modes.
 
 config DM_CACHE_SMQ
-       tristate "Stochastic MQ Cache Policy (EXPERIMENTAL)"
-       depends on DM_CACHE
-       default y
-       ---help---
-         A cache policy that uses a multiqueue ordered by recent hits
-         to select which blocks should be promoted and demoted.
-         This is meant to be a general purpose policy.  It prioritises
-         reads over writes.  This SMQ policy (vs MQ) offers the promise
-         of less memory utilization, improved performance and increased
-         adaptability in the face of changing workloads.
+	tristate "Stochastic MQ Cache Policy (EXPERIMENTAL)"
+	depends on DM_CACHE
+	default y
+	---help---
+	  A cache policy that uses a multiqueue ordered by recent hits
+	  to select which blocks should be promoted and demoted.
+	  This is meant to be a general purpose policy.  It prioritises
+	  reads over writes.  This SMQ policy (vs MQ) offers the promise
+	  of less memory utilization, improved performance and increased
+	  adaptability in the face of changing workloads.
 
 config DM_WRITECACHE
 	tristate "Writecache target"
 	depends on BLK_DEV_DM
 	---help---
-	   The writecache target caches writes on persistent memory or SSD.
-	   It is intended for databases or other programs that need extremely
-	   low commit latency.
+	  The writecache target caches writes on persistent memory or SSD.
+	  It is intended for databases or other programs that need extremely
+	  low commit latency.
 
-	   The writecache target doesn't cache reads because reads are supposed
-	   to be cached in standard RAM.
+	  The writecache target doesn't cache reads because reads are supposed
+	  to be cached in standard RAM.
 
 config DM_ERA
-       tristate "Era target (EXPERIMENTAL)"
-       depends on BLK_DEV_DM
-       default n
-       select DM_PERSISTENT_DATA
-       select DM_BIO_PRISON
-       ---help---
-         dm-era tracks which parts of a block device are written to
-         over time.  Useful for maintaining cache coherency when using
-         vendor snapshots.
+	tristate "Era target (EXPERIMENTAL)"
+	depends on BLK_DEV_DM
+	default n
+	select DM_PERSISTENT_DATA
+	select DM_BIO_PRISON
+	---help---
+	  dm-era tracks which parts of a block device are written to
+	  over time.  Useful for maintaining cache coherency when using
+	  vendor snapshots.
 
 config DM_MIRROR
-       tristate "Mirror target"
-       depends on BLK_DEV_DM
-       ---help---
-         Allow volume managers to mirror logical volumes, also
-         needed for live data migration tools such as 'pvmove'.
+	tristate "Mirror target"
+	depends on BLK_DEV_DM
+	---help---
+	  Allow volume managers to mirror logical volumes, also
+	  needed for live data migration tools such as 'pvmove'.
 
 config DM_LOG_USERSPACE
 	tristate "Mirror userspace logging"
@@ -364,31 +364,31 @@ config DM_LOG_USERSPACE
 	  by leveraging this framework.
 
 config DM_RAID
-       tristate "RAID 1/4/5/6/10 target"
-       depends on BLK_DEV_DM
-       select MD_RAID0
-       select MD_RAID1
-       select MD_RAID10
-       select MD_RAID456
-       select BLK_DEV_MD
-       ---help---
-	 A dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings
-
-	 A RAID-5 set of N drives with a capacity of C MB per drive provides
-	 the capacity of C * (N - 1) MB, and protects against a failure
-	 of a single drive. For a given sector (row) number, (N - 1) drives
-	 contain data sectors, and one drive contains the parity protection.
-	 For a RAID-4 set, the parity blocks are present on a single drive,
-	 while a RAID-5 set distributes the parity across the drives in one
-	 of the available parity distribution methods.
-
-	 A RAID-6 set of N drives with a capacity of C MB per drive
-	 provides the capacity of C * (N - 2) MB, and protects
-	 against a failure of any two drives. For a given sector
-	 (row) number, (N - 2) drives contain data sectors, and two
-	 drives contains two independent redundancy syndromes.  Like
-	 RAID-5, RAID-6 distributes the syndromes across the drives
-	 in one of the available parity distribution methods.
+	tristate "RAID 1/4/5/6/10 target"
+	depends on BLK_DEV_DM
+	select MD_RAID0
+	select MD_RAID1
+	select MD_RAID10
+	select MD_RAID456
+	select BLK_DEV_MD
+	---help---
+	  A dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings
+
+	  A RAID-5 set of N drives with a capacity of C MB per drive provides
+	  the capacity of C * (N - 1) MB, and protects against a failure
+	  of a single drive. For a given sector (row) number, (N - 1) drives
+	  contain data sectors, and one drive contains the parity protection.
+	  For a RAID-4 set, the parity blocks are present on a single drive,
+	  while a RAID-5 set distributes the parity across the drives in one
+	  of the available parity distribution methods.
+
+	  A RAID-6 set of N drives with a capacity of C MB per drive
+	  provides the capacity of C * (N - 2) MB, and protects
+	  against a failure of any two drives. For a given sector
+	  (row) number, (N - 2) drives contain data sectors, and two
+	  drives contains two independent redundancy syndromes.  Like
+	  RAID-5, RAID-6 distributes the syndromes across the drives
+	  in one of the available parity distribution methods.
 
 config DM_ZERO
 	tristate "Zero target"
@@ -431,10 +431,10 @@ config DM_DELAY
 	tristate "I/O delaying target"
 	depends on BLK_DEV_DM
 	---help---
-	A target that delays reads and/or writes and can send
-	them to different devices.  Useful for testing.
+	  A target that delays reads and/or writes and can send
+	  them to different devices.  Useful for testing.
 
-	If unsure, say N.
+	  If unsure, say N.
 
 config DM_INIT
 	bool "DM \"dm-mod.create=\" parameter support"
@@ -455,10 +455,10 @@ config DM_UEVENT
 	Generate udev events for DM events.
 
 config DM_FLAKEY
-       tristate "Flakey target"
-       depends on BLK_DEV_DM
-       ---help---
-         A target that intermittently fails I/O for debugging purposes.
+	tristate "Flakey target"
+	depends on BLK_DEV_DM
+	---help---
+	  A target that intermittently fails I/O for debugging purposes.
 
 config DM_VERITY
 	tristate "Verity target support"
drivers/md/persistent-data/Kconfig +7 -8
index a53cbc9..28b77ee 100644
@@ -1,9 +1,8 @@
 config DM_PERSISTENT_DATA
-       tristate
-       depends on BLK_DEV_DM
-       select LIBCRC32C
-       select DM_BUFIO
-       ---help---
-	 Library providing immutable on-disk data structure support for
-	 device-mapper targets such as the thin provisioning target.
-
+	tristate
+	depends on BLK_DEV_DM
+	select LIBCRC32C
+	select DM_BUFIO
+	---help---
+	  Library providing immutable on-disk data structure support for
+	  device-mapper targets such as the thin provisioning target.
Signature · 1 line
1.9.1
#80 lore raw

PATCH 75/114 drivers: soc: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/soc/fsl/Kconfig      |  9 +++++----
 drivers/soc/qcom/Kconfig     | 23 ++++++++++++-----------
 drivers/soc/rockchip/Kconfig | 18 +++++++++---------
 3 files changed, 26 insertions(+), 24 deletions(-)
drivers/soc/fsl/Kconfig +5 -4
index 61f8e14..0db980a 100644
@@ -20,13 +20,14 @@ config FSL_GUTS
 	  into this driver as well.
 
 config FSL_MC_DPIO
-        tristate "QorIQ DPAA2 DPIO driver"
-        depends on FSL_MC_BUS
-        select SOC_BUS
-        help
+	tristate "QorIQ DPAA2 DPIO driver"
+	depends on FSL_MC_BUS
+	select SOC_BUS
+	help
 	  Driver for the DPAA2 DPIO object.  A DPIO provides queue and
 	  buffer management facilities for software to interact with
 	  other DPAA2 objects. This driver does not expose the DPIO
 	  objects individually, but groups them under a service layer
 	  API.
+
 endmenu
drivers/soc/qcom/Kconfig +12 -11
index 1ee298f..e885233 100644
@@ -32,13 +32,13 @@ config QCOM_GLINK_SSR
 	  neighboring subsystems going up or down.
 
 config QCOM_GSBI
-        tristate "QCOM General Serial Bus Interface"
-        depends on ARCH_QCOM || COMPILE_TEST
-        select MFD_SYSCON
-        help
-          Say y here to enable GSBI support.  The GSBI provides control
-          functions for connecting the underlying serial UART, SPI, and I2C
-          devices to the output pins.
+	tristate "QCOM General Serial Bus Interface"
+	depends on ARCH_QCOM || COMPILE_TEST
+	select MFD_SYSCON
+	help
+	  Say y here to enable GSBI support.  The GSBI provides control
+	  functions for connecting the underlying serial UART, SPI, and I2C
+	  devices to the output pins.
 
 config QCOM_LLCC
 	tristate "Qualcomm Technologies, Inc. LLCC driver"
@@ -175,8 +175,9 @@ config QCOM_APR
 	depends on ARCH_QCOM || COMPILE_TEST
 	depends on RPMSG
 	help
-          Enable APR IPC protocol support between
-          application processor and QDSP6. APR is
-          used by audio driver to configure QDSP6
-          ASM, ADM and AFE modules.
+	  Enable APR IPC protocol support between
+	  application processor and QDSP6. APR is
+	  used by audio driver to configure QDSP6
+	  ASM, ADM and AFE modules.
+
 endmenu
drivers/soc/rockchip/Kconfig +9 -9
index 20da55d..f468b79 100644
@@ -14,15 +14,15 @@ config ROCKCHIP_GRF
 	  to make some of them conform to expectations of the kernel.
 
 config ROCKCHIP_PM_DOMAINS
-        bool "Rockchip generic power domain"
-        depends on PM
-        select PM_GENERIC_DOMAINS
-        help
-          Say y here to enable power domain support.
-          In order to meet high performance and low power requirements, a power
-          management unit is designed or saving power when RK3288 in low power
-          mode. The RK3288 PMU is dedicated for managing the power of the whole chip.
+	bool "Rockchip generic power domain"
+	depends on PM
+	select PM_GENERIC_DOMAINS
+	help
+	  Say y here to enable power domain support.
+	  In order to meet high performance and low power requirements, a power
+	  management unit is designed or saving power when RK3288 in low power
+	  mode. The RK3288 PMU is dedicated for managing the power of the whole chip.
 
-          If unsure, say N.
+	  If unsure, say N.
 
 endif
Signature · 1 line
1.9.1
#81 lore raw

PATCH 76/114 drivers: virt: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/virt/Kconfig | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
drivers/virt/Kconfig +5 -5
index 8d9cdfb..17a8685 100644
@@ -17,17 +17,17 @@ config FSL_HV_MANAGER
 	depends on FSL_SOC
 	select EPAPR_PARAVIRT
 	help
-          The Freescale hypervisor management driver provides several services
+	  The Freescale hypervisor management driver provides several services
 	  to drivers and applications related to the Freescale hypervisor:
 
-          1) An ioctl interface for querying and managing partitions.
+	  1) An ioctl interface for querying and managing partitions.
 
-          2) A file interface to reading incoming doorbells.
+	  2) A file interface to reading incoming doorbells.
 
-          3) An interrupt handler for shutting down the partition upon
+	  3) An interrupt handler for shutting down the partition upon
 	     receiving the shutdown doorbell from a manager partition.
 
-          4) A kernel interface for receiving callbacks when a managed
+	  4) A kernel interface for receiving callbacks when a managed
 	     partition shuts down.
 
 source "drivers/virt/vboxguest/Kconfig"
Signature · 1 line
1.9.1
#82 lore raw

PATCH 77/114 drivers: clk: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/clk/Kconfig           |  2 +-
 drivers/clk/imx/Kconfig       |  2 +-
 drivers/clk/mediatek/Kconfig  | 44 +++++++++++++++++++++----------------------
 drivers/clk/mvebu/Kconfig     |  2 +-
 drivers/clk/qcom/Kconfig      | 12 ++++++------
 drivers/clk/versatile/Kconfig |  2 +-
 6 files changed, 32 insertions(+), 32 deletions(-)
drivers/clk/Kconfig +1 -1
index d2f0bb5..c988a1d 100644
@@ -26,7 +26,7 @@ config COMMON_CLK_WM831X
 	tristate "Clock driver for WM831x/2x PMICs"
 	depends on MFD_WM831X
 	---help---
-          Supports the clocking subsystem of the WM831x/2x series of
+	  Supports the clocking subsystem of the WM831x/2x series of
 	  PMICs from Wolfson Microelectronics.
 
 source "drivers/clk/versatile/Kconfig"
drivers/clk/imx/Kconfig +1 -1
index 4aae31a..48bc676 100644
@@ -12,7 +12,7 @@ config CLK_IMX8MQ
 	bool "IMX8MQ CCM Clock Driver"
 	depends on ARCH_MXC && ARM64
 	help
-	    Build the driver for i.MX8MQ CCM Clock Driver
+	  Build the driver for i.MX8MQ CCM Clock Driver
 
 config CLK_IMX8QXP
 	bool "IMX8QXP SCU Clock"
drivers/clk/mediatek/Kconfig +22 -22

58 lines not on this page · raw message

drivers/clk/mvebu/Kconfig +1 -1
index fddc8ac..a765b0b 100644
@@ -25,7 +25,7 @@ config ARMADA_39X_CLK
 	select MVEBU_CLK_COMMON
 
 config ARMADA_37XX_CLK
-       bool
+	bool
 
 config ARMADA_XP_CLK
 	bool
drivers/clk/qcom/Kconfig +6 -6
index 1c04575c..c866cab 100644
@@ -1,6 +1,6 @@
 config KRAIT_CLOCKS
-       bool
-       select KRAIT_L2_ACCESSORS
+	bool
+	select KRAIT_L2_ACCESSORS
 
 config QCOM_GDSC
 	bool
@@ -67,10 +67,10 @@ config QCOM_CLK_RPMH
 	tristate "RPMh Clock Driver"
 	depends on QCOM_RPMH
 	help
-	 RPMh manages shared resources on some Qualcomm Technologies, Inc.
-	 SoCs. It accepts requests from other hardware subsystems via RSC.
-	 Say Y if you want to support the clocks exposed by RPMh on
-	 platforms such as SDM845.
+	  RPMh manages shared resources on some Qualcomm Technologies, Inc.
+	  SoCs. It accepts requests from other hardware subsystems via RSC.
+	  Say Y if you want to support the clocks exposed by RPMh on
+	  platforms such as SDM845.
 
 config APQ_GCC_8084
 	tristate "APQ8084 Global Clock Controller"
drivers/clk/versatile/Kconfig +1 -1
index 8aa875f..5607683 100644
@@ -8,7 +8,7 @@ config COMMON_CLK_VERSATILE
 		COMPILE_TEST
 	select REGMAP_MMIO
 	---help---
-          Supports clocking on ARM Reference designs:
+	  Supports clocking on ARM Reference designs:
 	  - Integrator/AP and Integrator/CP
 	  - RealView PB1176, EB, PB11MP and PBX
 	  - Versatile Express
Signature · 1 line
1.9.1
#83 lore raw

PATCH 78/114 drivers: firmware: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/firmware/Kconfig     | 28 ++++++++++++++--------------
 drivers/firmware/efi/Kconfig |  2 +-
 2 files changed, 15 insertions(+), 15 deletions(-)
drivers/firmware/Kconfig +14 -14
index cac16c4..1a18ccb 100644
@@ -99,8 +99,8 @@ config EDD
 	  BIOS tries boot from.  This information is then exported via sysfs.
 
 	  This option is experimental and is known to fail to boot on some
-          obscure configurations. Most disk controller BIOS vendors do
-          not yet implement this feature.
+	  obscure configurations. Most disk controller BIOS vendors do
+	  not yet implement this feature.
 
 config EDD_OFF
 	bool "Sets default behavior for EDD detection to off"
@@ -112,14 +112,14 @@ config EDD_OFF
 	  using the kernel parameter 'edd={on|skipmbr|off}'.
 
 config FIRMWARE_MEMMAP
-    bool "Add firmware-provided memory map to sysfs" if EXPERT
-    default X86
-    help
-      Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
-      That memory map is used for example by kexec to set up parameter area
-      for the next kernel, but can also be used for debugging purposes.
+	bool "Add firmware-provided memory map to sysfs" if EXPERT
+	default X86
+	help
+	  Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
+	  That memory map is used for example by kexec to set up parameter area
+	  for the next kernel, but can also be used for debugging purposes.
 
-      See also Documentation/ABI/testing/sysfs-firmware-memmap.
+	  See also Documentation/ABI/testing/sysfs-firmware-memmap.
 
 config EFI_PCDP
 	bool "Console device selection via EFI PCDP or HCDP table"
@@ -143,12 +143,12 @@ config EFI_PCDP
 	  You must also enable the appropriate drivers (serial, VGA, etc.)
 
 	  See DIG64_HCDPv20_042804.pdf available from
-	  <http://www.dig64.org/specifications/> 
+	  <http://www.dig64.org/specifications/>
 
 config DMIID
-    bool "Export DMI identification via sysfs to userspace"
-    depends on DMI
-    default y
+	bool "Export DMI identification via sysfs to userspace"
+	depends on DMI
+	default y
 	help
 	  Say Y here if you want to query SMBIOS/DMI system identification
 	  information from userspace through /sys/class/dmi/id/ or if you want
@@ -182,7 +182,7 @@ config ISCSI_IBFT
 	tristate "iSCSI Boot Firmware Table Attributes module"
 	select ISCSI_BOOT_SYSFS
 	depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
-	default	n
+	default n
 	help
 	  This option enables support for detection and exposing of iSCSI
 	  Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
drivers/firmware/efi/Kconfig +1 -1
index 190be0b..96badaa 100644
@@ -79,7 +79,7 @@ config EFI_PARAMS_FROM_FDT
 	help
 	  Select this config option from the architecture Kconfig if
 	  the EFI runtime support gets system table address, memory
-          map address, and other parameters from the device tree.
+	  map address, and other parameters from the device tree.
 
 config EFI_RUNTIME_WRAPPERS
 	bool
Signature · 1 line
1.9.1
#84 lore raw

PATCH 79/114 drivers: char: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/char/Kconfig           | 24 +++++-----
 drivers/char/agp/Kconfig       | 13 +++---
 drivers/char/hw_random/Kconfig | 24 +++++-----
 drivers/char/ipmi/Kconfig      | 99 +++++++++++++++++++++---------------------
 4 files changed, 80 insertions(+), 80 deletions(-)
drivers/char/Kconfig +12 -12
index 72866a0..ab33583 100644
@@ -35,18 +35,18 @@ config SGI_SNSC
 	  say Y.  Otherwise, say N.
 
 config SGI_TIOCX
-       bool "SGI TIO CX driver support"
-       depends on (IA64_SGI_SN2 || IA64_GENERIC)
-       help
-         If you have an SGI Altix and you have fpga devices attached
-         to your TIO, say Y here, otherwise say N.
+	bool "SGI TIO CX driver support"
+	depends on (IA64_SGI_SN2 || IA64_GENERIC)
+	help
+	  If you have an SGI Altix and you have fpga devices attached
+	  to your TIO, say Y here, otherwise say N.
 
 config SGI_MBCS
-       tristate "SGI FPGA Core Services driver support"
-       depends on SGI_TIOCX
-       help
-         If you have an SGI Altix with an attached SABrick
-         say Y or M here, otherwise say N.
+	tristate "SGI FPGA Core Services driver support"
+	depends on SGI_TIOCX
+	help
+	  If you have an SGI Altix with an attached SABrick
+	  say Y or M here, otherwise say N.
 
 source "drivers/tty/serial/Kconfig"
 source "drivers/tty/serdev/Kconfig"
@@ -461,8 +461,8 @@ config RAW_DRIVER
 	  Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
 	  See the raw(8) manpage for more details.
 
-          Applications should preferably open the device (eg /dev/hda1)
-          with the O_DIRECT flag.
+	  Applications should preferably open the device (eg /dev/hda1)
+	  with the O_DIRECT flag.
 
 config MAX_RAW_DEVS
 	int "Maximum number of RAW devices to support (1-65536)"
drivers/char/agp/Kconfig +6 -7
index 6231714..6da28d5 100644
@@ -63,7 +63,7 @@ config AGP_AMD64
 	  This option gives you AGP support for the GLX component of
 	  X using the on-CPU northbridge of the AMD Athlon64/Opteron CPUs.
 	  You still need an external AGP bridge like the AMD 8151, VIA
-          K8T400M, SiS755. It may also support other AGP bridges when loaded
+	  K8T400M, SiS755. It may also support other AGP bridges when loaded
 	  with agp_try_unsupported=1.
 
 config AGP_INTEL
@@ -151,13 +151,12 @@ config AGP_EFFICEON
 	  series processors with integrated northbridges.
 
 config AGP_SGI_TIOCA
-        tristate "SGI TIO chipset AGP support"
-        depends on AGP && (IA64_SGI_SN2 || IA64_GENERIC)
-        help
-          This option gives you AGP GART support for the SGI TIO chipset
-          for IA64 processors.
+	tristate "SGI TIO chipset AGP support"
+	depends on AGP && (IA64_SGI_SN2 || IA64_GENERIC)
+	help
+	  This option gives you AGP GART support for the SGI TIO chipset
+	  for IA64 processors.
 
 config INTEL_GTT
 	tristate
 	depends on X86 && PCI
-
drivers/char/hw_random/Kconfig +12 -12
index 25a7d8f..6265931 100644
@@ -156,15 +156,15 @@ config HW_RANDOM_OMAP
 	tristate "OMAP Random Number Generator support"
 	depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS || ARCH_MVEBU
 	default HW_RANDOM
- 	---help---
- 	  This driver provides kernel-side support for the Random Number
+	---help---
+	  This driver provides kernel-side support for the Random Number
 	  Generator hardware found on OMAP16xx, OMAP2/3/4/5, AM33xx/AM43xx
 	  multimedia processors, and Marvell Armada 7k/8k SoCs.
 
 	  To compile this driver as a module, choose M here: the
 	  module will be called omap-rng.
 
- 	  If unsure, say Y.
+	  If unsure, say Y.
 
 config HW_RANDOM_OMAP3_ROM
 	tristate "OMAP3 ROM Random Number Generator support"
@@ -372,17 +372,17 @@ config HW_RANDOM_MESON
 	  If unsure, say Y.
 
 config HW_RANDOM_CAVIUM
-       tristate "Cavium ThunderX Random Number Generator support"
-       depends on HW_RANDOM && PCI && (ARM64 || (COMPILE_TEST && 64BIT))
-       default HW_RANDOM
-       ---help---
-         This driver provides kernel-side support for the Random Number
-         Generator hardware found on Cavium SoCs.
+	tristate "Cavium ThunderX Random Number Generator support"
+	depends on HW_RANDOM && PCI && (ARM64 || (COMPILE_TEST && 64BIT))
+	default HW_RANDOM
+	---help---
+	  This driver provides kernel-side support for the Random Number
+	  Generator hardware found on Cavium SoCs.
 
-         To compile this driver as a module, choose M here: the
-         module will be called cavium_rng.
+	  To compile this driver as a module, choose M here: the
+	  module will be called cavium_rng.
 
-         If unsure, say Y.
+	  If unsure, say Y.
 
 config HW_RANDOM_MTK
 	tristate "Mediatek Random Number Generator support"
drivers/char/ipmi/Kconfig +50 -49

140 lines not on this page · raw message

Signature · 1 line
1.9.1
Acked-by on v1 79/114
#85 lore raw

Re: [PATCH 079/114] drivers: char: Kconfig: pedantic formatting

Quoted 4 lines · metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

IPMI portions look ok to me.

Quoted 283 lines
---
 drivers/char/Kconfig           | 24 +++++-----
 drivers/char/agp/Kconfig       | 13 +++---
 drivers/char/hw_random/Kconfig | 24 +++++-----
 drivers/char/ipmi/Kconfig      | 99 +++++++++++++++++++++---------------------
 4 files changed, 80 insertions(+), 80 deletions(-)
drivers/char/Kconfig +12 -12
index 72866a0..ab33583 100644
@@ -35,18 +35,18 @@ config SGI_SNSC
 	  say Y.  Otherwise, say N.
 
 config SGI_TIOCX
-       bool "SGI TIO CX driver support"
-       depends on (IA64_SGI_SN2 || IA64_GENERIC)
-       help
-         If you have an SGI Altix and you have fpga devices attached
-         to your TIO, say Y here, otherwise say N.
+	bool "SGI TIO CX driver support"
+	depends on (IA64_SGI_SN2 || IA64_GENERIC)
+	help
+	  If you have an SGI Altix and you have fpga devices attached
+	  to your TIO, say Y here, otherwise say N.
 
 config SGI_MBCS
-       tristate "SGI FPGA Core Services driver support"
-       depends on SGI_TIOCX
-       help
-         If you have an SGI Altix with an attached SABrick
-         say Y or M here, otherwise say N.
+	tristate "SGI FPGA Core Services driver support"
+	depends on SGI_TIOCX
+	help
+	  If you have an SGI Altix with an attached SABrick
+	  say Y or M here, otherwise say N.
 
 source "drivers/tty/serial/Kconfig"
 source "drivers/tty/serdev/Kconfig"
@@ -461,8 +461,8 @@ config RAW_DRIVER
 	  Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
 	  See the raw(8) manpage for more details.
 
-          Applications should preferably open the device (eg /dev/hda1)
-          with the O_DIRECT flag.
+	  Applications should preferably open the device (eg /dev/hda1)
+	  with the O_DIRECT flag.
 
 config MAX_RAW_DEVS
 	int "Maximum number of RAW devices to support (1-65536)"
drivers/char/agp/Kconfig +6 -7
index 6231714..6da28d5 100644
@@ -63,7 +63,7 @@ config AGP_AMD64
 	  This option gives you AGP support for the GLX component of
 	  X using the on-CPU northbridge of the AMD Athlon64/Opteron CPUs.
 	  You still need an external AGP bridge like the AMD 8151, VIA
-          K8T400M, SiS755. It may also support other AGP bridges when loaded
+	  K8T400M, SiS755. It may also support other AGP bridges when loaded
 	  with agp_try_unsupported=1.
 
 config AGP_INTEL
@@ -151,13 +151,12 @@ config AGP_EFFICEON
 	  series processors with integrated northbridges.
 
 config AGP_SGI_TIOCA
-        tristate "SGI TIO chipset AGP support"
-        depends on AGP && (IA64_SGI_SN2 || IA64_GENERIC)
-        help
-          This option gives you AGP GART support for the SGI TIO chipset
-          for IA64 processors.
+	tristate "SGI TIO chipset AGP support"
+	depends on AGP && (IA64_SGI_SN2 || IA64_GENERIC)
+	help
+	  This option gives you AGP GART support for the SGI TIO chipset
+	  for IA64 processors.
 
 config INTEL_GTT
 	tristate
 	depends on X86 && PCI
-
drivers/char/hw_random/Kconfig +12 -12
index 25a7d8f..6265931 100644
@@ -156,15 +156,15 @@ config HW_RANDOM_OMAP
 	tristate "OMAP Random Number Generator support"
 	depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS || ARCH_MVEBU
 	default HW_RANDOM
- 	---help---
- 	  This driver provides kernel-side support for the Random Number
+	---help---
+	  This driver provides kernel-side support for the Random Number
 	  Generator hardware found on OMAP16xx, OMAP2/3/4/5, AM33xx/AM43xx
 	  multimedia processors, and Marvell Armada 7k/8k SoCs.
 
 	  To compile this driver as a module, choose M here: the
 	  module will be called omap-rng.
 
- 	  If unsure, say Y.
+	  If unsure, say Y.
 
 config HW_RANDOM_OMAP3_ROM
 	tristate "OMAP3 ROM Random Number Generator support"
@@ -372,17 +372,17 @@ config HW_RANDOM_MESON
 	  If unsure, say Y.
 
 config HW_RANDOM_CAVIUM
-       tristate "Cavium ThunderX Random Number Generator support"
-       depends on HW_RANDOM && PCI && (ARM64 || (COMPILE_TEST && 64BIT))
-       default HW_RANDOM
-       ---help---
-         This driver provides kernel-side support for the Random Number
-         Generator hardware found on Cavium SoCs.
+	tristate "Cavium ThunderX Random Number Generator support"
+	depends on HW_RANDOM && PCI && (ARM64 || (COMPILE_TEST && 64BIT))
+	default HW_RANDOM
+	---help---
+	  This driver provides kernel-side support for the Random Number
+	  Generator hardware found on Cavium SoCs.
 
-         To compile this driver as a module, choose M here: the
-         module will be called cavium_rng.
+	  To compile this driver as a module, choose M here: the
+	  module will be called cavium_rng.
 
-         If unsure, say Y.
+	  If unsure, say Y.
 
 config HW_RANDOM_MTK
 	tristate "Mediatek Random Number Generator support"
drivers/char/ipmi/Kconfig +50 -49
index 94719fc..b6219c3 100644
@@ -1,40 +1,41 @@
+
 #
 # IPMI device configuration
 #
 
 menuconfig IPMI_HANDLER
-       tristate 'IPMI top-level message handler'
-       depends on HAS_IOMEM
-       select IPMI_DMI_DECODE if DMI
-       help
-         This enables the central IPMI message handler, required for IPMI
-	 to work.
+	tristate 'IPMI top-level message handler'
+	depends on HAS_IOMEM
+	select IPMI_DMI_DECODE if DMI
+	help
+	  This enables the central IPMI message handler, required for IPMI
+	  to work.
 
-         IPMI is a standard for managing sensors (temperature,
-         voltage, etc.) in a system.
+	  IPMI is a standard for managing sensors (temperature,
+	  voltage, etc.) in a system.
 
-         See <file:Documentation/IPMI.txt> for more details on the driver.
+	  See <file:Documentation/IPMI.txt> for more details on the driver.
 
-	 If unsure, say N.
+	  If unsure, say N.
 
 config IPMI_DMI_DECODE
-       select IPMI_PLAT_DATA
-       bool
+	select IPMI_PLAT_DATA
+	bool
 
 config IPMI_PLAT_DATA
-       bool
+	bool
 
 if IPMI_HANDLER
 
 config IPMI_PANIC_EVENT
-       bool 'Generate a panic event to all BMCs on a panic'
-       help
-	 When a panic occurs, this will cause the IPMI message handler to,
-	 by default, generate an IPMI event describing the panic to each
-	 interface registered with the message handler.  This is always
-	 available, the module parameter for ipmi_msghandler named
-	 panic_op can be set to "event" to chose this value, this config
-	 simply causes the default value to be set to "event".
+	bool 'Generate a panic event to all BMCs on a panic'
+	help
+	  When a panic occurs, this will cause the IPMI message handler to,
+	  by default, generate an IPMI event describing the panic to each
+	  interface registered with the message handler.  This is always
+	  available, the module parameter for ipmi_msghandler named
+	  panic_op can be set to "event" to chose this value, this config
+	  simply causes the default value to be set to "event".
 
 config IPMI_PANIC_STRING
 	bool 'Generate OEM events containing the panic string'
@@ -53,43 +54,43 @@ config IPMI_PANIC_STRING
 	  causes the default value to be set to "string".
 
 config IPMI_DEVICE_INTERFACE
-       tristate 'Device interface for IPMI'
-       help
-         This provides an IOCTL interface to the IPMI message handler so
-	 userland processes may use IPMI.  It supports poll() and select().
+	tristate 'Device interface for IPMI'
+	help
+	  This provides an IOCTL interface to the IPMI message handler so
+	  userland processes may use IPMI.  It supports poll() and select().
 
 config IPMI_SI
-       tristate 'IPMI System Interface handler'
-       select IPMI_PLAT_DATA
-       help
-         Provides a driver for System Interfaces (KCS, SMIC, BT).
-	 Currently, only KCS and SMIC are supported.  If
-	 you are using IPMI, you should probably say "y" here.
+	tristate 'IPMI System Interface handler'
+	select IPMI_PLAT_DATA
+	help
+	  Provides a driver for System Interfaces (KCS, SMIC, BT).
+	  Currently, only KCS and SMIC are supported.  If
+	  you are using IPMI, you should probably say "y" here.
 
 config IPMI_SSIF
-       tristate 'IPMI SMBus handler (SSIF)'
-       select I2C
-       help
-         Provides a driver for a SMBus interface to a BMC, meaning that you
-	 have a driver that must be accessed over an I2C bus instead of a
-	 standard interface.  This module requires I2C support.
+	tristate 'IPMI SMBus handler (SSIF)'
+	select I2C
+	help
+	  Provides a driver for a SMBus interface to a BMC, meaning that you
+	  have a driver that must be accessed over an I2C bus instead of a
+	  standard interface.  This module requires I2C support.
 
 config IPMI_POWERNV
-       depends on PPC_POWERNV
-       tristate 'POWERNV (OPAL firmware) IPMI interface'
-       help
-         Provides a driver for OPAL firmware-based IPMI interfaces.
+	depends on PPC_POWERNV
+	tristate 'POWERNV (OPAL firmware) IPMI interface'
+	help
+	  Provides a driver for OPAL firmware-based IPMI interfaces.
 
 config IPMI_WATCHDOG
-       tristate 'IPMI Watchdog Timer'
-       help
-         This enables the IPMI watchdog timer.
+	tristate 'IPMI Watchdog Timer'
+	help
+	  This enables the IPMI watchdog timer.
 
 config IPMI_POWEROFF
-       tristate 'IPMI Poweroff'
-       help
-         This enables a function to power off the system with IPMI if
-	 the IPMI management controller is capable of this.
+	tristate 'IPMI Poweroff'
+	help
+	  This enables a function to power off the system with IPMI if
+	  the IPMI management controller is capable of this.
 
 endif # IPMI_HANDLER
 
@@ -125,7 +126,7 @@ config NPCM7XX_KCS_IPMI_BMC
 
 config ASPEED_BT_IPMI_BMC
 	depends on ARCH_ASPEED || COMPILE_TEST
-       depends on REGMAP && REGMAP_MMIO && MFD_SYSCON
+	depends on REGMAP && REGMAP_MMIO && MFD_SYSCON
 	tristate "BT IPMI bmc driver"
 	help
 	  Provides a driver for the BT (Block Transfer) IPMI interface
Signature · 1 line
1.9.1
#86 lore raw

Re: [PATCH 079/114] drivers: char: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult
Quoted 7 lines · metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/char/Kconfig           | 24 +++++-----

While you are touching this file,
why don't you fix checkpatch.pl warnings?

WARNING: prefer 'help' over '---help---' for new help texts #54: FILE: drivers/char/Kconfig:54:
+config TTY_PRINTK

WARNING: prefer 'help' over '---help---' for new help texts #77: FILE: drivers/char/Kconfig:77:
+config PRINTER

WARNING: prefer 'help' over '---help---' for new help texts #120: FILE: drivers/char/Kconfig:120:
+config PPDEV

WARNING: prefer 'help' over '---help---' for new help texts #245: FILE: drivers/char/Kconfig:245:
+config NVRAM

WARNING: prefer 'help' over '---help---' for new help texts #274: FILE: drivers/char/Kconfig:274:
+config RTC

WARNING: prefer 'help' over '---help---' for new help texts #300: FILE: drivers/char/Kconfig:300:
+config JS_RTC

Quoted 281 lines
 drivers/char/agp/Kconfig       | 13 +++---
 drivers/char/hw_random/Kconfig | 24 +++++-----
 drivers/char/ipmi/Kconfig      | 99 +++++++++++++++++++++---------------------
 4 files changed, 80 insertions(+), 80 deletions(-)
drivers/char/Kconfig +12 -12
index 72866a0..ab33583 100644
@@ -35,18 +35,18 @@ config SGI_SNSC
          say Y.  Otherwise, say N.
 
 config SGI_TIOCX
-       bool "SGI TIO CX driver support"
-       depends on (IA64_SGI_SN2 || IA64_GENERIC)
-       help
-         If you have an SGI Altix and you have fpga devices attached
-         to your TIO, say Y here, otherwise say N.
+       bool "SGI TIO CX driver support"
+       depends on (IA64_SGI_SN2 || IA64_GENERIC)
+       help
+         If you have an SGI Altix and you have fpga devices attached
+         to your TIO, say Y here, otherwise say N.
 
 config SGI_MBCS
-       tristate "SGI FPGA Core Services driver support"
-       depends on SGI_TIOCX
-       help
-         If you have an SGI Altix with an attached SABrick
-         say Y or M here, otherwise say N.
+       tristate "SGI FPGA Core Services driver support"
+       depends on SGI_TIOCX
+       help
+         If you have an SGI Altix with an attached SABrick
+         say Y or M here, otherwise say N.
 
 source "drivers/tty/serial/Kconfig"
 source "drivers/tty/serdev/Kconfig"
@@ -461,8 +461,8 @@ config RAW_DRIVER
          Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
          See the raw(8) manpage for more details.
 
-          Applications should preferably open the device (eg /dev/hda1)
-          with the O_DIRECT flag.
+         Applications should preferably open the device (eg /dev/hda1)
+         with the O_DIRECT flag.
 
 config MAX_RAW_DEVS
        int "Maximum number of RAW devices to support (1-65536)"
drivers/char/agp/Kconfig +6 -7
index 6231714..6da28d5 100644
@@ -63,7 +63,7 @@ config AGP_AMD64
          This option gives you AGP support for the GLX component of
          X using the on-CPU northbridge of the AMD Athlon64/Opteron CPUs.
          You still need an external AGP bridge like the AMD 8151, VIA
-          K8T400M, SiS755. It may also support other AGP bridges when loaded
+         K8T400M, SiS755. It may also support other AGP bridges when loaded
          with agp_try_unsupported=1.
 
 config AGP_INTEL
@@ -151,13 +151,12 @@ config AGP_EFFICEON
          series processors with integrated northbridges.
 
 config AGP_SGI_TIOCA
-        tristate "SGI TIO chipset AGP support"
-        depends on AGP && (IA64_SGI_SN2 || IA64_GENERIC)
-        help
-          This option gives you AGP GART support for the SGI TIO chipset
-          for IA64 processors.
+       tristate "SGI TIO chipset AGP support"
+       depends on AGP && (IA64_SGI_SN2 || IA64_GENERIC)
+       help
+         This option gives you AGP GART support for the SGI TIO chipset
+         for IA64 processors.
 
 config INTEL_GTT
        tristate
        depends on X86 && PCI
-
drivers/char/hw_random/Kconfig +12 -12
index 25a7d8f..6265931 100644
@@ -156,15 +156,15 @@ config HW_RANDOM_OMAP
        tristate "OMAP Random Number Generator support"
        depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS || ARCH_MVEBU
        default HW_RANDOM
-       ---help---
-         This driver provides kernel-side support for the Random Number
+       ---help---
+         This driver provides kernel-side support for the Random Number
          Generator hardware found on OMAP16xx, OMAP2/3/4/5, AM33xx/AM43xx
          multimedia processors, and Marvell Armada 7k/8k SoCs.
 
          To compile this driver as a module, choose M here: the
          module will be called omap-rng.
 
-         If unsure, say Y.
+         If unsure, say Y.
 
 config HW_RANDOM_OMAP3_ROM
        tristate "OMAP3 ROM Random Number Generator support"
@@ -372,17 +372,17 @@ config HW_RANDOM_MESON
          If unsure, say Y.
 
 config HW_RANDOM_CAVIUM
-       tristate "Cavium ThunderX Random Number Generator support"
-       depends on HW_RANDOM && PCI && (ARM64 || (COMPILE_TEST && 64BIT))
-       default HW_RANDOM
-       ---help---
-         This driver provides kernel-side support for the Random Number
-         Generator hardware found on Cavium SoCs.
+       tristate "Cavium ThunderX Random Number Generator support"
+       depends on HW_RANDOM && PCI && (ARM64 || (COMPILE_TEST && 64BIT))
+       default HW_RANDOM
+       ---help---
+         This driver provides kernel-side support for the Random Number
+         Generator hardware found on Cavium SoCs.
 
-         To compile this driver as a module, choose M here: the
-         module will be called cavium_rng.
+         To compile this driver as a module, choose M here: the
+         module will be called cavium_rng.
 
-         If unsure, say Y.
+         If unsure, say Y.
 
 config HW_RANDOM_MTK
        tristate "Mediatek Random Number Generator support"
drivers/char/ipmi/Kconfig +50 -50
index 94719fc..b6219c3 100644
@@ -1,40 +1,41 @@
+
 #
 # IPMI device configuration
 #
 
 menuconfig IPMI_HANDLER
-       tristate 'IPMI top-level message handler'
-       depends on HAS_IOMEM
-       select IPMI_DMI_DECODE if DMI
-       help
-         This enables the central IPMI message handler, required for IPMI
-        to work.
+       tristate 'IPMI top-level message handler'
+       depends on HAS_IOMEM
+       select IPMI_DMI_DECODE if DMI
+       help
+         This enables the central IPMI message handler, required for IPMI
+         to work.
 
-         IPMI is a standard for managing sensors (temperature,
-         voltage, etc.) in a system.
+         IPMI is a standard for managing sensors (temperature,
+         voltage, etc.) in a system.
 
-         See <file:Documentation/IPMI.txt> for more details on the driver.
+         See <file:Documentation/IPMI.txt> for more details on the driver.
 
-        If unsure, say N.
+         If unsure, say N.
 
 config IPMI_DMI_DECODE
-       select IPMI_PLAT_DATA
-       bool
+       select IPMI_PLAT_DATA
+       bool
 
 config IPMI_PLAT_DATA
-       bool
+       bool
 
 if IPMI_HANDLER
 
 config IPMI_PANIC_EVENT
-       bool 'Generate a panic event to all BMCs on a panic'
-       help
-        When a panic occurs, this will cause the IPMI message handler to,
-        by default, generate an IPMI event describing the panic to each
-        interface registered with the message handler.  This is always
-        available, the module parameter for ipmi_msghandler named
-        panic_op can be set to "event" to chose this value, this config
-        simply causes the default value to be set to "event".
+       bool 'Generate a panic event to all BMCs on a panic'
+       help
+         When a panic occurs, this will cause the IPMI message handler to,
+         by default, generate an IPMI event describing the panic to each
+         interface registered with the message handler.  This is always
+         available, the module parameter for ipmi_msghandler named
+         panic_op can be set to "event" to chose this value, this config
+         simply causes the default value to be set to "event".
 
 config IPMI_PANIC_STRING
        bool 'Generate OEM events containing the panic string'
@@ -53,43 +54,43 @@ config IPMI_PANIC_STRING
          causes the default value to be set to "string".
 
 config IPMI_DEVICE_INTERFACE
-       tristate 'Device interface for IPMI'
-       help
-         This provides an IOCTL interface to the IPMI message handler so
-        userland processes may use IPMI.  It supports poll() and select().
+       tristate 'Device interface for IPMI'
+       help
+         This provides an IOCTL interface to the IPMI message handler so
+         userland processes may use IPMI.  It supports poll() and select().
 
 config IPMI_SI
-       tristate 'IPMI System Interface handler'
-       select IPMI_PLAT_DATA
-       help
-         Provides a driver for System Interfaces (KCS, SMIC, BT).
-        Currently, only KCS and SMIC are supported.  If
-        you are using IPMI, you should probably say "y" here.
+       tristate 'IPMI System Interface handler'
+       select IPMI_PLAT_DATA
+       help
+         Provides a driver for System Interfaces (KCS, SMIC, BT).
+         Currently, only KCS and SMIC are supported.  If
+         you are using IPMI, you should probably say "y" here.
 
 config IPMI_SSIF
-       tristate 'IPMI SMBus handler (SSIF)'
-       select I2C
-       help
-         Provides a driver for a SMBus interface to a BMC, meaning that you
-        have a driver that must be accessed over an I2C bus instead of a
-        standard interface.  This module requires I2C support.
+       tristate 'IPMI SMBus handler (SSIF)'
+       select I2C
+       help
+         Provides a driver for a SMBus interface to a BMC, meaning that you
+         have a driver that must be accessed over an I2C bus instead of a
+         standard interface.  This module requires I2C support.
 
 config IPMI_POWERNV
-       depends on PPC_POWERNV
-       tristate 'POWERNV (OPAL firmware) IPMI interface'
-       help
-         Provides a driver for OPAL firmware-based IPMI interfaces.
+       depends on PPC_POWERNV
+       tristate 'POWERNV (OPAL firmware) IPMI interface'
+       help
+         Provides a driver for OPAL firmware-based IPMI interfaces.
 
 config IPMI_WATCHDOG
-       tristate 'IPMI Watchdog Timer'
-       help
-         This enables the IPMI watchdog timer.
+       tristate 'IPMI Watchdog Timer'
+       help
+         This enables the IPMI watchdog timer.
 
 config IPMI_POWEROFF
-       tristate 'IPMI Poweroff'
-       help
-         This enables a function to power off the system with IPMI if
-        the IPMI management controller is capable of this.
+       tristate 'IPMI Poweroff'
+       help
+         This enables a function to power off the system with IPMI if
+         the IPMI management controller is capable of this.
 
 endif # IPMI_HANDLER
 
@@ -125,7 +126,7 @@ config NPCM7XX_KCS_IPMI_BMC
 
 config ASPEED_BT_IPMI_BMC
        depends on ARCH_ASPEED || COMPILE_TEST
-       depends on REGMAP && REGMAP_MMIO && MFD_SYSCON
+       depends on REGMAP && REGMAP_MMIO && MFD_SYSCON
        tristate "BT IPMI bmc driver"
        help
          Provides a driver for the BT (Block Transfer) IPMI interface
--

1.9.1

Signature · 2 lines
Best Regards
Masahiro Yamada
#87 lore raw

PATCH 80/114 drivers: devfreq: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/devfreq/Kconfig | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/devfreq/Kconfig +3 -3
index 6a172d3..1af5ca3 100644
@@ -109,9 +109,9 @@ config ARM_RK3399_DMC_DEVFREQ
 	select PM_DEVFREQ_EVENT
 	select PM_OPP
 	help
-          This adds the DEVFREQ driver for the RK3399 DMC(Dynamic Memory Controller).
-          It sets the frequency for the memory controller and reads the usage counts
-          from hardware.
+	  This adds the DEVFREQ driver for the RK3399 DMC(Dynamic Memory Controller).
+	  It sets the frequency for the memory controller and reads the usage counts
+	  from hardware.
 
 source "drivers/devfreq/event/Kconfig"
 
Signature · 1 line
1.9.1
#88 lore raw

PATCH 81/114 drivers: memstick: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/memstick/core/Kconfig | 18 +++++++++---------
 drivers/memstick/host/Kconfig |  4 ++--
 2 files changed, 11 insertions(+), 11 deletions(-)
drivers/memstick/core/Kconfig +9 -9
index 1d38949..219ce91 100644
@@ -5,16 +5,16 @@
 comment "MemoryStick drivers"
 
 config MEMSTICK_UNSAFE_RESUME
-        bool "Allow unsafe resume (DANGEROUS)"
-        help
-          If you say Y here, the MemoryStick layer will assume that all
-          cards stayed in their respective slots during the suspend. The
-          normal behaviour is to remove them at suspend and
-          redetecting them at resume. Breaking this assumption will
-          in most cases result in data corruption.
+	bool "Allow unsafe resume (DANGEROUS)"
+	help
+	  If you say Y here, the MemoryStick layer will assume that all
+	  cards stayed in their respective slots during the suspend. The
+	  normal behaviour is to remove them at suspend and
+	  redetecting them at resume. Breaking this assumption will
+	  in most cases result in data corruption.
 
-          This option is usually just for embedded systems which use
-          a MemoryStick card for rootfs. Most people should say N here.
+	  This option is usually just for embedded systems which use
+	  a MemoryStick card for rootfs. Most people should say N here.
 
 config MSPRO_BLOCK
 	tristate "MemoryStick Pro block device driver"
drivers/memstick/host/Kconfig +2 -2
index aa2b078..5810c78 100644
@@ -17,7 +17,7 @@ config MEMSTICK_TIFM_MS
 	  'Misc devices: TI Flash Media PCI74xx/PCI76xx host adapter support
 	  (TIFM_7XX1)'.
 
-          To compile this driver as a module, choose M here: the
+	  To compile this driver as a module, choose M here: the
 	  module will be called tifm_ms.
 
 config MEMSTICK_JMICRON_38X
@@ -28,7 +28,7 @@ config MEMSTICK_JMICRON_38X
 	  Say Y here if you want to be able to access MemoryStick cards with
 	  the JMicron(R) JMB38X MemoryStick card reader.
 
-          To compile this driver as a module, choose M here: the
+	  To compile this driver as a module, choose M here: the
 	  module will be called jmb38x_ms.
 
 config MEMSTICK_R592
Signature · 1 line
1.9.1
#89 lore raw

PATCH 82/114 drivers: pwm: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/pwm/Kconfig | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/pwm/Kconfig +3 -3
index a8f47df..3a5c20f 100644
@@ -447,7 +447,7 @@ config PWM_TEGRA
 	  To compile this driver as a module, choose M here: the module
 	  will be called pwm-tegra.
 
-config  PWM_TIECAP
+config PWM_TIECAP
 	tristate "ECAP PWM support"
 	depends on ARCH_OMAP2PLUS || ARCH_DAVINCI_DA8XX || ARCH_KEYSTONE || ARCH_K3
 	help
@@ -456,7 +456,7 @@ config  PWM_TIECAP
 	  To compile this driver as a module, choose M here: the module
 	  will be called pwm-tiecap.
 
-config  PWM_TIEHRPWM
+config PWM_TIEHRPWM
 	tristate "EHRPWM PWM support"
 	depends on ARCH_OMAP2PLUS || ARCH_DAVINCI_DA8XX
 	help
@@ -466,7 +466,7 @@ config  PWM_TIEHRPWM
 	  To compile this driver as a module, choose M here: the module
 	  will be called pwm-tiehrpwm.
 
-config  PWM_TIPWMSS
+config PWM_TIPWMSS
 	bool
 	default y if (ARCH_OMAP2PLUS) && (PWM_TIECAP || PWM_TIEHRPWM)
 	help
Signature · 1 line
1.9.1
#90 lore raw

PATCH 83/114 drivers: vme: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/vme/bridges/Kconfig | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)
drivers/vme/bridges/Kconfig +8 -8
index f6ddc37..adbb92d 100644
@@ -4,20 +4,20 @@ config VME_CA91CX42
 	tristate "Universe II"
 	depends on VIRT_TO_BUS
 	help
-	 If you say Y here you get support for the Tundra CA91C142
-	 (Universe II) VME bridge chip.
+	  If you say Y here you get support for the Tundra CA91C142
+	  (Universe II) VME bridge chip.
 
 config VME_TSI148
 	tristate "Tempe"
 	depends on HAS_DMA
 	help
-	 If you say Y here you get support for the Tundra TSI148 VME bridge
-	 chip.
+	  If you say Y here you get support for the Tundra TSI148 VME bridge
+	  chip.
 
 config VME_FAKE
 	tristate "Fake"
 	help
-	 If you say Y here you get support for the fake VME bridge. This
-	 provides a virtualised VME Bus for devices with no VME bridge. This
-	 is mainly useful for VME development (in the absence of VME
-	 hardware).
+	  If you say Y here you get support for the fake VME bridge. This
+	  provides a virtualised VME Bus for devices with no VME bridge. This
+	  is mainly useful for VME development (in the absence of VME
+	  hardware).
Signature · 1 line
1.9.1
#91 lore raw

PATCH 84/114 drivers: acpi: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/acpi/Kconfig | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)
drivers/acpi/Kconfig +12 -12
index 4e015c7..d00f7a6 100644
@@ -13,17 +13,17 @@ menuconfig ACPI
 	select NLS
 	default y if X86
 	help
-	  Advanced Configuration and Power Interface (ACPI) support for 
+	  Advanced Configuration and Power Interface (ACPI) support for
 	  Linux requires an ACPI-compliant platform (hardware/firmware),
 	  and assumes the presence of OS-directed configuration and power
-	  management (OSPM) software.  This option will enlarge your 
+	  management (OSPM) software.  This option will enlarge your
 	  kernel by about 70K.
 
-	  Linux ACPI provides a robust functional replacement for several 
+	  Linux ACPI provides a robust functional replacement for several
 	  legacy configuration and power management interfaces, including
-	  the Plug-and-Play BIOS specification (PnP BIOS), the 
-	  MultiProcessor Specification (MPS), and the Advanced Power 
-	  Management (APM) specification.  If both ACPI and APM support 
+	  the Plug-and-Play BIOS specification (PnP BIOS), the
+	  MultiProcessor Specification (MPS), and the Advanced Power
+	  Management (APM) specification.  If both ACPI and APM support
 	  are configured, ACPI is used.
 
 	  The project home page for the Linux ACPI subsystem is here:
@@ -104,9 +104,9 @@ config ACPI_PROCFS_POWER
 	depends on X86 && PROC_FS
 	help
 	  For backwards compatibility, this option allows
-          deprecated power /proc/acpi/ directories to exist, even when
-          they have been replaced by functions in /sys.
-          The deprecated directories (and their replacements) include:
+	  deprecated power /proc/acpi/ directories to exist, even when
+	  they have been replaced by functions in /sys.
+	  The deprecated directories (and their replacements) include:
 	  /proc/acpi/battery/* (/sys/class/power_supply/*) and
 	  /proc/acpi/ac_adapter/* (sys/class/power_supply/*).
 	  This option has no effect on /proc/acpi/ directories
@@ -173,7 +173,7 @@ config ACPI_BATTERY
 	default y
 	help
 	  This driver adds support for battery information through
-	  /proc/acpi/battery. If you have a mobile system with a battery, 
+	  /proc/acpi/battery. If you have a mobile system with a battery,
 	  say Y.
 
 	  To compile this driver as a module, choose M here:
@@ -456,7 +456,7 @@ config ACPI_CUSTOM_METHOD
 config ACPI_BGRT
 	bool "Boottime Graphics Resource Table support"
 	depends on EFI && (X86 || ARM64)
-        help
+	help
 	  This driver adds support for exposing the ACPI Boottime Graphics
 	  Resource Table, which allows the operating system to obtain
 	  data from the firmware boot splash. It will appear under
@@ -577,7 +577,7 @@ config TPS68470_PMIC_OPREGION
 	  region, which must be available before any of the devices
 	  using this, are probed.
 
-endif	# ACPI
+endif # ACPI
 
 config X86_PM_TIMER
 	bool "Power Management Timer Support" if EXPERT
Signature · 1 line
1.9.1
#92 lore raw

PATCH 85/114 drivers: auxdisplay: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/auxdisplay/Kconfig | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)
drivers/auxdisplay/Kconfig +8 -8
index 57410f9..d08dcc2 100644
@@ -111,7 +111,7 @@ config CFAG12864B
 	  If unsure, say N.
 
 config CFAG12864B_RATE
-       int "Refresh rate (hertz)"
+	int "Refresh rate (hertz)"
 	depends on CFAG12864B
 	default "20"
 	---help---
@@ -331,7 +331,7 @@ config PANEL_LCD_PROTO
 
 config PANEL_LCD_PIN_E
 	depends on PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0"
-        int "Parallel port pin number & polarity connected to the LCD E signal (-17...17) "
+	int "Parallel port pin number & polarity connected to the LCD E signal (-17...17) "
 	range -17 17
 	default 14
 	---help---
@@ -346,7 +346,7 @@ config PANEL_LCD_PIN_E
 
 config PANEL_LCD_PIN_RS
 	depends on PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0"
-        int "Parallel port pin number & polarity connected to the LCD RS signal (-17...17) "
+	int "Parallel port pin number & polarity connected to the LCD RS signal (-17...17) "
 	range -17 17
 	default 17
 	---help---
@@ -361,7 +361,7 @@ config PANEL_LCD_PIN_RS
 
 config PANEL_LCD_PIN_RW
 	depends on PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0"
-        int "Parallel port pin number & polarity connected to the LCD RW signal (-17...17) "
+	int "Parallel port pin number & polarity connected to the LCD RW signal (-17...17) "
 	range -17 17
 	default 16
 	---help---
@@ -376,7 +376,7 @@ config PANEL_LCD_PIN_RW
 
 config PANEL_LCD_PIN_SCL
 	depends on PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO!="0"
-        int "Parallel port pin number & polarity connected to the LCD SCL signal (-17...17) "
+	int "Parallel port pin number & polarity connected to the LCD SCL signal (-17...17) "
 	range -17 17
 	default 1
 	---help---
@@ -391,7 +391,7 @@ config PANEL_LCD_PIN_SCL
 
 config PANEL_LCD_PIN_SDA
 	depends on PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO!="0"
-        int "Parallel port pin number & polarity connected to the LCD SDA signal (-17...17) "
+	int "Parallel port pin number & polarity connected to the LCD SDA signal (-17...17) "
 	range -17 17
 	default 2
 	---help---
@@ -406,12 +406,12 @@ config PANEL_LCD_PIN_SDA
 
 config PANEL_LCD_PIN_BL
 	depends on PANEL_PROFILE="0" && PANEL_LCD="1"
-        int "Parallel port pin number & polarity connected to the LCD backlight signal (-17...17) "
+	int "Parallel port pin number & polarity connected to the LCD backlight signal (-17...17) "
 	range -17 17
 	default 0
 	---help---
 	  This describes the number of the parallel port pin to which the LCD 'BL' signal
-          has been connected. It can be :
+	  has been connected. It can be :
 
 	          0 : no connection (eg: connected to ground)
 	      1..17 : directly connected to any of these pins on the DB25 plug
Signature · 1 line
1.9.1
#93 lore raw

Re: [PATCH 085/114] drivers: auxdisplay: Kconfig: pedantic formatting

Hi Enrico,

Quoted 3 lines · metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

I am all for humor in the right places, but this does not even explain why this is being done nor what is being done. :) Also, "pretty" is not really a good description.

Instead, please simply state that you are replacing spaces with tabs, or whatever you feel it is best, and if possible, what triggered this change (e.g. a reference to some discussion, or at least the motivation).

Quoted 1 line

That Signed-off-by line looks wrong. It should only be your legal name.

Thanks,
Miguel

#94 lore raw

PATCH 86/114 drivers: cpufreq: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/cpufreq/Kconfig | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)
drivers/cpufreq/Kconfig +6 -6
index b22e6bb..b453330 100644
@@ -4,8 +4,8 @@ config CPU_FREQ
 	bool "CPU Frequency scaling"
 	select SRCU
 	help
-	  CPU Frequency scaling allows you to change the clock speed of 
-	  CPUs on the fly. This is a nice method to save power, because 
+	  CPU Frequency scaling allows you to change the clock speed of
+	  CPUs on the fly. This is a nice method to save power, because
 	  the lower the CPU clock speed, the less power the CPU consumes.
 
 	  Note that this driver doesn't automatically change the CPU
@@ -66,7 +66,7 @@ config CPU_FREQ_DEFAULT_GOV_USERSPACE
 	select CPU_FREQ_GOV_USERSPACE
 	help
 	  Use the CPUFreq governor 'userspace' as default. This allows
-	  you to set the CPU frequency manually or when a userspace 
+	  you to set the CPU frequency manually or when a userspace
 	  program shall be able to set the CPU dynamically without having
 	  to enable the userspace governor manually.
 
@@ -133,7 +133,7 @@ config CPU_FREQ_GOV_USERSPACE
 	help
 	  Enable this cpufreq governor when you either want to set the
 	  CPU frequency manually or when a userspace program shall
-	  be able to set the CPU dynamically, like on LART 
+	  be able to set the CPU dynamically, like on LART
 	  <http://www.lartmaker.nl/>.
 
 	  To compile this driver as a module, choose M here: the
@@ -148,11 +148,11 @@ config CPU_FREQ_GOV_ONDEMAND
 	select CPU_FREQ_GOV_COMMON
 	help
 	  'ondemand' - This driver adds a dynamic cpufreq policy governor.
-	  The governor does a periodic polling and 
+	  The governor does a periodic polling and
 	  changes frequency based on the CPU utilization.
 	  The support for this governor depends on CPU capability to
 	  do fast frequency switching (i.e, very low latency frequency
-	  transitions). 
+	  transitions).
 
 	  To compile this driver as a module, choose M here: the
 	  module will be called cpufreq_ondemand.
Signature · 1 line
1.9.1
#95 lore raw

PATCH 87/114 drivers: hwmon: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/hwmon/Kconfig     | 40 ++++++++++++++++++++--------------------
 drivers/hwmon/occ/Kconfig | 20 ++++++++++----------
 2 files changed, 30 insertions(+), 30 deletions(-)
drivers/hwmon/Kconfig +20 -20
index 6f929bf..0ea07fe 100644
@@ -484,10 +484,10 @@ config SENSORS_F75375S
 	  will be called f75375s.
 
 config SENSORS_MC13783_ADC
-        tristate "Freescale MC13783/MC13892 ADC"
-        depends on MFD_MC13XXX
-        help
-          Support for the A/D converter on MC13783 and MC13892 PMIC.
+	tristate "Freescale MC13783/MC13892 ADC"
+	depends on MFD_MC13XXX
+	help
+	  Support for the A/D converter on MC13783 and MC13892 PMIC.
 
 config SENSORS_FSCHMD
 	tristate "Fujitsu Siemens Computers sensor chips"
@@ -1027,18 +1027,18 @@ config SENSORS_LM75
 	  If you say yes here you get support for one common type of
 	  temperature sensor chip, with models including:
 
-		- Analog Devices ADT75
-		- Dallas Semiconductor DS75, DS1775 and DS7505
-		- Global Mixed-mode Technology (GMT) G751
-		- Maxim MAX6625 and MAX6626
-		- Microchip MCP980x
-		- National Semiconductor LM75, LM75A
-		- NXP's LM75A
-		- ST Microelectronics STDS75
-		- ST Microelectronics STLM75
-		- TelCom (now Microchip) TCN75
-		- Texas Instruments TMP100, TMP101, TMP105, TMP112, TMP75,
-		  TMP175, TMP275
+	        - Analog Devices ADT75
+	        - Dallas Semiconductor DS75, DS1775 and DS7505
+	        - Global Mixed-mode Technology (GMT) G751
+	        - Maxim MAX6625 and MAX6626
+	        - Microchip MCP980x
+	        - National Semiconductor LM75, LM75A
+	        - NXP's LM75A
+	        - ST Microelectronics STDS75
+	        - ST Microelectronics STLM75
+	        - TelCom (now Microchip) TCN75
+	        - Texas Instruments TMP100, TMP101, TMP105, TMP112, TMP75,
+	          TMP175, TMP275
 
 	  This driver supports driver model based binding through board
 	  specific I2C device tables.
@@ -1275,10 +1275,10 @@ config SENSORS_NPCM7XX
 	imply THERMAL
 	help
 	  This driver provides support for Nuvoton NPCM750/730/715/705 PWM
-          and Fan controllers.
+	  and Fan controllers.
 
-          This driver can also be built as a module. If so, the module
-          will be called npcm750-pwm-fan.
+	  This driver can also be built as a module. If so, the module
+	  will be called npcm750-pwm-fan.
 
 config SENSORS_NSA320
 	tristate "ZyXEL NSA320 and compatible fan speed and temperature sensors"
@@ -1591,7 +1591,7 @@ config SENSORS_ADS7871
 
 config SENSORS_AMC6821
 	tristate "Texas Instruments AMC6821"
-	depends on I2C 
+	depends on I2C
 	help
 	  If you say yes here you get support for the Texas Instruments
 	  AMC6821 hardware monitoring chips.
drivers/hwmon/occ/Kconfig +10 -10
index 6668662..82f32c0 100644
@@ -7,24 +7,24 @@ config SENSORS_OCC_P8_I2C
 	depends on I2C
 	select SENSORS_OCC
 	help
-	 This option enables support for monitoring sensors provided by the
-	 On-Chip Controller (OCC) on a POWER8 processor. Communications with
-	 the OCC are established through I2C bus.
+	  This option enables support for monitoring sensors provided by the
+	  On-Chip Controller (OCC) on a POWER8 processor. Communications with
+	  the OCC are established through I2C bus.
 
-	 This driver can also be built as a module. If so, the module will be
-	 called occ-p8-hwmon.
+	  This driver can also be built as a module. If so, the module will be
+	  called occ-p8-hwmon.
 
 config SENSORS_OCC_P9_SBE
 	tristate "POWER9 OCC through SBE"
 	depends on FSI_OCC
 	select SENSORS_OCC
 	help
-	 This option enables support for monitoring sensors provided by the
-	 On-Chip Controller (OCC) on a POWER9 processor. Communications with
-	 the OCC are established through SBE fifo on an FSI bus.
+	  This option enables support for monitoring sensors provided by the
+	  On-Chip Controller (OCC) on a POWER9 processor. Communications with
+	  the OCC are established through SBE fifo on an FSI bus.
 
-	 This driver can also be built as a module. If so, the module will be
-	 called occ-p9-hwmon.
+	  This driver can also be built as a module. If so, the module will be
+	  called occ-p9-hwmon.
 
 config SENSORS_OCC
 	bool "POWER On-Chip Controller"
Signature · 1 line
1.9.1
#96 lore raw

PATCH 88/114 drivers: irqchip: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/irqchip/Kconfig | 52 ++++++++++++++++++++++++-------------------------
 1 file changed, 26 insertions(+), 26 deletions(-)
drivers/irqchip/Kconfig +26 -26
index 5438abb..134c7c8 100644
@@ -251,9 +251,9 @@ config VERSATILE_FPGA_IRQ
 	select IRQ_DOMAIN
 
 config VERSATILE_FPGA_IRQ_NR
-       int
-       default 4
-       depends on VERSATILE_FPGA_IRQ
+	int
+	default 4
+	depends on VERSATILE_FPGA_IRQ
 
 config XTENSA_MX
 	bool
@@ -276,8 +276,8 @@ config KEYSTONE_IRQ
 	tristate "Keystone 2 IRQ controller IP"
 	depends on ARCH_KEYSTONE
 	help
-		Support for Texas Instruments Keystone 2 IRQ controller IP which
-		is part of the Keystone 2 IPC mechanism
+	  Support for Texas Instruments Keystone 2 IRQ controller IP which
+	  is part of the Keystone 2 IPC mechanism
 
 config MIPS_GIC
 	bool
@@ -291,11 +291,11 @@ config INGENIC_IRQ
 	default y
 
 config RENESAS_H8300H_INTC
-        bool
+	bool
 	select IRQ_DOMAIN
 
 config RENESAS_H8S_INTC
-        bool
+	bool
 	select IRQ_DOMAIN
 
 config IMX_GPCV2
@@ -328,7 +328,7 @@ config MVEBU_PIC
 	bool
 
 config MVEBU_SEI
-        bool
+	bool
 
 config LS_SCFG_MSI
 	def_bool y if SOC_LS1021A || ARCH_LAYERSCAPE
@@ -367,20 +367,20 @@ config IRQ_UNIPHIER_AIDET
 	  Support for the UniPhier AIDET (ARM Interrupt Detector).
 
 config MESON_IRQ_GPIO
-       bool "Meson GPIO Interrupt Multiplexer"
-       depends on ARCH_MESON
-       select IRQ_DOMAIN
-       select IRQ_DOMAIN_HIERARCHY
-       help
-         Support Meson SoC Family GPIO Interrupt Multiplexer
+	bool "Meson GPIO Interrupt Multiplexer"
+	depends on ARCH_MESON
+	select IRQ_DOMAIN
+	select IRQ_DOMAIN_HIERARCHY
+	help
+	  Support Meson SoC Family GPIO Interrupt Multiplexer
 
 config GOLDFISH_PIC
-       bool "Goldfish programmable interrupt controller"
-       depends on MIPS && (GOLDFISH || COMPILE_TEST)
-       select IRQ_DOMAIN
-       help
-         Say yes here to enable Goldfish interrupt controller driver used
-         for Goldfish based virtual platforms.
+	bool "Goldfish programmable interrupt controller"
+	depends on MIPS && (GOLDFISH || COMPILE_TEST)
+	select IRQ_DOMAIN
+	help
+	  Say yes here to enable Goldfish interrupt controller driver used
+	  for Goldfish based virtual platforms.
 
 config QCOM_PDC
 	bool "QCOM PDC"
@@ -431,10 +431,10 @@ config SIFIVE_PLIC
 	bool "SiFive Platform-Level Interrupt Controller"
 	depends on RISCV
 	help
-	   This enables support for the PLIC chip found in SiFive (and
-	   potentially other) RISC-V systems.  The PLIC controls devices
-	   interrupts and connects them to each core's local interrupt
-	   controller.  Aside from timer and software interrupts, all other
-	   interrupt sources are subordinate to the PLIC.
+	  This enables support for the PLIC chip found in SiFive (and
+	  potentially other) RISC-V systems.  The PLIC controls devices
+	  interrupts and connects them to each core's local interrupt
+	  controller.  Aside from timer and software interrupts, all other
+	  interrupt sources are subordinate to the PLIC.
 
-	   If you don't know what to do here, say Y.
+	  If you don't know what to do here, say Y.
Signature · 1 line
1.9.1
#97 lore raw

PATCH 89/114 drivers: virtio: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/virtio/Kconfig | 44 ++++++++++++++++++++++----------------------
 1 file changed, 22 insertions(+), 22 deletions(-)
drivers/virtio/Kconfig +22 -22
index 3589764..390f6e0 100644
@@ -28,17 +28,17 @@ config VIRTIO_PCI_LEGACY
 	default y
 	depends on VIRTIO_PCI
 	---help---
-          Virtio PCI Card 0.9.X Draft (circa 2014) and older device support.
+	  Virtio PCI Card 0.9.X Draft (circa 2014) and older device support.
 
 	  This option enables building a transitional driver, supporting
 	  both devices conforming to Virtio 1 specification, and legacy devices.
 	  If disabled, you get a slightly smaller, non-transitional driver,
 	  with no legacy compatibility.
 
-          So look out into your driveway.  Do you have a flying car?  If
-          so, you can happily disable this option and virtio will not
-          break.  Otherwise, leave it set.  Unless you're testing what
-          life will be like in The Future.
+	  So look out into your driveway.  Do you have a flying car?  If
+	  so, you can happily disable this option and virtio will not
+	  break.  Otherwise, leave it set.  Unless you're testing what
+	  life will be like in The Future.
 
 	  If unsure, say Y.
 
@@ -47,40 +47,40 @@ config VIRTIO_BALLOON
 	depends on VIRTIO
 	select MEMORY_BALLOON
 	---help---
-	 This driver supports increasing and decreasing the amount
-	 of memory within a KVM guest.
+	  This driver supports increasing and decreasing the amount
+	  of memory within a KVM guest.
 
-	 If unsure, say M.
+	  If unsure, say M.
 
 config VIRTIO_INPUT
 	tristate "Virtio input driver"
 	depends on VIRTIO
 	depends on INPUT
 	---help---
-	 This driver supports virtio input devices such as
-	 keyboards, mice and tablets.
+	  This driver supports virtio input devices such as
+	  keyboards, mice and tablets.
 
-	 If unsure, say M.
+	  If unsure, say M.
 
- config VIRTIO_MMIO
+config VIRTIO_MMIO
 	tristate "Platform bus driver for memory mapped virtio devices"
 	depends on HAS_IOMEM && HAS_DMA
- 	select VIRTIO
- 	---help---
- 	 This drivers provides support for memory mapped virtio
-	 platform device driver.
+	select VIRTIO
+	---help---
+	  This drivers provides support for memory mapped virtio
+	  platform device driver.
 
- 	 If unsure, say N.
+	  If unsure, say N.
 
 config VIRTIO_MMIO_CMDLINE_DEVICES
 	bool "Memory mapped virtio devices parameter parsing"
 	depends on VIRTIO_MMIO
 	---help---
-	 Allow virtio-mmio devices instantiation via the kernel command line
-	 or module parameters. Be aware that using incorrect parameters (base
-	 address in particular) can crash your system - you have been warned.
-	 See Documentation/admin-guide/kernel-parameters.rst for details.
+	  Allow virtio-mmio devices instantiation via the kernel command line
+	  or module parameters. Be aware that using incorrect parameters (base
+	  address in particular) can crash your system - you have been warned.
+	  See Documentation/admin-guide/kernel-parameters.rst for details.
 
-	 If unsure, say 'N'.
+	  If unsure, say 'N'.
 
 endif # VIRTIO_MENU
Signature · 1 line
1.9.1
#98 lore raw

PATCH 90/114 certs: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 certs/Kconfig | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)
certs/Kconfig +7 -7
index c94e93d..e8a5fd4 100644
@@ -6,14 +6,14 @@ config MODULE_SIG_KEY
 	default "certs/signing_key.pem"
 	depends on MODULE_SIG
 	help
-         Provide the file name of a private key/certificate in PEM format,
-         or a PKCS#11 URI according to RFC7512. The file should contain, or
-         the URI should identify, both the certificate and its corresponding
-         private key.
+	  Provide the file name of a private key/certificate in PEM format,
+	  or a PKCS#11 URI according to RFC7512. The file should contain, or
+	  the URI should identify, both the certificate and its corresponding
+	  private key.
 
-         If this option is unchanged from its default "certs/signing_key.pem",
-         then the kernel will automatically generate the private key and
-         certificate as described in Documentation/admin-guide/module-signing.rst
+	  If this option is unchanged from its default "certs/signing_key.pem",
+	  then the kernel will automatically generate the private key and
+	  certificate as described in Documentation/admin-guide/module-signing.rst
 
 config SYSTEM_TRUSTED_KEYRING
 	bool "Provide system-wide ring of trusted keys"
Signature · 1 line
1.9.1
#99 lore raw

PATCH 91/114 block: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 block/Kconfig | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)
block/Kconfig +15 -15
index 028bc08..eb7e1bf 100644
@@ -3,26 +3,26 @@
 # Block layer core configuration
 #
 menuconfig BLOCK
-       bool "Enable the block layer" if EXPERT
-       default y
-       select SBITMAP
-       select SRCU
-       help
-	 Provide block layer support for the kernel.
+	bool "Enable the block layer" if EXPERT
+	default y
+	select SBITMAP
+	select SRCU
+	help
+	  Provide block layer support for the kernel.
 
-	 Disable this option to remove the block layer support from the
-	 kernel. This may be useful for embedded devices.
+	  Disable this option to remove the block layer support from the
+	  kernel. This may be useful for embedded devices.
 
-	 If this option is disabled:
+	  If this option is disabled:
 
 	   - block device files will become unusable
 	   - some filesystems (such as ext3) will become unavailable.
 
-	 Also, SCSI character devices and USB storage will be disabled since
-	 they make use of various block layer definitions and facilities.
+	  Also, SCSI character devices and USB storage will be disabled since
+	  they make use of various block layer definitions and facilities.
 
-	 Say Y here unless you know you really don't want to mount disks and
-	 suchlike.
+	  Say Y here unless you know you really don't want to mount disks and
+	  suchlike.
 
 if BLOCK
 
@@ -177,8 +177,8 @@ config BLK_DEBUG_FS
 	say Y here.
 
 config BLK_DEBUG_FS_ZONED
-       bool
-       default BLK_DEBUG_FS && BLK_DEV_ZONED
+	bool
+	default BLK_DEBUG_FS && BLK_DEV_ZONED
 
 config BLK_SED_OPAL
 	bool "Logic for interfacing with Opal enabled SEDs"
Signature · 1 line
1.9.1
#100 lore raw

PATCH 92/114 drivers: dma: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/dma/Kconfig | 40 ++++++++++++++++++++--------------------
 1 file changed, 20 insertions(+), 20 deletions(-)
drivers/dma/Kconfig +20 -20
index d2286c7..305cf36 100644
@@ -14,19 +14,19 @@ menuconfig DMADEVICES
 	  be empty in some cases.
 
 config DMADEVICES_DEBUG
-        bool "DMA Engine debugging"
-        depends on DMADEVICES != n
-        help
-          This is an option for use by developers; most people should
-          say N here.  This enables DMA engine core and driver debugging.
+	bool "DMA Engine debugging"
+	depends on DMADEVICES != n
+	help
+	  This is an option for use by developers; most people should
+	  say N here.  This enables DMA engine core and driver debugging.
 
 config DMADEVICES_VDEBUG
-        bool "DMA Engine verbose debugging"
-        depends on DMADEVICES_DEBUG != n
-        help
-          This is an option for use by developers; most people should
-          say N here.  This enables deeper (more verbose) debugging of
-          the DMA engine core and drivers.
+	bool "DMA Engine verbose debugging"
+	depends on DMADEVICES_DEBUG != n
+	help
+	  This is an option for use by developers; most people should
+	  say N here.  This enables deeper (more verbose) debugging of
+	  the DMA engine core and drivers.
 
 
 if DMADEVICES
@@ -219,14 +219,14 @@ config FSL_EDMA
 	  This module can be found on Freescale Vybrid and LS-1 SoCs.
 
 config FSL_RAID
-        tristate "Freescale RAID engine Support"
-        depends on FSL_SOC && !ASYNC_TX_ENABLE_CHANNEL_SWITCH
-        select DMA_ENGINE
-        select DMA_ENGINE_RAID
-        ---help---
-          Enable support for Freescale RAID Engine. RAID Engine is
-          available on some QorIQ SoCs (like P5020/P5040). It has
-          the capability to offload memcpy, xor and pq computation
+	tristate "Freescale RAID engine Support"
+	depends on FSL_SOC && !ASYNC_TX_ENABLE_CHANNEL_SWITCH
+	select DMA_ENGINE
+	select DMA_ENGINE_RAID
+	---help---
+	  Enable support for Freescale RAID Engine. RAID Engine is
+	  available on some QorIQ SoCs (like P5020/P5040). It has
+	  the capability to offload memcpy, xor and pq computation
 	  for raid5/6.
 
 config IMG_MDC_DMA
@@ -357,7 +357,7 @@ config MOXART_DMA
 	select DMA_VIRTUAL_CHANNELS
 	help
 	  Enable support for the MOXA ART SoC DMA controller.
- 
+
 	  Say Y here if you enabled MMP ADMA, otherwise say N.
 
 config MPC512X_DMA
Signature · 1 line
1.9.1
#101 lore raw

PATCH 93/114 arch: h8300: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 arch/h8300/Kconfig | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
arch/h8300/Kconfig +2 -2
index c071da3..eb6854d 100644
@@ -1,6 +1,6 @@
 # SPDX-License-Identifier: GPL-2.0
 config H8300
-        def_bool y
+	def_bool y
 	select ARCH_32BIT_OFF_T
 	select GENERIC_ATOMIC64
 	select HAVE_UID16
@@ -37,7 +37,7 @@ config NO_IOPORT_MAP
 	def_bool y
 
 config GENERIC_CSUM
-        def_bool y
+	def_bool y
 
 config HZ
 	int
Signature · 1 line
1.9.1
#102 lore raw

PATCH 94/114 arch: nds32: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 arch/nds32/Kconfig | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)
arch/nds32/Kconfig +8 -8
index addb7f5..c0b13bf 100644
@@ -4,7 +4,7 @@
 #
 
 config NDS32
-        def_bool y
+	def_bool y
 	select ARCH_32BIT_OFF_T
 	select ARCH_HAS_SYNC_DMA_FOR_CPU
 	select ARCH_HAS_SYNC_DMA_FOR_DEVICE
@@ -51,13 +51,13 @@ config GENERIC_CALIBRATE_DELAY
 	def_bool y
 
 config GENERIC_CSUM
-        def_bool y
+	def_bool y
 
 config GENERIC_HWEIGHT
-        def_bool y
+	def_bool y
 
 config GENERIC_LOCKBREAK
-        def_bool y
+	def_bool y
 	depends on PREEMPT
 
 config RWSEM_GENERIC_SPINLOCK
@@ -67,7 +67,7 @@ config TRACE_IRQFLAGS_SUPPORT
 	def_bool y
 
 config STACKTRACE_SUPPORT
-        def_bool y
+	def_bool y
 
 config FIX_EARLYCON_MEM
 	def_bool y
@@ -82,11 +82,11 @@ config NR_CPUS
 	default 1
 
 config MMU
-        def_bool y
+	def_bool y
 
 config NDS32_BUILTIN_DTB
-        string "Builtin DTB"
-        default ""
+	string "Builtin DTB"
+	default ""
 	help
 	  User can use it to specify the dts of the SoC
 endmenu
Signature · 1 line
1.9.1
#103 lore raw

PATCH 95/114 arch: ia64: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 arch/ia64/Kconfig | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)
arch/ia64/Kconfig +6 -6
index 8d7396b..ab43a52 100644
@@ -353,7 +353,7 @@ config PERMIT_BSP_REMOVE
 	default n
 	---help---
 	Say Y here if your platform SAL will support removal of BSP with HOTPLUG_CPU
-	support. 
+	support.
 
 config FORCE_CPEI_RETARGET
 	bool "Force assumption that CPEI can be re-targeted"
@@ -470,7 +470,7 @@ config IA64_PALINFO
 config IA64_MC_ERR_INJECT
 	tristate "MC error injection support"
 	help
-	  Adds support for MC error injection. If enabled, the kernel 
+	  Adds support for MC error injection. If enabled, the kernel
 	  will provide a sysfs interface for user applications to
 	  call MC error injection PAL procedures to inject various errors.
 	  This is a useful tool for MCA testing.
@@ -519,10 +519,10 @@ config KEXEC
 	  made.
 
 config CRASH_DUMP
-	  bool "kernel crash dumps"
-	  depends on IA64_MCA_RECOVERY && !IA64_HP_SIM && (!SMP || HOTPLUG_CPU)
-	  help
-	    Generate crash dump after being started by kexec.
+	bool "kernel crash dumps"
+	depends on IA64_MCA_RECOVERY && !IA64_HP_SIM && (!SMP || HOTPLUG_CPU)
+	help
+	  Generate crash dump after being started by kexec.
 
 source "drivers/firmware/Kconfig"
 
Signature · 1 line
1.9.1
#104 lore raw

PATCH 96/114 arch: openrisc: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 arch/openrisc/Kconfig | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)
arch/openrisc/Kconfig +13 -13
index a5e361f..4722291 100644
@@ -13,7 +13,7 @@ config OPENRISC
 	select IRQ_DOMAIN
 	select HANDLE_DOMAIN_IRQ
 	select GPIOLIB
-        select HAVE_ARCH_TRACEHOOK
+	select HAVE_ARCH_TRACEHOOK
 	select SPARSE_IRQ
 	select GENERIC_IRQ_CHIP
 	select GENERIC_IRQ_PROBE
@@ -56,12 +56,12 @@ config NO_IOPORT_MAP
 	def_bool y
 
 config TRACE_IRQFLAGS_SUPPORT
-        def_bool y
+	def_bool y
 
 # For now, use generic checksum functions
 #These can be reimplemented in assembly later if so inclined
 config GENERIC_CSUM
-        def_bool y
+	def_bool y
 
 config STACKTRACE_SUPPORT
 	def_bool y
@@ -94,8 +94,8 @@ config DCACHE_WRITETHROUGH
 	  If unsure say N here
 
 config OPENRISC_BUILTIN_DTB
-        string "Builtin DTB"
-        default ""
+	string "Builtin DTB"
+	default ""
 
 menu "Class II Instructions"
 
@@ -166,13 +166,13 @@ config OPENRISC_HAVE_SHADOW_GPRS
 	  On a unicore system it's safe to say N here if you are unsure.
 
 config CMDLINE
-        string "Default kernel command string"
-        default ""
-        help
-          On some architectures there is currently no way for the boot loader
-          to pass arguments to the kernel. For these architectures, you should
-          supply some command-line options at build time by entering them
-          here.
+	string "Default kernel command string"
+	default ""
+	help
+	  On some architectures there is currently no way for the boot loader
+	  to pass arguments to the kernel. For these architectures, you should
+	  supply some command-line options at build time by entering them
+	  here.
 
 menu "Debugging options"
 
@@ -190,7 +190,7 @@ config OPENRISC_ESR_EXCEPTION_BUG_CHECK
 	default n
 	help
 	  This option enables some checks that might expose some problems
-          in kernel.
+	  in kernel.
 
 	  Say N if you are unsure.
 
Signature · 1 line
1.9.1
#105 lore raw

PATCH 97/114 arch: riscv: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 arch/riscv/Kconfig | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
arch/riscv/Kconfig +4 -4
index eb56c82..5dc6a2b 100644
@@ -191,11 +191,11 @@ config RISCV_ISA_C
 	bool "Emit compressed instructions when building Linux"
 	default y
 	help
-	   Adds "C" to the ISA subsets that the toolchain is allowed to emit
-	   when building Linux, which results in compressed instructions in the
-	   Linux binary.
+	  Adds "C" to the ISA subsets that the toolchain is allowed to emit
+	  when building Linux, which results in compressed instructions in the
+	  Linux binary.
 
-	   If you don't know what to do here, say Y.
+	  If you don't know what to do here, say Y.
 
 config RISCV_ISA_A
 	def_bool y
Signature · 1 line
1.9.1
#106 lore raw

PATCH 98/114 crypto: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 crypto/Kconfig | 23 +++++++++++------------
 1 file changed, 11 insertions(+), 12 deletions(-)
crypto/Kconfig +11 -12
index bbab6bf..3395b1a 100644
@@ -210,7 +210,7 @@ config CRYPTO_PCRYPT
 	  algorithm that executes in kernel threads.
 
 config CRYPTO_WORKQUEUE
-       tristate
+	tristate
 
 config CRYPTO_CRYPTD
 	tristate "Software async crypto daemon"
@@ -290,21 +290,21 @@ config CRYPTO_AEGIS128
 	select CRYPTO_AEAD
 	select CRYPTO_AES  # for AES S-box tables
 	help
-	 Support for the AEGIS-128 dedicated AEAD algorithm.
+	  Support for the AEGIS-128 dedicated AEAD algorithm.
 
 config CRYPTO_AEGIS128L
 	tristate "AEGIS-128L AEAD algorithm"
 	select CRYPTO_AEAD
 	select CRYPTO_AES  # for AES S-box tables
 	help
-	 Support for the AEGIS-128L dedicated AEAD algorithm.
+	  Support for the AEGIS-128L dedicated AEAD algorithm.
 
 config CRYPTO_AEGIS256
 	tristate "AEGIS-256 AEAD algorithm"
 	select CRYPTO_AEAD
 	select CRYPTO_AES  # for AES S-box tables
 	help
-	 Support for the AEGIS-256 dedicated AEAD algorithm.
+	  Support for the AEGIS-256 dedicated AEAD algorithm.
 
 config CRYPTO_AEGIS128_AESNI_SSE2
 	tristate "AEGIS-128 AEAD algorithm (x86_64 AESNI+SSE2 implementation)"
@@ -312,7 +312,7 @@ config CRYPTO_AEGIS128_AESNI_SSE2
 	select CRYPTO_AEAD
 	select CRYPTO_CRYPTD
 	help
-	 AESNI+SSE2 implementation of the AEGSI-128 dedicated AEAD algorithm.
+	  AESNI+SSE2 implementation of the AEGSI-128 dedicated AEAD algorithm.
 
 config CRYPTO_AEGIS128L_AESNI_SSE2
 	tristate "AEGIS-128L AEAD algorithm (x86_64 AESNI+SSE2 implementation)"
@@ -320,7 +320,7 @@ config CRYPTO_AEGIS128L_AESNI_SSE2
 	select CRYPTO_AEAD
 	select CRYPTO_CRYPTD
 	help
-	 AESNI+SSE2 implementation of the AEGSI-128L dedicated AEAD algorithm.
+	  AESNI+SSE2 implementation of the AEGSI-128L dedicated AEAD algorithm.
 
 config CRYPTO_AEGIS256_AESNI_SSE2
 	tristate "AEGIS-256 AEAD algorithm (x86_64 AESNI+SSE2 implementation)"
@@ -328,7 +328,7 @@ config CRYPTO_AEGIS256_AESNI_SSE2
 	select CRYPTO_AEAD
 	select CRYPTO_CRYPTD
 	help
-	 AESNI+SSE2 implementation of the AEGSI-256 dedicated AEAD algorithm.
+	  AESNI+SSE2 implementation of the AEGSI-256 dedicated AEAD algorithm.
 
 config CRYPTO_MORUS640
 	tristate "MORUS-640 AEAD algorithm"
@@ -577,9 +577,8 @@ config CRYPTO_XCBC
 	select CRYPTO_MANAGER
 	help
 	  XCBC: Keyed-Hashing with encryption algorithm
-		http://www.ietf.org/rfc/rfc3566.txt
-		http://csrc.nist.gov/encryption/modes/proposedmodes/
-		 xcbc-mac/xcbc-mac-spec.pdf
+	        <http://www.ietf.org/rfc/rfc3566.txt>
+	        <http://csrc.nist.gov/encryption/modes/proposedmodes/xcbc-mac/xcbc-mac-spec.pdf>
 
 config CRYPTO_VMAC
 	tristate "VMAC support"
@@ -1830,7 +1829,7 @@ config CRYPTO_DRBG
 	select CRYPTO_RNG
 	select CRYPTO_JITTERENTROPY
 
-endif	# if CRYPTO_DRBG_MENU
+endif # if CRYPTO_DRBG_MENU
 
 config CRYPTO_JITTERENTROPY
 	tristate "Jitterentropy Non-Deterministic Random Number Generator"
@@ -1902,4 +1901,4 @@ source "drivers/crypto/Kconfig"
 source "crypto/asymmetric_keys/Kconfig"
 source "certs/Kconfig"
 
-endif	# if CRYPTO
+endif # if CRYPTO
Signature · 1 line
1.9.1
#107 lore raw

PATCH 99/114 drivers: block: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/block/Kconfig          | 32 ++++++++++++++++----------------
 drivers/block/mtip32xx/Kconfig |  2 +-
 drivers/block/zram/Kconfig     | 20 ++++++++++----------
 3 files changed, 27 insertions(+), 27 deletions(-)
drivers/block/Kconfig +16 -16
index 20bb4bf..07964cc 100644
@@ -142,10 +142,10 @@ config BLK_DEV_UBD
 	bool "Virtual block device"
 	depends on UML
 	---help---
-          The User-Mode Linux port includes a driver called UBD which will let
-          you access arbitrary files on the host computer as block devices.
-          Unless you know that you do not need such virtual block devices say
-          Y here.
+	  The User-Mode Linux port includes a driver called UBD which will let
+	  you access arbitrary files on the host computer as block devices.
+	  Unless you know that you do not need such virtual block devices say
+	  Y here.
 
 config BLK_DEV_UBD_SYNC
 	bool "Always do synchronous disk IO for UBD"
@@ -156,16 +156,16 @@ config BLK_DEV_UBD_SYNC
 	  Linux 'Virtual Machine' uses a journalling filesystem and the host
 	  computer crashes.
 
-          Synchronous operation (i.e. always writing data to the host's disk
-          immediately) is configurable on a per-UBD basis by using a special
-          kernel command line option.  Alternatively, you can say Y here to
-          turn on synchronous operation by default for all block devices.
+	  Synchronous operation (i.e. always writing data to the host's disk
+	  immediately) is configurable on a per-UBD basis by using a special
+	  kernel command line option.  Alternatively, you can say Y here to
+	  turn on synchronous operation by default for all block devices.
 
-          If you're running a journalling file system (like reiserfs, for
-          example) in your virtual machine, you will want to say Y here.  If
-          you care for the safety of the data in your virtual machine, Y is a
-          wise choice too.  In all other cases (for example, if you're just
-          playing around with User-Mode Linux) you can choose N.
+	  If you're running a journalling file system (like reiserfs, for
+	  example) in your virtual machine, you will want to say Y here.  If
+	  you care for the safety of the data in your virtual machine, Y is a
+	  wise choice too.  In all other cases (for example, if you're just
+	  playing around with User-Mode Linux) you can choose N.
 
 config BLK_DEV_COW_COMMON
 	bool
@@ -235,7 +235,7 @@ config BLK_DEV_CRYPTOLOOP
 	select CRYPTO_CBC
 	depends on BLK_DEV_LOOP
 	---help---
-	  Say Y here if you want to be able to use the ciphers that are 
+	  Say Y here if you want to be able to use the ciphers that are
 	  provided by the CryptoAPI as loop transformation. This might be
 	  used as hard disk encryption.
 
@@ -287,7 +287,7 @@ config BLK_DEV_SX8
 	tristate "Promise SATA SX8 support"
 	depends on PCI
 	---help---
-	  Saying Y or M here will enable support for the 
+	  Saying Y or M here will enable support for the
 	  Promise SATA SX8 controllers.
 
 	  Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
@@ -430,7 +430,7 @@ config VIRTIO_BLK
 	depends on VIRTIO
 	---help---
 	  This is the virtual block driver for virtio.  It can be used with
-          QEMU based VMMs (like KVM or Xen).  Say Y or M.
+	  QEMU based VMMs (like KVM or Xen).  Say Y or M.
 
 config VIRTIO_BLK_SCSI
 	bool "SCSI passthrough request for the Virtio block driver"
drivers/block/mtip32xx/Kconfig +1 -1
index bf22135..a469dc7 100644
@@ -7,4 +7,4 @@ config BLK_DEV_PCIESSD_MTIP32XX
 	tristate "Block Device Driver for Micron PCIe SSDs"
 	depends on PCI
 	help
-          This enables the block driver for Micron PCIe SSDs.
+	  This enables the block driver for Micron PCIe SSDs.
drivers/block/zram/Kconfig +10 -10
index 1ffc647..b39b402 100644
@@ -15,18 +15,18 @@ config ZRAM
 	  See Documentation/blockdev/zram.txt for more information.
 
 config ZRAM_WRITEBACK
-       bool "Write back incompressible or idle page to backing device"
-       depends on ZRAM
-       help
-	 With incompressible page, there is no memory saving to keep it
-	 in memory. Instead, write it out to backing device.
-	 For this feature, admin should set up backing device via
-	 /sys/block/zramX/backing_dev.
+	bool "Write back incompressible or idle page to backing device"
+	depends on ZRAM
+	help
+	  With incompressible page, there is no memory saving to keep it
+	  in memory. Instead, write it out to backing device.
+	  For this feature, admin should set up backing device via
+	  /sys/block/zramX/backing_dev.
 
-	 With /sys/block/zramX/{idle,writeback}, application could ask
-	 idle page's writeback to the backing device to save in memory.
+	  With /sys/block/zramX/{idle,writeback}, application could ask
+	  idle page's writeback to the backing device to save in memory.
 
-	 See Documentation/blockdev/zram.txt for more information.
+	  See Documentation/blockdev/zram.txt for more information.
 
 config ZRAM_MEMORY_TRACKING
 	bool "Track zRam block status"
Signature · 1 line
1.9.1
#108 lore raw

PATCH 100/114 arch: sparc: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 arch/sparc/Kconfig | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)
arch/sparc/Kconfig +11 -11
index 40f8f4f..574fd92 100644
@@ -430,28 +430,28 @@ config UBOOT_LOAD_ADDR
 	hex "uImage Load Address"
 	default 0x40004000
 	---help---
-	 U-Boot kernel load address, the address in physical address space
-	 where u-boot will place the Linux kernel before booting it.
-	 This address is normally the base address of main memory + 0x4000.
+	  U-Boot kernel load address, the address in physical address space
+	  where u-boot will place the Linux kernel before booting it.
+	  This address is normally the base address of main memory + 0x4000.
 
 config UBOOT_FLASH_ADDR
 	hex "uImage.o Load Address"
 	default 0x00080000
 	---help---
-	 Optional setting only affecting the uImage.o ELF-image used to
-	 download the uImage file to the target using a ELF-loader other than
-	 U-Boot. It may for example be used to download an uImage to FLASH with
-	 the GRMON utility before even starting u-boot.
+	  Optional setting only affecting the uImage.o ELF-image used to
+	  download the uImage file to the target using a ELF-loader other than
+	  U-Boot. It may for example be used to download an uImage to FLASH with
+	  the GRMON utility before even starting u-boot.
 
 config UBOOT_ENTRY_ADDR
 	hex "uImage Entry Address"
 	default 0xf0004000
 	---help---
-	 Do not change this unless you know what you're doing. This is
-	 hardcoded by the SPARC32 and LEON port.
+	  Do not change this unless you know what you're doing. This is
+	  hardcoded by the SPARC32 and LEON port.
 
-	 This is the virtual address u-boot jumps to when booting the Linux
-	 Kernel.
+	  This is the virtual address u-boot jumps to when booting the Linux
+	  Kernel.
 
 endmenu
 endif
Signature · 1 line
1.9.1
#109 lore raw

PATCH 101/114 drivers: atm: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/atm/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/atm/Kconfig +1 -1
index 2e2efa5..a156e06d 100644
@@ -302,7 +302,7 @@ config ATM_IA
 	  control memory (128K-1KVC, 512K-4KVC), the size of the packet
 	  memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
 	  UTP155, UTP25, DS3 and E3). Go to:
-	  	<http://www.iphase.com/>
+	        <http://www.iphase.com/>
 	  for more info about the cards. Say Y (or M to compile as a module
 	  named iphase) here if you have one of these cards.
 
Signature · 1 line
1.9.1
#110 lore raw

PATCH 102/114 drivers: cpuidle: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/cpuidle/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/cpuidle/Kconfig +1 -1
index 8caccbb..b1e3635 100644
@@ -15,7 +15,7 @@ config CPU_IDLE
 if CPU_IDLE
 
 config CPU_IDLE_MULTIPLE_DRIVERS
-        bool
+	bool
 
 config CPU_IDLE_GOV_LADDER
 	bool "Ladder governor (for periodic timer tick)"
Signature · 1 line
1.9.1
#111 lore raw

PATCH 103/114 drivers: iommu: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/iommu/Kconfig | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/iommu/Kconfig +3 -3
index 6f07f3b..1103239 100644
@@ -77,7 +77,7 @@ config IOMMU_DEBUGFS
 config IOMMU_DEFAULT_PASSTHROUGH
 	bool "IOMMU passthrough by default"
 	depends on IOMMU_API
-        help
+	help
 	  Enable passthrough by default, removing the need to pass in
 	  iommu.passthrough=on or iommu=pt through command line. If this
 	  is enabled, you can still disable with iommu.passthrough=off
@@ -86,8 +86,8 @@ config IOMMU_DEFAULT_PASSTHROUGH
 	  If unsure, say N here.
 
 config OF_IOMMU
-       def_bool y
-       depends on OF && IOMMU_API
+	def_bool y
+	depends on OF && IOMMU_API
 
 # IOMMU-agnostic DMA-mapping layer
 config IOMMU_DMA
Signature · 1 line
1.9.1
#112 lore raw

PATCH 104/114 drivers: edac: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/edac/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/edac/Kconfig +1 -1
index 47eb4d1..a299da4 100644
@@ -479,7 +479,7 @@ config EDAC_TI
 	depends on ARCH_KEYSTONE || SOC_DRA7XX
 	help
 	  Support for error detection and correction on the
-          TI SoCs.
+	  TI SoCs.
 
 config EDAC_QCOM
 	tristate "QCOM EDAC Controller"
Signature · 1 line
1.9.1
#113 lore raw

PATCH 105/114 drivers: hid: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/hid/Kconfig | 496 ++++++++++++++++++++++++++--------------------------
 1 file changed, 248 insertions(+), 248 deletions(-)
drivers/hid/Kconfig +248 -248
index 6ca8d32..9521d3d 100644
@@ -2,7 +2,7 @@
 # HID driver configuration
 #
 menu "HID support"
-     depends on INPUT
+	depends on INPUT
 
 config HID
 	tristate "HID bus support"
@@ -31,62 +31,62 @@ config HID_BATTERY_STRENGTH
 	select POWER_SUPPLY
 	default n
 	---help---
-	This option adds support of reporting battery strength (for HID devices
-	that support this feature) through power_supply class so that userspace
-	tools, such as upower, can display it.
+	  This option adds support of reporting battery strength (for HID devices
+	  that support this feature) through power_supply class so that userspace
+	  tools, such as upower, can display it.
 
 config HIDRAW
 	bool "/dev/hidraw raw HID device support"
 	depends on HID
 	---help---
-	Say Y here if you want to support HID devices (from the USB
-	specification standpoint) that aren't strictly user interface
-	devices, like monitor controls and Uninterruptable Power Supplies.
+	  Say Y here if you want to support HID devices (from the USB
+	  specification standpoint) that aren't strictly user interface
+	  devices, like monitor controls and Uninterruptable Power Supplies.
 
-	This module supports these devices separately using a separate
-	event interface on /dev/hidraw.
+	  This module supports these devices separately using a separate
+	  event interface on /dev/hidraw.
 
-	There is also a /dev/hiddev configuration option in the USB HID
-	configuration menu. In comparison to hiddev, this device does not process
-	the hid events at all (no parsing, no lookups). This lets applications
-	to work on raw hid events when they want to, and avoid using transport-specific
-	userspace libhid/libusb libraries.
+	  There is also a /dev/hiddev configuration option in the USB HID
+	  configuration menu. In comparison to hiddev, this device does not process
+	  the hid events at all (no parsing, no lookups). This lets applications
+	  to work on raw hid events when they want to, and avoid using transport-specific
+	  userspace libhid/libusb libraries.
 
-	If unsure, say Y.
+	  If unsure, say Y.
 
 config UHID
 	tristate "User-space I/O driver support for HID subsystem"
 	depends on HID
 	default n
 	---help---
-	Say Y here if you want to provide HID I/O Drivers from user-space.
-	This allows to write I/O drivers in user-space and feed the data from
-	the device into the kernel. The kernel parses the HID reports, loads the
-	corresponding HID Device Driver or provides input devices on top of your
-	user-space device.
+	  Say Y here if you want to provide HID I/O Drivers from user-space.
+	  This allows to write I/O drivers in user-space and feed the data from
+	  the device into the kernel. The kernel parses the HID reports, loads the
+	  corresponding HID Device Driver or provides input devices on top of your
+	  user-space device.
 
-	This driver cannot be used to parse HID-reports in user-space and write
-	special HID-drivers. You should use hidraw for that.
-	Instead, this driver allows to write the transport-layer driver in
-	user-space like USB-HID and Bluetooth-HID do in kernel-space.
+	  This driver cannot be used to parse HID-reports in user-space and write
+	  special HID-drivers. You should use hidraw for that.
+	  Instead, this driver allows to write the transport-layer driver in
+	  user-space like USB-HID and Bluetooth-HID do in kernel-space.
 
-	If unsure, say N.
+	  If unsure, say N.
 
-	To compile this driver as a module, choose M here: the
-	module will be called uhid.
+	  To compile this driver as a module, choose M here: the
+	 module will be called uhid.
 
 config HID_GENERIC
 	tristate "Generic HID driver"
 	depends on HID
 	default HID
 	---help---
-	Support for generic devices on the HID bus. This includes most
-	keyboards and mice, joysticks, tablets and digitizers.
+	  Support for generic devices on the HID bus. This includes most
+	  keyboards and mice, joysticks, tablets and digitizers.
 
-	To compile this driver as a module, choose M here: the module
-	will be called hid-generic.
+	  To compile this driver as a module, choose M here: the module
+	  will be called hid-generic.
 
-	If unsure, say Y.
+	  If unsure, say Y.
 
 menu "Special HID drivers"
 	depends on HID
@@ -96,7 +96,7 @@ config HID_A4TECH
 	depends on HID
 	default !EXPERT
 	---help---
-	Support for A4 tech X5 and WOP-35 / Trust 450L mice.
+	  Support for A4 tech X5 and WOP-35 / Trust 450L mice.
 
 config HID_ACCUTOUCH
 	tristate "Accutouch touch device"
@@ -106,7 +106,7 @@ config HID_ACCUTOUCH
 
 	  The driver works around a problem in the reported device capabilities
 	  which causes userspace to detect the device as a mouse rather than
-          a touchscreen.
+	  a touchscreen.
 
 	  Say Y here if you have a Accutouch 2216 touch controller.
 
@@ -114,74 +114,74 @@ config HID_ACRUX
 	tristate "ACRUX game controller support"
 	depends on HID
 	---help---
-	Say Y here if you want to enable support for ACRUX game controllers.
+	  Say Y here if you want to enable support for ACRUX game controllers.
 
 config HID_ACRUX_FF
 	bool "ACRUX force feedback support"
 	depends on HID_ACRUX
 	select INPUT_FF_MEMLESS
 	---help---
-	Say Y here if you want to enable force feedback support for ACRUX
-	game controllers.
+	  Say Y here if you want to enable force feedback support for ACRUX
+	  game controllers.
 
 config HID_APPLE
 	tristate "Apple {i,Power,Mac}Books"
 	depends on HID
 	default !EXPERT
 	---help---
-	Support for some Apple devices which less or more break
-	HID specification.
+	  Support for some Apple devices which less or more break
+	  HID specification.
 
-	Say Y here if you want support for keyboards of	Apple iBooks, PowerBooks,
-	MacBooks, MacBook Pros and Apple Aluminum.
+	  Say Y here if you want support for keyboards of	Apple iBooks, PowerBooks,
+	  MacBooks, MacBook Pros and Apple Aluminum.
 
 config HID_APPLEIR
 	tristate "Apple infrared receiver"
 	depends on (USB_HID)
 	---help---
-	Support for Apple infrared remote control. All the Apple computers from
+	  Support for Apple infrared remote control. All the Apple computers from
 	  2005 onwards include such a port, except the unibody Macbook (2009),
 	  and Mac Pros. This receiver is also used in the Apple TV set-top box
 	  prior to the 2010 model.
 
-	Say Y here if you want support for Apple infrared remote control.
+	  Say Y here if you want support for Apple infrared remote control.
 
 config HID_ASUS
 	tristate "Asus"
 	depends on LEDS_CLASS
 	depends on ASUS_WMI || ASUS_WMI=n
 	---help---
-	Support for Asus notebook built-in keyboard and touchpad via i2c, and
-	the Asus Republic of Gamers laptop keyboard special keys.
+	  Support for Asus notebook built-in keyboard and touchpad via i2c, and
+	  the Asus Republic of Gamers laptop keyboard special keys.
 
-	Supported devices:
-	- EeeBook X205TA
-	- VivoBook E200HA
-	- GL553V series
-	- GL753V series
+	  Supported devices:
+	  - EeeBook X205TA
+	  - VivoBook E200HA
+	  - GL553V series
+	  - GL753V series
 
 config HID_AUREAL
 	tristate "Aureal"
 	depends on HID
 	---help---
-	Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
+	  Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
 
 config HID_BELKIN
 	tristate "Belkin Flip KVM and Wireless keyboard"
 	depends on HID
 	default !EXPERT
 	---help---
-	Support for Belkin Flip KVM and Wireless keyboard.
+	  Support for Belkin Flip KVM and Wireless keyboard.
 
 config HID_BETOP_FF
 	tristate "Betop Production Inc. force feedback support"
 	depends on USB_HID
 	select INPUT_FF_MEMLESS
 	---help---
-	Say Y here if you want to enable force feedback support for devices by
-	BETOP Production Ltd.
-	Currently the following devices are known to be supported:
-	 - BETOP 2185 PC & BFM MODE
+	  Say Y here if you want to enable force feedback support for devices by
+	  BETOP Production Ltd.
+	  Currently the following devices are known to be supported:
+	   - BETOP 2185 PC & BFM MODE
 
 config HID_BIGBEN_FF
 	tristate "BigBen Interactive Kids' gamepad support"
@@ -200,159 +200,159 @@ config HID_CHERRY
 	depends on HID
 	default !EXPERT
 	---help---
-	Support for Cherry Cymotion keyboard.
+	  Support for Cherry Cymotion keyboard.
 
 config HID_CHICONY
 	tristate "Chicony devices"
 	depends on HID
 	default !EXPERT
 	---help---
-	Support for Chicony Tactical pad and special keys on Chicony keyboards.
+	  Support for Chicony Tactical pad and special keys on Chicony keyboards.
 
 config HID_CORSAIR
 	tristate "Corsair devices"
 	depends on HID && USB && LEDS_CLASS
 	---help---
-	Support for Corsair devices that are not fully compliant with the
-	HID standard.
+	  Support for Corsair devices that are not fully compliant with the
+	  HID standard.
 
-	Supported devices:
-	- Vengeance K90
-	- Scimitar PRO RGB
+	  Supported devices:
+	  - Vengeance K90
+	  - Scimitar PRO RGB
 
 config HID_COUGAR
 	tristate "Cougar devices"
 	depends on HID
 	help
-	Support for Cougar devices that are not fully compliant with the
-	HID standard.
+	  Support for Cougar devices that are not fully compliant with the
+	  HID standard.
 
-	Supported devices:
-	- Cougar 500k Gaming Keyboard
+	  Supported devices:
+	  - Cougar 500k Gaming Keyboard
 
 config HID_PRODIKEYS
 	tristate "Prodikeys PC-MIDI Keyboard support"
 	depends on HID && SND
 	select SND_RAWMIDI
 	---help---
-	Support for Prodikeys PC-MIDI Keyboard device support.
-	Say Y here to enable support for this device.
-	- Prodikeys PC-MIDI keyboard.
-	  The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
-	  input and one MIDI output. These MIDI jacks appear as
-	  a sound "card" in the ALSA sound system.
-	  Note: if you say N here, this device will still function as a basic
-	  multimedia keyboard, but will lack support for the musical keyboard
-	  and some additional multimedia keys.
+	  Support for Prodikeys PC-MIDI Keyboard device support.
+	  Say Y here to enable support for this device.
+	  - Prodikeys PC-MIDI keyboard.
+	    The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
+	    input and one MIDI output. These MIDI jacks appear as
+	    a sound "card" in the ALSA sound system.
+	    Note: if you say N here, this device will still function as a basic
+	    multimedia keyboard, but will lack support for the musical keyboard
+	    and some additional multimedia keys.
 
 config HID_CMEDIA
 	tristate "CMedia CM6533 HID audio jack controls"
 	depends on HID
 	---help---
-	Support for CMedia CM6533 HID audio jack controls.
+	  Support for CMedia CM6533 HID audio jack controls.
 
 config HID_CP2112
 	tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
 	depends on USB_HID && HIDRAW && I2C && GPIOLIB
 	select GPIOLIB_IRQCHIP
 	---help---
-	Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
-	This is a HID device driver which registers as an i2c adapter
-	and gpiochip to expose these functions of the CP2112. The
-	customizable USB descriptor fields are exposed as sysfs attributes.
+	  Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
+	  This is a HID device driver which registers as an i2c adapter
+	  and gpiochip to expose these functions of the CP2112. The
+	  customizable USB descriptor fields are exposed as sysfs attributes.
 
 config HID_CYPRESS
 	tristate "Cypress mouse and barcode readers"
 	depends on HID
 	default !EXPERT
 	---help---
-	Support for cypress mouse and barcode readers.
+	  Support for cypress mouse and barcode readers.
 
 config HID_DRAGONRISE
 	tristate "DragonRise Inc. game controller"
 	depends on HID
 	---help---
-	Say Y here if you have DragonRise Inc. game controllers.
-	These might be branded as:
-	- Tesun USB-703
-	- Media-tech MT1504 "Rogue"
-	- DVTech JS19 "Gear"
-	- Defender Game Master
+	  Say Y here if you have DragonRise Inc. game controllers.
+	  These might be branded as:
+	  - Tesun USB-703
+	  - Media-tech MT1504 "Rogue"
+	  - DVTech JS19 "Gear"
+	  - Defender Game Master
 
 config DRAGONRISE_FF
 	bool "DragonRise Inc. force feedback"
 	depends on HID_DRAGONRISE
 	select INPUT_FF_MEMLESS
 	---help---
-	Say Y here if you want to enable force feedback support for DragonRise Inc.
-	game controllers.
+	  Say Y here if you want to enable force feedback support for DragonRise Inc.
+	  game controllers.
 
 config HID_EMS_FF
 	tristate "EMS Production Inc. force feedback support"
 	depends on HID
 	select INPUT_FF_MEMLESS
 	---help---
-	Say Y here if you want to enable force feedback support for devices by
-	EMS Production Ltd.
-	Currently the following devices are known to be supported:
-	 - Trio Linker Plus II
+	  Say Y here if you want to enable force feedback support for devices by
+	  EMS Production Ltd.
+	  Currently the following devices are known to be supported:
+	   - Trio Linker Plus II
 
 config HID_ELAN
 	tristate "ELAN USB Touchpad Support"
 	depends on LEDS_CLASS && USB_HID
 	---help---
-	Say Y to enable support for the USB ELAN touchpad
-	Currently the following devices are known to be supported:
-	 - HP Pavilion X2 10-p0XX.
+	  Say Y to enable support for the USB ELAN touchpad
+	  Currently the following devices are known to be supported:
+	   - HP Pavilion X2 10-p0XX.
 
 config HID_ELECOM
 	tristate "ELECOM HID devices"
 	depends on HID
 	---help---
-	Support for ELECOM devices:
-	  - BM084 Bluetooth Mouse
-	  - EX-G Trackballs (M-XT3DRBK, M-XT3URBK)
-	  - DEFT Trackballs (M-DT1DRBK, M-DT1URBK, M-DT2DRBK, M-DT2URBK)
-	  - HUGE Trackballs (M-HT1DRBK, M-HT1URBK)
+	  Support for ELECOM devices:
+	    - BM084 Bluetooth Mouse
+	    - EX-G Trackballs (M-XT3DRBK, M-XT3URBK)
+	    - DEFT Trackballs (M-DT1DRBK, M-DT1URBK, M-DT2DRBK, M-DT2URBK)
+	    - HUGE Trackballs (M-HT1DRBK, M-HT1URBK)
 
 config HID_ELO
 	tristate "ELO USB 4000/4500 touchscreen"
 	depends on USB_HID
 	---help---
-	Support for the ELO USB 4000/4500 touchscreens. Note that this is for
-	different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
+	  Support for the ELO USB 4000/4500 touchscreens. Note that this is for
+	  different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
 
 config HID_EZKEY
 	tristate "Ezkey BTC 8193 keyboard"
 	depends on HID
 	default !EXPERT
 	---help---
-	Support for Ezkey BTC 8193 keyboard.
+	  Support for Ezkey BTC 8193 keyboard.
 
 config HID_GEMBIRD
 	tristate "Gembird Joypad"
 	depends on HID
 	---help---
-	Support for Gembird JPD-DualForce 2.
+	  Support for Gembird JPD-DualForce 2.
 
 config HID_GFRM
 	tristate "Google Fiber TV Box remote control support"
 	depends on HID
 	---help---
-	Support for Google Fiber TV Box remote controls
+	  Support for Google Fiber TV Box remote controls
 
 config HID_HOLTEK
 	tristate "Holtek HID devices"
 	depends on USB_HID
 	---help---
-	Support for Holtek based devices:
-	  - Holtek On Line Grip based game controller
-	  - Trust GXT 18 Gaming Keyboard
-	  - Sharkoon Drakonia / Perixx MX-2000 gaming mice
-	  - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
-	    Zalman ZM-GM1
-	  - SHARKOON DarkGlider Gaming mouse
-	  - LEETGION Hellion Gaming Mouse
+	  Support for Holtek based devices:
+	    - Holtek On Line Grip based game controller
+	    - Trust GXT 18 Gaming Keyboard
+	    - Sharkoon Drakonia / Perixx MX-2000 gaming mice
+	    - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
+	      Zalman ZM-GM1
+	    - SHARKOON DarkGlider Gaming mouse
+	    - LEETGION Hellion Gaming Mouse
 
 config HOLTEK_FF
 	bool "Holtek On Line Grip force feedback support"
@@ -366,51 +366,51 @@ config HID_GOOGLE_HAMMER
 	tristate "Google Hammer Keyboard"
 	depends on USB_HID && LEDS_CLASS && MFD_CROS_EC
 	---help---
-	Say Y here if you have a Google Hammer device.
+	  Say Y here if you have a Google Hammer device.
 
 config HID_GT683R
 	tristate "MSI GT68xR LED support"
 	depends on LEDS_CLASS && USB_HID
 	---help---
-	Say Y here if you want to enable support for the three MSI GT68xR LEDs
+	  Say Y here if you want to enable support for the three MSI GT68xR LEDs
 
-	This driver support following modes:
-	  - Normal: LEDs are fully on when enabled
-	  - Audio:  LEDs brightness depends on sound level
-	  - Breathing: LEDs brightness varies at human breathing rate
+	  This driver support following modes:
+	    - Normal: LEDs are fully on when enabled
+	    - Audio:  LEDs brightness depends on sound level
+	    - Breathing: LEDs brightness varies at human breathing rate
 
-	Currently the following devices are know to be supported:
-	  - MSI GT683R
+	  Currently the following devices are know to be supported:
+	    - MSI GT683R
 
 config HID_KEYTOUCH
 	tristate "Keytouch HID devices"
 	depends on HID
 	---help---
-	Support for Keytouch HID devices not fully compliant with
-	the specification. Currently supported:
-		- Keytouch IEC 60945
+	  Support for Keytouch HID devices not fully compliant with
+	  the specification. Currently supported:
+	    - Keytouch IEC 60945
 
 config HID_KYE
 	tristate "KYE/Genius devices"
 	depends on HID
 	---help---
-	Support for KYE/Genius devices not fully compliant with HID standard:
-	- Ergo Mouse
-	- EasyPen i405X tablet
-	- MousePen i608X tablet
-	- EasyPen M610X tablet
+	  Support for KYE/Genius devices not fully compliant with HID standard:
+	  - Ergo Mouse
+	  - EasyPen i405X tablet
+	  - MousePen i608X tablet
+	  - EasyPen M610X tablet
 
 config HID_UCLOGIC
 	tristate "UC-Logic"
 	depends on USB_HID
 	---help---
-	Support for UC-Logic and Huion tablets.
+	  Support for UC-Logic and Huion tablets.
 
 config HID_WALTOP
 	tristate "Waltop"
 	depends on HID
 	---help---
-	Support for Waltop tablets.
+	  Support for Waltop tablets.
 
 config HID_VIEWSONIC
 	tristate "ViewSonic/Signotec"
@@ -422,68 +422,68 @@ config HID_GYRATION
 	tristate "Gyration remote control"
 	depends on HID
 	---help---
-	Support for Gyration remote control.
+	  Support for Gyration remote control.
 
 config HID_ICADE
 	tristate "ION iCade arcade controller"
 	depends on HID
 	---help---
-	Support for the ION iCade arcade controller to work as a joystick.
+	  Support for the ION iCade arcade controller to work as a joystick.
 
-	To compile this driver as a module, choose M here: the
-	module will be called hid-icade.
+	  To compile this driver as a module, choose M here: the
+	  module will be called hid-icade.
 
 config HID_ITE
 	tristate "ITE devices"
 	depends on HID
 	default !EXPERT
 	---help---
-	Support for ITE devices not fully compliant with HID standard.
+	  Support for ITE devices not fully compliant with HID standard.
 
 config HID_JABRA
 	tristate "Jabra USB HID Driver"
 	depends on HID
 	---help---
-	Support for Jabra USB HID devices.
+	  Support for Jabra USB HID devices.
 
-	Prevents mapping of vendor defined HID usages to input events. Without
-	this driver HID	reports from Jabra devices may incorrectly be seen as
-	mouse button events.
-	Say M here if you may ever plug in a Jabra USB device.
+	  Prevents mapping of vendor defined HID usages to input events. Without
+	  this driver HID reports from Jabra devices may incorrectly be seen as
+	  mouse button events.
+	  Say M here if you may ever plug in a Jabra USB device.
 
 config HID_TWINHAN
 	tristate "Twinhan IR remote control"
 	depends on HID
 	---help---
-	Support for Twinhan IR remote control.
+	  Support for Twinhan IR remote control.
 
 config HID_KENSINGTON
 	tristate "Kensington Slimblade Trackball"
 	depends on HID
 	default !EXPERT
 	---help---
-	Support for Kensington Slimblade Trackball.
+	  Support for Kensington Slimblade Trackball.
 
 config HID_LCPOWER
 	tristate "LC-Power"
 	depends on HID
 	---help---
-	Support for LC-Power RC1000MCE RF remote control.
+	  Support for LC-Power RC1000MCE RF remote control.
 
 config HID_LED
 	tristate "Simple RGB LED support"
 	depends on HID
 	depends on LEDS_CLASS
 	---help---
-	Support for simple RGB LED devices. Currently supported are:
-	- Riso Kagaku Webmail Notifier
-	- Dream Cheeky Webmail Notifier and Friends Alert
-	- ThingM blink(1)
-	- Delcom Visual Signal Indicator Generation 2
-	- Greynut Luxafor
+	  Support for simple RGB LED devices. Currently supported are:
+	  - Riso Kagaku Webmail Notifier
+	  - Dream Cheeky Webmail Notifier and Friends Alert
+	  - ThingM blink(1)
+	  - Delcom Visual Signal Indicator Generation 2
+	  - Greynut Luxafor
 
-	To compile this driver as a module, choose M here: the
-	module will be called hid-led.
+	  To compile this driver as a module, choose M here: the
+	  module will be called hid-led.
 
 config HID_LENOVO
 	tristate "Lenovo / Thinkpad devices"
@@ -491,22 +491,22 @@ config HID_LENOVO
 	select NEW_LEDS
 	select LEDS_CLASS
 	---help---
-	Support for IBM/Lenovo devices that are not fully compliant with HID standard.
+	  Support for IBM/Lenovo devices that are not fully compliant with HID standard.
 
-	Say Y if you want support for horizontal scrolling of the IBM/Lenovo
-	Scrollpoint mice or the non-compliant features of the Lenovo Thinkpad
-	standalone keyboards, e.g:
-	- ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
-	  configuration)
-	- ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
-	- ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
+	  Say Y if you want support for horizontal scrolling of the IBM/Lenovo
+	  Scrollpoint mice or the non-compliant features of the Lenovo Thinkpad
+	  standalone keyboards, e.g:
+	  - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
+	    configuration)
+	  - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
+	  - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
 
 config HID_LOGITECH
 	tristate "Logitech devices"
 	depends on HID
 	default !EXPERT
 	---help---
-	Support for Logitech devices that are not fully compliant with HID standard.
+	  Support for Logitech devices that are not fully compliant with HID standard.
 
 config HID_LOGITECH_DJ
 	tristate "Logitech Unifying receivers full support"
@@ -514,23 +514,23 @@ config HID_LOGITECH_DJ
 	depends on HID_LOGITECH
 	select HID_LOGITECH_HIDPP
 	---help---
-	Say Y if you want support for Logitech Unifying receivers and devices.
-	Unifying receivers are capable of pairing up to 6 Logitech compliant
-	devices to the same receiver. Without this driver it will be handled by
-	generic USB_HID driver and all incoming events will be multiplexed
-	into a single mouse and a single keyboard device.
+	  Say Y if you want support for Logitech Unifying receivers and devices.
+	  Unifying receivers are capable of pairing up to 6 Logitech compliant
+	  devices to the same receiver. Without this driver it will be handled by
+	  generic USB_HID driver and all incoming events will be multiplexed
+	  into a single mouse and a single keyboard device.
 
 config HID_LOGITECH_HIDPP
 	tristate "Logitech HID++ devices support"
 	depends on HID_LOGITECH
 	select POWER_SUPPLY
 	---help---
-	Support for Logitech devices relyingon the HID++ Logitech specification
+	  Support for Logitech devices relyingon the HID++ Logitech specification
 
-	Say Y if you want support for Logitech devices relying on the HID++
-	specification. Such devices are the various Logitech Touchpads (T650,
-	T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
-	Keyboard).
+	  Say Y if you want support for Logitech devices relying on the HID++
+	  specification. Such devices are the various Logitech Touchpads (T650,
+	  T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
+	  Keyboard).
 
 config LOGITECH_FF
 	bool "Logitech force feedback support"
@@ -591,10 +591,10 @@ config HID_MAGICMOUSE
 	tristate "Apple Magic Mouse/Trackpad multi-touch support"
 	depends on HID
 	---help---
-	Support for the Apple Magic Mouse/Trackpad multi-touch.
+	  Support for the Apple Magic Mouse/Trackpad multi-touch.
 
-	Say Y here if you want support for the multi-touch features of the
-	Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
+	  Say Y here if you want support for the multi-touch features of the
+	  Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
 
 config HID_MALTRON
 	tristate "Maltron L90 keyboard"
@@ -608,15 +608,15 @@ config HID_MAYFLASH
 	depends on HID
 	select INPUT_FF_MEMLESS
 	---help---
-	Say Y here if you have HJZ Mayflash PS3 game controller adapters
-	and want to enable force feedback support.
+	  Say Y here if you have HJZ Mayflash PS3 game controller adapters
+	  and want to enable force feedback support.
 
 config HID_REDRAGON
 	tristate "Redragon keyboards"
 	depends on HID
 	default !EXPERT
 	---help---
-    Support for Redragon keyboards that need fix-ups to work properly.
+	  Support for Redragon keyboards that need fix-ups to work properly.
 
 config HID_MICROSOFT
 	tristate "Microsoft non-fully HID-compliant devices"
@@ -624,14 +624,14 @@ config HID_MICROSOFT
 	default !EXPERT
 	select INPUT_FF_MEMLESS
 	---help---
-	Support for Microsoft devices that are not fully compliant with HID standard.
+	  Support for Microsoft devices that are not fully compliant with HID standard.
 
 config HID_MONTEREY
 	tristate "Monterey Genius KB29E keyboard"
 	depends on HID
 	default !EXPERT
 	---help---
-	Support for Monterey Genius KB29E.
+	  Support for Monterey Genius KB29E.
 
 config HID_MULTITOUCH
 	tristate "HID Multitouch panels"
@@ -682,14 +682,14 @@ config HID_MULTITOUCH
 config HID_NTI
 	tristate "NTI keyboard adapters"
 	---help---
-	Support for the "extra" Sun keyboard keys on keyboards attached
-	through Network Technologies USB-SUN keyboard adapters.
+	  Support for the "extra" Sun keyboard keys on keyboards attached
+	  through Network Technologies USB-SUN keyboard adapters.
 
 config HID_NTRIG
 	tristate "N-Trig touch screen"
 	depends on USB_HID
 	---help---
-	Support for N-Trig touch screen.
+	  Support for N-Trig touch screen.
 
 config HID_ORTEK
 	tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
@@ -817,41 +817,41 @@ config HID_PRIMAX
 	tristate "Primax non-fully HID-compliant devices"
 	depends on HID
 	---help---
-	Support for Primax devices that are not fully compliant with the
-	HID standard.
+	  Support for Primax devices that are not fully compliant with the
+	  HID standard.
 
 config HID_RETRODE
 	tristate "Retrode 2 USB adapter for vintage video games"
 	depends on USB_HID
 	---help---
-	Support for
-	  * Retrode 2 cartridge and controller adapter
+	  Support for
+	    * Retrode 2 cartridge and controller adapter
 
 config HID_ROCCAT
 	tristate "Roccat device support"
 	depends on USB_HID
 	---help---
-	Support for Roccat devices.
-	Say Y here if you have a Roccat mouse or keyboard and want
-	support for its special functionalities.
+	  Support for Roccat devices.
+	  Say Y here if you have a Roccat mouse or keyboard and want
+	  support for its special functionalities.
 
 config HID_SAITEK
 	tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
 	depends on HID
 	---help---
-	Support for Saitek devices that are not fully compliant with the
-	HID standard.
+	  Support for Saitek devices that are not fully compliant with the
+	  HID standard.
 
-	Supported devices:
-	- PS1000 Dual Analog Pad
-	- Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
-	- Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
+	  Supported devices:
+	  - PS1000 Dual Analog Pad
+	  - Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
+	  - Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
 
 config HID_SAMSUNG
 	tristate "Samsung InfraRed remote control or keyboards"
 	depends on HID
 	---help---
-	Support for Samsung InfraRed remote control or keyboards.
+	  Support for Samsung InfraRed remote control or keyboards.
 
 config HID_SONY
 	tristate "Sony PS2/3/4 accessories"
@@ -860,48 +860,48 @@ config HID_SONY
 	depends on LEDS_CLASS
 	select POWER_SUPPLY
 	---help---
-	Support for
+	  Support for
 
-	  * Sony PS3 6-axis controllers
-	  * Sony PS4 DualShock 4 controllers
-	  * Buzz controllers
-	  * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
-	  * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
+	    * Sony PS3 6-axis controllers
+	    * Sony PS4 DualShock 4 controllers
+	    * Buzz controllers
+	    * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
+	    * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
 
 config SONY_FF
-	bool "Sony PS2/3/4 accessories force feedback support" 
+	bool "Sony PS2/3/4 accessories force feedback support"
 	depends on HID_SONY
 	select INPUT_FF_MEMLESS
 	---help---
-	Say Y here if you have a Sony PS2/3/4 accessory and want to enable
-	force feedback support for it.
+	  Say Y here if you have a Sony PS2/3/4 accessory and want to enable
+	  force feedback support for it.
 
 config HID_SPEEDLINK
 	tristate "Speedlink VAD Cezanne mouse support"
 	depends on HID
 	---help---
-	Support for Speedlink Vicious and Divine Cezanne mouse.
+	  Support for Speedlink Vicious and Divine Cezanne mouse.
 
 config HID_STEAM
 	tristate "Steam Controller support"
 	depends on HID
 	select POWER_SUPPLY
 	---help---
-	Say Y here if you have a Steam Controller if you want to use it
-	without running the Steam Client. It supports both the wired and
-	the wireless adaptor.
+	  Say Y here if you have a Steam Controller if you want to use it
+	  without running the Steam Client. It supports both the wired and
+	  the wireless adaptor.
 
 config HID_STEELSERIES
 	tristate "Steelseries SRW-S1 steering wheel support"
 	depends on HID
 	---help---
-	Support for Steelseries SRW-S1 steering wheel
+	  Support for Steelseries SRW-S1 steering wheel
 
 config HID_SUNPLUS
 	tristate "Sunplus wireless desktop"
 	depends on HID
 	---help---
-	Support for Sunplus wireless desktop.
+	  Support for Sunplus wireless desktop.
 
 config HID_RMI
 	tristate "Synaptics RMI4 device support"
@@ -912,9 +912,9 @@ config HID_RMI
 	select RMI4_F12
 	select RMI4_F30
 	---help---
-	Support for Synaptics RMI4 touchpads.
-	Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
-	and want support for its special functionalities.
+	  Support for Synaptics RMI4 touchpads.
+	  Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
+	  and want support for its special functionalities.
 
 config HID_GREENASIA
 	tristate "GreenAsia (Product ID 0x12) game controller support"
@@ -928,46 +928,46 @@ config GREENASIA_FF
 	depends on HID_GREENASIA
 	select INPUT_FF_MEMLESS
 	---help---
-	Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
-	(like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
-	and want to enable force feedback support for it.
+	  Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
+	  (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
+	  and want to enable force feedback support for it.
 
 config HID_HYPERV_MOUSE
 	tristate "Microsoft Hyper-V mouse driver"
 	depends on HYPERV
 	---help---
-	Select this option to enable the Hyper-V mouse driver.
+	  Select this option to enable the Hyper-V mouse driver.
 
 config HID_SMARTJOYPLUS
 	tristate "SmartJoy PLUS PS2/USB adapter support"
 	depends on HID
 	---help---
-	Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
-	Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
+	  Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
+	  Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
 
-	Note that DDR (Dance Dance Revolution) mode is not supported, nor
-	is pressure sensitive buttons on the pro models.
+	  Note that DDR (Dance Dance Revolution) mode is not supported, nor
+	  is pressure sensitive buttons on the pro models.
 
 config SMARTJOYPLUS_FF
 	bool "SmartJoy PLUS PS2/USB adapter force feedback support"
 	depends on HID_SMARTJOYPLUS
 	select INPUT_FF_MEMLESS
 	---help---
-	Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
-	enable force feedback support for it.
+	  Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
+	  enable force feedback support for it.
 
 config HID_TIVO
 	tristate "TiVo Slide Bluetooth remote control support"
 	depends on HID
 	---help---
-	Say Y if you have a TiVo Slide Bluetooth remote control.
+	  Say Y if you have a TiVo Slide Bluetooth remote control.
 
 config HID_TOPSEED
 	tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
 	depends on HID
 	---help---
-	Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
-	CLLRCMCE remote control.
+	  Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
+	  CLLRCMCE remote control.
 
 config HID_THINGM
 	tristate "ThingM blink(1) USB RGB LED"
@@ -1023,31 +1023,31 @@ config HID_WIIMOTE
 	select POWER_SUPPLY
 	select INPUT_FF_MEMLESS
 	---help---
-	Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
-	devices are the Wii Remote and its extension devices, but also devices
-	based on the Wii Remote like the Wii U Pro Controller or the
-	Wii Balance Board.
+	  Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
+	  devices are the Wii Remote and its extension devices, but also devices
+	  based on the Wii Remote like the Wii U Pro Controller or the
+	  Wii Balance Board.
 
-	Support for all official Nintendo extensions is available, however, 3rd
-	party extensions might not be supported. Please report these devices to:
-	  http://github.com/dvdhrm/xwiimote/issues
+	  Support for all official Nintendo extensions is available, however, 3rd
+	  party extensions might not be supported. Please report these devices to:
+	    http://github.com/dvdhrm/xwiimote/issues
 
-	Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
-	the Wii U Gamepad) might be supported in the future. But currently
-	support is limited to Bluetooth based devices.
+	  Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
+	  the Wii U Gamepad) might be supported in the future. But currently
+	  support is limited to Bluetooth based devices.
 
-	If unsure, say N.
+	  If unsure, say N.
 
-	To compile this driver as a module, choose M here: the
-	module will be called hid-wiimote.
+	  To compile this driver as a module, choose M here: the
+	  module will be called hid-wiimote.
 
 config HID_XINMO
 	tristate "Xin-Mo non-fully compliant devices"
 	depends on HID
 	---help---
-	Support for Xin-Mo devices that are not fully compliant with the HID
-	standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
-	if you have a Xin-Mo Dual Arcade controller.
+	  Support for Xin-Mo devices that are not fully compliant with the HID
+	  standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
+	  if you have a Xin-Mo Dual Arcade controller.
 
 config HID_ZEROPLUS
 	tristate "Zeroplus based game controller support"
@@ -1102,9 +1102,9 @@ config HID_ALPS
 	tristate "Alps HID device support"
 	depends on HID
 	---help---
-	Support for Alps I2C HID touchpads and StickPointer.
-	Say Y here if you have a Alps touchpads over i2c-hid or usbhid
-	and want support for its special functionalities.
+	  Support for Alps I2C HID touchpads and StickPointer.
+	  Say Y here if you have a Alps touchpads over i2c-hid or usbhid
+	  and want support for its special functionalities.
 
 endmenu
 
Signature · 1 line
1.9.1
#114 lore raw

PATCH 106/114 drivers: rtc: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/rtc/Kconfig | 82 ++++++++++++++++++++++++++---------------------------
 1 file changed, 41 insertions(+), 41 deletions(-)
drivers/rtc/Kconfig +41 -41
index e1a1f2b..f7d2553 100644
@@ -1211,8 +1211,8 @@ config RTC_DRV_SPEAR
 	depends on PLAT_SPEAR || COMPILE_TEST
 	default y
 	help
-	 If you say Y here you will get support for the RTC found on
-	 spear
+	  If you say Y here you will get support for the RTC found on
+	  spear
 
 config RTC_DRV_PCF50633
 	depends on MFD_PCF50633
@@ -1309,10 +1309,10 @@ config RTC_DRV_IMXDI
 	tristate "Freescale IMX DryIce Real Time Clock"
 	depends on ARCH_MXC
 	help
-	   Support for Freescale IMX DryIce RTC
+	  Support for Freescale IMX DryIce RTC
 
-	   This driver can also be built as a module, if so, the module
-	   will be called "rtc-imxdi".
+	  This driver can also be built as a module, if so, the module
+	  will be called "rtc-imxdi".
 
 config RTC_DRV_MESON
 	tristate "Amlogic Meson RTC"
@@ -1475,12 +1475,12 @@ config RTC_DRV_PXA
 	depends on ARCH_PXA
 	select RTC_DRV_SA1100
 	help
-         If you say Y here you will get access to the real time clock
-         built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
-         consisting of an SA1100 compatible RTC and the extended PXA RTC.
+	  If you say Y here you will get access to the real time clock
+	  built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
+	  consisting of an SA1100 compatible RTC and the extended PXA RTC.
 
-	 This RTC driver uses PXA RTC registers available since pxa27x
-	 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
+	  This RTC driver uses PXA RTC registers available since pxa27x
+	  series (RDxR, RYxR) instead of legacy RCNR, RTAR.
 
 config RTC_DRV_VT8500
 	tristate "VIA/WonderMedia 85xx SoC RTC"
@@ -1699,21 +1699,21 @@ config RTC_DRV_MXC
 	tristate "Freescale MXC Real Time Clock"
 	depends on ARCH_MXC
 	help
-	   If you say yes here you get support for the Freescale MXC
-	   RTC module.
+	  If you say yes here you get support for the Freescale MXC
+	  RTC module.
 
-	   This driver can also be built as a module, if so, the module
-	   will be called "rtc-mxc".
+	  This driver can also be built as a module, if so, the module
+	  will be called "rtc-mxc".
 
 config RTC_DRV_MXC_V2
 	tristate "Freescale MXC Real Time Clock for i.MX53"
 	depends on ARCH_MXC
 	help
-	   If you say yes here you get support for the Freescale MXC
-	   SRTC module in i.MX53 processor.
+	  If you say yes here you get support for the Freescale MXC
+	  SRTC module in i.MX53 processor.
 
-	   This driver can also be built as a module, if so, the module
-	   will be called "rtc-mxc_v2".
+	  This driver can also be built as a module, if so, the module
+	  will be called "rtc-mxc_v2".
 
 config RTC_DRV_SNVS
 	tristate "Freescale SNVS RTC support"
@@ -1721,19 +1721,19 @@ config RTC_DRV_SNVS
 	depends on HAS_IOMEM
 	depends on OF
 	help
-	   If you say yes here you get support for the Freescale SNVS
-	   Low Power (LP) RTC module.
+	  If you say yes here you get support for the Freescale SNVS
+	  Low Power (LP) RTC module.
 
-	   This driver can also be built as a module, if so, the module
-	   will be called "rtc-snvs".
+	  This driver can also be built as a module, if so, the module
+	  will be called "rtc-snvs".
 
 config RTC_DRV_IMX_SC
 	depends on IMX_SCU
 	depends on HAVE_ARM_SMCCC
 	tristate "NXP i.MX System Controller RTC support"
 	help
-	   If you say yes here you get support for the NXP i.MX System
-	   Controller RTC module.
+	  If you say yes here you get support for the NXP i.MX System
+	  Controller RTC module.
 
 config RTC_DRV_SIRFSOC
 	tristate "SiRFSOC RTC"
@@ -1757,11 +1757,11 @@ config RTC_DRV_MOXART
 	tristate "MOXA ART RTC"
 	depends on ARCH_MOXART || COMPILE_TEST
 	help
-	   If you say yes here you get support for the MOXA ART
-	   RTC module.
+	  If you say yes here you get support for the MOXA ART
+	  RTC module.
 
-	   This driver can also be built as a module. If so, the module
-	   will be called rtc-moxart
+	  This driver can also be built as a module. If so, the module
+	  will be called rtc-moxart
 
 config RTC_DRV_MT6397
 	tristate "MediaTek PMIC based RTC"
@@ -1799,39 +1799,39 @@ config RTC_DRV_PIC32
 	depends on MACH_PIC32
 	default y
 	help
-	   If you say yes here you get support for the PIC32 RTC module.
+	  If you say yes here you get support for the PIC32 RTC module.
 
-	   This driver can also be built as a module. If so, the module
-	   will be called rtc-pic32
+	  This driver can also be built as a module. If so, the module
+	  will be called rtc-pic32
 
 config RTC_DRV_R7301
 	tristate "EPSON TOYOCOM RTC-7301SF/DG"
 	select REGMAP_MMIO
 	depends on OF && HAS_IOMEM
 	help
-	   If you say yes here you get support for the EPSON TOYOCOM
-	   RTC-7301SF/DG chips.
+	  If you say yes here you get support for the EPSON TOYOCOM
+	  RTC-7301SF/DG chips.
 
-	   This driver can also be built as a module. If so, the module
-	   will be called rtc-r7301.
+	  This driver can also be built as a module. If so, the module
+	  will be called rtc-r7301.
 
 config RTC_DRV_STM32
 	tristate "STM32 RTC"
 	select REGMAP_MMIO
 	depends on ARCH_STM32 || COMPILE_TEST
 	help
-	   If you say yes here you get support for the STM32 On-Chip
-	   Real Time Clock.
+	  If you say yes here you get support for the STM32 On-Chip
+	  Real Time Clock.
 
-	   This driver can also be built as a module, if so, the module
-	   will be called "rtc-stm32".
+	  This driver can also be built as a module, if so, the module
+	  will be called "rtc-stm32".
 
 config RTC_DRV_CPCAP
 	depends on MFD_CPCAP
 	tristate "Motorola CPCAP RTC"
 	help
-	   Say y here for CPCAP rtc found on some Motorola phones
-	   and tablets such as Droid 4.
+	  Say y here for CPCAP rtc found on some Motorola phones
+	  and tablets such as Droid 4.
 
 config RTC_DRV_RTD119X
 	bool "Realtek RTD129x RTC"
Signature · 1 line
1.9.1
#115 lore raw

PATCH 107/114 drivers: xen: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/xen/Kconfig | 62 ++++++++++++++++++++++++++---------------------------
 1 file changed, 31 insertions(+), 31 deletions(-)
drivers/xen/Kconfig +31 -31
index 838b66a..22a8a14 100644
@@ -53,8 +53,8 @@ config XEN_BALLOON_MEMORY_HOTPLUG
 	  the newly added memory can be manually onlined in the target domain
 	  by doing the following:
 
-		for i in /sys/devices/system/memory/memory*/state; do \
-		  [ "`cat "$i"`" = offline ] && echo online > "$i"; done
+	        for i in /sys/devices/system/memory/memory*/state; do \
+	          [ "`cat "$i"`" = offline ] && echo online > "$i"; done
 
 	  or by adding the following line to udev rules:
 
@@ -120,27 +120,27 @@ config XENFS
 	  If in doubt, say yes.
 
 config XEN_COMPAT_XENFS
-       bool "Create compatibility mount point /proc/xen"
-       depends on XENFS
-       default y
-       help
-         The old xenstore userspace tools expect to find "xenbus"
-         under /proc/xen, but "xenbus" is now found at the root of the
-         xenfs filesystem.  Selecting this causes the kernel to create
-         the compatibility mount point /proc/xen if it is running on
-         a xen platform.
-         If in doubt, say yes.
+	bool "Create compatibility mount point /proc/xen"
+	depends on XENFS
+	default y
+	help
+	  The old xenstore userspace tools expect to find "xenbus"
+	  under /proc/xen, but "xenbus" is now found at the root of the
+	  xenfs filesystem.  Selecting this causes the kernel to create
+	  the compatibility mount point /proc/xen if it is running on
+	  a xen platform.
+	  If in doubt, say yes.
 
 config XEN_SYS_HYPERVISOR
-       bool "Create xen entries under /sys/hypervisor"
-       depends on SYSFS
-       select SYS_HYPERVISOR
-       default y
-       help
-         Create entries under /sys/hypervisor describing the Xen
-	 hypervisor environment.  When running native or in another
-	 virtual environment, /sys/hypervisor will still be present,
-	 but will have no xen contents.
+	bool "Create xen entries under /sys/hypervisor"
+	depends on SYSFS
+	select SYS_HYPERVISOR
+	default y
+	help
+	  Create entries under /sys/hypervisor describing the Xen
+	  hypervisor environment.  When running native or in another
+	  virtual environment, /sys/hypervisor will still be present,
+	  but will have no xen contents.
 
 config XEN_XENBUS_FRONTEND
 	tristate
@@ -292,7 +292,7 @@ config XEN_ACPI_PROCESSOR
 	depends on XEN && XEN_DOM0 && X86 && ACPI_PROCESSOR && CPU_FREQ
 	default m
 	help
-          This ACPI processor uploads Power Management information to the Xen
+	  This ACPI processor uploads Power Management information to the Xen
 	  hypervisor.
 
 	  To do that the driver parses the Power Management data and uploads
@@ -301,7 +301,7 @@ config XEN_ACPI_PROCESSOR
 	  SMM so that other drivers (such as ACPI cpufreq scaling driver) will
 	  not load.
 
-          To compile this driver as a module, choose M here: the module will be
+	  To compile this driver as a module, choose M here: the module will be
 	  called xen_acpi_processor  If you do not know what to choose, select
 	  M here. If the CPUFREQ drivers are built in, select Y here.
 
@@ -313,7 +313,7 @@ config XEN_MCE_LOG
 	  converting it into Linux mcelog format for mcelog tools
 
 config XEN_HAVE_PVMMU
-       bool
+	bool
 
 config XEN_EFI
 	def_bool y
@@ -330,15 +330,15 @@ config XEN_ACPI
 	depends on X86 && ACPI
 
 config XEN_SYMS
-       bool "Xen symbols"
-       depends on X86 && XEN_DOM0 && XENFS
-       default y if KALLSYMS
-       help
-          Exports hypervisor symbols (along with their types and addresses) via
-          /proc/xen/xensyms file, similar to /proc/kallsyms
+	bool "Xen symbols"
+	depends on X86 && XEN_DOM0 && XENFS
+	default y if KALLSYMS
+	help
+	  Exports hypervisor symbols (along with their types and addresses) via
+	  /proc/xen/xensyms file, similar to /proc/kallsyms
 
 config XEN_HAVE_VPMU
-       bool
+	bool
 
 config XEN_FRONT_PGDIR_SHBUF
 	tristate
Signature · 1 line
1.9.1
#116 lore raw

PATCH 108/114 drivers: firmware_loader: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/base/firmware_loader/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/base/firmware_loader/Kconfig +1 -1
index eb15d97..592e689 100644
@@ -143,7 +143,7 @@ config FW_LOADER_USER_HELPER_FALLBACK
 	  to be used for all firmware requests which explicitly do not disable a
 	  a fallback mechanism. Firmware calls which do prohibit a fallback
 	  mechanism is request_firmware_direct(). This option is kept for
-          backward compatibility purposes given this precise mechanism can also
+	  backward compatibility purposes given this precise mechanism can also
 	  be enabled by setting the proc sysctl value to true:
 
 	       /proc/sys/kernel/firmware_config/force_sysfs_fallback
Signature · 1 line
1.9.1
#117 lore raw

PATCH 109/114 drivers: clocksource: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/clocksource/Kconfig | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)
drivers/clocksource/Kconfig +11 -11
index 171502a..4e5b091 100644
@@ -389,7 +389,7 @@ config CLKSRC_ARM_GLOBAL_TIMER_SCHED_CLOCK
 	depends on ARM_GLOBAL_TIMER
 	default y
 	help
-	 Use ARM global timer clock source as sched_clock
+	  Use ARM global timer clock source as sched_clock
 
 config ARMV7M_SYSTICK
 	bool "Support for the ARMv7M system time" if COMPILE_TEST
@@ -446,7 +446,7 @@ config OXNAS_RPS_TIMER
 	  This enables support for the Oxford Semiconductor OXNAS RPS timers.
 
 config SYS_SUPPORTS_SH_CMT
-        bool
+	bool
 
 config MTK_TIMER
 	bool "Mediatek timer driver" if COMPILE_TEST
@@ -466,13 +466,13 @@ config SPRD_TIMER
 	  Enables support for the Spreadtrum timer driver.
 
 config SYS_SUPPORTS_SH_MTU2
-        bool
+	bool
 
 config SYS_SUPPORTS_SH_TMU
-        bool
+	bool
 
 config SYS_SUPPORTS_EM_STI
-        bool
+	bool
 
 config CLKSRC_JCORE_PIT
 	bool "J-Core PIT timer driver" if COMPILE_TEST
@@ -566,21 +566,21 @@ config CLKSRC_PXA
 	  platforms.
 
 config H8300_TMR8
-        bool "Clockevent timer for the H8300 platform" if COMPILE_TEST
-        depends on HAS_IOMEM
+	bool "Clockevent timer for the H8300 platform" if COMPILE_TEST
+	depends on HAS_IOMEM
 	help
 	  This enables the 8 bits timer for the H8300 platform.
 
 config H8300_TMR16
-        bool "Clockevent timer for the H83069 platform" if COMPILE_TEST
-        depends on HAS_IOMEM
+	bool "Clockevent timer for the H83069 platform" if COMPILE_TEST
+	depends on HAS_IOMEM
 	help
 	  This enables the 16 bits timer for the H8300 platform with the
 	  H83069 cpu.
 
 config H8300_TPU
-        bool "Clocksource for the H8300 platform" if COMPILE_TEST
-        depends on HAS_IOMEM
+	bool "Clocksource for the H8300 platform" if COMPILE_TEST
+	depends on HAS_IOMEM
 	help
 	  This enables the clocksource for the H8300 platform with the
 	  H8S2678 cpu.
Signature · 1 line
1.9.1
#118 lore raw

PATCH 110/114 drivers: hv: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/hv/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/hv/Kconfig +1 -1
index 1c1a251..016c77e 100644
@@ -11,7 +11,7 @@ config HYPERV
 	  system.
 
 config HYPERV_TSCPAGE
-       def_bool HYPERV && X86_64
+	def_bool HYPERV && X86_64
 
 config HYPERV_UTILS
 	tristate "Microsoft Hyper-V Utilities driver"
Signature · 1 line
1.9.1
#119 lore raw

PATCH 111/114 drivers: mcb: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/mcb/Kconfig | 47 ++++++++++++++++++++++-------------------------
 1 file changed, 22 insertions(+), 25 deletions(-)
drivers/mcb/Kconfig +22 -25
index 76d9c51..85b4f22 100644
@@ -3,38 +3,35 @@
 #
 
 menuconfig MCB
-	   tristate "MCB support"
-	   default n
-	   depends on HAS_IOMEM
-	   help
+	tristate "MCB support"
+	default n
+	depends on HAS_IOMEM
+	help
+	  The MCB (MEN Chameleon Bus) is a Bus specific to MEN Mikroelektronik
+	  FPGA based devices. It is used to identify MCB based IP-Cores within
+	  an FPGA and provide the necessary framework for instantiating drivers
+	  for these devices.
 
-	   The MCB (MEN Chameleon Bus) is a Bus specific to MEN Mikroelektronik
-	   FPGA based devices. It is used to identify MCB based IP-Cores within
-	   an FPGA and provide the necessary framework for instantiating drivers
-	   for these devices.
-
-	   If build as a module, the module is called mcb.ko
+	  If build as a module, the module is called mcb.ko
 
 if MCB
 config MCB_PCI
-	   tristate "PCI based MCB carrier"
-	   default n
-	   depends on PCI
-	   help
-
-	   This is a MCB carrier on a PCI device. Both PCI attached on-board
-	   FPGAs as well as CompactPCI attached MCB FPGAs are supported with
-	   this driver.
+	tristate "PCI based MCB carrier"
+	default n
+	depends on PCI
+	help
+	  This is a MCB carrier on a PCI device. Both PCI attached on-board
+	  FPGAs as well as CompactPCI attached MCB FPGAs are supported with
+	  this driver.
 
-	   If build as a module, the module is called mcb-pci.ko
+	  If build as a module, the module is called mcb-pci.ko
 
 config MCB_LPC
-	   tristate "LPC (non PCI) based MCB carrier"
-	   default n
-	   help
-
-	   This is a MCB carrier on a LPC or non PCI device.
+	tristate "LPC (non PCI) based MCB carrier"
+	default n
+	help
+	  This is a MCB carrier on a LPC or non PCI device.
 
-	   If build as a module, the module is called mcb-lpc.ko
+	  If build as a module, the module is called mcb-lpc.ko
 
 endif # MCB
Signature · 1 line
1.9.1
#120 lore raw

PATCH 112/114 drivers: misc: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/misc/Kconfig | 44 ++++++++++++++++++++++----------------------
 1 file changed, 22 insertions(+), 22 deletions(-)
drivers/misc/Kconfig +22 -22
index 42ab8ec..4cc60aa 100644
@@ -370,25 +370,25 @@ config SENSORS_TSL2550
 	  will be called tsl2550.
 
 config SENSORS_BH1770
-         tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
-         depends on I2C
-         ---help---
-           Say Y here if you want to build a driver for BH1770GLC (ROHM) or
-	   SFH7770 (Osram) combined ambient light and proximity sensor chip.
+	tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
+	depends on I2C
+	---help---
+	  Say Y here if you want to build a driver for BH1770GLC (ROHM) or
+	  SFH7770 (Osram) combined ambient light and proximity sensor chip.
 
-           To compile this driver as a module, choose M here: the
-           module will be called bh1770glc. If unsure, say N here.
+	  To compile this driver as a module, choose M here: the
+	  module will be called bh1770glc. If unsure, say N here.
 
 config SENSORS_APDS990X
-	 tristate "APDS990X combined als and proximity sensors"
-	 depends on I2C
-	 default n
-	 ---help---
-	   Say Y here if you want to build a driver for Avago APDS990x
-	   combined ambient light and proximity sensor chip.
+	tristate "APDS990X combined als and proximity sensors"
+	depends on I2C
+	default n
+	---help---
+	  Say Y here if you want to build a driver for Avago APDS990x
+	  combined ambient light and proximity sensor chip.
 
-	   To compile this driver as a module, choose M here: the
-	   module will be called apds990x. If unsure, say N here.
+	  To compile this driver as a module, choose M here: the
+	  module will be called apds990x. If unsure, say N here.
 
 config HMC6352
 	tristate "Honeywell HMC6352 compass"
@@ -412,10 +412,10 @@ config SPEAR13XX_PCIE_GADGET
 	depends on ARCH_SPEAR13XX && BROKEN
 	default n
 	help
-	 This option enables gadget support for PCIe controller. If
-	 board file defines any controller as PCIe endpoint then a sysfs
-	 entry will be created for that controller. User can use these
-	 sysfs node to configure PCIe EP as per his requirements.
+	  This option enables gadget support for PCIe controller. If
+	  board file defines any controller as PCIe endpoint then a sysfs
+	  entry will be created for that controller. User can use these
+	  sysfs node to configure PCIe EP as per his requirements.
 
 config VMWARE_BALLOON
 	tristate "VMware Balloon Driver"
@@ -467,7 +467,7 @@ config LATTICE_ECP3_CONFIG
 	tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
 	depends on SPI && SYSFS
 	select FW_LOADER
-	default	n
+	default n
 	help
 	  This option enables support for bitstream configuration (programming
 	  or loading) of the Lattice ECP3 FPGA family via SPI.
@@ -517,8 +517,8 @@ config PCI_ENDPOINT_TEST
 	select CRC32
 	tristate "PCI Endpoint Test driver"
 	---help---
-           Enable this configuration option to enable the host side test driver
-           for PCI Endpoint.
+	  Enable this configuration option to enable the host side test driver
+	  for PCI Endpoint.
 
 config MISC_RTSX
 	tristate
Signature · 1 line
1.9.1
#121 lore raw

PATCH 113/114 drivers: rpmsg: Kconfig: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.

---
 drivers/rpmsg/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/rpmsg/Kconfig +1 -1
index d0322b4..7092765 100644
@@ -21,7 +21,7 @@ config RPMSG_QCOM_GLINK_NATIVE
 
 config RPMSG_QCOM_GLINK_RPM
 	tristate "Qualcomm RPM Glink driver"
-        select RPMSG_QCOM_GLINK_NATIVE
+	select RPMSG_QCOM_GLINK_NATIVE
 	depends on HAS_IOMEM
 	depends on MAILBOX
 	help
Signature · 1 line
1.9.1
#122 lore raw

PATCH 114/114 arch: arm: boot: dts: pedantic formatting

In reply to Enrico Weigelt, metux IT consult

Formatting of dts(i) files doesn't look so pretty, so just take damp cloth and clean it up. Just indention changes.

---
 arch/arm/boot/dts/alpine-db.dts                    |   1 -
 arch/arm/boot/dts/am335x-baltos-ir2110.dts         |  16 +-
 arch/arm/boot/dts/am335x-baltos-ir3220.dts         |  38 +--
 arch/arm/boot/dts/am335x-baltos-ir5221.dts         |  42 +--
 arch/arm/boot/dts/am335x-baltos.dtsi               |  40 +--
 arch/arm/boot/dts/am335x-bone-common.dtsi          |  20 +-
 arch/arm/boot/dts/am335x-boneblack-common.dtsi     |  10 +-
 arch/arm/boot/dts/am335x-boneblack-wireless.dts    |  12 +-
 arch/arm/boot/dts/am335x-chiliboard.dts            |  22 +-
 arch/arm/boot/dts/am335x-evm.dts                   |  12 +-
 arch/arm/boot/dts/am335x-evmsk.dts                 |  56 ++--
 arch/arm/boot/dts/am335x-icev2.dts                 |  44 +--
 arch/arm/boot/dts/am335x-igep0033.dtsi             |   1 -
 arch/arm/boot/dts/am335x-lxm.dts                   |  21 +-
 arch/arm/boot/dts/am335x-moxa-uc-8100-me-t.dts     |  52 +--
 arch/arm/boot/dts/am335x-nano.dts                  |   2 +-
 arch/arm/boot/dts/am335x-osd3358-sm-red.dts        |  62 ++--
 arch/arm/boot/dts/am335x-pepper.dts                |  68 ++--
 arch/arm/boot/dts/am335x-phycore-rdk.dts           |   1 -
 arch/arm/boot/dts/am335x-sancloud-bbe.dts          |   6 +-
 arch/arm/boot/dts/am335x-shc.dts                   |   2 +-
 arch/arm/boot/dts/am335x-sl50.dts                  |  50 +--
 arch/arm/boot/dts/am335x-wega.dtsi                 |  18 +-
 arch/arm/boot/dts/am3517-craneboard.dts            |   2 +-
 arch/arm/boot/dts/am3517-evm.dts                   |  68 ++--
 arch/arm/boot/dts/am3517-som.dtsi                  |  26 +-
 arch/arm/boot/dts/am3874-iceboard.dts              |  82 ++---
 arch/arm/boot/dts/am437x-cm-t43.dts                |  32 +-
 arch/arm/boot/dts/am437x-gp-evm.dts                | 238 ++++++-------
 arch/arm/boot/dts/am437x-idk-evm.dts               |  24 +-
 arch/arm/boot/dts/am437x-l4.dtsi                   |   1 -
 arch/arm/boot/dts/am43xx-clocks.dtsi               |   1 -
 arch/arm/boot/dts/am57xx-beagle-x15-common.dtsi    |   1 -
 arch/arm/boot/dts/armada-370-seagate-nas-4bay.dts  |   1 -
 arch/arm/boot/dts/armada-370-xp.dtsi               |   2 +-
 arch/arm/boot/dts/armada-375.dtsi                  |   1 -
 arch/arm/boot/dts/armada-388-rd.dts                |   1 -
 arch/arm/boot/dts/armada-xp-98dx3236.dtsi          |   1 -
 arch/arm/boot/dts/armada-xp-db-dxbc2.dts           |   1 -
 arch/arm/boot/dts/armada-xp-db-xc3-24g4xg.dts      |   1 -
 arch/arm/boot/dts/armada-xp-gp.dts                 |  14 +-
 arch/arm/boot/dts/armada-xp-lenovo-ix4-300d.dts    |   8 +-
 arch/arm/boot/dts/armada-xp-mv78230.dtsi           |  30 +-
 arch/arm/boot/dts/armada-xp-mv78260.dtsi           |  54 +--
 arch/arm/boot/dts/armada-xp-mv78460.dtsi           |  60 ++--
 arch/arm/boot/dts/at91-ariag25.dts                 |   1 -
 arch/arm/boot/dts/at91-dvk_som60.dts               |   1 -
 arch/arm/boot/dts/at91-dvk_su60_somc.dtsi          |   1 -
 arch/arm/boot/dts/at91-linea.dtsi                  |   1 -
 arch/arm/boot/dts/at91-sama5d2_xplained.dts        |   1 -
 arch/arm/boot/dts/at91-sama5d4_ma5d4evk.dts        |   2 -
 arch/arm/boot/dts/at91-vinco.dts                   |   2 -
 arch/arm/boot/dts/at91-wb45n.dtsi                  |   2 -
 arch/arm/boot/dts/at91-wb50n.dts                   |   1 -
 arch/arm/boot/dts/at91sam9g20ek_common.dtsi        |   2 -
 arch/arm/boot/dts/at91sam9x5cm.dtsi                |   1 -
 arch/arm/boot/dts/atlas6-evb.dts                   |  32 +-
 arch/arm/boot/dts/atlas6.dtsi                      | 368 ++++++++++-----------
 arch/arm/boot/dts/atlas7-evb.dts                   |   2 -
 arch/arm/boot/dts/atlas7.dtsi                      |   4 +-
 arch/arm/boot/dts/axm55xx.dtsi                     |   7 -
 arch/arm/boot/dts/bcm4708-buffalo-wzr-1750dhp.dts  |   1 -
 arch/arm/boot/dts/bcm4708.dtsi                     |   1 -
 arch/arm/boot/dts/bcm47081-buffalo-wzr-600dhp2.dts |   1 -
 arch/arm/boot/dts/bcm4709-buffalo-wxr-1900dhp.dts  |   1 -
 arch/arm/boot/dts/dra7-l4.dtsi                     |   1 -
 arch/arm/boot/dts/dra7xx-clocks.dtsi               |   8 +-
 arch/arm/boot/dts/evk-pro3.dts                     |   1 -
 arch/arm/boot/dts/exynos4412-ppmu-common.dtsi      |  48 +--
 arch/arm/boot/dts/exynos5410-pinctrl.dtsi          |   1 -
 arch/arm/boot/dts/exynos5422-odroidhc1.dts         |   1 -
 arch/arm/boot/dts/highbank.dts                     |   2 -
 arch/arm/boot/dts/imx23-sansa.dts                  |   1 -
 arch/arm/boot/dts/imx28-eukrea-mbmx283lc.dts       |   1 -
 arch/arm/boot/dts/imx28-evk.dts                    |   1 -
 arch/arm/boot/dts/imx28-sps1.dts                   |   1 -
 arch/arm/boot/dts/imx28-ts4600.dts                 |   4 -
 arch/arm/boot/dts/imx6dl-gw52xx.dts                |  26 +-
 arch/arm/boot/dts/imx6dl-gw53xx.dts                |  26 +-
 arch/arm/boot/dts/imx6dl-gw54xx.dts                |  26 +-
 arch/arm/boot/dts/imx6dl-mamoj.dts                 | 100 +++---
 arch/arm/boot/dts/imx6q-ba16.dtsi                  | 178 +++++-----
 arch/arm/boot/dts/imx6q-bx50v3.dtsi                |   8 +-
 arch/arm/boot/dts/imx6q-cm-fx6.dts                 |  46 +--
 arch/arm/boot/dts/imx6q-display5.dtsi              |  44 +--
 arch/arm/boot/dts/imx6q-dmo-edmqmx6.dts            |   8 +-
 arch/arm/boot/dts/imx6q-dms-ba16.dts               |  16 +-
 arch/arm/boot/dts/imx6q-evi.dts                    | 300 ++++++++---------
 arch/arm/boot/dts/imx6q-gw52xx.dts                 |  26 +-
 arch/arm/boot/dts/imx6q-gw53xx.dts                 |  26 +-
 arch/arm/boot/dts/imx6q-gw54xx.dts                 |  26 +-
 arch/arm/boot/dts/imx6q-kp.dtsi                    | 168 +++++-----
 arch/arm/boot/dts/imx6q-mccmon6.dts                |  24 +-
 arch/arm/boot/dts/imx6q-pistachio.dts              |  62 ++--
 arch/arm/boot/dts/imx6q-tbs2910.dts                | 128 +++----
 arch/arm/boot/dts/imx6q-utilite-pro.dts            | 116 +++----
 arch/arm/boot/dts/imx6qdl-apalis.dtsi              | 358 ++++++++++----------
 arch/arm/boot/dts/imx6qdl-apf6dev.dtsi             | 102 +++---
 arch/arm/boot/dts/imx6qdl-aristainetos.dtsi        | 180 +++++-----
 arch/arm/boot/dts/imx6qdl-aristainetos2.dtsi       | 174 +++++-----
 arch/arm/boot/dts/imx6qdl-colibri.dtsi             | 118 +++----
 arch/arm/boot/dts/imx6qdl-cubox-i.dtsi             |  42 +--
 arch/arm/boot/dts/imx6qdl-dfi-fs700-m60.dtsi       |  12 +-
 arch/arm/boot/dts/imx6qdl-emcon.dtsi               | 100 +++---
 arch/arm/boot/dts/imx6qdl-gw51xx.dtsi              | 140 ++++----
 arch/arm/boot/dts/imx6qdl-gw52xx.dtsi              |  10 +-
 arch/arm/boot/dts/imx6qdl-gw53xx.dtsi              |  10 +-
 arch/arm/boot/dts/imx6qdl-gw54xx.dtsi              |   8 +-
 arch/arm/boot/dts/imx6qdl-gw551x.dtsi              |   2 +-
 arch/arm/boot/dts/imx6qdl-gw553x.dtsi              | 158 ++++-----
 arch/arm/boot/dts/imx6qdl-gw5904.dtsi              |  16 +-
 arch/arm/boot/dts/imx6qdl-hummingboard.dtsi        |  54 +--
 arch/arm/boot/dts/imx6qdl-hummingboard2-emmc.dtsi  |  22 +-
 arch/arm/boot/dts/imx6qdl-hummingboard2.dtsi       | 164 ++++-----
 arch/arm/boot/dts/imx6qdl-icore-rqs.dtsi           | 184 +++++------
 arch/arm/boot/dts/imx6qdl-icore.dtsi               | 108 +++---
 arch/arm/boot/dts/imx6qdl-nit6xlite.dtsi           |  18 +-
 arch/arm/boot/dts/imx6qdl-nitrogen6_max.dtsi       | 116 +++----
 arch/arm/boot/dts/wm8750.dtsi                      | 110 +++---
 arch/arm/boot/dts/wm8850.dtsi                      |  54 +--
 120 files changed, 2648 insertions(+), 2713 deletions(-)
arch/arm/boot/dts/alpine-db.dts +0 -1
index dfb5a08..a6d7b23 100644
@@ -32,4 +32,3 @@
 	model = "Annapurna Labs Alpine Dev Board";
 	/* no need for anything outside SOC */
 };
-
arch/arm/boot/dts/am335x-baltos-ir2110.dts +8 -8
index 50dcf12..182d825 100644
@@ -23,14 +23,14 @@
 &am33xx_pinmux {
 	uart1_pins: pinmux_uart1_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x980, PIN_INPUT | MUX_MODE0)      /* uart1_rxd */
-			AM33XX_IOPAD(0x984, PIN_INPUT | MUX_MODE0)      /* uart1_txd */
-			AM33XX_IOPAD(0x978, PIN_INPUT_PULLDOWN | MUX_MODE0)      /* uart1_ctsn */
-			AM33XX_IOPAD(0x97c, PIN_OUTPUT_PULLDOWN | MUX_MODE0)      /* uart1_rtsn */
-			AM33XX_IOPAD(0x8e0, PIN_OUTPUT_PULLDOWN | MUX_MODE7)      /* lcd_vsync.gpio2[22] DTR */
-			AM33XX_IOPAD(0x8e4, PIN_INPUT_PULLDOWN | MUX_MODE7)      /* lcd_hsync.gpio2[23] DSR */
-			AM33XX_IOPAD(0x8e8, PIN_INPUT_PULLDOWN | MUX_MODE7)      /* lcd_pclk.gpio2[24] DCD */
-			AM33XX_IOPAD(0x8ec, PIN_INPUT_PULLDOWN | MUX_MODE7)      /* lcd_ac_bias_en.gpio2[25] RI */
+			AM33XX_IOPAD(0x980, PIN_INPUT | MUX_MODE0)		/* uart1_rxd */
+			AM33XX_IOPAD(0x984, PIN_INPUT | MUX_MODE0)		/* uart1_txd */
+			AM33XX_IOPAD(0x978, PIN_INPUT_PULLDOWN | MUX_MODE0)	/* uart1_ctsn */
+			AM33XX_IOPAD(0x97c, PIN_OUTPUT_PULLDOWN | MUX_MODE0)	/* uart1_rtsn */
+			AM33XX_IOPAD(0x8e0, PIN_OUTPUT_PULLDOWN | MUX_MODE7)	/* lcd_vsync.gpio2[22] DTR */
+			AM33XX_IOPAD(0x8e4, PIN_INPUT_PULLDOWN | MUX_MODE7)	/* lcd_hsync.gpio2[23] DSR */
+			AM33XX_IOPAD(0x8e8, PIN_INPUT_PULLDOWN | MUX_MODE7)	/* lcd_pclk.gpio2[24] DCD */
+			AM33XX_IOPAD(0x8ec, PIN_INPUT_PULLDOWN | MUX_MODE7)	/* lcd_ac_bias_en.gpio2[25] RI */
 		>;
 	};
 };
arch/arm/boot/dts/am335x-baltos-ir3220.dts +19 -19
index f3f1abd..9e7cec5 100644
@@ -23,35 +23,35 @@
 &am33xx_pinmux {
 	tca6416_pins: pinmux_tca6416_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x9b4, PIN_INPUT_PULLUP | MUX_MODE7)      /* xdma_event_intr1.gpio0[20] tca6416 stuff */
+			AM33XX_IOPAD(0x9b4, PIN_INPUT_PULLUP | MUX_MODE7)	/* xdma_event_intr1.gpio0[20] tca6416 stuff */
 		>;
 	};
 
 	uart1_pins: pinmux_uart1_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x980, PIN_INPUT | MUX_MODE0)      /* uart1_rxd */
-			AM33XX_IOPAD(0x984, PIN_INPUT | MUX_MODE0)      /* uart1_txd */
-			AM33XX_IOPAD(0x978, PIN_INPUT_PULLDOWN | MUX_MODE0)      /* uart1_ctsn */
-			AM33XX_IOPAD(0x97c, PIN_OUTPUT_PULLDOWN | MUX_MODE0)      /* uart1_rtsn */
-			AM33XX_IOPAD(0x8e0, PIN_OUTPUT_PULLDOWN | MUX_MODE7)      /* lcd_vsync.gpio2[22] DTR */
-			AM33XX_IOPAD(0x8e4, PIN_INPUT_PULLDOWN | MUX_MODE7)      /* lcd_hsync.gpio2[23] DSR */
-			AM33XX_IOPAD(0x8e8, PIN_INPUT_PULLDOWN | MUX_MODE7)      /* lcd_pclk.gpio2[24] DCD */
-			AM33XX_IOPAD(0x8ec, PIN_INPUT_PULLDOWN | MUX_MODE7)      /* lcd_ac_bias_en.gpio2[25] RI */
+			AM33XX_IOPAD(0x980, PIN_INPUT | MUX_MODE0)		/* uart1_rxd */
+			AM33XX_IOPAD(0x984, PIN_INPUT | MUX_MODE0)		/* uart1_txd */
+			AM33XX_IOPAD(0x978, PIN_INPUT_PULLDOWN | MUX_MODE0)	/* uart1_ctsn */
+			AM33XX_IOPAD(0x97c, PIN_OUTPUT_PULLDOWN | MUX_MODE0)	/* uart1_rtsn */
+			AM33XX_IOPAD(0x8e0, PIN_OUTPUT_PULLDOWN | MUX_MODE7)	/* lcd_vsync.gpio2[22] DTR */
+			AM33XX_IOPAD(0x8e4, PIN_INPUT_PULLDOWN | MUX_MODE7)	/* lcd_hsync.gpio2[23] DSR */
+			AM33XX_IOPAD(0x8e8, PIN_INPUT_PULLDOWN | MUX_MODE7)	/* lcd_pclk.gpio2[24] DCD */
+			AM33XX_IOPAD(0x8ec, PIN_INPUT_PULLDOWN | MUX_MODE7)	/* lcd_ac_bias_en.gpio2[25] RI */
 		>;
 	};
 
 	uart2_pins: pinmux_uart2_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x950, PIN_INPUT | MUX_MODE1)      /* spi0_sclk.uart2_rxd_mux3 */
-			AM33XX_IOPAD(0x954, PIN_OUTPUT | MUX_MODE1)      /* spi0_d0.uart2_txd_mux3 */
-			AM33XX_IOPAD(0x988, PIN_INPUT_PULLDOWN | MUX_MODE2)      /* i2c0_sda.uart2_ctsn_mux0 */
-			AM33XX_IOPAD(0x98c, PIN_OUTPUT_PULLDOWN | MUX_MODE2)      /* i2c0_scl.uart2_rtsn_mux0 */
-			AM33XX_IOPAD(0x830, PIN_OUTPUT_PULLDOWN | MUX_MODE7)      /* gpmc_ad12.gpio1[12] DTR */
-			AM33XX_IOPAD(0x834, PIN_INPUT_PULLDOWN | MUX_MODE7)      /* gpmc_ad13.gpio1[13] DSR */
-			AM33XX_IOPAD(0x838, PIN_INPUT_PULLDOWN | MUX_MODE7)      /* gpmc_ad14.gpio1[14] DCD */
-			AM33XX_IOPAD(0x83c, PIN_INPUT_PULLDOWN | MUX_MODE7)     /* gpmc_ad15.gpio1[15] RI */
-
-			AM33XX_IOPAD(0x9a0, PIN_INPUT_PULLUP | MUX_MODE7)      /* mcasp0_aclkr.gpio3[18], INPUT_PULLDOWN | MODE7 */
+			AM33XX_IOPAD(0x950, PIN_INPUT | MUX_MODE1)		/* spi0_sclk.uart2_rxd_mux3 */
+			AM33XX_IOPAD(0x954, PIN_OUTPUT | MUX_MODE1)		/* spi0_d0.uart2_txd_mux3 */
+			AM33XX_IOPAD(0x988, PIN_INPUT_PULLDOWN | MUX_MODE2)	/* i2c0_sda.uart2_ctsn_mux0 */
+			AM33XX_IOPAD(0x98c, PIN_OUTPUT_PULLDOWN | MUX_MODE2)	/* i2c0_scl.uart2_rtsn_mux0 */
+			AM33XX_IOPAD(0x830, PIN_OUTPUT_PULLDOWN | MUX_MODE7)	/* gpmc_ad12.gpio1[12] DTR */
+			AM33XX_IOPAD(0x834, PIN_INPUT_PULLDOWN | MUX_MODE7)	/* gpmc_ad13.gpio1[13] DSR */
+			AM33XX_IOPAD(0x838, PIN_INPUT_PULLDOWN | MUX_MODE7)	/* gpmc_ad14.gpio1[14] DCD */
+			AM33XX_IOPAD(0x83c, PIN_INPUT_PULLDOWN | MUX_MODE7)	/* gpmc_ad15.gpio1[15] RI */
+
+			AM33XX_IOPAD(0x9a0, PIN_INPUT_PULLUP | MUX_MODE7)	/* mcasp0_aclkr.gpio3[18], INPUT_PULLDOWN | MODE7 */
 		>;
 	};
 };
arch/arm/boot/dts/am335x-baltos-ir5221.dts +21 -21

64 lines not on this page · raw message

arch/arm/boot/dts/am335x-baltos.dtsi +20 -20
index 8c6fc41..a624a2e 100644
@@ -53,52 +53,52 @@
 &am33xx_pinmux {
 	mmc2_pins: pinmux_mmc2_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x820, PIN_INPUT_PULLUP | MUX_MODE2)      /* gpmc_ad8.mmc1_dat0_mux0 */
-			AM33XX_IOPAD(0x824, PIN_INPUT_PULLUP | MUX_MODE2)      /* gpmc_ad9.mmc1_dat1_mux0 */
-			AM33XX_IOPAD(0x828, PIN_INPUT_PULLUP | MUX_MODE2)      /* gpmc_ad10.mmc1_dat2_mux0 */
-			AM33XX_IOPAD(0x82c, PIN_INPUT_PULLUP | MUX_MODE2)      /* gpmc_ad11.mmc1_dat3_mux0 */
-			AM33XX_IOPAD(0x880, PIN_INPUT_PULLUP | MUX_MODE2)      /* gpmc_csn1.mmc1_clk_mux0 */
-			AM33XX_IOPAD(0x884, PIN_INPUT_PULLUP | MUX_MODE2)      /* gpmc_csn2.mmc1_cmd_mux0 */
-			AM33XX_IOPAD(0x9e4, PIN_INPUT_PULLUP | MUX_MODE7)      /* emu0.gpio3[7] */
+			AM33XX_IOPAD(0x820, PIN_INPUT_PULLUP | MUX_MODE2)	/* gpmc_ad8.mmc1_dat0_mux0 */
+			AM33XX_IOPAD(0x824, PIN_INPUT_PULLUP | MUX_MODE2)	/* gpmc_ad9.mmc1_dat1_mux0 */
+			AM33XX_IOPAD(0x828, PIN_INPUT_PULLUP | MUX_MODE2)	/* gpmc_ad10.mmc1_dat2_mux0 */
+			AM33XX_IOPAD(0x82c, PIN_INPUT_PULLUP | MUX_MODE2)	/* gpmc_ad11.mmc1_dat3_mux0 */
+			AM33XX_IOPAD(0x880, PIN_INPUT_PULLUP | MUX_MODE2)	/* gpmc_csn1.mmc1_clk_mux0 */
+			AM33XX_IOPAD(0x884, PIN_INPUT_PULLUP | MUX_MODE2)	/* gpmc_csn2.mmc1_cmd_mux0 */
+			AM33XX_IOPAD(0x9e4, PIN_INPUT_PULLUP | MUX_MODE7)	/* emu0.gpio3[7] */
 		>;
 	};
 
 	wl12xx_gpio: pinmux_wl12xx_gpio {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x9e8, PIN_OUTPUT_PULLUP | MUX_MODE7)      /* emu1.gpio3[8] */
+			AM33XX_IOPAD(0x9e8, PIN_OUTPUT_PULLUP | MUX_MODE7)	/* emu1.gpio3[8] */
 		>;
 	};
 
 	tps65910_pins: pinmux_tps65910_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x878, PIN_INPUT_PULLUP | MUX_MODE7)      /* gpmc_ben1.gpio1[28] */
+			AM33XX_IOPAD(0x878, PIN_INPUT_PULLUP | MUX_MODE7)	/* gpmc_ben1.gpio1[28] */
 		>;
 	};
 
 	i2c1_pins: pinmux_i2c1_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x958, PIN_INPUT | MUX_MODE2)      /* spi0_d1.i2c1_sda_mux3 */
-			AM33XX_IOPAD(0x95c, PIN_INPUT | MUX_MODE2)      /* spi0_cs0.i2c1_scl_mux3 */
+			AM33XX_IOPAD(0x958, PIN_INPUT | MUX_MODE2)		/* spi0_d1.i2c1_sda_mux3 */
+			AM33XX_IOPAD(0x95c, PIN_INPUT | MUX_MODE2)		/* spi0_cs0.i2c1_scl_mux3 */
 		>;
 	};
 
 	uart0_pins: pinmux_uart0_pins {
 		pinctrl-single,pins = <
 			AM33XX_IOPAD(0x970, PIN_INPUT_PULLUP | MUX_MODE0)	/* uart0_rxd.uart0_rxd */
-			AM33XX_IOPAD(0x974, PIN_OUTPUT_PULLDOWN | MUX_MODE0)		/* uart0_txd.uart0_txd */
+			AM33XX_IOPAD(0x974, PIN_OUTPUT_PULLDOWN | MUX_MODE0)	/* uart0_txd.uart0_txd */
 		>;
 	};
 
 	cpsw_default: cpsw_default {
 		pinctrl-single,pins = <
 			/* Slave 1 */
-			AM33XX_IOPAD(0x90c, PIN_INPUT_PULLDOWN | MUX_MODE1)       /* mii1_crs.rmii1_crs_dv */
-			AM33XX_IOPAD(0x914, PIN_OUTPUT_PULLDOWN | MUX_MODE1)      /* mii1_tx_en.rmii1_txen */
-			AM33XX_IOPAD(0x924, PIN_OUTPUT_PULLDOWN | MUX_MODE1)      /* mii1_txd1.rmii1_txd1 */
-			AM33XX_IOPAD(0x928, PIN_OUTPUT_PULLDOWN | MUX_MODE1)      /* mii1_txd0.rmii1_txd0 */
-			AM33XX_IOPAD(0x93c, PIN_INPUT_PULLDOWN | MUX_MODE1)      /* mii1_rxd1.rmii1_rxd1 */
-			AM33XX_IOPAD(0x940, PIN_INPUT_PULLDOWN | MUX_MODE1)      /* mii1_rxd0.rmii1_rxd0 */
-			AM33XX_IOPAD(0x944, PIN_INPUT_PULLDOWN | MUX_MODE0)      /* rmii1_ref_clk.rmii1_refclk */
+			AM33XX_IOPAD(0x90c, PIN_INPUT_PULLDOWN | MUX_MODE1)	/* mii1_crs.rmii1_crs_dv */
+			AM33XX_IOPAD(0x914, PIN_OUTPUT_PULLDOWN | MUX_MODE1)	/* mii1_tx_en.rmii1_txen */
+			AM33XX_IOPAD(0x924, PIN_OUTPUT_PULLDOWN | MUX_MODE1)	/* mii1_txd1.rmii1_txd1 */
+			AM33XX_IOPAD(0x928, PIN_OUTPUT_PULLDOWN | MUX_MODE1)	/* mii1_txd0.rmii1_txd0 */
+			AM33XX_IOPAD(0x93c, PIN_INPUT_PULLDOWN | MUX_MODE1)	/* mii1_rxd1.rmii1_rxd1 */
+			AM33XX_IOPAD(0x940, PIN_INPUT_PULLDOWN | MUX_MODE1)	/* mii1_rxd0.rmii1_rxd0 */
+			AM33XX_IOPAD(0x944, PIN_INPUT_PULLDOWN | MUX_MODE0)	/* rmii1_ref_clk.rmii1_refclk */
 
 
 			/* Slave 2 */
@@ -196,7 +196,7 @@
 		reg = <0 0 4>; /* CS0, offset 0, IO size 4 */
 		interrupt-parent = <&gpmc>;
 		interrupts = <0 IRQ_TYPE_NONE>, /* fifoevent */
-			     <1 IRQ_TYPE_NONE>;	/* termcount */
+			     <1 IRQ_TYPE_NONE>; /* termcount */
 		rb-gpios = <&gpmc 0 GPIO_ACTIVE_HIGH>; /* gpmc_wait0 */
 		nand-bus-width = <8>;
 		ti,nand-ecc-opt = "bch8";
arch/arm/boot/dts/am335x-bone-common.dtsi +10 -10
index 456eef5..7105144 100644
@@ -173,16 +173,16 @@
 
 	emmc_pins: pinmux_emmc_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x880, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_csn1.mmc1_clk */
-			AM33XX_IOPAD(0x884, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_csn2.mmc1_cmd */
-			AM33XX_IOPAD(0x800, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad0.mmc1_dat0 */
-			AM33XX_IOPAD(0x804, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad1.mmc1_dat1 */
-			AM33XX_IOPAD(0x808, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad2.mmc1_dat2 */
-			AM33XX_IOPAD(0x80c, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad3.mmc1_dat3 */
-			AM33XX_IOPAD(0x810, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad4.mmc1_dat4 */
-			AM33XX_IOPAD(0x814, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad5.mmc1_dat5 */
-			AM33XX_IOPAD(0x818, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad6.mmc1_dat6 */
-			AM33XX_IOPAD(0x81c, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad7.mmc1_dat7 */
+			AM33XX_IOPAD(0x880, PIN_INPUT_PULLUP | MUX_MODE2)	/* gpmc_csn1.mmc1_clk */
+			AM33XX_IOPAD(0x884, PIN_INPUT_PULLUP | MUX_MODE2)	/* gpmc_csn2.mmc1_cmd */
+			AM33XX_IOPAD(0x800, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad0.mmc1_dat0 */
+			AM33XX_IOPAD(0x804, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad1.mmc1_dat1 */
+			AM33XX_IOPAD(0x808, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad2.mmc1_dat2 */
+			AM33XX_IOPAD(0x80c, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad3.mmc1_dat3 */
+			AM33XX_IOPAD(0x810, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad4.mmc1_dat4 */
+			AM33XX_IOPAD(0x814, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad5.mmc1_dat5 */
+			AM33XX_IOPAD(0x818, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad6.mmc1_dat6 */
+			AM33XX_IOPAD(0x81c, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad7.mmc1_dat7 */
 		>;
 	};
 };
arch/arm/boot/dts/am335x-boneblack-common.dtsi +5 -5
index e543c2b..d4609bb 100644
@@ -62,11 +62,11 @@
 
 	mcasp0_pins: mcasp0_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x9ac, PIN_INPUT_PULLUP | MUX_MODE0) /* mcasp0_ahcklx.mcasp0_ahclkx */
-			AM33XX_IOPAD(0x99c, PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* mcasp0_ahclkr.mcasp0_axr2*/
-			AM33XX_IOPAD(0x994, PIN_OUTPUT_PULLUP | MUX_MODE0) /* mcasp0_fsx.mcasp0_fsx */
-			AM33XX_IOPAD(0x990, PIN_OUTPUT_PULLDOWN | MUX_MODE0) /* mcasp0_aclkx.mcasp0_aclkx */
-			AM33XX_IOPAD(0x86c, PIN_OUTPUT_PULLDOWN | MUX_MODE7) /* gpmc_a11.GPIO1_27 */
+			AM33XX_IOPAD(0x9ac, PIN_INPUT_PULLUP | MUX_MODE0)	/* mcasp0_ahcklx.mcasp0_ahclkx */
+			AM33XX_IOPAD(0x99c, PIN_OUTPUT_PULLDOWN | MUX_MODE2)	/* mcasp0_ahclkr.mcasp0_axr2*/
+			AM33XX_IOPAD(0x994, PIN_OUTPUT_PULLUP | MUX_MODE0)	/* mcasp0_fsx.mcasp0_fsx */
+			AM33XX_IOPAD(0x990, PIN_OUTPUT_PULLDOWN | MUX_MODE0)	/* mcasp0_aclkx.mcasp0_aclkx */
+			AM33XX_IOPAD(0x86c, PIN_OUTPUT_PULLDOWN | MUX_MODE7)	/* gpmc_a11.GPIO1_27 */
 		>;
 	};
 };
arch/arm/boot/dts/am335x-boneblack-wireless.dts +6 -6
index 83f49f6..9162fb9 100644
@@ -38,12 +38,12 @@
 
 	mmc3_pins: pinmux_mmc3_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x93c, PIN_INPUT_PULLUP | MUX_MODE6 ) /* (L15) gmii1_rxd1.mmc2_clk */
-			AM33XX_IOPAD(0x914, PIN_INPUT_PULLUP | MUX_MODE6 ) /* (J16) gmii1_txen.mmc2_cmd */
-			AM33XX_IOPAD(0x918, PIN_INPUT_PULLUP | MUX_MODE5 ) /* (J17) gmii1_rxdv.mmc2_dat0 */
-			AM33XX_IOPAD(0x91c, PIN_INPUT_PULLUP | MUX_MODE5 ) /* (J18) gmii1_txd3.mmc2_dat1 */
-			AM33XX_IOPAD(0x920, PIN_INPUT_PULLUP | MUX_MODE5 ) /* (K15) gmii1_txd2.mmc2_dat2 */
-			AM33XX_IOPAD(0x908, PIN_INPUT_PULLUP | MUX_MODE5 ) /* (H16) gmii1_col.mmc2_dat3 */
+			AM33XX_IOPAD(0x93c, PIN_INPUT_PULLUP | MUX_MODE6 )	/* (L15) gmii1_rxd1.mmc2_clk */
+			AM33XX_IOPAD(0x914, PIN_INPUT_PULLUP | MUX_MODE6 )	/* (J16) gmii1_txen.mmc2_cmd */
+			AM33XX_IOPAD(0x918, PIN_INPUT_PULLUP | MUX_MODE5 )	/* (J17) gmii1_rxdv.mmc2_dat0 */
+			AM33XX_IOPAD(0x91c, PIN_INPUT_PULLUP | MUX_MODE5 )	/* (J18) gmii1_txd3.mmc2_dat1 */
+			AM33XX_IOPAD(0x920, PIN_INPUT_PULLUP | MUX_MODE5 )	/* (K15) gmii1_txd2.mmc2_dat2 */
+			AM33XX_IOPAD(0x908, PIN_INPUT_PULLUP | MUX_MODE5 )	/* (H16) gmii1_col.mmc2_dat3 */
 		>;
 	};
 
arch/arm/boot/dts/am335x-chiliboard.dts +11 -11
index bffa5dc..6838821 100644
@@ -49,7 +49,7 @@
 	cpsw_default: cpsw_default {
 		pinctrl-single,pins = <
 			/* Slave 1 */
-			AM33XX_IOPAD(0x90c, PIN_INPUT_PULLDOWN | MUX_MODE1)  /* mii1_crs.rmii1_crs */
+			AM33XX_IOPAD(0x90c, PIN_INPUT_PULLDOWN | MUX_MODE1)	/* mii1_crs.rmii1_crs */
 			AM33XX_IOPAD(0x910, PIN_INPUT_PULLUP | MUX_MODE1)	/* mii1_rxerr.rmii1_rxerr */
 			AM33XX_IOPAD(0x914, PIN_OUTPUT_PULLDOWN | MUX_MODE1)	/* mii1_txen.rmii1_txen */
 			AM33XX_IOPAD(0x924, PIN_OUTPUT_PULLDOWN | MUX_MODE1)	/* mii1_txd1.rmii1_txd1 */
@@ -94,26 +94,26 @@
 
 	usb1_drvvbus: usb1_drvvbus {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0xa34, PIN_OUTPUT_PULLDOWN | MUX_MODE0) /* usb1_drvvbus.usb1_drvvbus */
+			AM33XX_IOPAD(0xa34, PIN_OUTPUT_PULLDOWN | MUX_MODE0)	/* usb1_drvvbus.usb1_drvvbus */
 		>;
 	};
 
 	sd_pins: pinmux_sd_card {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x8f0, PIN_INPUT | MUX_MODE0) /* mmc0_dat0.mmc0_dat0 */
-			AM33XX_IOPAD(0x8f4, PIN_INPUT | MUX_MODE0) /* mmc0_dat1.mmc0_dat1 */
-			AM33XX_IOPAD(0x8f8, PIN_INPUT | MUX_MODE0) /* mmc0_dat2.mmc0_dat2 */
-			AM33XX_IOPAD(0x8fc, PIN_INPUT | MUX_MODE0) /* mmc0_dat3.mmc0_dat3 */
-			AM33XX_IOPAD(0x900, PIN_INPUT | MUX_MODE0) /* mmc0_clk.mmc0_clk */
-			AM33XX_IOPAD(0x904, PIN_INPUT | MUX_MODE0) /* mmc0_cmd.mmc0_cmd */
-			AM33XX_IOPAD(0x960, PIN_INPUT | MUX_MODE7) /* spi0_cs1.gpio0_6 */
+			AM33XX_IOPAD(0x8f0, PIN_INPUT | MUX_MODE0)		/* mmc0_dat0.mmc0_dat0 */
+			AM33XX_IOPAD(0x8f4, PIN_INPUT | MUX_MODE0)		/* mmc0_dat1.mmc0_dat1 */
+			AM33XX_IOPAD(0x8f8, PIN_INPUT | MUX_MODE0)		/* mmc0_dat2.mmc0_dat2 */
+			AM33XX_IOPAD(0x8fc, PIN_INPUT | MUX_MODE0)		/* mmc0_dat3.mmc0_dat3 */
+			AM33XX_IOPAD(0x900, PIN_INPUT | MUX_MODE0)		/* mmc0_clk.mmc0_clk */
+			AM33XX_IOPAD(0x904, PIN_INPUT | MUX_MODE0)		/* mmc0_cmd.mmc0_cmd */
+			AM33XX_IOPAD(0x960, PIN_INPUT | MUX_MODE7)		/* spi0_cs1.gpio0_6 */
 		>;
 	};
 
 	led_gpio_pins: led_gpio_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x9e4, PIN_OUTPUT | MUX_MODE7) /* emu0.gpio3_7 */
-			AM33XX_IOPAD(0x9e8, PIN_OUTPUT | MUX_MODE7) /* emu1.gpio3_8 */
+			AM33XX_IOPAD(0x9e4, PIN_OUTPUT | MUX_MODE7)		/* emu0.gpio3_7 */
+			AM33XX_IOPAD(0x9e8, PIN_OUTPUT | MUX_MODE7)		/* emu1.gpio3_8 */
 		>;
 	};
 };
arch/arm/boot/dts/am335x-evm.dts +6 -6
index dce5be5..167b3a9 100644
@@ -368,10 +368,10 @@
 
 	mcasp1_pins: mcasp1_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x90c, PIN_INPUT_PULLDOWN | MUX_MODE4) /* mii1_crs.mcasp1_aclkx */
-			AM33XX_IOPAD(0x910, PIN_INPUT_PULLDOWN | MUX_MODE4) /* mii1_rxerr.mcasp1_fsx */
-			AM33XX_IOPAD(0x908, PIN_OUTPUT_PULLDOWN | MUX_MODE4) /* mii1_col.mcasp1_axr2 */
-			AM33XX_IOPAD(0x944, PIN_INPUT_PULLDOWN | MUX_MODE4) /* rmii1_ref_clk.mcasp1_axr3 */
+			AM33XX_IOPAD(0x90c, PIN_INPUT_PULLDOWN | MUX_MODE4)	/* mii1_crs.mcasp1_aclkx */
+			AM33XX_IOPAD(0x910, PIN_INPUT_PULLDOWN | MUX_MODE4)	/* mii1_rxerr.mcasp1_fsx */
+			AM33XX_IOPAD(0x908, PIN_OUTPUT_PULLDOWN | MUX_MODE4)	/* mii1_col.mcasp1_axr2 */
+			AM33XX_IOPAD(0x944, PIN_INPUT_PULLDOWN | MUX_MODE4)	/* rmii1_ref_clk.mcasp1_axr3 */
 		>;
 	};
 
@@ -386,8 +386,8 @@
 
 	dcan1_pins_default: dcan1_pins_default {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x968, PIN_OUTPUT | MUX_MODE2) /* uart0_ctsn.d_can1_tx */
-			AM33XX_IOPAD(0x96c, PIN_INPUT_PULLDOWN | MUX_MODE2) /* uart0_rtsn.d_can1_rx */
+			AM33XX_IOPAD(0x968, PIN_OUTPUT | MUX_MODE2)		/* uart0_ctsn.d_can1_tx */
+			AM33XX_IOPAD(0x96c, PIN_INPUT_PULLDOWN | MUX_MODE2)	/* uart0_rtsn.d_can1_rx */
 		>;
 	};
 };
arch/arm/boot/dts/am335x-evmsk.dts +28 -28

79 lines not on this page · raw message

arch/arm/boot/dts/am335x-icev2.dts +22 -22

70 lines not on this page · raw message

arch/arm/boot/dts/am335x-igep0033.dtsi +0 -1
index cbd22f2..af2b749 100644
@@ -325,4 +325,3 @@
 		};
 	};
 };
-
arch/arm/boot/dts/am335x-lxm.dts +10 -11
index d0e8e72..cd01d08 100644
@@ -132,16 +132,16 @@
 
 	emmc_pins: pinmux_emmc_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x880, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_csn1.mmc1_clk */
-			AM33XX_IOPAD(0x884, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_csn2.mmc1_cmd */
-			AM33XX_IOPAD(0x800, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad0.mmc1_dat0 */
-			AM33XX_IOPAD(0x804, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad1.mmc1_dat1 */
-			AM33XX_IOPAD(0x808, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad2.mmc1_dat2 */
-			AM33XX_IOPAD(0x80c, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad3.mmc1_dat3 */
-			AM33XX_IOPAD(0x810, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad4.mmc1_dat4 */
-			AM33XX_IOPAD(0x814, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad5.mmc1_dat5 */
-			AM33XX_IOPAD(0x818, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad6.mmc1_dat6 */
-			AM33XX_IOPAD(0x81c, PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad7.mmc1_dat7 */
+			AM33XX_IOPAD(0x880, PIN_INPUT_PULLUP | MUX_MODE2)	/* gpmc_csn1.mmc1_clk */
+			AM33XX_IOPAD(0x884, PIN_INPUT_PULLUP | MUX_MODE2)	/* gpmc_csn2.mmc1_cmd */
+			AM33XX_IOPAD(0x800, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad0.mmc1_dat0 */
+			AM33XX_IOPAD(0x804, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad1.mmc1_dat1 */
+			AM33XX_IOPAD(0x808, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad2.mmc1_dat2 */
+			AM33XX_IOPAD(0x80c, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad3.mmc1_dat3 */
+			AM33XX_IOPAD(0x810, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad4.mmc1_dat4 */
+			AM33XX_IOPAD(0x814, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad5.mmc1_dat5 */
+			AM33XX_IOPAD(0x818, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad6.mmc1_dat6 */
+			AM33XX_IOPAD(0x81c, PIN_INPUT_PULLUP | MUX_MODE1)	/* gpmc_ad7.mmc1_dat7 */
 		>;
 	};
 
@@ -367,4 +367,3 @@
 	ti,non-removable;
 	status = "okay";
 };
-
arch/arm/boot/dts/am335x-moxa-uc-8100-me-t.dts +26 -26

90 lines not on this page · raw message

arch/arm/boot/dts/am335x-nano.dts +1 -1
index 9c9143e..0d129b6 100644
@@ -41,7 +41,7 @@
 
 	misc_pins: misc_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x95c, PIN_OUTPUT | MUX_MODE7)	/* spi0_cs0.gpio0_5 */
+			AM33XX_IOPAD(0x95c, PIN_OUTPUT | MUX_MODE7)		/* spi0_cs0.gpio0_5 */
 		>;
 	};
 
arch/arm/boot/dts/am335x-osd3358-sm-red.dts +31 -31

105 lines not on this page · raw message

arch/arm/boot/dts/am335x-pepper.dts +34 -34

92 lines not on this page · raw message

arch/arm/boot/dts/am335x-phycore-rdk.dts +0 -1
index 305f0b3..2b2ada6 100644
@@ -23,5 +23,4 @@
 
 &serial_flash {
 	status = "okay";
-
 };
arch/arm/boot/dts/am335x-sancloud-bbe.dts +3 -3
index 35527fd..e6d2ce6 100644
@@ -74,19 +74,19 @@
 
 	usb_hub_ctrl: usb_hub_ctrl {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x944, PIN_OUTPUT_PULLUP | MUX_MODE7)     /* rmii1_refclk.gpio0_29 */
+			AM33XX_IOPAD(0x944, PIN_OUTPUT_PULLUP | MUX_MODE7)	/* rmii1_refclk.gpio0_29 */
 		>;
 	};
 
 	mpu6050_pins: pinmux_mpu6050_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x968, PIN_INPUT | MUX_MODE7)    /* uart0_ctsn.gpio1_8 */
+			AM33XX_IOPAD(0x968, PIN_INPUT | MUX_MODE7)		/* uart0_ctsn.gpio1_8 */
 		>;
 	};
 
 	lps3331ap_pins: pinmux_lps3331ap_pins {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x868, PIN_INPUT | MUX_MODE7)     /* gpmc_a10.gpio1_26 */
+			AM33XX_IOPAD(0x868, PIN_INPUT | MUX_MODE7)		/* gpmc_a10.gpio1_26 */
 		>;
 	};
 };
arch/arm/boot/dts/am335x-shc.dts +1 -1
index bfbe27a..58c060e 100644
@@ -443,7 +443,7 @@
 
 	ehrpwm1_pins: pinmux_ehrpwm1 {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x84c, PIN_OUTPUT | MUX_MODE6) /* gpmc_a3.gpio1_19 */
+			AM33XX_IOPAD(0x84c, PIN_OUTPUT | MUX_MODE6)		/* gpmc_a3.gpio1_19 */
 		>;
 	};
 
arch/arm/boot/dts/am335x-sl50.dts +25 -25

83 lines not on this page · raw message

arch/arm/boot/dts/am335x-wega.dtsi +9 -9
index 8ce5417..d497578 100644
@@ -32,11 +32,11 @@
 &am33xx_pinmux {
 	mcasp0_pins: pinmux_mcasp0 {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x9AC, PIN_OUTPUT_PULLDOWN | MUX_MODE0) /* mcasp0_ahclkx.mcasp0_ahclkx */
-			AM33XX_IOPAD(0x990, PIN_INPUT_PULLDOWN | MUX_MODE0)  /* mcasp0_aclkx.mcasp0_aclkx */
-			AM33XX_IOPAD(0x994, PIN_INPUT_PULLDOWN | MUX_MODE0)  /* mcasp0_fsx.mcasp0_fsx */
-			AM33XX_IOPAD(0x998, PIN_INPUT_PULLDOWN | MUX_MODE0)  /* mcasp0_axr0.mcasp0_axr0 */
-			AM33XX_IOPAD(0x9A8, PIN_OUTPUT_PULLDOWN | MUX_MODE0) /* mcasp0_axr1.mcasp0_axr1 */
+			AM33XX_IOPAD(0x9AC, PIN_OUTPUT_PULLDOWN | MUX_MODE0)	/* mcasp0_ahclkx.mcasp0_ahclkx */
+			AM33XX_IOPAD(0x990, PIN_INPUT_PULLDOWN | MUX_MODE0)	/* mcasp0_aclkx.mcasp0_aclkx */
+			AM33XX_IOPAD(0x994, PIN_INPUT_PULLDOWN | MUX_MODE0)	/* mcasp0_fsx.mcasp0_fsx */
+			AM33XX_IOPAD(0x998, PIN_INPUT_PULLDOWN | MUX_MODE0)	/* mcasp0_axr0.mcasp0_axr0 */
+			AM33XX_IOPAD(0x9A8, PIN_OUTPUT_PULLDOWN | MUX_MODE0)	/* mcasp0_axr1.mcasp0_axr1 */
 		>;
 	};
 };
@@ -84,8 +84,8 @@
 &am33xx_pinmux {
 	dcan1_pins: pinmux_dcan1 {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x968, PIN_OUTPUT_PULLUP | MUX_MODE2) /* uart0_ctsn.d_can1_tx */
-			AM33XX_IOPAD(0x96c, PIN_INPUT_PULLUP | MUX_MODE2) /* uart0_rtsn.d_can1_rx */
+			AM33XX_IOPAD(0x968, PIN_OUTPUT_PULLUP | MUX_MODE2)	/* uart0_ctsn.d_can1_tx */
+			AM33XX_IOPAD(0x96c, PIN_INPUT_PULLUP | MUX_MODE2)	/* uart0_rtsn.d_can1_rx */
 		>;
 	};
 };
@@ -171,8 +171,8 @@
 &am33xx_pinmux {
 	uart0_pins: pinmux_uart0 {
 		pinctrl-single,pins = <
-			AM33XX_IOPAD(0x970, PIN_INPUT_PULLUP | MUX_MODE0)    /* uart0_rxd.uart0_rxd */
-			AM33XX_IOPAD(0x974, PIN_OUTPUT_PULLDOWN | MUX_MODE0) /* uart0_txd.uart0_txd */
+			AM33XX_IOPAD(0x970, PIN_INPUT_PULLUP | MUX_MODE0)	/* uart0_rxd.uart0_rxd */
+			AM33XX_IOPAD(0x974, PIN_OUTPUT_PULLDOWN | MUX_MODE0)	/* uart0_txd.uart0_txd */
 		>;
 	};
 
arch/arm/boot/dts/am3517-craneboard.dts +1 -1
index 083ff50..8323ec5 100644
@@ -77,7 +77,7 @@
 &omap3_pmx_core {
 	tps_pins: pinmux_tps_pins {
 		pinctrl-single,pins = <
-			OMAP3_CORE1_IOPAD(0x21e0, PIN_INPUT_PULLUP | MUX_MODE0) /* sys_nirq.sys_nirq */
+			OMAP3_CORE1_IOPAD(0x21e0, PIN_INPUT_PULLUP | MUX_MODE0)	/* sys_nirq.sys_nirq */
 		>;
 	};
 };
arch/arm/boot/dts/am3517-evm.dts +34 -34

110 lines not on this page · raw message

arch/arm/boot/dts/am3517-som.dtsi +13 -13
index b1c988e..53f09b3 100644
@@ -184,35 +184,35 @@
 
 	wl12xx_buffer_pins: pinmux_wl12xx_buffer_pins {
 		pinctrl-single,pins = <
-			OMAP3_CORE1_IOPAD(0x2156, PIN_OUTPUT | MUX_MODE4)  /* mmc1_dat7.gpio_129 */
+			OMAP3_CORE1_IOPAD(0x2156, PIN_OUTPUT | MUX_MODE4)	/* mmc1_dat7.gpio_129 */
 		>;
 	};
 
 	mmc2_pins: pinmux_mmc2_pins {
 		pinctrl-single,pins = <
-			OMAP3_CORE1_IOPAD(0x2158, PIN_INPUT_PULLUP | MUX_MODE0)  /* mmc2_clk.mmc2_clk */
-			OMAP3_CORE1_IOPAD(0x215a, PIN_INPUT_PULLUP | MUX_MODE0)  /* mmc2_cmd.mmc2_cmd */
-			OMAP3_CORE1_IOPAD(0x215c, PIN_INPUT_PULLUP | MUX_MODE0)  /* mmc2_dat0.mmc2_dat0 */
-			OMAP3_CORE1_IOPAD(0x215e, PIN_INPUT_PULLUP | MUX_MODE0)  /* mmc2_dat1.mmc2_dat1 */
-			OMAP3_CORE1_IOPAD(0x2160, PIN_INPUT_PULLUP | MUX_MODE0)  /* mmc2_dat2.mmc2_dat2 */
-			OMAP3_CORE1_IOPAD(0x2162, PIN_INPUT_PULLUP | MUX_MODE0)  /* mmc2_dat3.mmc2_dat3 */
-			OMAP3_CORE1_IOPAD(0x2164, PIN_OUTPUT | MUX_MODE1) /* mmc2_dat4.mmc2_dir_dat0 */
-			OMAP3_CORE1_IOPAD(0x2166, PIN_OUTPUT | MUX_MODE1) /* mmc2_dat5.mmc2_dir_dat1 */
-			OMAP3_CORE1_IOPAD(0x2168, PIN_OUTPUT | MUX_MODE1) /* mmc2_dat6.mmc2_dir_cmd */
-			OMAP3_CORE1_IOPAD(0x216a, PIN_INPUT | MUX_MODE1) /* mmc2_dat7.mmc2_clkin */
+			OMAP3_CORE1_IOPAD(0x2158, PIN_INPUT_PULLUP | MUX_MODE0)	/* mmc2_clk.mmc2_clk */
+			OMAP3_CORE1_IOPAD(0x215a, PIN_INPUT_PULLUP | MUX_MODE0)	/* mmc2_cmd.mmc2_cmd */
+			OMAP3_CORE1_IOPAD(0x215c, PIN_INPUT_PULLUP | MUX_MODE0)	/* mmc2_dat0.mmc2_dat0 */
+			OMAP3_CORE1_IOPAD(0x215e, PIN_INPUT_PULLUP | MUX_MODE0)	/* mmc2_dat1.mmc2_dat1 */
+			OMAP3_CORE1_IOPAD(0x2160, PIN_INPUT_PULLUP | MUX_MODE0)	/* mmc2_dat2.mmc2_dat2 */
+			OMAP3_CORE1_IOPAD(0x2162, PIN_INPUT_PULLUP | MUX_MODE0)	/* mmc2_dat3.mmc2_dat3 */
+			OMAP3_CORE1_IOPAD(0x2164, PIN_OUTPUT | MUX_MODE1)	/* mmc2_dat4.mmc2_dir_dat0 */
+			OMAP3_CORE1_IOPAD(0x2166, PIN_OUTPUT | MUX_MODE1)	/* mmc2_dat5.mmc2_dir_dat1 */
+			OMAP3_CORE1_IOPAD(0x2168, PIN_OUTPUT | MUX_MODE1)	/* mmc2_dat6.mmc2_dir_cmd */
+			OMAP3_CORE1_IOPAD(0x216a, PIN_INPUT | MUX_MODE1)	/* mmc2_dat7.mmc2_clkin */
 			OMAP3_CORE1_IOPAD(0x21c6, PIN_INPUT_PULLUP | MUX_MODE4)	/* hdq_sio.gpio_170 */
 		>;
 	};
 
 	rtc_pins: pinmux_rtc_pins {
 		pinctrl-single,pins = <
-			OMAP3_CORE1_IOPAD(0x20b6, PIN_INPUT_PULLUP | MUX_MODE4) /* gpmc_ncs4.gpio_55 */
+			OMAP3_CORE1_IOPAD(0x20b6, PIN_INPUT_PULLUP | MUX_MODE4)	/* gpmc_ncs4.gpio_55 */
 		>;
 	};
 
 	tsc2004_pins: pinmux_tsc2004_pins {
 		pinctrl-single,pins = <
-			OMAP3_CORE1_IOPAD(0x20d2, PIN_INPUT | MUX_MODE4) /* gpmc_wait3.gpio_65 */
+			OMAP3_CORE1_IOPAD(0x20d2, PIN_INPUT | MUX_MODE4)	/* gpmc_wait3.gpio_65 */
 		>;
 	};
 
arch/arm/boot/dts/am3874-iceboard.dts +41 -41

125 lines not on this page · raw message

arch/arm/boot/dts/am437x-cm-t43.dts +16 -16
index 4fcf647..c609cba 100644
@@ -49,32 +49,32 @@
 
 	i2c0_pins: i2c0_pins {
 		pinctrl-single,pins = <
-			AM4372_IOPAD(0x988, PIN_INPUT_PULLUP | SLEWCTRL_FAST | MUX_MODE0)  /* i2c0_sda.i2c0_sda */
-			AM4372_IOPAD(0x98c, PIN_INPUT_PULLUP | SLEWCTRL_FAST | MUX_MODE0)  /* i2c0_scl.i2c0_scl */
+			AM4372_IOPAD(0x988, PIN_INPUT_PULLUP | SLEWCTRL_FAST | MUX_MODE0)	/* i2c0_sda.i2c0_sda */
+			AM4372_IOPAD(0x98c, PIN_INPUT_PULLUP | SLEWCTRL_FAST | MUX_MODE0)	/* i2c0_scl.i2c0_scl */
 		>;
 	};
 
 	emmc_pins: emmc_pins {
 		pinctrl-single,pins = <
-			AM4372_IOPAD(0x820, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_ad8.mmc1_dat0 */
-			AM4372_IOPAD(0x824, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_ad9.mmc1_dat1 */
-			AM4372_IOPAD(0x828, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_ad10.mmc1_dat2 */
-			AM4372_IOPAD(0x82c, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_ad11.mmc1_dat3 */
-			AM4372_IOPAD(0x830, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_ad12.mmc1_dat4 */
-			AM4372_IOPAD(0x834, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_ad13.mmc1_dat5 */
-			AM4372_IOPAD(0x838, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_ad14.mmc1_dat6 */
-			AM4372_IOPAD(0x83c, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_ad15.mmc1_dat7 */
-			AM4372_IOPAD(0x880, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_csn1.mmc1_clk */
-			AM4372_IOPAD(0x884, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_csn2.mmc1_cmd */
+			AM4372_IOPAD(0x820, PIN_INPUT_PULLUP | MUX_MODE2)			/* gpmc_ad8.mmc1_dat0 */
+			AM4372_IOPAD(0x824, PIN_INPUT_PULLUP | MUX_MODE2)			/* gpmc_ad9.mmc1_dat1 */
+			AM4372_IOPAD(0x828, PIN_INPUT_PULLUP | MUX_MODE2)			/* gpmc_ad10.mmc1_dat2 */
+			AM4372_IOPAD(0x82c, PIN_INPUT_PULLUP | MUX_MODE2)			/* gpmc_ad11.mmc1_dat3 */
+			AM4372_IOPAD(0x830, PIN_INPUT_PULLUP | MUX_MODE2)			/* gpmc_ad12.mmc1_dat4 */
+			AM4372_IOPAD(0x834, PIN_INPUT_PULLUP | MUX_MODE2)			/* gpmc_ad13.mmc1_dat5 */
+			AM4372_IOPAD(0x838, PIN_INPUT_PULLUP | MUX_MODE2)			/* gpmc_ad14.mmc1_dat6 */
+			AM4372_IOPAD(0x83c, PIN_INPUT_PULLUP | MUX_MODE2)			/* gpmc_ad15.mmc1_dat7 */
+			AM4372_IOPAD(0x880, PIN_INPUT_PULLUP | MUX_MODE2)			/* gpmc_csn1.mmc1_clk */
+			AM4372_IOPAD(0x884, PIN_INPUT_PULLUP | MUX_MODE2)			/* gpmc_csn2.mmc1_cmd */
 		>;
 	};
 
 	spi0_pins: pinmux_spi0_pins {
 		pinctrl-single,pins = <
-			AM4372_IOPAD(0x950, PIN_INPUT | MUX_MODE0) /* spi0_sclk.spi0_sclk */
-			AM4372_IOPAD(0x954, PIN_INPUT | MUX_MODE0) /* spi0_d0.spi0_d0 */
-			AM4372_IOPAD(0x958, PIN_OUTPUT | MUX_MODE0) /* spi0_d1.spi0_d1 */
-			AM4372_IOPAD(0x95C, PIN_OUTPUT | MUX_MODE0) /* spi0_cs0.spi0_cs0 */
+			AM4372_IOPAD(0x950, PIN_INPUT | MUX_MODE0)			/* spi0_sclk.spi0_sclk */
+			AM4372_IOPAD(0x954, PIN_INPUT | MUX_MODE0)			/* spi0_d0.spi0_d0 */
+			AM4372_IOPAD(0x958, PIN_OUTPUT | MUX_MODE0)			/* spi0_d1.spi0_d1 */
+			AM4372_IOPAD(0x95C, PIN_OUTPUT | MUX_MODE0)			/* spi0_cs0.spi0_cs0 */
 		>;
 	};
 
arch/arm/boot/dts/am437x-gp-evm.dts +119 -119

354 lines not on this page · raw message

arch/arm/boot/dts/am437x-idk-evm.dts +12 -12
index bb28540..f99957c 100644
@@ -178,14 +178,14 @@
 &am43xx_pinmux {
 	gpio_keys_pins_default: gpio_keys_pins_default {
 		pinctrl-single,pins = <
-			AM4372_IOPAD(0x9b8, PIN_INPUT | MUX_MODE7)	/* cam0_field.gpio4_2 */
+			AM4372_IOPAD(0x9b8, PIN_INPUT | MUX_MODE7)			/* cam0_field.gpio4_2 */
 		>;
 	};
 
 	i2c0_pins_default: i2c0_pins_default {
 		pinctrl-single,pins = <
-			AM4372_IOPAD(0x988, PIN_INPUT | SLEWCTRL_FAST | MUX_MODE0) /* i2c0_sda.i2c0_sda */
-			AM4372_IOPAD(0x98c, PIN_INPUT | SLEWCTRL_FAST | MUX_MODE0) /* i2c0_scl.i2c0_scl */
+			AM4372_IOPAD(0x988, PIN_INPUT | SLEWCTRL_FAST | MUX_MODE0)	/* i2c0_sda.i2c0_sda */
+			AM4372_IOPAD(0x98c, PIN_INPUT | SLEWCTRL_FAST | MUX_MODE0)	/* i2c0_scl.i2c0_scl */
 		>;
 	};
 
@@ -198,8 +198,8 @@
 
 	i2c2_pins_default: i2c2_pins_default {
 		pinctrl-single,pins = <
-			AM4372_IOPAD(0x9e8, PIN_INPUT | SLEWCTRL_FAST | MUX_MODE3) /* cam1_data1.i2c2_scl */
-			AM4372_IOPAD(0x9ec, PIN_INPUT | SLEWCTRL_FAST | MUX_MODE3) /* cam1_data0.i2c2_sda */
+			AM4372_IOPAD(0x9e8, PIN_INPUT | SLEWCTRL_FAST | MUX_MODE3)	/* cam1_data1.i2c2_scl */
+			AM4372_IOPAD(0x9ec, PIN_INPUT | SLEWCTRL_FAST | MUX_MODE3)	/* cam1_data0.i2c2_sda */
 		>;
 	};
 
@@ -212,13 +212,13 @@
 
 	mmc1_pins_default: pinmux_mmc1_pins_default {
 		pinctrl-single,pins = <
-			AM4372_IOPAD(0x900, PIN_INPUT | MUX_MODE0) /* mmc0_clk.mmc0_clk */
-			AM4372_IOPAD(0x904, PIN_INPUT | MUX_MODE0) /* mmc0_cmd.mmc0_cmd */
-			AM4372_IOPAD(0x9f0, PIN_INPUT | MUX_MODE0) /* mmc0_dat3.mmc0_dat3 */
-			AM4372_IOPAD(0x9f4, PIN_INPUT | MUX_MODE0) /* mmc0_dat2.mmc0_dat2 */
-			AM4372_IOPAD(0x9f8, PIN_INPUT | MUX_MODE0) /* mmc0_dat1.mmc0_dat1 */
-			AM4372_IOPAD(0x9fc, PIN_INPUT | MUX_MODE0) /* mmc0_dat0.mmc0_dat0 */
-			AM4372_IOPAD(0x960, PIN_INPUT | MUX_MODE7) /* spi0_cs1.gpio0_6 */
+			AM4372_IOPAD(0x900, PIN_INPUT | MUX_MODE0)	/* mmc0_clk.mmc0_clk */
+			AM4372_IOPAD(0x904, PIN_INPUT | MUX_MODE0)	/* mmc0_cmd.mmc0_cmd */
+			AM4372_IOPAD(0x9f0, PIN_INPUT | MUX_MODE0)	/* mmc0_dat3.mmc0_dat3 */
+			AM4372_IOPAD(0x9f4, PIN_INPUT | MUX_MODE0)	/* mmc0_dat2.mmc0_dat2 */
+			AM4372_IOPAD(0x9f8, PIN_INPUT | MUX_MODE0)	/* mmc0_dat1.mmc0_dat1 */
+			AM4372_IOPAD(0x9fc, PIN_INPUT | MUX_MODE0)	/* mmc0_dat0.mmc0_dat0 */
+			AM4372_IOPAD(0x960, PIN_INPUT | MUX_MODE7)	/* spi0_cs1.gpio0_6 */
 		>;
 	};
 
arch/arm/boot/dts/am437x-l4.dtsi +0 -1
index 85c6f4f..3391218 100644
@@ -2503,4 +2503,3 @@
 		};
 	};
 };
-
arch/arm/boot/dts/am43xx-clocks.dtsi +0 -1
index e3f4207..edc46cce 100644
@@ -827,6 +827,5 @@
 			reg = <0xb20 0x4>;
 			#clock-cells = <2>;
 		};
-
 	};
 };
arch/arm/boot/dts/am57xx-beagle-x15-common.dtsi +0 -1
index 1e6620f..b6a6daf 100644
@@ -333,7 +333,6 @@
 			ti,enable-vbus-detection;
 			vbus-gpio = <&gpio4 21 GPIO_ACTIVE_HIGH>;
 		};
-
 	};
 
 	tmp102: tmp102@48 {
arch/arm/boot/dts/armada-370-seagate-nas-4bay.dts +0 -1
index 3cf70c7..539f9b6 100644
@@ -128,4 +128,3 @@
 		reg = <1>;
 	};
 };
-
arch/arm/boot/dts/armada-370-xp.dtsi +1 -1
index c15f5e9..4344eb8 100644
@@ -312,4 +312,4 @@
 			clock-frequency = <2000000000>;
 		};
 	};
- };
+};
arch/arm/boot/dts/armada-375.dtsi +0 -1
index 2932a29..9532ca9 100644
@@ -599,7 +599,6 @@
 				clocks = <&gateclk 6>;
 				status = "disabled";
 			};
-
 		};
 
 		crypto_sram0: sa-sram0 {
arch/arm/boot/dts/armada-388-rd.dts +0 -1
index 328a4d6..82951c7 100644
@@ -105,4 +105,3 @@
 		spi-max-frequency = <108000000>;
 	};
 };
-
arch/arm/boot/dts/armada-xp-98dx3236.dtsi +0 -1
index 5975347..ccc61e2 100644
@@ -335,4 +335,3 @@
 &sdio {
 	status = "disabled";
 };
-
arch/arm/boot/dts/armada-xp-db-dxbc2.dts +0 -1
index 8a3aa61..d18855b 100644
@@ -113,6 +113,5 @@
 			reg = <0x00140000 0x00ec0000>;
 			label = "unused";
 		};
-
 	};
 };
arch/arm/boot/dts/armada-xp-db-xc3-24g4xg.dts +0 -1
index df04805..0e0de21 100644
@@ -104,6 +104,5 @@
 			reg = <0x00140000 0x00ec0000>;
 			label = "unused";
 		};
-
 	};
 };
arch/arm/boot/dts/armada-xp-gp.dts +7 -7
index b4cca50..6f8f88f 100644
@@ -34,13 +34,13 @@
 	memory@0 {
 		device_type = "memory";
 		/*
-                 * 8 GB of plug-in RAM modules by default.The amount
-                 * of memory available can be changed by the
-                 * bootloader according the size of the module
-                 * actually plugged. However, memory between
-                 * 0xF0000000 to 0xFFFFFFFF cannot be used, as it is
-                 * the address range used for I/O (internal registers,
-                 * MBus windows).
+		 * 8 GB of plug-in RAM modules by default.The amount
+		 * of memory available can be changed by the
+		 * bootloader according the size of the module
+		 * actually plugged. However, memory between
+		 * 0xF0000000 to 0xFFFFFFFF cannot be used, as it is
+		 * the address range used for I/O (internal registers,
+		 * MBus windows).
 		 */
 		reg = <0x00000000 0x00000000 0x00000000 0xf0000000>,
 		      <0x00000001 0x00000000 0x00000001 0x00000000>;
arch/arm/boot/dts/armada-xp-lenovo-ix4-300d.dts +3 -5
index 87dcb50..7499402 100644
@@ -27,9 +27,9 @@
 
 	soc {
 		ranges = <MBUS_ID(0xf0, 0x01) 0 0 0xd0000000 0x100000
-			MBUS_ID(0x01, 0x1d) 0 0 0xfff00000 0x100000
-			MBUS_ID(0x09, 0x09) 0 0 0xf1100000 0x10000
-			MBUS_ID(0x09, 0x05) 0 0 0xf1110000 0x10000>;
+			  MBUS_ID(0x01, 0x1d) 0 0 0xfff00000 0x100000
+			  MBUS_ID(0x09, 0x09) 0 0 0xf1100000 0x10000
+			  MBUS_ID(0x09, 0x05) 0 0 0xf1110000 0x10000>;
 
 		internal-regs {
 			serial@12000 {
@@ -78,7 +78,6 @@
 					compatible = "nxp,pcf8563";
 					reg = <0x51>;
 				};
-
 			};
 
 			nand-controller@d0000 {
@@ -220,7 +219,6 @@
 			gpios = <&gpio_spi 4 GPIO_ACTIVE_HIGH>;
 			default-state = "off";
 		};
-
 	};
 
 	/*
arch/arm/boot/dts/armada-xp-mv78230.dtsi +15 -15
index 8558bf6..04f526c 100644
@@ -61,21 +61,21 @@
 			bus-range = <0x00 0xff>;
 
 			ranges =
-			       <0x82000000 0 0x40000 MBUS_ID(0xf0, 0x01) 0x40000 0 0x00002000   /* Port 0.0 registers */
-				0x82000000 0 0x44000 MBUS_ID(0xf0, 0x01) 0x44000 0 0x00002000   /* Port 0.1 registers */
-				0x82000000 0 0x48000 MBUS_ID(0xf0, 0x01) 0x48000 0 0x00002000   /* Port 0.2 registers */
-				0x82000000 0 0x4c000 MBUS_ID(0xf0, 0x01) 0x4c000 0 0x00002000   /* Port 0.3 registers */
-				0x82000000 0 0x80000 MBUS_ID(0xf0, 0x01) 0x80000 0 0x00002000   /* Port 1.0 registers */
-				0x82000000 0x1 0       MBUS_ID(0x04, 0xe8) 0 1 0 /* Port 0.0 MEM */
-				0x81000000 0x1 0       MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO  */
-				0x82000000 0x2 0       MBUS_ID(0x04, 0xd8) 0 1 0 /* Port 0.1 MEM */
-				0x81000000 0x2 0       MBUS_ID(0x04, 0xd0) 0 1 0 /* Port 0.1 IO  */
-				0x82000000 0x3 0       MBUS_ID(0x04, 0xb8) 0 1 0 /* Port 0.2 MEM */
-				0x81000000 0x3 0       MBUS_ID(0x04, 0xb0) 0 1 0 /* Port 0.2 IO  */
-				0x82000000 0x4 0       MBUS_ID(0x04, 0x78) 0 1 0 /* Port 0.3 MEM */
-				0x81000000 0x4 0       MBUS_ID(0x04, 0x70) 0 1 0 /* Port 0.3 IO  */
-				0x82000000 0x5 0       MBUS_ID(0x08, 0xe8) 0 1 0 /* Port 1.0 MEM */
-				0x81000000 0x5 0       MBUS_ID(0x08, 0xe0) 0 1 0 /* Port 1.0 IO  */>;
+			       <0x82000000   0 0x40000 MBUS_ID(0xf0, 0x01) 0x40000 0 0x00002000 /* Port 0.0 registers */
+				0x82000000   0 0x44000 MBUS_ID(0xf0, 0x01) 0x44000 0 0x00002000 /* Port 0.1 registers */
+				0x82000000   0 0x48000 MBUS_ID(0xf0, 0x01) 0x48000 0 0x00002000 /* Port 0.2 registers */
+				0x82000000   0 0x4c000 MBUS_ID(0xf0, 0x01) 0x4c000 0 0x00002000 /* Port 0.3 registers */
+				0x82000000   0 0x80000 MBUS_ID(0xf0, 0x01) 0x80000 0 0x00002000 /* Port 1.0 registers */
+				0x82000000 0x1       0 MBUS_ID(0x04, 0xe8)       0 1          0 /* Port 0.0 MEM */
+				0x81000000 0x1       0 MBUS_ID(0x04, 0xe0)       0 1          0 /* Port 0.0 IO  */
+				0x82000000 0x2       0 MBUS_ID(0x04, 0xd8)       0 1          0 /* Port 0.1 MEM */
+				0x81000000 0x2       0 MBUS_ID(0x04, 0xd0)       0 1          0 /* Port 0.1 IO  */
+				0x82000000 0x3       0 MBUS_ID(0x04, 0xb8)       0 1          0 /* Port 0.2 MEM */
+				0x81000000 0x3       0 MBUS_ID(0x04, 0xb0)       0 1          0 /* Port 0.2 IO  */
+				0x82000000 0x4       0 MBUS_ID(0x04, 0x78)       0 1          0 /* Port 0.3 MEM */
+				0x81000000 0x4       0 MBUS_ID(0x04, 0x70)       0 1          0 /* Port 0.3 IO  */
+				0x82000000 0x5       0 MBUS_ID(0x08, 0xe8)       0 1          0 /* Port 1.0 MEM */
+				0x81000000 0x5       0 MBUS_ID(0x08, 0xe0)       0 1          0 /* Port 1.0 IO  */>;
 
 			pcie1: pcie@1,0 {
 				device_type = "pci";
arch/arm/boot/dts/armada-xp-mv78260.dtsi +27 -27

62 lines not on this page · raw message

arch/arm/boot/dts/armada-xp-mv78460.dtsi +30 -30

69 lines not on this page · raw message

arch/arm/boot/dts/at91-ariag25.dts +0 -1
index e3e14b7..4c812af 100644
@@ -178,7 +178,6 @@
 			gpios = <&pioB 8 GPIO_ACTIVE_HIGH>; /* PB8 */
 			linux,default-trigger = "heartbeat";
 		};
-
 	};
 
 	onewire {
arch/arm/boot/dts/at91-dvk_som60.dts +0 -1
index ededd5b..772ca23 100644
@@ -92,4 +92,3 @@
 &usb2 {
 	status = "okay";
 };
-
arch/arm/boot/dts/at91-dvk_su60_somc.dtsi +0 -1
index 21876da..7cc496c 100644
@@ -156,4 +156,3 @@
 &usb2 {
 	status = "okay";
 };
-
arch/arm/boot/dts/at91-linea.dtsi +0 -1
index c7b964e..8597261 100644
@@ -55,7 +55,6 @@
 	status = "okay";
 };
 
-
 &nand_controller {
 	status = "okay";
 
arch/arm/boot/dts/at91-sama5d2_xplained.dts +0 -1
index fa54e88..9fe12f6 100644
@@ -609,7 +609,6 @@
 			gpios = <&pioA PIN_PB6 GPIO_ACTIVE_LOW>;
 		};
 
-
 		green {
 			label = "green";
 			gpios = <&pioA PIN_PB5 GPIO_ACTIVE_LOW>;
arch/arm/boot/dts/at91-sama5d4_ma5d4evk.dts +0 -2
index fe05aaa..07294c7 100644
@@ -56,7 +56,6 @@
 						};
 					};
 				};
-
 			};
 
 			macb0: ethernet@f8020000 {
@@ -94,7 +93,6 @@
 				atmel,adc-ts-pressure-threshold = <10000>;
 			};
 
-
 			pinctrl@fc06a000 {
 				board {
 					pinctrl_mmc1_cd: mmc1_cd {
arch/arm/boot/dts/at91-vinco.dts +0 -2
index 4302772..0d0d9eb 100644
@@ -212,7 +212,6 @@
 			/* 4G Modem */
 			status = "okay";
 		};
-
 	};
 
 	leds {
@@ -254,7 +253,6 @@
 			gpios = <&pioA 26 GPIO_ACTIVE_LOW>;
 			default-state = "on";
 		};
-
 	};
 
 	vcc_3v3_reg: fixedregulator_3v3 {
arch/arm/boot/dts/at91-wb45n.dtsi +0 -2
index ebe61a2..3b5adb8 100644
@@ -115,7 +115,6 @@
 					label = "logs";
 					reg = <0x7fa0000 0x60000>;
 				};
-
 			};
 		};
 	};
@@ -162,4 +161,3 @@
 		};
 	};
 };
-
arch/arm/boot/dts/at91-wb50n.dts +0 -1
index a5e45bb..ab92e40 100644
@@ -109,4 +109,3 @@
 &usb2 {
 	status = "okay";
 };
-
arch/arm/boot/dts/at91sam9g20ek_common.dtsi +0 -2
index ec1f17a..4a69341 100644
@@ -8,7 +8,6 @@
 #include "at91sam9g20.dtsi"
 
 / {
-
 	chosen {
 		bootargs = "mem=64M root=/dev/mtdblock5 rw rootfstype=ubifs";
 		stdout-path = "serial0:115200n8";
@@ -36,7 +35,6 @@
 						atmel,pins =
 							<AT91_PIOC 1 AT91_PERIPH_B AT91_PINCTRL_NONE>;	/* PC1 periph B */
 					};
-
 				};
 
 				mmc0_slot1 {
arch/arm/boot/dts/at91sam9x5cm.dtsi +0 -1
index c4cc9cc..a836dcc 100644
@@ -141,5 +141,4 @@
 		pinctrl-0 = <&pinctrl_1wire_cm>;
 		status = "okay";
 	};
-
 };
arch/arm/boot/dts/atlas6-evb.dts +16 -16
index 4088241..5b9ebfa 100644
@@ -48,7 +48,6 @@
 					reg = <0x40>;
 				};
 			};
-
 		};
 		disp-iobg {
 			lcd@90010000 {
@@ -58,22 +57,23 @@
 			};
 		};
 	};
+
 	display: display@0 {
-	    panels {
-		panel0: panel@0 {
-			panel-name = "Innolux TFT";
-			hactive = <800>;
-			vactive = <480>;
-			left_margin = <20>;
-			right_margin = <234>;
-			upper_margin = <3>;
-			lower_margin = <41>;
-			hsync_len = <3>;
-			vsync_len = <2>;
-			pixclock = <33264000>;
-			sync = <3>;
-			timing = <0x88>;
+		panels {
+			panel0: panel@0 {
+				panel-name = "Innolux TFT";
+				hactive = <800>;
+				vactive = <480>;
+				left_margin = <20>;
+				right_margin = <234>;
+				upper_margin = <3>;
+				lower_margin = <41>;
+				hsync_len = <3>;
+				vsync_len = <2>;
+				pixclock = <33264000>;
+				sync = <3>;
+				timing = <0x88>;
 			};
-	    };
+		};
 	};
 };
arch/arm/boot/dts/atlas6.dtsi +184 -184

388 lines not on this page · raw message

arch/arm/boot/dts/atlas7-evb.dts +0 -2
index 900e03b..3a2a886 100644
@@ -42,7 +42,6 @@
 		};
 	};
 
-
 	noc {
 		mediam {
 			nand@17050000 {
@@ -123,6 +122,5 @@
 				debounce_interval = <100>;
 			};
 		};
-
 	};
 };
arch/arm/boot/dts/atlas7.dtsi +1 -3
index f3de9af..0708372 100644
@@ -1783,7 +1783,6 @@
 				compatible = "sirf,atlas7-memc";
 				reg = <0x10800000 0x2000>;
 			};
-
 		};
 
 		btm {
@@ -1899,8 +1898,8 @@
 				compatible = "sirf,atlas7-retain";
 				reg = <0x188D0000 0x1000>;
 			};
-
 		};
+
 		disp-iobg {
 			/* lcdc0 */
 			compatible = "simple-bus";
@@ -1936,7 +1935,6 @@
 				interrupts = <0 61 0>;
 				clocks = <&car 104>;
 			};
-
 		};
 
 		graphics-iobg {
arch/arm/boot/dts/axm55xx.dtsi +0 -7
index 2a93d3e..dc0fe5a 100644
@@ -82,7 +82,6 @@
 				(GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>;
 	};
 
-
 	pmu {
 		compatible = "arm,cortex-a15-pmu";
 		interrupts = <GIC_SPI 190 IRQ_TYPE_LEVEL_HIGH>;
@@ -196,9 +195,3 @@
 		};
 	};
 };
-
-/*
-  Local Variables:
-  mode: C
-  End:
-*/
arch/arm/boot/dts/bcm4708-buffalo-wzr-1750dhp.dts +0 -1
index bc330b1..bd25862 100644
@@ -41,7 +41,6 @@
 
 			gpio-controller;
 			#gpio-cells = <2>;
-
 		};
 	};
 
arch/arm/boot/dts/bcm4708.dtsi +0 -1
index 1a19e97..f77f16c 100644
@@ -40,7 +40,6 @@
 			reg = <0x1>;
 		};
 	};
-
 };
 
 &uart0 {
arch/arm/boot/dts/bcm47081-buffalo-wzr-600dhp2.dts +0 -1
index 6fcbb05..a35df53 100644
@@ -42,7 +42,6 @@
 
 			gpio-controller;
 			#gpio-cells = <2>;
-
 		};
 	};
 
arch/arm/boot/dts/bcm4709-buffalo-wxr-1900dhp.dts +0 -1
index 77d1687..340228f 100644
@@ -119,7 +119,6 @@
 	};
 };
 
-
 &usb2 {
 	vcc-gpio = <&chipcommon 13 GPIO_ACTIVE_HIGH>;
 };
arch/arm/boot/dts/dra7-l4.dtsi +0 -1
index 414f1cd..86b37d1 100644
@@ -4598,4 +4598,3 @@
 		};
 	};
 };
-
arch/arm/boot/dts/dra7xx-clocks.dtsi +1 -7
index bb52c6f..0e6576b 100644
@@ -815,6 +815,7 @@
 		clock-frequency = <0>;
 	};
 };
+
 &prm_clocks {
 	sys_clkin1: sys_clkin1@110 {
 		#clock-cells = <0>;
@@ -1538,7 +1539,6 @@
 			reg = <0x20 0x4>;
 			#clock-cells = <2>;
 		};
-
 	};
 
 	dsp1_cm: dsp1-cm@400 {
@@ -1553,7 +1553,6 @@
 			reg = <0x20 0x4>;
 			#clock-cells = <2>;
 		};
-
 	};
 
 	ipu_cm: ipu-cm@500 {
@@ -1574,7 +1573,6 @@
 			reg = <0x50 0x34>;
 			#clock-cells = <2>;
 		};
-
 	};
 
 	dsp2_cm: dsp2-cm@600 {
@@ -1589,7 +1587,6 @@
 			reg = <0x20 0x4>;
 			#clock-cells = <2>;
 		};
-
 	};
 
 	rtc_cm: rtc-cm@700 {
@@ -1605,7 +1602,6 @@
 			#clock-cells = <2>;
 		};
 	};
-
 };
 
 &cm_core {
@@ -1635,7 +1631,6 @@
 			reg = <0x20 0x74>;
 			#clock-cells = <2>;
 		};
-
 	};
 
 	ipu2_cm: ipu2-cm@900 {
@@ -1798,7 +1793,6 @@
 			#clock-cells = <2>;
 		};
 	};
-
 };
 
 &prm {
arch/arm/boot/dts/evk-pro3.dts +0 -1
index 20a4481..ea246fb 100644
@@ -55,5 +55,4 @@
 	i2c-gpio-0 {
 		status = "okay";
 	};
-
 };
arch/arm/boot/dts/exynos4412-ppmu-common.dtsi +24 -24

65 lines not on this page · raw message

arch/arm/boot/dts/exynos5410-pinctrl.dtsi +0 -1
index 369a8a7..2d818ef 100644
@@ -620,5 +620,4 @@
 		samsung,pin-pud = <0>;
 		samsung,pin-drv = <0>;
 	};
-
 };
arch/arm/boot/dts/exynos5422-odroidhc1.dts +0 -1
index d271e75..69a0104 100644
@@ -216,7 +216,6 @@
 			};
 		};
 	};
-
 };
 
 &pwm {
arch/arm/boot/dts/highbank.dts +0 -2
index 5027871..c7552a5 100644
@@ -159,13 +159,11 @@
 			interrupts = <0 76 4  0 75 4  0 74 4  0 73 4>;
 		};
 
-
 		sregs@fff3c200 {
 			compatible = "calxeda,hb-sregs-l2-ecc";
 			reg = <0xfff3c200 0x100>;
 			interrupts = <0 71 4  0 72 4>;
 		};
-
 	};
 };
 
arch/arm/boot/dts/imx23-sansa.dts +0 -1
index 46057d9..9744d02 100644
@@ -203,5 +203,4 @@
 			pagesize = <32>;
 		};
 	};
-
 };
arch/arm/boot/dts/imx28-eukrea-mbmx283lc.dts +0 -1
index 28dab6d..227f352 100644
@@ -46,7 +46,6 @@
 	};
 };
 
-
 &mac0 {
 	phy-mode = "rmii";
 	pinctrl-names = "default";
arch/arm/boot/dts/imx28-evk.dts +0 -1
index 96c1d10..39b365c 100644
@@ -14,7 +14,6 @@
 		reg = <0x40000000 0x08000000>;
 	};
 
-
 	reg_3p3v: regulator-3p3v {
 		compatible = "regulator-fixed";
 		regulator-name = "3P3V";
arch/arm/boot/dts/imx28-sps1.dts +0 -1
index 42c88a6..1cd1d61 100644
@@ -167,6 +167,5 @@
 			default-trigger = "heartbeat";
 			reg = <2>;
 		};
-
 	};
 };
arch/arm/boot/dts/imx28-ts4600.dts +0 -4
index e3fd411..cfc119b 100644
@@ -15,7 +15,6 @@
 #include "dt-bindings/gpio/gpio.h"
 
 / {
-
 	model = "Technologic Systems i.MX28 TS-4600";
 	compatible = "technologic,imx28-ts4600", "fsl,imx28";
 
@@ -39,7 +38,6 @@
 			};
 
 			pinctrl@80018000 {
-
 				en_sd_pwr: en-sd-pwr@0 {
 					reg = <0>;
 					fsl,pinmux-ids = <
@@ -49,7 +47,6 @@
 					fsl,voltage = <MXS_VOLTAGE_HIGH>;
 					fsl,pull-up = <MXS_PULL_DISABLE>;
 				};
-
 			};
 		};
 
@@ -76,5 +73,4 @@
 		regulator-boot-on;
 		gpio = <&gpio3 28 GPIO_ACTIVE_LOW>;
 	};
-
 };
arch/arm/boot/dts/imx6dl-gw52xx.dts +13 -13
index 5f9f894..5b95a026 100644
@@ -54,24 +54,24 @@
 &iomuxc {
 	pinctrl_adv7180: adv7180grp {
 		fsl,pins = <
-			MX6QDL_PAD_EIM_D30__GPIO3_IO30          0x0001b0b0
-			MX6QDL_PAD_EIM_D31__GPIO3_IO31          0x4001b0b0
+			MX6QDL_PAD_EIM_D30__GPIO3_IO30		0x0001b0b0
+			MX6QDL_PAD_EIM_D31__GPIO3_IO31		0x4001b0b0
 		>;
 	};
 
 	pinctrl_ipu1_csi1: ipu1_csi1grp {
 		fsl,pins = <
-			MX6QDL_PAD_EIM_EB2__IPU1_CSI1_DATA19    0x1b0b0
-			MX6QDL_PAD_EIM_D16__IPU1_CSI1_DATA18    0x1b0b0
-			MX6QDL_PAD_EIM_D18__IPU1_CSI1_DATA17    0x1b0b0
-			MX6QDL_PAD_EIM_D19__IPU1_CSI1_DATA16    0x1b0b0
-			MX6QDL_PAD_EIM_D20__IPU1_CSI1_DATA15    0x1b0b0
-			MX6QDL_PAD_EIM_D26__IPU1_CSI1_DATA14    0x1b0b0
-			MX6QDL_PAD_EIM_D27__IPU1_CSI1_DATA13    0x1b0b0
-			MX6QDL_PAD_EIM_A17__IPU1_CSI1_DATA12    0x1b0b0
-			MX6QDL_PAD_EIM_D29__IPU1_CSI1_VSYNC     0x1b0b0
-			MX6QDL_PAD_EIM_EB3__IPU1_CSI1_HSYNC     0x1b0b0
-			MX6QDL_PAD_EIM_A16__IPU1_CSI1_PIXCLK    0x1b0b0
+			MX6QDL_PAD_EIM_EB2__IPU1_CSI1_DATA19	0x1b0b0
+			MX6QDL_PAD_EIM_D16__IPU1_CSI1_DATA18	0x1b0b0
+			MX6QDL_PAD_EIM_D18__IPU1_CSI1_DATA17	0x1b0b0
+			MX6QDL_PAD_EIM_D19__IPU1_CSI1_DATA16	0x1b0b0
+			MX6QDL_PAD_EIM_D20__IPU1_CSI1_DATA15	0x1b0b0
+			MX6QDL_PAD_EIM_D26__IPU1_CSI1_DATA14	0x1b0b0
+			MX6QDL_PAD_EIM_D27__IPU1_CSI1_DATA13	0x1b0b0
+			MX6QDL_PAD_EIM_A17__IPU1_CSI1_DATA12	0x1b0b0
+			MX6QDL_PAD_EIM_D29__IPU1_CSI1_VSYNC	0x1b0b0
+			MX6QDL_PAD_EIM_EB3__IPU1_CSI1_HSYNC	0x1b0b0
+			MX6QDL_PAD_EIM_A16__IPU1_CSI1_PIXCLK	0x1b0b0
 		>;
 	};
 };
arch/arm/boot/dts/imx6dl-gw53xx.dts +13 -13
index 9bfc620..bd2095b 100644
@@ -54,24 +54,24 @@
 &iomuxc {
 	pinctrl_adv7180: adv7180grp {
 		fsl,pins = <
-			MX6QDL_PAD_EIM_D30__GPIO3_IO30          0x0001b0b0
-			MX6QDL_PAD_EIM_D31__GPIO3_IO31          0x4001b0b0
+			MX6QDL_PAD_EIM_D30__GPIO3_IO30		0x0001b0b0
+			MX6QDL_PAD_EIM_D31__GPIO3_IO31		0x4001b0b0
 		>;
 	};
 
 	pinctrl_ipu1_csi1: ipu1_csi1grp {
 		fsl,pins = <
-			MX6QDL_PAD_EIM_EB2__IPU1_CSI1_DATA19    0x1b0b0
-			MX6QDL_PAD_EIM_D16__IPU1_CSI1_DATA18    0x1b0b0
-			MX6QDL_PAD_EIM_D18__IPU1_CSI1_DATA17    0x1b0b0
-			MX6QDL_PAD_EIM_D19__IPU1_CSI1_DATA16    0x1b0b0
-			MX6QDL_PAD_EIM_D20__IPU1_CSI1_DATA15    0x1b0b0
-			MX6QDL_PAD_EIM_D26__IPU1_CSI1_DATA14    0x1b0b0
-			MX6QDL_PAD_EIM_D27__IPU1_CSI1_DATA13    0x1b0b0
-			MX6QDL_PAD_EIM_A17__IPU1_CSI1_DATA12    0x1b0b0
-			MX6QDL_PAD_EIM_D29__IPU1_CSI1_VSYNC     0x1b0b0
-			MX6QDL_PAD_EIM_EB3__IPU1_CSI1_HSYNC     0x1b0b0
-			MX6QDL_PAD_EIM_A16__IPU1_CSI1_PIXCLK    0x1b0b0
+			MX6QDL_PAD_EIM_EB2__IPU1_CSI1_DATA19	0x1b0b0
+			MX6QDL_PAD_EIM_D16__IPU1_CSI1_DATA18	0x1b0b0
+			MX6QDL_PAD_EIM_D18__IPU1_CSI1_DATA17	0x1b0b0
+			MX6QDL_PAD_EIM_D19__IPU1_CSI1_DATA16	0x1b0b0
+			MX6QDL_PAD_EIM_D20__IPU1_CSI1_DATA15	0x1b0b0
+			MX6QDL_PAD_EIM_D26__IPU1_CSI1_DATA14	0x1b0b0
+			MX6QDL_PAD_EIM_D27__IPU1_CSI1_DATA13	0x1b0b0
+			MX6QDL_PAD_EIM_A17__IPU1_CSI1_DATA12	0x1b0b0
+			MX6QDL_PAD_EIM_D29__IPU1_CSI1_VSYNC	0x1b0b0
+			MX6QDL_PAD_EIM_EB3__IPU1_CSI1_HSYNC	0x1b0b0
+			MX6QDL_PAD_EIM_A16__IPU1_CSI1_PIXCLK	0x1b0b0
 		>;
 	};
 };
arch/arm/boot/dts/imx6dl-gw54xx.dts +13 -13
index b909bdf..9a7174fe 100644
@@ -54,24 +54,24 @@
 &iomuxc {
 	pinctrl_adv7180: adv7180grp {
 		fsl,pins = <
-			MX6QDL_PAD_EIM_D30__GPIO3_IO30          0x0001b0b0
-			MX6QDL_PAD_EIM_D31__GPIO3_IO31          0x4001b0b0
+			MX6QDL_PAD_EIM_D30__GPIO3_IO30		0x0001b0b0
+			MX6QDL_PAD_EIM_D31__GPIO3_IO31		0x4001b0b0
 		>;
 	};
 
 	pinctrl_ipu1_csi1: ipu1_csi1grp {
 		fsl,pins = <
-			MX6QDL_PAD_EIM_EB2__IPU1_CSI1_DATA19    0x1b0b0
-			MX6QDL_PAD_EIM_D16__IPU1_CSI1_DATA18    0x1b0b0
-			MX6QDL_PAD_EIM_D18__IPU1_CSI1_DATA17    0x1b0b0
-			MX6QDL_PAD_EIM_D19__IPU1_CSI1_DATA16    0x1b0b0
-			MX6QDL_PAD_EIM_D20__IPU1_CSI1_DATA15    0x1b0b0
-			MX6QDL_PAD_EIM_D26__IPU1_CSI1_DATA14    0x1b0b0
-			MX6QDL_PAD_EIM_D27__IPU1_CSI1_DATA13    0x1b0b0
-			MX6QDL_PAD_EIM_A17__IPU1_CSI1_DATA12    0x1b0b0
-			MX6QDL_PAD_EIM_D29__IPU1_CSI1_VSYNC     0x1b0b0
-			MX6QDL_PAD_EIM_EB3__IPU1_CSI1_HSYNC     0x1b0b0
-			MX6QDL_PAD_EIM_A16__IPU1_CSI1_PIXCLK    0x1b0b0
+			MX6QDL_PAD_EIM_EB2__IPU1_CSI1_DATA19	0x1b0b0
+			MX6QDL_PAD_EIM_D16__IPU1_CSI1_DATA18	0x1b0b0
+			MX6QDL_PAD_EIM_D18__IPU1_CSI1_DATA17	0x1b0b0
+			MX6QDL_PAD_EIM_D19__IPU1_CSI1_DATA16	0x1b0b0
+			MX6QDL_PAD_EIM_D20__IPU1_CSI1_DATA15	0x1b0b0
+			MX6QDL_PAD_EIM_D26__IPU1_CSI1_DATA14	0x1b0b0
+			MX6QDL_PAD_EIM_D27__IPU1_CSI1_DATA13	0x1b0b0
+			MX6QDL_PAD_EIM_A17__IPU1_CSI1_DATA12	0x1b0b0
+			MX6QDL_PAD_EIM_D29__IPU1_CSI1_VSYNC	0x1b0b0
+			MX6QDL_PAD_EIM_EB3__IPU1_CSI1_HSYNC	0x1b0b0
+			MX6QDL_PAD_EIM_A16__IPU1_CSI1_PIXCLK	0x1b0b0
 		>;
 	};
 };
arch/arm/boot/dts/imx6dl-mamoj.dts +50 -50

90 lines not on this page · raw message

arch/arm/boot/dts/imx6q-ba16.dtsi +89 -89

178 lines not on this page · raw message

arch/arm/boot/dts/imx6q-bx50v3.dtsi +4 -4
index fa27dcd..fce203a 100644

Lines of this file are not shown. View the raw message.

arch/arm/boot/dts/imx6q-cm-fx6.dts +23 -23

46 lines not on this page · raw message

arch/arm/boot/dts/imx6q-display5.dtsi +22 -22

44 lines not on this page · raw message

arch/arm/boot/dts/imx6q-dmo-edmqmx6.dts +4 -4
index ee8c38e..9b08c10 100644

Lines of this file are not shown. View the raw message.

arch/arm/boot/dts/imx6q-dms-ba16.dts +8 -8
index 57761f3..bef7a4b 100644

Lines of this file are not shown. View the raw message.

arch/arm/boot/dts/imx6q-evi.dts +150 -150

300 lines not on this page · raw message

arch/arm/boot/dts/imx6q-gw52xx.dts +13 -13
index 0b8ae00..96227d6 100644

Lines of this file are not shown. View the raw message.

arch/arm/boot/dts/imx6q-gw53xx.dts +13 -13
index a56ef77..a3b6469 100644

Lines of this file are not shown. View the raw message.

arch/arm/boot/dts/imx6q-gw54xx.dts +13 -13
index 56e5b50..420e4ae 100644

Lines of this file are not shown. View the raw message.

arch/arm/boot/dts/imx6q-kp.dtsi +84 -84

168 lines not on this page · raw message

arch/arm/boot/dts/imx6q-mccmon6.dts +12 -12
index 74d9824..8abf217 100644

Lines of this file are not shown. View the raw message.

arch/arm/boot/dts/imx6q-pistachio.dts +31 -31

62 lines not on this page · raw message

arch/arm/boot/dts/imx6q-tbs2910.dts +64 -64

128 lines not on this page · raw message

arch/arm/boot/dts/imx6q-utilite-pro.dts +58 -58

116 lines not on this page · raw message

arch/arm/boot/dts/imx6qdl-apalis.dtsi +179 -179

358 lines not on this page · raw message

arch/arm/boot/dts/imx6qdl-apf6dev.dtsi +51 -51

102 lines not on this page · raw message

arch/arm/boot/dts/imx6qdl-aristainetos.dtsi +90 -90

180 lines not on this page · raw message

arch/arm/boot/dts/imx6qdl-aristainetos2.dtsi +87 -87

174 lines not on this page · raw message

arch/arm/boot/dts/imx6qdl-colibri.dtsi +59 -59

118 lines not on this page · raw message

arch/arm/boot/dts/imx6qdl-cubox-i.dtsi +21 -21

42 lines not on this page · raw message

arch/arm/boot/dts/imx6qdl-dfi-fs700-m60.dtsi +6 -6
index ebe7a8b..3e2714d 100644

Lines of this file are not shown. View the raw message.

arch/arm/boot/dts/imx6qdl-emcon.dtsi +50 -50

100 lines not on this page · raw message

arch/arm/boot/dts/imx6qdl-gw51xx.dtsi +70 -70

140 lines not on this page · raw message

arch/arm/boot/dts/imx6qdl-gw52xx.dtsi +5 -5
index 2ff377d..b7ecdef 100644

Lines of this file are not shown. View the raw message.

arch/arm/boot/dts/imx6qdl-gw53xx.dtsi +5 -5
index 68ab543..7e9535c 100644

Lines of this file are not shown. View the raw message.

arch/arm/boot/dts/imx6qdl-gw54xx.dtsi +4 -4
index 81b2fcf..675a8e2 100644

Lines of this file are not shown. View the raw message.

arch/arm/boot/dts/imx6qdl-gw551x.dtsi +1 -1
index 8e46a80..100ed13 100644

Lines of this file are not shown. View the raw message.

arch/arm/boot/dts/imx6qdl-gw553x.dtsi +79 -79

158 lines not on this page · raw message

arch/arm/boot/dts/imx6qdl-gw5904.dtsi +8 -8
index 6d21cc6..3a1549a 100644

Lines of this file are not shown. View the raw message.

arch/arm/boot/dts/imx6qdl-hummingboard.dtsi +27 -27

54 lines not on this page · raw message

arch/arm/boot/dts/imx6qdl-hummingboard2-emmc.dtsi +11 -11
index f400405..449e9cb 100644

Lines of this file are not shown. View the raw message.

arch/arm/boot/dts/imx6qdl-hummingboard2.dtsi +82 -82

164 lines not on this page · raw message

arch/arm/boot/dts/imx6qdl-icore-rqs.dtsi +92 -92

184 lines not on this page · raw message

arch/arm/boot/dts/imx6qdl-icore.dtsi +54 -54

108 lines not on this page · raw message

arch/arm/boot/dts/imx6qdl-nit6xlite.dtsi +9 -9
index 7a85116..f575068 100644

Lines of this file are not shown. View the raw message.

arch/arm/boot/dts/imx6qdl-nitrogen6_max.dtsi +58 -58

116 lines not on this page · raw message

arch/arm/boot/dts/wm8750.dtsi +55 -55

110 lines not on this page · raw message

arch/arm/boot/dts/wm8850.dtsi +27 -27

54 lines not on this page · raw message

The rest of this diff is not shown. View the raw message.

Signature · 1 line
1.9.1

Part of the diff is not shown here. View the raw message.