[OS-BUILD PATCH] [redhat] New configs in drivers/phy
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_PHY_CADENCE_SALVO:
Enable this to support the Cadence SALVO PHY driver,
this PHY is a legacy PHY, and only are used for USB3
and USB2.
Symbol: PHY_CADENCE_SALVO [=n]
Type : tristate
Defined at drivers/phy/cadence/Kconfig:31
Prompt: Cadence Salvo PHY Driver
Depends on: OF [=y] && HAS_IOMEM [=y]
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=n]
---
CONFIG_PHY_QCOM_IPQ4019_USB:
Support for the USB PHY-s on Qualcomm IPQ40xx SoC-s.
Symbol: PHY_QCOM_IPQ4019_USB [=n]
Type : tristate
Defined at drivers/phy/qualcomm/Kconfig:21
Prompt: Qualcomm IPQ4019 USB PHY driver
Depends on: OF [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=y]
---
CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2:
Enable support for the USB high-speed SNPS Femto phy on Qualcomm
chipsets. This PHY has differences in the register map compared
to the V1 variants. The PHY is paired with a Synopsys DWC3 USB
controller on Qualcomm SOCs.
Symbol: PHY_QCOM_USB_SNPS_FEMTO_V2 [=n]
Type : tristate
Defined at drivers/phy/qualcomm/Kconfig:95
Prompt: Qualcomm SNPS FEMTO USB HS PHY V2 module
Depends on: OF [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_PHY_CADENCE_SALVO | 1 +
.../generic/CONFIG_PHY_QCOM_IPQ4019_USB | 1 +
.../generic/CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2 | 1 +
.../generic/CONFIG_PHY_CADENCE_SALVO | 19 ------------------
.../generic/CONFIG_PHY_QCOM_IPQ4019_USB | 17 ----------------
.../generic/CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2 | 20 -------------------
6 files changed, 3 insertions(+), 56 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_PHY_CADENCE_SALVO
create mode 100644 redhat/configs/common/generic/CONFIG_PHY_QCOM_IPQ4019_USB
create mode 100644 redhat/configs/common/generic/CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PHY_CADENCE_SALVO
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PHY_QCOM_IPQ4019_USB
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2
diff --git a/redhat/configs/common/generic/CONFIG_PHY_CADENCE_SALVO b/redhat/configs/common/generic/CONFIG_PHY_CADENCE_SALVO
new file mode 100644
index 000000000000..bb0551527d7e
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PHY_CADENCE_SALVO
@@ -0,0 +1 @@
+# CONFIG_PHY_CADENCE_SALVO is not set
diff --git a/redhat/configs/common/generic/CONFIG_PHY_QCOM_IPQ4019_USB b/redhat/configs/common/generic/CONFIG_PHY_QCOM_IPQ4019_USB
new file mode 100644
index 000000000000..feefe01f6694
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PHY_QCOM_IPQ4019_USB
@@ -0,0 +1 @@
+# CONFIG_PHY_QCOM_IPQ4019_USB is not set
diff --git a/redhat/configs/common/generic/CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2 b/redhat/configs/common/generic/CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2
new file mode 100644
index 000000000000..7f13bc31554a
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2
@@ -0,0 +1 @@
+# CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_PHY_CADENCE_SALVO b/redhat/configs/pending-common/generic/CONFIG_PHY_CADENCE_SALVO
deleted file mode 100644
index 754d68b65675..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PHY_CADENCE_SALVO
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_PHY_CADENCE_SALVO:
-#
-# Enable this to support the Cadence SALVO PHY driver,
-# this PHY is a legacy PHY, and only are used for USB3
-# and USB2.
-#
-# Symbol: PHY_CADENCE_SALVO [=n]
-# Type : tristate
-# Defined at drivers/phy/cadence/Kconfig:31
-# Prompt: Cadence Salvo PHY Driver
-# Depends on: OF [=y] && HAS_IOMEM [=y]
-# Location:
-# -> Device Drivers
-# -> PHY Subsystem
-# Selects: GENERIC_PHY [=n]
-#
-#
-#
-# CONFIG_PHY_CADENCE_SALVO is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_PHY_QCOM_IPQ4019_USB b/redhat/configs/pending-common/generic/CONFIG_PHY_QCOM_IPQ4019_USB
deleted file mode 100644
index bde742128880..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PHY_QCOM_IPQ4019_USB
+++ /dev/null
@@ -1,17 +0,0 @@
-# CONFIG_PHY_QCOM_IPQ4019_USB:
-#
-# Support for the USB PHY-s on Qualcomm IPQ40xx SoC-s.
-#
-# Symbol: PHY_QCOM_IPQ4019_USB [=n]
-# Type : tristate
-# Defined at drivers/phy/qualcomm/Kconfig:21
-# Prompt: Qualcomm IPQ4019 USB PHY driver
-# Depends on: OF [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
-# Location:
-# -> Device Drivers
-# -> PHY Subsystem
-# Selects: GENERIC_PHY [=y]
-#
-#
-#
-# CONFIG_PHY_QCOM_IPQ4019_USB is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2 b/redhat/configs/pending-common/generic/CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2
deleted file mode 100644
index 0f01bb6daa3e..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2
+++ /dev/null
@@ -1,20 +0,0 @@
-# CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2:
-#
-# Enable support for the USB high-speed SNPS Femto phy on Qualcomm
-# chipsets. This PHY has differences in the register map compared
-# to the V1 variants. The PHY is paired with a Synopsys DWC3 USB
-# controller on Qualcomm SOCs.
-#
-# Symbol: PHY_QCOM_USB_SNPS_FEMTO_V2 [=n]
-# Type : tristate
-# Defined at drivers/phy/qualcomm/Kconfig:95
-# Prompt: Qualcomm SNPS FEMTO USB HS PHY V2 module
-# Depends on: OF [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
-# Location:
-# -> Device Drivers
-# -> PHY Subsystem
-# Selects: GENERIC_PHY [=y]
-#
-#
-#
-# CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2 is not set
--
2.26.2
3 years, 10 months
[OS-BUILD PATCH] [redhat] New configs in drivers/iio
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_AD9467:
Say yes here to build support for Analog Devices:
* AD9467 16-Bit, 200 MSPS/250 MSPS Analog-to-Digital Converter
The driver requires the assistance of the AXI ADC IP core to operate,
since SPI is used for configuration only, while data has to be
streamed into memory via DMA.
To compile this driver as a module, choose M here: the module will be
called ad9467.
Symbol: AD9467 [=n]
Type : tristate
Defined at drivers/iio/adc/Kconfig:249
Prompt: Analog Devices AD9467 High Speed ADC driver
Depends on: IIO [=m] && SPI [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Analog to digital converters
Selects: ADI_AXI_ADC [=n]
---
CONFIG_ADIS16475:
Say yes here to build support for Analog Devices ADIS16470, ADIS16475,
ADIS16477, ADIS16465, ADIS16467, ADIS16500, ADIS16505, ADIS16507 inertial
sensors.
To compile this driver as a module, choose M here: the module will be
called adis16475.
Symbol: ADIS16475 [=n]
Type : tristate
Defined at drivers/iio/imu/Kconfig:32
Prompt: Analog Devices ADIS16475 and similar IMU driver
Depends on: IIO [=m] && SPI [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Inertial measurement units
Selects: IIO_ADIS_LIB [=n] && IIO_ADIS_LIB_BUFFER [=n]
---
CONFIG_ADI_AXI_ADC:
Say yes here to build support for Analog Devices Generic
AXI ADC IP core. The IP core is used for interfacing with
analog-to-digital (ADC) converters that require either a high-speed
serial interface (JESD204B/C) or a source synchronous parallel
interface (LVDS/CMOS).
Typically (for such devices) SPI will be used for configuration only,
while this IP core handles the streaming of data into memory via DMA.
Link: https://wiki.analog.com/resources/fpga/docs/axi_adc_ip
If unsure, say N (but it's safe to say "Y").
To compile this driver as a module, choose M here: the
module will be called adi-axi-adc.
Symbol: ADI_AXI_ADC [=n]
Type : tristate
Defined at drivers/iio/adc/Kconfig:264
Prompt: Analog Devices Generic AXI ADC IP core driver
Depends on: IIO [=m]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Analog to digital converters
Selects: IIO_BUFFER [=y] && IIO_BUFFER_HW_CONSUMER [=n] && IIO_BUFFER_DMAENGINE [=n]
Selected by [n]:
- AD9467 [=n] && IIO [=m] && SPI [=y]
---
CONFIG_ATLAS_EZO_SENSOR:
Say Y here to build I2C interface support for the following
Atlas Scientific EZO sensors
* CO2 EZO Sensor
To compile this driver as module, choose M here: the
module will be called atlas-ezo-sensor.
Symbol: ATLAS_EZO_SENSOR [=n]
Type : tristate
Defined at drivers/iio/chemical/Kconfig:25
Prompt: Atlas Scientific EZO sensors
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Chemical Sensors
---
CONFIG_MAX1241:
Say yes here to build support for Maxim max1241 12-bit, single-channel
ADC.
To compile this driver as a module, choose M here: the module will be
called max1241.
Symbol: MAX1241 [=n]
Type : tristate
Defined at drivers/iio/adc/Kconfig:633
Prompt: Maxim max1241 ADC driver
Depends on: IIO [=m] && SPI_MASTER [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Analog to digital converters
---
CONFIG_SX9310:
Say Y here to build a driver for Semtech's SX9310/SX9311 capacitive
proximity/button sensor.
To compile this driver as a module, choose M here: the
module will be called sx9310.
Symbol: SX9310 [=n]
Type : tristate
Defined at drivers/iio/proximity/Kconfig:104
Prompt: SX9310/SX9311 Semtech proximity sensor
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Proximity and distance sensors
Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] && REGMAP_I2C [=m]
---
CONFIG_VCNL3020:
Say Y here if you want to build a driver for the Vishay VCNL3020
proximity sensor.
To compile this driver as a module, choose M here: the
module will be called vcnl3020.
Symbol: VCNL3020 [=n]
Type : tristate
Defined at drivers/iio/proximity/Kconfig:143
Prompt: VCNL3020 proximity sensor
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Proximity and distance sensors
Selects: REGMAP_I2C [=m]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
redhat/configs/common/generic/CONFIG_AD9467 | 1 +
.../configs/common/generic/CONFIG_ADIS16475 | 1 +
.../configs/common/generic/CONFIG_ADI_AXI_ADC | 1 +
.../common/generic/CONFIG_ATLAS_EZO_SENSOR | 1 +
redhat/configs/common/generic/CONFIG_MAX1241 | 1 +
redhat/configs/common/generic/CONFIG_SX9310 | 1 +
redhat/configs/common/generic/CONFIG_VCNL3020 | 1 +
.../pending-common/generic/CONFIG_AD9467 | 26 ---------------
.../pending-common/generic/CONFIG_ADIS16475 | 23 -------------
.../pending-common/generic/CONFIG_ADI_AXI_ADC | 32 -------------------
.../generic/CONFIG_ATLAS_EZO_SENSOR | 22 -------------
.../pending-common/generic/CONFIG_MAX1241 | 21 ------------
.../pending-common/generic/CONFIG_SX9310 | 22 -------------
.../pending-common/generic/CONFIG_VCNL3020 | 22 -------------
14 files changed, 7 insertions(+), 168 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_AD9467
create mode 100644 redhat/configs/common/generic/CONFIG_ADIS16475
create mode 100644 redhat/configs/common/generic/CONFIG_ADI_AXI_ADC
create mode 100644 redhat/configs/common/generic/CONFIG_ATLAS_EZO_SENSOR
create mode 100644 redhat/configs/common/generic/CONFIG_MAX1241
create mode 100644 redhat/configs/common/generic/CONFIG_SX9310
create mode 100644 redhat/configs/common/generic/CONFIG_VCNL3020
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_AD9467
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ADIS16475
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ADI_AXI_ADC
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ATLAS_EZO_SENSOR
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_MAX1241
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SX9310
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_VCNL3020
diff --git a/redhat/configs/common/generic/CONFIG_AD9467 b/redhat/configs/common/generic/CONFIG_AD9467
new file mode 100644
index 000000000000..421ac1f25eec
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_AD9467
@@ -0,0 +1 @@
+# CONFIG_AD9467 is not set
diff --git a/redhat/configs/common/generic/CONFIG_ADIS16475 b/redhat/configs/common/generic/CONFIG_ADIS16475
new file mode 100644
index 000000000000..18dd3612a10f
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ADIS16475
@@ -0,0 +1 @@
+# CONFIG_ADIS16475 is not set
diff --git a/redhat/configs/common/generic/CONFIG_ADI_AXI_ADC b/redhat/configs/common/generic/CONFIG_ADI_AXI_ADC
new file mode 100644
index 000000000000..e98b407ac85f
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ADI_AXI_ADC
@@ -0,0 +1 @@
+# CONFIG_ADI_AXI_ADC is not set
diff --git a/redhat/configs/common/generic/CONFIG_ATLAS_EZO_SENSOR b/redhat/configs/common/generic/CONFIG_ATLAS_EZO_SENSOR
new file mode 100644
index 000000000000..be8768690df2
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ATLAS_EZO_SENSOR
@@ -0,0 +1 @@
+# CONFIG_ATLAS_EZO_SENSOR is not set
diff --git a/redhat/configs/common/generic/CONFIG_MAX1241 b/redhat/configs/common/generic/CONFIG_MAX1241
new file mode 100644
index 000000000000..813c3f2cd883
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_MAX1241
@@ -0,0 +1 @@
+# CONFIG_MAX1241 is not set
diff --git a/redhat/configs/common/generic/CONFIG_SX9310 b/redhat/configs/common/generic/CONFIG_SX9310
new file mode 100644
index 000000000000..14c168021e5f
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SX9310
@@ -0,0 +1 @@
+# CONFIG_SX9310 is not set
diff --git a/redhat/configs/common/generic/CONFIG_VCNL3020 b/redhat/configs/common/generic/CONFIG_VCNL3020
new file mode 100644
index 000000000000..256fb80de2f7
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_VCNL3020
@@ -0,0 +1 @@
+# CONFIG_VCNL3020 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_AD9467 b/redhat/configs/pending-common/generic/CONFIG_AD9467
deleted file mode 100644
index ac8205adacae..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_AD9467
+++ /dev/null
@@ -1,26 +0,0 @@
-# CONFIG_AD9467:
-#
-# Say yes here to build support for Analog Devices:
-# * AD9467 16-Bit, 200 MSPS/250 MSPS Analog-to-Digital Converter
-#
-# The driver requires the assistance of the AXI ADC IP core to operate,
-# since SPI is used for configuration only, while data has to be
-# streamed into memory via DMA.
-#
-# To compile this driver as a module, choose M here: the module will be
-# called ad9467.
-#
-# Symbol: AD9467 [=n]
-# Type : tristate
-# Defined at drivers/iio/adc/Kconfig:249
-# Prompt: Analog Devices AD9467 High Speed ADC driver
-# Depends on: IIO [=m] && SPI [=y]
-# Location:
-# -> Device Drivers
-# -> Industrial I/O support (IIO [=m])
-# -> Analog to digital converters
-# Selects: ADI_AXI_ADC [=n]
-#
-#
-#
-# CONFIG_AD9467 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_ADIS16475 b/redhat/configs/pending-common/generic/CONFIG_ADIS16475
deleted file mode 100644
index 86f94b26e6dc..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_ADIS16475
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_ADIS16475:
-#
-# Say yes here to build support for Analog Devices ADIS16470, ADIS16475,
-# ADIS16477, ADIS16465, ADIS16467, ADIS16500, ADIS16505, ADIS16507 inertial
-# sensors.
-#
-# To compile this driver as a module, choose M here: the module will be
-# called adis16475.
-#
-# Symbol: ADIS16475 [=n]
-# Type : tristate
-# Defined at drivers/iio/imu/Kconfig:32
-# Prompt: Analog Devices ADIS16475 and similar IMU driver
-# Depends on: IIO [=m] && SPI [=y]
-# Location:
-# -> Device Drivers
-# -> Industrial I/O support (IIO [=m])
-# -> Inertial measurement units
-# Selects: IIO_ADIS_LIB [=n] && IIO_ADIS_LIB_BUFFER [=n]
-#
-#
-#
-# CONFIG_ADIS16475 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_ADI_AXI_ADC b/redhat/configs/pending-common/generic/CONFIG_ADI_AXI_ADC
deleted file mode 100644
index a3373539ee88..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_ADI_AXI_ADC
+++ /dev/null
@@ -1,32 +0,0 @@
-# CONFIG_ADI_AXI_ADC:
-#
-# Say yes here to build support for Analog Devices Generic
-# AXI ADC IP core. The IP core is used for interfacing with
-# analog-to-digital (ADC) converters that require either a high-speed
-# serial interface (JESD204B/C) or a source synchronous parallel
-# interface (LVDS/CMOS).
-# Typically (for such devices) SPI will be used for configuration only,
-# while this IP core handles the streaming of data into memory via DMA.
-#
-# Link: https://wiki.analog.com/resources/fpga/docs/axi_adc_ip
-# If unsure, say N (but it's safe to say "Y").
-#
-# To compile this driver as a module, choose M here: the
-# module will be called adi-axi-adc.
-#
-# Symbol: ADI_AXI_ADC [=n]
-# Type : tristate
-# Defined at drivers/iio/adc/Kconfig:264
-# Prompt: Analog Devices Generic AXI ADC IP core driver
-# Depends on: IIO [=m]
-# Location:
-# -> Device Drivers
-# -> Industrial I/O support (IIO [=m])
-# -> Analog to digital converters
-# Selects: IIO_BUFFER [=y] && IIO_BUFFER_HW_CONSUMER [=n] && IIO_BUFFER_DMAENGINE [=n]
-# Selected by [n]:
-# - AD9467 [=n] && IIO [=m] && SPI [=y]
-#
-#
-#
-# CONFIG_ADI_AXI_ADC is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_ATLAS_EZO_SENSOR b/redhat/configs/pending-common/generic/CONFIG_ATLAS_EZO_SENSOR
deleted file mode 100644
index 2915eee296d2..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_ATLAS_EZO_SENSOR
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_ATLAS_EZO_SENSOR:
-#
-# Say Y here to build I2C interface support for the following
-# Atlas Scientific EZO sensors
-# * CO2 EZO Sensor
-#
-# To compile this driver as module, choose M here: the
-# module will be called atlas-ezo-sensor.
-#
-# Symbol: ATLAS_EZO_SENSOR [=n]
-# Type : tristate
-# Defined at drivers/iio/chemical/Kconfig:25
-# Prompt: Atlas Scientific EZO sensors
-# Depends on: IIO [=m] && I2C [=y]
-# Location:
-# -> Device Drivers
-# -> Industrial I/O support (IIO [=m])
-# -> Chemical Sensors
-#
-#
-#
-# CONFIG_ATLAS_EZO_SENSOR is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_MAX1241 b/redhat/configs/pending-common/generic/CONFIG_MAX1241
deleted file mode 100644
index 95ce69d71955..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_MAX1241
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_MAX1241:
-#
-# Say yes here to build support for Maxim max1241 12-bit, single-channel
-# ADC.
-#
-# To compile this driver as a module, choose M here: the module will be
-# called max1241.
-#
-# Symbol: MAX1241 [=n]
-# Type : tristate
-# Defined at drivers/iio/adc/Kconfig:633
-# Prompt: Maxim max1241 ADC driver
-# Depends on: IIO [=m] && SPI_MASTER [=y]
-# Location:
-# -> Device Drivers
-# -> Industrial I/O support (IIO [=m])
-# -> Analog to digital converters
-#
-#
-#
-# CONFIG_MAX1241 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SX9310 b/redhat/configs/pending-common/generic/CONFIG_SX9310
deleted file mode 100644
index 371d6020b9e9..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SX9310
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_SX9310:
-#
-# Say Y here to build a driver for Semtech's SX9310/SX9311 capacitive
-# proximity/button sensor.
-#
-# To compile this driver as a module, choose M here: the
-# module will be called sx9310.
-#
-# Symbol: SX9310 [=n]
-# Type : tristate
-# Defined at drivers/iio/proximity/Kconfig:104
-# Prompt: SX9310/SX9311 Semtech proximity sensor
-# Depends on: IIO [=m] && I2C [=y]
-# Location:
-# -> Device Drivers
-# -> Industrial I/O support (IIO [=m])
-# -> Proximity and distance sensors
-# Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] && REGMAP_I2C [=m]
-#
-#
-#
-# CONFIG_SX9310 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_VCNL3020 b/redhat/configs/pending-common/generic/CONFIG_VCNL3020
deleted file mode 100644
index 7dd6f9f0f8d5..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_VCNL3020
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_VCNL3020:
-#
-# Say Y here if you want to build a driver for the Vishay VCNL3020
-# proximity sensor.
-#
-# To compile this driver as a module, choose M here: the
-# module will be called vcnl3020.
-#
-# Symbol: VCNL3020 [=n]
-# Type : tristate
-# Defined at drivers/iio/proximity/Kconfig:143
-# Prompt: VCNL3020 proximity sensor
-# Depends on: IIO [=m] && I2C [=y]
-# Location:
-# -> Device Drivers
-# -> Industrial I/O support (IIO [=m])
-# -> Proximity and distance sensors
-# Selects: REGMAP_I2C [=m]
-#
-#
-#
-# CONFIG_VCNL3020 is not set
--
2.26.2
3 years, 10 months
[OS-BUILD PATCH] [redhat] New configs in lib/Kconfig.debug
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_DEBUG_INFO_COMPRESSED:
Compress the debug information using zlib. Requires GCC 5.0+ or Clang
5.0+, binutils 2.26+, and zlib.
Users of dpkg-deb via scripts/package/builddeb may find an increase in
size of their debug .deb packages with this config set, due to the
debug info being compressed with zlib, then the object files being
recompressed with a different compression scheme. But this is still
preferable to setting $KDEB_COMPRESS to "none" which would be even
larger.
Symbol: DEBUG_INFO_COMPRESSED [=n]
Type : bool
Defined at lib/Kconfig.debug:216
Prompt: Compressed debugging information
Depends on: DEBUG_INFO [=y]
Location:
-> Kernel hacking
-> Compile-time checks and compiler options
-> Compile the kernel with debug info (DEBUG_INFO [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../generic/CONFIG_DEBUG_INFO_COMPRESSED | 1 +
.../generic/CONFIG_DEBUG_INFO_COMPRESSED | 25 -------------------
2 files changed, 1 insertion(+), 25 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_DEBUG_INFO_COMPRESSED
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DEBUG_INFO_COMPRESSED
diff --git a/redhat/configs/common/generic/CONFIG_DEBUG_INFO_COMPRESSED b/redhat/configs/common/generic/CONFIG_DEBUG_INFO_COMPRESSED
new file mode 100644
index 000000000000..a12a51893c75
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DEBUG_INFO_COMPRESSED
@@ -0,0 +1 @@
+# CONFIG_DEBUG_INFO_COMPRESSED is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_DEBUG_INFO_COMPRESSED b/redhat/configs/pending-common/generic/CONFIG_DEBUG_INFO_COMPRESSED
deleted file mode 100644
index ae75f0a2b31c..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DEBUG_INFO_COMPRESSED
+++ /dev/null
@@ -1,25 +0,0 @@
-# CONFIG_DEBUG_INFO_COMPRESSED:
-#
-# Compress the debug information using zlib. Requires GCC 5.0+ or Clang
-# 5.0+, binutils 2.26+, and zlib.
-#
-# Users of dpkg-deb via scripts/package/builddeb may find an increase in
-# size of their debug .deb packages with this config set, due to the
-# debug info being compressed with zlib, then the object files being
-# recompressed with a different compression scheme. But this is still
-# preferable to setting $KDEB_COMPRESS to "none" which would be even
-# larger.
-#
-# Symbol: DEBUG_INFO_COMPRESSED [=n]
-# Type : bool
-# Defined at lib/Kconfig.debug:216
-# Prompt: Compressed debugging information
-# Depends on: DEBUG_INFO [=y]
-# Location:
-# -> Kernel hacking
-# -> Compile-time checks and compiler options
-# -> Compile the kernel with debug info (DEBUG_INFO [=y])
-#
-#
-#
-# CONFIG_DEBUG_INFO_COMPRESSED is not set
--
2.26.2
3 years, 10 months
[OS-BUILD PATCH] [redhat] New configs in drivers/gpio
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_GPIO_AGGREGATOR:
Say yes here to enable the GPIO Aggregator, which provides a way to
aggregate existing GPIO lines into a new virtual GPIO chip.
This can serve the following purposes:
- Assign permissions for a collection of GPIO lines to a user,
- Export a collection of GPIO lines to a virtual machine,
- Provide a generic driver for a GPIO-operated device in an
industrial control context, to be operated from userspace using
the GPIO chardev interface.
Symbol: GPIO_AGGREGATOR [=n]
Type : tristate
Defined at drivers/gpio/Kconfig:1548
Prompt: GPIO Aggregator
Depends on: GPIOLIB [=y]
Location:
-> Device Drivers
-> GPIO Support (GPIOLIB [=y])
---
CONFIG_GPIO_PCA953X_IRQ:
Say yes here to enable the pca953x to be used as an interrupt
controller. It requires the driver to be built in the kernel.
Symbol: GPIO_PCA953X_IRQ [=n]
Type : bool
Defined at drivers/gpio/Kconfig:957
Prompt: Interrupt controller support for PCA953x
Depends on: GPIOLIB [=y] && I2C [=y] && GPIO_PCA953X [=m]
Location:
-> Device Drivers
-> GPIO Support (GPIOLIB [=y])
-> I2C GPIO expanders
-> PCA95[357]x, PCA9698, TCA64xx, and MAX7310 I/O ports (GPIO_PCA953X [=m])
Selects: GPIOLIB_IRQCHIP [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_GPIO_AGGREGATOR | 1 +
.../common/generic/CONFIG_GPIO_PCA953X_IRQ | 1 +
.../generic/CONFIG_GPIO_AGGREGATOR | 23 -------------------
.../generic/CONFIG_GPIO_PCA953X_IRQ | 20 ----------------
4 files changed, 2 insertions(+), 43 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_GPIO_AGGREGATOR
create mode 100644 redhat/configs/common/generic/CONFIG_GPIO_PCA953X_IRQ
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_GPIO_AGGREGATOR
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_GPIO_PCA953X_IRQ
diff --git a/redhat/configs/common/generic/CONFIG_GPIO_AGGREGATOR b/redhat/configs/common/generic/CONFIG_GPIO_AGGREGATOR
new file mode 100644
index 000000000000..71bc3505a35f
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_GPIO_AGGREGATOR
@@ -0,0 +1 @@
+# CONFIG_GPIO_AGGREGATOR is not set
diff --git a/redhat/configs/common/generic/CONFIG_GPIO_PCA953X_IRQ b/redhat/configs/common/generic/CONFIG_GPIO_PCA953X_IRQ
new file mode 100644
index 000000000000..ea752dc521b3
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_GPIO_PCA953X_IRQ
@@ -0,0 +1 @@
+# CONFIG_GPIO_PCA953X_IRQ is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_GPIO_AGGREGATOR b/redhat/configs/pending-common/generic/CONFIG_GPIO_AGGREGATOR
deleted file mode 100644
index 2d7df009c4f1..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_GPIO_AGGREGATOR
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_GPIO_AGGREGATOR:
-#
-# Say yes here to enable the GPIO Aggregator, which provides a way to
-# aggregate existing GPIO lines into a new virtual GPIO chip.
-# This can serve the following purposes:
-# - Assign permissions for a collection of GPIO lines to a user,
-# - Export a collection of GPIO lines to a virtual machine,
-# - Provide a generic driver for a GPIO-operated device in an
-# industrial control context, to be operated from userspace using
-# the GPIO chardev interface.
-#
-# Symbol: GPIO_AGGREGATOR [=n]
-# Type : tristate
-# Defined at drivers/gpio/Kconfig:1548
-# Prompt: GPIO Aggregator
-# Depends on: GPIOLIB [=y]
-# Location:
-# -> Device Drivers
-# -> GPIO Support (GPIOLIB [=y])
-#
-#
-#
-# CONFIG_GPIO_AGGREGATOR is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_GPIO_PCA953X_IRQ b/redhat/configs/pending-common/generic/CONFIG_GPIO_PCA953X_IRQ
deleted file mode 100644
index 2364c079b550..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_GPIO_PCA953X_IRQ
+++ /dev/null
@@ -1,20 +0,0 @@
-# CONFIG_GPIO_PCA953X_IRQ:
-#
-# Say yes here to enable the pca953x to be used as an interrupt
-# controller. It requires the driver to be built in the kernel.
-#
-# Symbol: GPIO_PCA953X_IRQ [=n]
-# Type : bool
-# Defined at drivers/gpio/Kconfig:957
-# Prompt: Interrupt controller support for PCA953x
-# Depends on: GPIOLIB [=y] && I2C [=y] && GPIO_PCA953X [=m]
-# Location:
-# -> Device Drivers
-# -> GPIO Support (GPIOLIB [=y])
-# -> I2C GPIO expanders
-# -> PCA95[357]x, PCA9698, TCA64xx, and MAX7310 I/O ports (GPIO_PCA953X [=m])
-# Selects: GPIOLIB_IRQCHIP [=y]
-#
-#
-#
-# CONFIG_GPIO_PCA953X_IRQ is not set
--
2.26.2
3 years, 10 months
❌ FAIL: Test report for kernel (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: 1f709d7fed11 - [redhat] kernel-5.8.0-0.rc0.20200608gitaf7b4801030c.1
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
aarch64: FAILED (see build-aarch64.log.xz attachment)
ppc64le: FAILED (see build-ppc64le.log.xz attachment)
s390x: FAILED (see build-s390x.log.xz attachment)
x86_64: FAILED (see build-x86_64.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Compile testing
---------------
We compiled the kernel for 4 architectures:
aarch64:
rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
ppc64le:
rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
s390x:
rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
x86_64:
rpmbuild arguments: rpmbuild --target x86_64 --with=bpftool --with=selftests --with=kabidw_base --without=debug --without=ipaclones --without=perf --without=tools
3 years, 11 months
❌ FAIL: Test report for kernel (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: e269b060b065 - [redhat] kernel-5.8.0-0.rc0.20200607git3b69e8b45711.1
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
aarch64: FAILED (see build-aarch64.log.xz attachment)
ppc64le: FAILED (see build-ppc64le.log.xz attachment)
s390x: FAILED (see build-s390x.log.xz attachment)
x86_64: FAILED (see build-x86_64.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Compile testing
---------------
We compiled the kernel for 4 architectures:
aarch64:
rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
ppc64le:
rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
s390x:
rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
x86_64:
rpmbuild arguments: rpmbuild --target x86_64 --with=bpftool --with=selftests --with=kabidw_base --without=debug --without=ipaclones --without=perf --without=tools
3 years, 11 months
[OS-BUILD PATCH] [redhat] New configs in drivers/hwmon
by GitLab Bridge on behalf of jeremycline
From: "CKI@GitLab" <cki-project(a)redhat.com>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_SENSORS_AMD_ENERGY:
If you say yes here you get support for core and package energy
sensors, based on RAPL MSR for AMD family 17h and above CPUs.
This driver can also be built as a module. If so, the module
will be called as amd_energy.
Symbol: SENSORS_AMD_ENERGY [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:327
Prompt: AMD RAPL MSR based Energy driver
Depends on: HWMON [=y] && X86 [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
CONFIG_SENSORS_MAX16601:
If you say yes here you get hardware monitoring support for Maxim
MAX16601.
This driver can also be built as a module. If so, the module will
be called max16601.
Symbol: SENSORS_MAX16601 [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:149
Prompt: Maxim MAX16601
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
Cc: Dean Nelson <dnelson(a)redhat.com>
Signed-off-by: CKI@GitLab <cki-project(a)redhat.com>
---
.../common/generic/CONFIG_SENSORS_AMD_ENERGY | 1 +
.../common/generic/CONFIG_SENSORS_MAX16601 | 1 +
.../generic/CONFIG_SENSORS_AMD_ENERGY | 20 ------------------
.../generic/CONFIG_SENSORS_MAX16601 | 21 -------------------
4 files changed, 2 insertions(+), 41 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_SENSORS_AMD_ENERGY
create mode 100644 redhat/configs/common/generic/CONFIG_SENSORS_MAX16601
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SENSORS_AMD_ENERGY
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SENSORS_MAX16601
diff --git a/redhat/configs/common/generic/CONFIG_SENSORS_AMD_ENERGY b/redhat/configs/common/generic/CONFIG_SENSORS_AMD_ENERGY
new file mode 100644
index 000000000000..8a4fc5222e01
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SENSORS_AMD_ENERGY
@@ -0,0 +1 @@
+# CONFIG_SENSORS_AMD_ENERGY is not set
diff --git a/redhat/configs/common/generic/CONFIG_SENSORS_MAX16601 b/redhat/configs/common/generic/CONFIG_SENSORS_MAX16601
new file mode 100644
index 000000000000..4fa6afb577fa
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SENSORS_MAX16601
@@ -0,0 +1 @@
+# CONFIG_SENSORS_MAX16601 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SENSORS_AMD_ENERGY b/redhat/configs/pending-common/generic/CONFIG_SENSORS_AMD_ENERGY
deleted file mode 100644
index 6dabcd827652..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SENSORS_AMD_ENERGY
+++ /dev/null
@@ -1,20 +0,0 @@
-# CONFIG_SENSORS_AMD_ENERGY:
-#
-# If you say yes here you get support for core and package energy
-# sensors, based on RAPL MSR for AMD family 17h and above CPUs.
-#
-# This driver can also be built as a module. If so, the module
-# will be called as amd_energy.
-#
-# Symbol: SENSORS_AMD_ENERGY [=n]
-# Type : tristate
-# Defined at drivers/hwmon/Kconfig:327
-# Prompt: AMD RAPL MSR based Energy driver
-# Depends on: HWMON [=y] && X86 [=y]
-# Location:
-# -> Device Drivers
-# -> Hardware Monitoring support (HWMON [=y])
-#
-#
-#
-# CONFIG_SENSORS_AMD_ENERGY is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SENSORS_MAX16601 b/redhat/configs/pending-common/generic/CONFIG_SENSORS_MAX16601
deleted file mode 100644
index 8ad67a216208..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SENSORS_MAX16601
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_SENSORS_MAX16601:
-#
-# If you say yes here you get hardware monitoring support for Maxim
-# MAX16601.
-#
-# This driver can also be built as a module. If so, the module will
-# be called max16601.
-#
-# Symbol: SENSORS_MAX16601 [=n]
-# Type : tristate
-# Defined at drivers/hwmon/pmbus/Kconfig:149
-# Prompt: Maxim MAX16601
-# Depends on: HWMON [=y] && PMBUS [=m]
-# Location:
-# -> Device Drivers
-# -> Hardware Monitoring support (HWMON [=y])
-# -> PMBus support (PMBUS [=m])
-#
-#
-#
-# CONFIG_SENSORS_MAX16601 is not set
--
2.26.2
3 years, 11 months
[OS-BUILD PATCH 0/46] PCI: tegra: Revert raw_violation_fixup for
tegra124
by GitLab Bridge on behalf of jmflinuxtx
From: jmflinuxtx on gitlab.com
As reported in https://bugzilla.kernel.org/206217 , raw_violation_fixup
is causing more harm than good in some common use-cases.
This patch as RFC is a partial revert of the 191cd6fb5 commit:
"PCI: tegra: Add SW fixup for RAW violations"
that was first introduced in 5.3 kernel.
This fix the following regression since then.
When using both the network NIC and I/O on MMC this can lead to the
following message on jetson-tk1:
NETDEV WATCHDOG: enp1s0 (r8169): transmit queue 0 timed out
and
pcieport 0000:00:02.0: AER: Uncorrected (Non-Fatal) error received:
0000:01:00.0
r8169 0000:01:00.0: AER: PCIe Bus Error: severity=Uncorrected (Non-
Fatal), type=Transaction Layer, (Requester ID)
r8169 0000:01:00.0: AER: device [10ec:8168] error
status/mask=00004000/00400000
r8169 0000:01:00.0: AER: [14] CmpltTO (First)
r8169 0000:01:00.0: AER: can't recover (no error_detected callback)
pcieport 0000:00:02.0: AER: device recovery failed
After that, the ethernet NIC isn't functional anymore even after
reloading
the module.
After a reboot, this is reproducible by copying a large file over the
ethernet NIC to the MMC.
For some reasons this cannot be reproduced when the same file is copied
to a tmpfs.
This patch is RFC because it requires more understanding from Nvidia.
- Is the fixup (available in l4t downstrem) still needed for upstream ?
- Is there a need to update the fixup values for upstream ?
- If the fixup is reverted, does the hw bug can still be seen with
upstream ?
Others can also provides more understanding:
- Conditions to reproduce the bug (or not)...
Signed-off-by: Nicolas Chauvet <kwizart(a)gmail.com>
Upstream Status: https://patchwork.ozlabs.org/project/linux-
tegra/patch/20200420164304.28810-1-kwizart(a)gmail.com/
Note:
The patch series is too large to sent by email.
To review the series locally, set up your repository to fetch from the GitLab
remote:
$ git remote add gitlab https://gitlab.com/cki-project/kernel-ark.git
$ git config remote.gitlab.fetch '+refs/merge-requests/*/head:refs/remotes/gitlab/merge-requests/*'
$ git fetch gitlab
Finally, check out the merge request:
$ git checkout gitlab/merge-requests/427
It is also possible to review the merge request on GitLab at:
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/427
3 years, 11 months
❌ FAIL: Test report for kernel (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: a6c8d6b72e28 - [redhat] kernel-5.8.0-0.rc0.20200605git435faf5c218a.1
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
Source RPM: FAILED (see build-generic.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Compile testing
---------------
We tried to create the SRPM package but failed.
3 years, 11 months