[OS-BUILD PATCH] [redhat] New configs in drivers/acpi
by CKI Gitlab (via Email Bridge)
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
[redhat] New configs in drivers/acpi
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_ACPI_PLATFORM_PROFILE:
This driver adds support for platform-profiles on platforms that
support it.
Platform-profiles can be used to control the platform behaviour. For
example whether to operate in a lower power mode, in a higher
power performance mode or between the two.
This driver provides the sysfs interface and is used as the registration
point for platform specific drivers.
Which profiles are supported is determined on a per-platform basis and
should be obtained from the platform specific driver.
Symbol: ACPI_PLATFORM_PROFILE [=m]
Type : tristate
Defined at drivers/acpi/Kconfig:329
Prompt: ACPI Platform Profile Driver
Depends on: ACPI [=y]
Location:
-> Power management and ACPI options
-> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y])
---
Cc: Al Stone <ahs3(a)redhat.com>
Cc: Lenny Szubowicz <lszubowi(a)redhat.com>
Cc: Prarit Bhargava <prarit(a)redhat.com>
Cc: David Arcari <darcari(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
diff a/redhat/configs/common/generic/CONFIG_ACPI_PLATFORM_PROFILE b/redhat/configs/common/generic/CONFIG_ACPI_PLATFORM_PROFILE
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ACPI_PLATFORM_PROFILE
@@ -0,0 +1 @@
+CONFIG_ACPI_PLATFORM_PROFILE=m
diff a/redhat/configs/pending-common/generic/CONFIG_ACPI_PLATFORM_PROFILE b/redhat/configs/pending-common/generic/CONFIG_ACPI_PLATFORM_PROFILE
--- a/redhat/configs/pending-common/generic/CONFIG_ACPI_PLATFORM_PROFILE
+++ /dev/null
@@ -1,27 +0,0 @@
-# CONFIG_ACPI_PLATFORM_PROFILE:
-#
-# This driver adds support for platform-profiles on platforms that
-# support it.
-#
-# Platform-profiles can be used to control the platform behaviour. For
-# example whether to operate in a lower power mode, in a higher
-# power performance mode or between the two.
-#
-# This driver provides the sysfs interface and is used as the registration
-# point for platform specific drivers.
-#
-# Which profiles are supported is determined on a per-platform basis and
-# should be obtained from the platform specific driver.
-#
-# Symbol: ACPI_PLATFORM_PROFILE [=m]
-# Type : tristate
-# Defined at drivers/acpi/Kconfig:329
-# Prompt: ACPI Platform Profile Driver
-# Depends on: ACPI [=y]
-# Location:
-# -> Power management and ACPI options
-# -> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y])
-#
-#
-#
-CONFIG_ACPI_PLATFORM_PROFILE=m
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/901
3 years, 2 months
[OS-BUILD PATCH] Bluetooth: L2CAP: Try harder to accept device not
knowing
options
by Bastien Nocera (via Email Bridge)
From: Bastien Nocera <hadess(a)hadess.net>
Bluetooth: L2CAP: Try harder to accept device not knowing options
The current implementation of L2CAP options negotiation will continue
the negotiation when a device responds with L2CAP_CONF_UNACCEPT ("unaccepted
options"), but not when the device replies with L2CAP_CONF_UNKNOWN ("unknown
options").
Trying to continue the negotiation without ERTM support will allow
Bluetooth-capable XBox One controllers (notably models 1708 and 1797)
to connect.
btmon before patch:
> ACL Data RX: Handle 256 flags 0x02 dlen 16 #64 [hci0] 59.182702
L2CAP: Connection Response (0x03) ident 2 len 8
Destination CID: 64
Source CID: 64
Result: Connection successful (0x0000)
Status: No further information available (0x0000)
< ACL Data TX: Handle 256 flags 0x00 dlen 23 #65 [hci0] 59.182744
L2CAP: Configure Request (0x04) ident 3 len 15
Destination CID: 64
Flags: 0x0000
Option: Retransmission and Flow Control (0x04) [mandatory]
Mode: Basic (0x00)
TX window size: 0
Max transmit: 0
Retransmission timeout: 0
Monitor timeout: 0
Maximum PDU size: 0
> ACL Data RX: Handle 256 flags 0x02 dlen 16 #66 [hci0] 59.183948
L2CAP: Configure Request (0x04) ident 1 len 8
Destination CID: 64
Flags: 0x0000
Option: Maximum Transmission Unit (0x01) [mandatory]
MTU: 1480
< ACL Data TX: Handle 256 flags 0x00 dlen 18 #67 [hci0] 59.183994
L2CAP: Configure Response (0x05) ident 1 len 10
Source CID: 64
Flags: 0x0000
Result: Success (0x0000)
Option: Maximum Transmission Unit (0x01) [mandatory]
MTU: 1480
> ACL Data RX: Handle 256 flags 0x02 dlen 15 #69 [hci0] 59.187676
L2CAP: Configure Response (0x05) ident 3 len 7
Source CID: 64
Flags: 0x0000
Result: Failure - unknown options (0x0003)
04 .
< ACL Data TX: Handle 256 flags 0x00 dlen 12 #70 [hci0] 59.187722
L2CAP: Disconnection Request (0x06) ident 4 len 4
Destination CID: 64
Source CID: 64
> ACL Data RX: Handle 256 flags 0x02 dlen 12 #73 [hci0] 59.192714
L2CAP: Disconnection Response (0x07) ident 4 len 4
Destination CID: 64
Source CID: 64
btmon after patch:
> ACL Data RX: Handle 256 flags 0x02 dlen 16 #248 [hci0] 103.502970
L2CAP: Connection Response (0x03) ident 5 len 8
Destination CID: 65
Source CID: 65
Result: Connection pending (0x0001)
Status: No further information available (0x0000)
> ACL Data RX: Handle 256 flags 0x02 dlen 16 #249 [hci0] 103.504184
L2CAP: Connection Response (0x03) ident 5 len 8
Destination CID: 65
Source CID: 65
Result: Connection successful (0x0000)
Status: No further information available (0x0000)
< ACL Data TX: Handle 256 flags 0x00 dlen 23 #250 [hci0] 103.504398
L2CAP: Configure Request (0x04) ident 6 len 15
Destination CID: 65
Flags: 0x0000
Option: Retransmission and Flow Control (0x04) [mandatory]
Mode: Basic (0x00)
TX window size: 0
Max transmit: 0
Retransmission timeout: 0
Monitor timeout: 0
Maximum PDU size: 0
> ACL Data RX: Handle 256 flags 0x02 dlen 16 #251 [hci0] 103.505472
L2CAP: Configure Request (0x04) ident 3 len 8
Destination CID: 65
Flags: 0x0000
Option: Maximum Transmission Unit (0x01) [mandatory]
MTU: 1480
< ACL Data TX: Handle 256 flags 0x00 dlen 18 #252 [hci0] 103.505689
L2CAP: Configure Response (0x05) ident 3 len 10
Source CID: 65
Flags: 0x0000
Result: Success (0x0000)
Option: Maximum Transmission Unit (0x01) [mandatory]
MTU: 1480
> ACL Data RX: Handle 256 flags 0x02 dlen 15 #254 [hci0] 103.509165
L2CAP: Configure Response (0x05) ident 6 len 7
Source CID: 65
Flags: 0x0000
Result: Failure - unknown options (0x0003)
04 .
< ACL Data TX: Handle 256 flags 0x00 dlen 12 #255 [hci0] 103.509426
L2CAP: Configure Request (0x04) ident 7 len 4
Destination CID: 65
Flags: 0x0000
< ACL Data TX: Handle 256 flags 0x00 dlen 12 #257 [hci0] 103.511870
L2CAP: Connection Request (0x02) ident 8 len 4
PSM: 1 (0x0001)
Source CID: 66
> ACL Data RX: Handle 256 flags 0x02 dlen 14 #259 [hci0] 103.514121
L2CAP: Configure Response (0x05) ident 7 len 6
Source CID: 65
Flags: 0x0000
Result: Success (0x0000)
Upstream Status: bluetooth/bluetooth-next.git
(cherry picked from commit 98d2c3e1731007acf03addf83c863df6694beb95)
Signed-off-by: Bastien Nocera <hadess(a)hadess.net>
Signed-off-by: Florian Dollinger <dollinger.florian(a)gmx.de>
Co-developed-by: Florian Dollinger <dollinger.florian(a)gmx.de>
Reviewed-by: Luiz Augusto Von Dentz <luiz.von.dentz(a)intel.com>
Signed-off-by: Marcel Holtmann <marcel(a)holtmann.org>
diff a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
--- a/net/bluetooth/l2cap_core.c
+++ b/net/bluetooth/l2cap_core.c
@@ -4519,6 +4519,7 @@ static inline int l2cap_config_rsp(struct l2cap_conn *conn,
}
goto done;
+ case L2CAP_CONF_UNKNOWN:
case L2CAP_CONF_UNACCEPT:
if (chan->num_conf_rsp <= L2CAP_CONF_MAX_CONF_RSP) {
char req[64];
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/872
3 years, 2 months
[OS-BUILD PATCH] [redhat] New configs in drivers/powercap
by CKI Gitlab (via Email Bridge)
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
[redhat] New configs in drivers/powercap
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_DTPM:
This enables support for the power capping for the dynamic
thermal power management userspace engine.
Symbol: DTPM [=n]
Type : bool
Defined at drivers/powercap/Kconfig:47
Prompt: Power capping for Dynamic Thermal Power Management
Depends on: POWERCAP [=y]
Location:
-> Device Drivers
-> Generic powercap sysfs driver (POWERCAP [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
diff a/redhat/configs/common/generic/CONFIG_DTPM b/redhat/configs/common/generic/CONFIG_DTPM
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DTPM
@@ -0,0 +1 @@
+# CONFIG_DTPM is not set
diff a/redhat/configs/pending-common/generic/CONFIG_DTPM b/redhat/configs/pending-common/generic/CONFIG_DTPM
--- a/redhat/configs/pending-common/generic/CONFIG_DTPM
+++ /dev/null
@@ -1,17 +0,0 @@
-# CONFIG_DTPM:
-#
-# This enables support for the power capping for the dynamic
-# thermal power management userspace engine.
-#
-# Symbol: DTPM [=n]
-# Type : bool
-# Defined at drivers/powercap/Kconfig:47
-# Prompt: Power capping for Dynamic Thermal Power Management
-# Depends on: POWERCAP [=y]
-# Location:
-# -> Device Drivers
-# -> Generic powercap sysfs driver (POWERCAP [=y])
-#
-#
-#
-# CONFIG_DTPM is not set
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/910
3 years, 2 months
[OS-BUILD PATCH] [redhat] New configs in
drivers/net/ethernet/mellanox
by CKI Gitlab (via Email Bridge)
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
[redhat] New configs in drivers/net/ethernet/mellanox
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_MLX5_SF:
Build support for subfuction device in the NIC. A Mellanox subfunction
device can support RDMA, netdevice and vdpa device.
It is similar to a SRIOV VF but it doesn't require SRIOV support.
Symbol: MLX5_SF [=n]
Type : bool
Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:205
Prompt: Mellanox Technologies subfunction device support using auxiliary device
Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_CORE [=m] && MLX5_CORE_EN [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Ethernet driver support (ETHERNET [=y])
-> Mellanox devices (NET_VENDOR_MELLANOX [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
diff a/redhat/configs/common/generic/CONFIG_MLX5_SF b/redhat/configs/common/generic/CONFIG_MLX5_SF
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_MLX5_SF
@@ -0,0 +1 @@
+# CONFIG_MLX5_SF is not set
diff a/redhat/configs/pending-common/generic/CONFIG_MLX5_SF b/redhat/configs/pending-common/generic/CONFIG_MLX5_SF
--- a/redhat/configs/pending-common/generic/CONFIG_MLX5_SF
+++ /dev/null
@@ -1,20 +0,0 @@
-# CONFIG_MLX5_SF:
-#
-# Build support for subfuction device in the NIC. A Mellanox subfunction
-# device can support RDMA, netdevice and vdpa device.
-# It is similar to a SRIOV VF but it doesn't require SRIOV support.
-#
-# Symbol: MLX5_SF [=n]
-# Type : bool
-# Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:205
-# Prompt: Mellanox Technologies subfunction device support using auxiliary device
-# Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_CORE [=m] && MLX5_CORE_EN [=y]
-# Location:
-# -> Device Drivers
-# -> Network device support (NETDEVICES [=y])
-# -> Ethernet driver support (ETHERNET [=y])
-# -> Mellanox devices (NET_VENDOR_MELLANOX [=y])
-#
-#
-#
-# CONFIG_MLX5_SF is not set
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/908
3 years, 2 months
[OS-BUILD PATCH] [redhat] New configs in drivers/leds
by CKI Gitlab (via Email Bridge)
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
[redhat] New configs in drivers/leds
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_LEDS_TRIGGER_TTY:
This allows LEDs to be controlled by activity on ttys which includes
serial devices like /dev/ttyS0.
When build as a module this driver will be called ledtrig-tty.
Symbol: LEDS_TRIGGER_TTY [=n]
Type : tristate
Defined at drivers/leds/trigger/Kconfig:147
Prompt: LED Trigger for TTY devices
Depends on: NEW_LEDS [=y] && LEDS_TRIGGERS [=y] && TTY [=y]
Location:
-> Device Drivers
-> LED Support (NEW_LEDS [=y])
-> LED Trigger support (LEDS_TRIGGERS [=y])
---
Cc: Tony Camuso <tcamuso(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
diff a/redhat/configs/common/generic/CONFIG_LEDS_TRIGGER_TTY b/redhat/configs/common/generic/CONFIG_LEDS_TRIGGER_TTY
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_LEDS_TRIGGER_TTY
@@ -0,0 +1 @@
+# CONFIG_LEDS_TRIGGER_TTY is not set
diff a/redhat/configs/pending-common/generic/CONFIG_LEDS_TRIGGER_TTY b/redhat/configs/pending-common/generic/CONFIG_LEDS_TRIGGER_TTY
--- a/redhat/configs/pending-common/generic/CONFIG_LEDS_TRIGGER_TTY
+++ /dev/null
@@ -1,20 +0,0 @@
-# CONFIG_LEDS_TRIGGER_TTY:
-#
-# This allows LEDs to be controlled by activity on ttys which includes
-# serial devices like /dev/ttyS0.
-#
-# When build as a module this driver will be called ledtrig-tty.
-#
-# Symbol: LEDS_TRIGGER_TTY [=n]
-# Type : tristate
-# Defined at drivers/leds/trigger/Kconfig:147
-# Prompt: LED Trigger for TTY devices
-# Depends on: NEW_LEDS [=y] && LEDS_TRIGGERS [=y] && TTY [=y]
-# Location:
-# -> Device Drivers
-# -> LED Support (NEW_LEDS [=y])
-# -> LED Trigger support (LEDS_TRIGGERS [=y])
-#
-#
-#
-# CONFIG_LEDS_TRIGGER_TTY is not set
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/905
3 years, 2 months
[OS-BUILD PATCH] [redhat] New configs in drivers/iio
by CKI Gitlab (via Email Bridge)
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
[redhat] New configs in drivers/iio
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_AD5766:
Say yes here to build support for Analog Devices AD5766, AD5767
Digital to Analog Converter.
To compile this driver as a module, choose M here: the
module will be called ad5766.
Symbol: AD5766 [=n]
Type : tristate
Defined at drivers/iio/dac/Kconfig:192
Prompt: Analog Devices AD5766/AD5767 DAC driver
Depends on: IIO [=m] && SPI_MASTER [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Digital to analog converters
---
CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE:
This sensor present three angles, hinge angel, screen angles
and keyboard angle respect to horizon (ground).
Say yes here to build support for the HID custom
intel hinge sensor.
To compile this driver as a module, choose M here: the
module will be called hid-sensor-custom-hinge.
Symbol: HID_SENSOR_CUSTOM_INTEL_HINGE [=n]
Type : tristate
Defined at drivers/iio/position/Kconfig:19
Prompt: HID Hinge
Depends on: IIO [=m] && HID_SENSOR_HUB [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Linear and angular position sensors
Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] && HID_SENSOR_IIO_COMMON [=m] && HID_SENSOR_IIO_TRIGGER [=m]
---
CONFIG_YAMAHA_YAS530:
Say Y here to add support for the Yamaha YAS530 series of
3-Axis Magnetometers. Right now YAS530, YAS532 and YAS533 are
fully supported.
This driver can also be compiled as a module.
To compile this driver as a module, choose M here: the module
will be called yamaha-yas.
Symbol: YAMAHA_YAS530 [=n]
Type : tristate
Defined at drivers/iio/magnetometer/Kconfig:208
Prompt: Yamaha YAS530 family of 3-Axis Magnetometers (I2C)
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Magnetometer sensors
Selects: REGMAP_I2C [=m] && IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
diff a/redhat/configs/common/generic/CONFIG_AD5766 b/redhat/configs/common/generic/CONFIG_AD5766
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_AD5766
@@ -0,0 +1 @@
+# CONFIG_AD5766 is not set
diff a/redhat/configs/common/generic/CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE b/redhat/configs/common/generic/CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE
@@ -0,0 +1 @@
+# CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE is not set
diff a/redhat/configs/common/generic/CONFIG_YAMAHA_YAS530 b/redhat/configs/common/generic/CONFIG_YAMAHA_YAS530
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_YAMAHA_YAS530
@@ -0,0 +1 @@
+# CONFIG_YAMAHA_YAS530 is not set
diff a/redhat/configs/pending-common/generic/CONFIG_AD5766 b/redhat/configs/pending-common/generic/CONFIG_AD5766
--- a/redhat/configs/pending-common/generic/CONFIG_AD5766
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_AD5766:
-#
-# Say yes here to build support for Analog Devices AD5766, AD5767
-# Digital to Analog Converter.
-#
-# To compile this driver as a module, choose M here: the
-# module will be called ad5766.
-#
-# Symbol: AD5766 [=n]
-# Type : tristate
-# Defined at drivers/iio/dac/Kconfig:192
-# Prompt: Analog Devices AD5766/AD5767 DAC driver
-# Depends on: IIO [=m] && SPI_MASTER [=y]
-# Location:
-# -> Device Drivers
-# -> Industrial I/O support (IIO [=m])
-# -> Digital to analog converters
-#
-#
-#
-# CONFIG_AD5766 is not set
diff a/redhat/configs/pending-common/generic/CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE b/redhat/configs/pending-common/generic/CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE
--- a/redhat/configs/pending-common/generic/CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE
+++ /dev/null
@@ -1,24 +0,0 @@
-# CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE:
-#
-# This sensor present three angles, hinge angel, screen angles
-# and keyboard angle respect to horizon (ground).
-# Say yes here to build support for the HID custom
-# intel hinge sensor.
-#
-# To compile this driver as a module, choose M here: the
-# module will be called hid-sensor-custom-hinge.
-#
-# Symbol: HID_SENSOR_CUSTOM_INTEL_HINGE [=n]
-# Type : tristate
-# Defined at drivers/iio/position/Kconfig:19
-# Prompt: HID Hinge
-# Depends on: IIO [=m] && HID_SENSOR_HUB [=y]
-# Location:
-# -> Device Drivers
-# -> Industrial I/O support (IIO [=m])
-# -> Linear and angular position sensors
-# Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] && HID_SENSOR_IIO_COMMON [=m] && HID_SENSOR_IIO_TRIGGER [=m]
-#
-#
-#
-# CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE is not set
diff a/redhat/configs/pending-common/generic/CONFIG_YAMAHA_YAS530 b/redhat/configs/pending-common/generic/CONFIG_YAMAHA_YAS530
--- a/redhat/configs/pending-common/generic/CONFIG_YAMAHA_YAS530
+++ /dev/null
@@ -1,24 +0,0 @@
-# CONFIG_YAMAHA_YAS530:
-#
-# Say Y here to add support for the Yamaha YAS530 series of
-# 3-Axis Magnetometers. Right now YAS530, YAS532 and YAS533 are
-# fully supported.
-#
-# This driver can also be compiled as a module.
-# To compile this driver as a module, choose M here: the module
-# will be called yamaha-yas.
-#
-# Symbol: YAMAHA_YAS530 [=n]
-# Type : tristate
-# Defined at drivers/iio/magnetometer/Kconfig:208
-# Prompt: Yamaha YAS530 family of 3-Axis Magnetometers (I2C)
-# Depends on: IIO [=m] && I2C [=y]
-# Location:
-# -> Device Drivers
-# -> Industrial I/O support (IIO [=m])
-# -> Magnetometer sensors
-# Selects: REGMAP_I2C [=m] && IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]
-#
-#
-#
-# CONFIG_YAMAHA_YAS530 is not set
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/904
3 years, 2 months
Rawhide kernels have CONFIG_USB_RTL8152 unset causing ethernet to not
work on many docking-stations ?
by Hans de Goede
Hi All,
I'm sending out an email about this as I'm not 100% sure how to fix this.
As a kernel-developer I usually build my own local kernels, since I'm also
a Fedora developer I try to keep the kernel .config of my local builds
synced with the Fedora kernel-configs. When grabbing the config from the
kernel-core-5.11.0-0.rc6.141.fc34.x86_64.rpm pkg and comparing it to
my local config I noticed this:
# CONFIG_USB_RTL8152 is not set
And I immediately thought that can't be right, that is used in my
Lenovo Thunderbolt docking station gen 2.
It took me some digging to figure out what is going on here:
[hans@x1 kernel-ark]$ pwd
/home/hans/projects/kernel-ark
[hans@x1 kernel-ark]$ find -name CONFIG_USB_RTL8152
./redhat/configs/common/generic/CONFIG_USB_RTL8152
[hans@x1 kernel-ark]$ cat ./redhat/configs/common/generic/CONFIG_USB_RTL8152
CONFIG_USB_RTL8152=m
That looks good, but is not what is in the rawhide-build, digging deeper
finds this:
[hans@x1 rawhide]$ pwd
/home/hans/projects/fedora/kernel/rawhide
[hans@x1 rawhide]$ grep CONFIG_USB_RTL8152 kernel-x86_64-fedora.config
# CONFIG_USB_RTL8152 is not set, or the RTL8153 device is not
Which looks weird and then I found this, which explains everything:
[hans@x1 kernel-ark]$ cat redhat/configs/fedora/generic/CONFIG_USB_RTL8153_ECM
# CONFIG_USB_RTL8153_ECM:
#
# This option supports ECM mode for RTL8153 ethernet adapter, when
# CONFIG_USB_RTL8152 is not set, or the RTL8153 device is not
# supported by r8152 driver.
#
# Symbol: USB_RTL8153_ECM [=m]
# Type : tristate
# Defined at drivers/net/usb/Kconfig:631
# Prompt: RTL8153 ECM support
# Depends on: NETDEVICES [=y] && USB_NET_DRIVERS [=y] && USB_NET_CDCETHER [=m] && (USB_RTL8152 [=m] || USB_RTL8152 [=m]=n)
# Location:
# -> Device Drivers
# -> Network device support (NETDEVICES [=y])
# -> USB Network Adapters (USB_NET_DRIVERS [=y])
#
#
#
CONFIG_USB_RTL8153_ECM=m
The script which is creating kernel-x86_64-fedora.config from all the CONFIG_FOO files is picking up the
line from the comment block because the line matches the standard "# CONFIG_FOO is not set" template
(with extra text at the end).
Interestingly enough, I also see this:
[hans@x1 kernel-ark]$ grep CONFIG_USB_RTL8152 redhat/configs/kernel-x86_64-fedora.config
CONFIG_USB_RTL8152=m
So on the kernel-x86_64-fedora.config in kernel-ark things are ok,
but in the kernel-x86_64-fedora.config file in distgit, rawhide branch
it is not ok ? I guess there is some difference in how these are generated ?
Regards,
Hans
3 years, 2 months
[OS-BUILD PATCH] rpmspec: ship gpio-watch.debug in the proper
debuginfo
package
by Herton Krzesinski (via Email Bridge)
From: Herton R. Krzesinski <herton(a)redhat.com>
rpmspec: ship gpio-watch.debug in the proper debuginfo package
The gpio-watch tool is shipped within the kernel-tools package. However,
when it was added some time ago, the debuginfo pattern inside the spec
file was not updated, so the gpio-watch.debug file ends up in the
kernel-debuginfo-common package instead of the kernel-tools-debuginfo.
This change fixes the problem, and also it's likely will fix an
update/downgrade test done on CI for RHEL that reports:
Error: Transaction test error:
file /usr/lib/debug/usr/bin/gpio-watch.debug from install of
kernel-debuginfo-common-x86_64-5.11.0-0.rc7.151.el9.x86_64 conflicts
with file from package kernel-debuginfo-common-x86_64-5.11.0-1.el9.x86_64
Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com>
diff a/redhat/kernel.spec.template b/redhat/kernel.spec.template
--- a/redhat/kernel.spec.template
+++ b/redhat/kernel.spec.template
@@ -930,7 +930,7 @@ This package provides debug information for package kernel-tools.
# symlinks because of the trailing nonmatching alternation and
# the leading .*, because of find-debuginfo.sh's buggy handling
# of matching the pattern against the symlinks file.
-%{expand:%%global _find_debuginfo_opts %{?_find_debuginfo_opts} -p '.*%%{_bindir}/centrino-decode(\.debug)?|.*%%{_bindir}/powernow-k8-decode(\.debug)?|.*%%{_bindir}/cpupower(\.debug)?|.*%%{_libdir}/libcpupower.*|.*%%{_bindir}/turbostat(\.debug)?|.*%%{_bindir}/x86_energy_perf_policy(\.debug)?|.*%%{_bindir}/tmon(\.debug)?|.*%%{_bindir}/lsgpio(\.debug)?|.*%%{_bindir}/gpio-hammer(\.debug)?|.*%%{_bindir}/gpio-event-mon(\.debug)?|.*%%{_bindir}/iio_event_monitor(\.debug)?|.*%%{_bindir}/iio_generic_buffer(\.debug)?|.*%%{_bindir}/lsiio(\.debug)?|.*%%{_bindir}/intel-speed-select(\.debug)?|XXX' -o kernel-tools-debuginfo.list}
+%{expand:%%global _find_debuginfo_opts %{?_find_debuginfo_opts} -p '.*%%{_bindir}/centrino-decode(\.debug)?|.*%%{_bindir}/powernow-k8-decode(\.debug)?|.*%%{_bindir}/cpupower(\.debug)?|.*%%{_libdir}/libcpupower.*|.*%%{_bindir}/turbostat(\.debug)?|.*%%{_bindir}/x86_energy_perf_policy(\.debug)?|.*%%{_bindir}/tmon(\.debug)?|.*%%{_bindir}/lsgpio(\.debug)?|.*%%{_bindir}/gpio-hammer(\.debug)?|.*%%{_bindir}/gpio-event-mon(\.debug)?|.*%%{_bindir}/gpio-watch(\.debug)?|.*%%{_bindir}/iio_event_monitor(\.debug)?|.*%%{_bindir}/iio_generic_buffer(\.debug)?|.*%%{_bindir}/lsiio(\.debug)?|.*%%{_bindir}/intel-speed-select(\.debug)?|XXX' -o kernel-tools-debuginfo.list}
# with_tools
%endif
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/896
3 years, 2 months
[OS-BUILD PATCHv3 0/2] [redhat] New configs in net/netfilter
by CKI Gitlab (via Email Bridge)
From: CKI Gitlab on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/812
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_NFT_REJECT_NETDEV:
This option enables the REJECT support from the netdev table.
The return packet generation will be delegated to the IPv4
or IPv6 ICMP or TCP RST implementation depending on the
protocol of the packet.
Symbol: NFT_REJECT_NETDEV [=n]
Type : tristate
Defined at net/netfilter/Kconfig:685
Prompt: Netfilter nf_tables netdev REJECT support
Depends on: NET [=y] && INET [=y] && NETFILTER [=y] && NF_TABLES [=m]
&& NF_TABLES_NETDEV [=y] && NFT_REJECT_IPV4 [=m] && NFT_REJECT_IPV6 [=m]
Location:
-> Networking support (NET [=y])
-> Networking options
-> Network packet filtering framework (Netfilter) (NETFILTER
[=y])
-> Core Netfilter Configuration
-> Netfilter nf_tables support (NF_TABLES [=m])
---
Cc: Florian Westphal <fwestpha(a)redhat.com>
Cc: Jiri Benc <jbenc(a)redhat.com>
Cc: Marcelo Leitner <mleitner(a)redhat.com>
Cc: Davide Caratti <dcaratti(a)redhat.com>
Cc: Eric Garver <egarver(a)redhat.com>
Cc: Flavio Leitner <fbl(a)redhat.com>
Cc: Guillaume Nault <gnault(a)redhat.com>
Cc: Hangbin Liu <haliu(a)redhat.com>
Cc: Ivan Vecera <ivecera(a)redhat.com>
Cc: Jarod Wilson <jarod(a)redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi(a)redhat.com>
Cc: Paolo Abeni <pabeni(a)redhat.com>
Cc: Phil Sutter <psutter(a)redhat.com>
Cc: Sabrina Dubroca <sdubroca(a)redhat.com>
Cc: Stefano Brivio <sbrivio(a)redhat.com>
Cc: Xin Long <lxin(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
3 years, 2 months
[OS-BUILD PATCH] [redhat] New configs in drivers/net/ethernet/chelsio
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_CHELSIO_INLINE_CRYPTO:
Enable support for inline crypto.
Allows enable/disable from list of inline crypto drivers.
Symbol: CHELSIO_INLINE_CRYPTO [=y]
Type : bool
Defined at drivers/net/ethernet/chelsio/inline_crypto/Kconfig:6
Prompt: Chelsio Inline Crypto support
Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_CHELSIO [=y] && CHELSIO_T4 [=m]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Ethernet driver support (ETHERNET [=y])
-> Chelsio devices (NET_VENDOR_CHELSIO [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../generic/CONFIG_CHELSIO_INLINE_CRYPTO | 1 +
.../generic/CONFIG_CHELSIO_INLINE_CRYPTO | 19 -------------------
2 files changed, 1 insertion(+), 19 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_CHELSIO_INLINE_CRYPTO
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CHELSIO_INLINE_CRYPTO
diff --git a/redhat/configs/common/generic/CONFIG_CHELSIO_INLINE_CRYPTO b/redhat/configs/common/generic/CONFIG_CHELSIO_INLINE_CRYPTO
new file mode 100644
index 000000000000..bd32df3059f2
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_CHELSIO_INLINE_CRYPTO
@@ -0,0 +1 @@
+CONFIG_CHELSIO_INLINE_CRYPTO=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_CHELSIO_INLINE_CRYPTO b/redhat/configs/pending-common/generic/CONFIG_CHELSIO_INLINE_CRYPTO
deleted file mode 100644
index 95b39e771a2a..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_CHELSIO_INLINE_CRYPTO
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_CHELSIO_INLINE_CRYPTO:
-#
-# Enable support for inline crypto.
-# Allows enable/disable from list of inline crypto drivers.
-#
-# Symbol: CHELSIO_INLINE_CRYPTO [=y]
-# Type : bool
-# Defined at drivers/net/ethernet/chelsio/inline_crypto/Kconfig:6
-# Prompt: Chelsio Inline Crypto support
-# Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_CHELSIO [=y] && CHELSIO_T4 [=m]
-# Location:
-# -> Device Drivers
-# -> Network device support (NETDEVICES [=y])
-# -> Ethernet driver support (ETHERNET [=y])
-# -> Chelsio devices (NET_VENDOR_CHELSIO [=y])
-#
-#
-#
-CONFIG_CHELSIO_INLINE_CRYPTO=y
--
GitLab
3 years, 2 months