cxl: Add support for Restricted CXL hosts (RCD mode)
cover cxl: Add support for Restricted CXL hosts (RCD mode)
In Restricted CXL Device (RCD) mode (formerly referred to as CXL 1.1) the PCIe enumeration hierarchy is different from CXL VH Enumeration (formerly referred to as 2.0, for both modes see CXL spec 3.0: 9.11 and 9.12, [1]). This series adds support for RCD mode. It implements the detection of Restricted CXL Hosts (RCHs) and its corresponding Restricted CXL Devices (RCDs). It does the necessary enumeration of ports and connects the endpoints. With all the plumbing an RCH/RCD pair is registered at the Linux CXL bus and becomes visible in sysfs in the same way as CXL VH hosts and devices do already. RCDs are brought up as CXL endpoints and bound to subsequent drivers such as cxl_mem.
For CXL VH the host driver (cxl_acpi) starts host bridge discovery once the ACPI0017 CXL root device is detected and then searches for ACPI0016 host bridges to enable CXL. In RCD mode an ACPI0017 device might not necessarily exist and the host bridge can have a standard PCIe host bridge PNP0A08 ID, there aren't any CXL port or switches in the PCIe hierarchy visible. As such the RCD mode enumeration and host discovery is very different from CXL VH. See patch #5 for implementation details.
This implementation expects the host's downstream and upstream port RCRBs base address being reported by firmware using the optional CEDT CHBS entry of the host bridge (see CXL spec 3.0, 9.17.1.2).
RCD mode does not support hot-plug, so host discovery is at boot time only.
Patches #1 to #4 are prerequisites of the series with fixes needed and a rework of debug messages for port enumeration. Those are general patches and could be applied earlier and independently from the rest assuming there are no objections with them. Patches #5 to #15 contain the actual implementation of RCD mode support.
[1] https://www.computeexpresslink.org/spec-landing
Robert Richter (15):
cxl/core: Remove duplicate declaration of devm_cxl_iomap_block() cxl/core: Check physical address before mapping it in
devm_cxl_iomap_block()
cxl: Unify debug messages when calling devm_cxl_add_port()
cxl: Unify debug messages when calling devm_cxl_add_dport() cxl/acpi: Add probe function to detect restricted CXL hosts in RCD
mode
PCI/ACPI: Link host bridge to its ACPI fw node
cxl/acpi: Check RCH's PCIe Host Bridge ACPI ID
cxl/acpi: Check RCH's CXL DVSEC capabilities
cxl/acpi: Determine PCI host bridge's ACPI UID
cxl/acpi: Extract the RCH's RCRB base address from CEDT cxl/acpi: Extract the host's component register base address from RCRB cxl/acpi: Skip devm_cxl_port_enumerate_dports() when in RCD mode cxl/acpi: Rework devm_cxl_enumerate_ports() to support RCD mode cxl/acpi: Enumerate ports in RCD mode to enable RCHs and RCDs cxl/acpi: Specify module load order dependency for the cxl_acpi module
drivers/acpi/pci_root.c | 1 + drivers/cxl/acpi.c | 311 ++++++++++++++++++++++++++++++++++- drivers/cxl/core/pci.c | 22 ++- drivers/cxl/core/port.c | 103 ++++++++---- drivers/cxl/core/regs.c | 3 + drivers/cxl/cxl.h | 2 - drivers/cxl/mem.c | 1 + tools/testing/cxl/test/cxl.c | 8 +- 8 files changed, 400 insertions(+), 51 deletions(-)
Signature · 1 line
2.30.2
PATCH 1/15 cxl/core: Remove duplicate declaration of devm_cxl_iomap_block()
The function devm_cxl_iomap_block() is only used in the core code. There are two declarations in header files of it, in drivers/cxl/core/core.h and drivers/cxl/cxl.h. Remove its unused declaration in drivers/cxl/cxl.h.
--- drivers/cxl/cxl.h | 2 -- 1 file changed, 2 deletions(-)
drivers/cxl/cxl.h +0 -2
@@ -218,8 +218,6 @@ int cxl_map_device_regs(struct pci_dev *pdev,enum cxl_regloc_type ;int cxl_find_regblock (struct pci_dev *pdev,enum cxl_regloc_type type,struct cxl_register_map *map); -void __iomem *devm_cxl_iomap_block (struct device *dev,resource_size_t addr, -resource_size_t length);#define CXL_RESOURCE_NONE ((resource_size_t) -1)#define CXL_TARGET_STRLEN 20
Signature · 1 line
2.30.2
Re: [PATCH 01/15] cxl/core: Remove duplicate declaration of devm_cxl_iomap_block()
Quoted 6 lines · On Wed, 31 Aug 2022 10:15:49 +0200 Robert Richter <[email protected]> wrote:
The function
devm_cxl_iomap_block()is only used in the core code. There are two declarations in header files of it, indrivers/cxl/core/core.handdrivers/cxl/cxl.h. Remove its unused declaration indrivers/cxl/cxl.h.Signed-off-by Robert Richter <[email protected]>
The wonders of code evolution leaving signs behind ;)
Quoted 17 lines
--- drivers/cxl/cxl.h | 2 -- 1 file changed, 2 deletions(-)drivers/cxl/cxl.h +0
-2@@ -218,8 +218,6 @@ int cxl_map_device_regs(struct pci_dev *pdev,enum cxl_regloc_type ;int cxl_find_regblock (struct pci_dev *pdev,enum cxl_regloc_type type,struct cxl_register_map *map); -void __iomem *devm_cxl_iomap_block (struct device *dev,resource_size_t addr, -resource_size_t length);#define CXL_RESOURCE_NONE ((resource_size_t) -1)#define CXL_TARGET_STRLEN 20
Re: [PATCH 01/15] cxl/core: Remove duplicate declaration of devm_cxl_iomap_block()
Thanks Jonathan for reviewing this series.
Quoted 10 lines · Jonathan Cameron
Quoted 6 lines · On Wed, 31 Aug 2022 10:15:49 +0200 Robert Richter <[email protected]> wrote:
The function
devm_cxl_iomap_block()is only used in the core code. There are two declarations in header files of it, indrivers/cxl/core/core.handdrivers/cxl/cxl.h. Remove its unused declaration indrivers/cxl/cxl.h.Signed-off-by Robert Richter <[email protected]>Reviewed-by Jonathan Cameron <[email protected]>
There is this 0day test bot warning and I will need to either extend this patch or add another one to fix regs.c.
-Robert
Quoted 6 lines
The wonders of code evolution leaving signs behind ;)
Quoted 3 lines
--- drivers/cxl/cxl.h | 2 -- 1 file changed, 2 deletions(-)
kernel test robot
build botRe: [PATCH 01/15] cxl/core: Remove duplicate declaration of devm_cxl_iomap_block()
In reply to Robert RichterI love your patch! Perhaps something to improve:
Hi Robert,
I love your patch! Perhaps something to improve:
[auto build test WARNING on helgaas-pci/next]
[also build test WARNING on linus/master v6.0-rc3 next-20220830] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Robert-Richter/cxl-Add-support-for-Restricted-CXL-hosts-RCD-mode/20220831-161955 base: https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next config: alpha-allyesconfig compiler: alpha-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/cb2fb876ae88418bdae58f974a4905b661792cc5
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Robert-Richter/cxl-Add-support-for-Restricted-CXL-hosts-RCD-mode/20220831-161955 git checkout cb2fb876ae88418bdae58f974a4905b661792cc5
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=alpha SHELL=/bin/bash drivers/cxl/core/
If you fix the issue, kindly add following tag where applicable
All warnings (new ones prefixed by >>):
>> drivers/cxl/core/regs.c:162:15: warning: no previous prototype for 'devm_cxl_iomap_block' [-Wmissing-prototypes]
162 | void __iomem *devm_cxl_iomap_block(struct device *dev, resource_size_t addr,
| ^~~~~~~~~~~~~~~~~~~~
vim +/devm_cxl_iomap_block +162 drivers/cxl/core/regs.c
0f06157e0135f5 Dan Williams 2021-08-03 161
d17d0540a0dbf1 Dan Williams 2022-02-01 @162 void __iomem *devm_cxl_iomap_block(struct device *dev, resource_size_t addr,
0f06157e0135f5 Dan Williams 2021-08-03 163 resource_size_t length)
0f06157e0135f5 Dan Williams 2021-08-03 164 {
0f06157e0135f5 Dan Williams 2021-08-03 165 void __iomem *ret_val;
0f06157e0135f5 Dan Williams 2021-08-03 166 struct resource *res;
0f06157e0135f5 Dan Williams 2021-08-03 167
0f06157e0135f5 Dan Williams 2021-08-03 168 res = devm_request_mem_region(dev, addr, length, dev_name(dev));
0f06157e0135f5 Dan Williams 2021-08-03 169 if (!res) {
0f06157e0135f5 Dan Williams 2021-08-03 170 resource_size_t end = addr + length - 1;
0f06157e0135f5 Dan Williams 2021-08-03 171
0f06157e0135f5 Dan Williams 2021-08-03 172 dev_err(dev, "Failed to request region %pa-%pa\n", &addr, &end);
0f06157e0135f5 Dan Williams 2021-08-03 173 return NULL;
0f06157e0135f5 Dan Williams 2021-08-03 174 }
0f06157e0135f5 Dan Williams 2021-08-03 175
0f06157e0135f5 Dan Williams 2021-08-03 176 ret_val = devm_ioremap(dev, addr, length);
0f06157e0135f5 Dan Williams 2021-08-03 177 if (!ret_val)
0f06157e0135f5 Dan Williams 2021-08-03 178 dev_err(dev, "Failed to map region %pr\n", res);
0f06157e0135f5 Dan Williams 2021-08-03 179
0f06157e0135f5 Dan Williams 2021-08-03 180 return ret_val;
0f06157e0135f5 Dan Williams 2021-08-03 181 }
0f06157e0135f5 Dan Williams 2021-08-03 182 Signature · 2 lines
0-DAY CI Kernel Test Service https://01.org/lkp
#
# Automatically generated file; DO NOT EDIT. # Linux/alpha 6.0.0-rc1 Kernel Configuration #CONFIG_CC_VERSION_TEXT="alpha-linux-gcc (GCC) 12.1.0" CONFIG_CC_IS_GCC=yCONFIG_GCC_VERSION=120100 CONFIG_CLANG_VERSION=0CONFIG_AS_IS_GNU=yCONFIG_AS_VERSION=23800CONFIG_LD_IS_BFD=yCONFIG_LD_VERSION=23800CONFIG_LLD_VERSION=0CONFIG_CC_HAS_ASM_GOTO=y CONFIG_CC_HAS_ASM_INLINE=y CONFIG_CC_HAS_NO_PROFILE_FN_ATTR=y CONFIG_PAHOLE_VERSION=123 CONFIG_CONSTRUCTORS=yCONFIG_IRQ_WORK=y
#
# General setup
#CONFIG_INIT_ENV_ARG_LIMIT=32CONFIG_COMPILE_TEST=y
# CONFIG_WERROR is not setCONFIG_LOCALVERSION=""CONFIG_BUILD_SALT=""CONFIG_DEFAULT_INIT=""CONFIG_DEFAULT_HOSTNAME="(none)"CONFIG_SYSVIPC=yCONFIG_SYSVIPC_SYSCTL=yCONFIG_POSIX_MQUEUE=yCONFIG_POSIX_MQUEUE_SYSCTL=yCONFIG_WATCH_QUEUE=yCONFIG_CROSS_MEMORY_ATTACH=yCONFIG_USELIB=yCONFIG_AUDIT=yCONFIG_HAVE_ARCH_AUDITSYSCALL=yCONFIG_AUDITSYSCALL=y
#
# IRQ subsystem
#CONFIG_GENERIC_IRQ_PROBE=yCONFIG_GENERIC_IRQ_SHOW=yCONFIG_AUTO_IRQ_AFFINITY=yCONFIG_GENERIC_IRQ_INJECTION=yCONFIG_GENERIC_IRQ_CHIP=yCONFIG_IRQ_DOMAIN=yCONFIG_IRQ_SIM=yCONFIG_IRQ_DOMAIN_HIERARCHY=yCONFIG_IRQ_FASTEOI_HIERARCHY_HANDLERS=yCONFIG_GENERIC_MSI_IRQ=yCONFIG_GENERIC_MSI_IRQ_DOMAIN=yCONFIG_GENERIC_IRQ_DEBUGFS=y
# end of IRQ subsystem
CONFIG_GENERIC_CLOCKEVENTS=yCONFIG_TIME_KUNIT_TEST=yCONFIG_CONTEXT_TRACKING=yCONFIG_CONTEXT_TRACKING_IDLE=y
#
# Timers subsystem
#CONFIG_TICK_ONESHOT=yCONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not setCONFIG_NO_HZ_IDLE=yCONFIG_NO_HZ=yCONFIG_HIGH_RES_TIMERS=y
# end of Timers subsystem
CONFIG_BPF=y
#
# BPF subsystem
#CONFIG_BPF_SYSCALL=yCONFIG_BPF_UNPRIV_DEFAULT_OFF=yCONFIG_USERMODE_DRIVER=y
# end of BPF subsystem
CONFIG_PREEMPT_NONE_BUILD=yCONFIG_PREEMPT_NONE=y
#
# CPU/Task time and stats accounting
#CONFIG_TICK_CPU_ACCOUNTING=yCONFIG_BSD_PROCESS_ACCT=yCONFIG_BSD_PROCESS_ACCT_V3=yCONFIG_TASKSTATS=yCONFIG_TASK_DELAY_ACCT=yCONFIG_TASK_XACCT=yCONFIG_TASK_IO_ACCOUNTING=yCONFIG_PSI=yCONFIG_PSI_DEFAULT_DISABLED=y
# end of CPU/Task time and stats accounting
CONFIG_CPU_ISOLATION=y
#
# RCU Subsystem
#CONFIG_TREE_RCU=yCONFIG_RCU_EXPERT=yCONFIG_SRCU=yCONFIG_TREE_SRCU=yCONFIG_TASKS_RCU_GENERIC=yCONFIG_FORCE_TASKS_RCU=yCONFIG_TASKS_RCU=yCONFIG_FORCE_TASKS_RUDE_RCU=yCONFIG_TASKS_RUDE_RCU=yCONFIG_FORCE_TASKS_TRACE_RCU=yCONFIG_TASKS_TRACE_RCU=yCONFIG_RCU_STALL_COMMON=yCONFIG_RCU_NEED_SEGCBLIST=yCONFIG_RCU_FANOUT=64CONFIG_RCU_FANOUT_LEAF=16CONFIG_RCU_NOCB_CPU=yCONFIG_RCU_NOCB_CPU_DEFAULT_ALL=yCONFIG_TASKS_TRACE_RCU_READ_MB=y
# end of RCU Subsystem
CONFIG_BUILD_BIN2C=yCONFIG_IKCONFIG=yCONFIG_IKCONFIG_PROC=yCONFIG_IKHEADERS=yCONFIG_LOG_BUF_SHIFT=17CONFIG_LOG_CPU_MAX_BUF_SHIFT=12CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13CONFIG_PRINTK_INDEX=y
#
# Scheduler features
#
# end of Scheduler features
CONFIG_CC_HAS_INT128=y CONFIG_CC_IMPLICIT_FALLTHROUGH="-Wimplicit-fallthrough=5" CONFIG_GCC12_NO_ARRAY_BOUNDS=y CONFIG_CC_NO_ARRAY_BOUNDS=yCONFIG_CGROUPS=yCONFIG_PAGE_COUNTER=y CONFIG_CGROUP_FAVOR_DYNMODS=yCONFIG_MEMCG=yCONFIG_MEMCG_SWAP=yCONFIG_MEMCG_KMEM=yCONFIG_BLK_CGROUP=yCONFIG_CGROUP_WRITEBACK=yCONFIG_CGROUP_SCHED=yCONFIG_FAIR_GROUP_SCHED=yCONFIG_CFS_BANDWIDTH=yCONFIG_RT_GROUP_SCHED=yCONFIG_CGROUP_PIDS=yCONFIG_CGROUP_RDMA=yCONFIG_CGROUP_FREEZER=yCONFIG_CPUSETS=yCONFIG_PROC_PID_CPUSET=yCONFIG_CGROUP_DEVICE=yCONFIG_CGROUP_CPUACCT=yCONFIG_CGROUP_PERF=yCONFIG_CGROUP_BPF=yCONFIG_CGROUP_MISC=yCONFIG_CGROUP_DEBUG=yCONFIG_SOCK_CGROUP_DATA=yCONFIG_NAMESPACES=yCONFIG_UTS_NS=yCONFIG_IPC_NS=yCONFIG_USER_NS=yCONFIG_PID_NS=yCONFIG_NET_NS=yCONFIG_CHECKPOINT_RESTORE=y CONFIG_SCHED_AUTOGROUP=y CONFIG_SYSFS_DEPRECATED=y CONFIG_SYSFS_DEPRECATED_V2=yCONFIG_RELAY=yCONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE=""CONFIG_RD_GZIP=yCONFIG_RD_BZIP2=yCONFIG_RD_LZMA=yCONFIG_RD_XZ=yCONFIG_RD_LZO=yCONFIG_RD_LZ4=yCONFIG_RD_ZSTD=yCONFIG_BOOT_CONFIG=yCONFIG_BOOT_CONFIG_EMBED=y CONFIG_BOOT_CONFIG_EMBED_FILE="" CONFIG_INITRAMFS_PRESERVE_MTIME=y CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=yCONFIG_HAVE_PCSPKR_PLATFORM=yCONFIG_EXPERT=yCONFIG_MULTIUSER=yCONFIG_SGETMASK_SYSCALL=yCONFIG_SYSFS_SYSCALL=yCONFIG_FHANDLE=yCONFIG_POSIX_TIMERS=yCONFIG_PRINTK=yCONFIG_BUG=yCONFIG_ELF_CORE=yCONFIG_PCSPKR_PLATFORM=yCONFIG_BASE_FULL=yCONFIG_FUTEX=yCONFIG_FUTEX_PI=yCONFIG_EPOLL=yCONFIG_SIGNALFD=yCONFIG_TIMERFD=yCONFIG_EVENTFD=yCONFIG_SHMEM=yCONFIG_AIO=yCONFIG_IO_URING=yCONFIG_ADVISE_SYSCALLS=yCONFIG_MEMBARRIER=yCONFIG_KALLSYMS=yCONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_BASE_RELATIVE=yCONFIG_KCMP=yCONFIG_EMBEDDED=yCONFIG_HAVE_PERF_EVENTS=y CONFIG_PERF_USE_VMALLOC=yCONFIG_PC104=y
#
# Kernel Performance Events And Counters
#CONFIG_PERF_EVENTS=yCONFIG_DEBUG_PERF_USE_VMALLOC=y
# end of Kernel Performance Events And Counters
CONFIG_SYSTEM_DATA_VERIFICATION=yCONFIG_PROFILING=y
# end of General setup
CONFIG_ALPHA=yCONFIG_64BIT=yCONFIG_MMU=yCONFIG_GENERIC_CALIBRATE_DELAY=yCONFIG_GENERIC_ISA_DMA=yCONFIG_PGTABLE_LEVELS=3CONFIG_AUDIT_ARCH=y
#
# System setup
#CONFIG_ALPHA_GENERIC=y
# CONFIG_ALPHA_ALCOR is not set
# CONFIG_ALPHA_XL is not set
# CONFIG_ALPHA_BOOK1 is not set
# CONFIG_ALPHA_AVANTI_CH is not set
# CONFIG_ALPHA_CABRIOLET is not set
# CONFIG_ALPHA_DP264 is not set
# CONFIG_ALPHA_EB164 is not set
# CONFIG_ALPHA_EB64P_CH is not set
# CONFIG_ALPHA_EB66 is not set
# CONFIG_ALPHA_EB66P is not set
# CONFIG_ALPHA_EIGER is not set
# CONFIG_ALPHA_JENSEN is not set
# CONFIG_ALPHA_LX164 is not set
# CONFIG_ALPHA_LYNX is not set
# CONFIG_ALPHA_MARVEL is not set
# CONFIG_ALPHA_MIATA is not set
# CONFIG_ALPHA_MIKASA is not set
# CONFIG_ALPHA_NAUTILUS is not set
# CONFIG_ALPHA_NONAME_CH is not set
# CONFIG_ALPHA_NORITAKE is not set
# CONFIG_ALPHA_PC164 is not set
# CONFIG_ALPHA_P2K is not set
# CONFIG_ALPHA_RAWHIDE is not set
# CONFIG_ALPHA_RUFFIAN is not set
# CONFIG_ALPHA_RX164 is not set
# CONFIG_ALPHA_SX164 is not set
# CONFIG_ALPHA_SABLE is not set
# CONFIG_ALPHA_SHARK is not set
# CONFIG_ALPHA_TAKARA is not set
# CONFIG_ALPHA_TITAN is not set
# CONFIG_ALPHA_WILDFIRE is not setCONFIG_ISA=yCONFIG_ISA_DMA_API=yCONFIG_GENERIC_HWEIGHT=yCONFIG_ALPHA_BROKEN_IRQ_MASK=yCONFIG_VGA_HOSE=yCONFIG_ARCH_MAY_HAVE_PC_FDC=yCONFIG_SMP=yCONFIG_NR_CPUS=32CONFIG_ARCH_SPARSEMEM_ENABLE=yCONFIG_ALPHA_WTINT=yCONFIG_VERBOSE_MCHECK=yCONFIG_VERBOSE_MCHECK_ON=1
# CONFIG_HZ_32 is not set
# CONFIG_HZ_64 is not set
# CONFIG_HZ_128 is not set
# CONFIG_HZ_256 is not setCONFIG_HZ_1024=y
# CONFIG_HZ_1200 is not setCONFIG_HZ=1024CONFIG_SRM_ENV=y
# end of System setup
CONFIG_DUMMY_CONSOLE=y
#
# General architecture-dependent options
#CONFIG_CRASH_CORE=yCONFIG_HAVE_64BIT_ALIGNED_ACCESS=yCONFIG_GENERIC_SMP_IDLE_THREAD=yCONFIG_ARCH_32BIT_USTAT_F_TINODE=yCONFIG_HAVE_ASM_MODVERSIONS=yCONFIG_MMU_GATHER_NO_RANGE=yCONFIG_MMU_GATHER_MERGE_VMAS=yCONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=yCONFIG_ARCH_WANT_IPC_PARSE_VERSION=yCONFIG_LTO_NONE=yCONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=yCONFIG_HAVE_MOD_ARCH_SPECIFIC=yCONFIG_MODULES_USE_ELF_RELA=yCONFIG_PAGE_SIZE_LESS_THAN_64KB=yCONFIG_PAGE_SIZE_LESS_THAN_256KB=yCONFIG_ISA_BUS_API=yCONFIG_ODD_RT_SIGACTION=yCONFIG_OLD_SIGSUSPEND=yCONFIG_COMPAT_32BIT_TIME=yCONFIG_ARCH_NO_PREEMPT=yCONFIG_CPU_NO_EFFICIENT_FFS=yCONFIG_LOCK_EVENT_COUNTS=y
#
# GCOV-based kernel profiling
#CONFIG_GCOV_KERNEL=y
# end of GCOV-based kernel profiling # end of General architecture-dependent options
CONFIG_RT_MUTEXES=yCONFIG_BASE_SMALL=0CONFIG_MODULE_SIG_FORMAT=yCONFIG_MODULES=yCONFIG_MODULE_FORCE_LOAD=yCONFIG_MODULE_UNLOAD=yCONFIG_MODULE_FORCE_UNLOAD=yCONFIG_MODULE_UNLOAD_TAINT_TRACKING=yCONFIG_MODVERSIONS=yCONFIG_ASM_MODVERSIONS=yCONFIG_MODULE_SRCVERSION_ALL=yCONFIG_MODULE_SIG=yCONFIG_MODULE_SIG_FORCE=yCONFIG_MODULE_SIG_ALL=yCONFIG_MODULE_SIG_SHA1=y
# CONFIG_MODULE_SIG_SHA224 is not set
# CONFIG_MODULE_SIG_SHA256 is not set
# CONFIG_MODULE_SIG_SHA384 is not set
# CONFIG_MODULE_SIG_SHA512 is not setCONFIG_MODULE_SIG_HASH="sha1"CONFIG_MODULE_COMPRESS_NONE=y
# CONFIG_MODULE_COMPRESS_GZIP is not set
# CONFIG_MODULE_COMPRESS_XZ is not set
# CONFIG_MODULE_COMPRESS_ZSTD is not setCONFIG_MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS=yCONFIG_MODPROBE_PATH="/sbin/modprobe"CONFIG_MODULES_TREE_LOOKUP=yCONFIG_BLOCK=yCONFIG_BLOCK_LEGACY_AUTOLOAD=yCONFIG_BLK_RQ_ALLOC_TIME=yCONFIG_BLK_CGROUP_RWSTAT=yCONFIG_BLK_DEV_BSG_COMMON=yCONFIG_BLK_ICQ=yCONFIG_BLK_DEV_BSGLIB=yCONFIG_BLK_DEV_INTEGRITY=yCONFIG_BLK_DEV_INTEGRITY_T10=yCONFIG_BLK_DEV_ZONED=yCONFIG_BLK_DEV_THROTTLING=yCONFIG_BLK_DEV_THROTTLING_LOW=yCONFIG_BLK_WBT=yCONFIG_BLK_WBT_MQ=yCONFIG_BLK_CGROUP_IOLATENCY=yCONFIG_BLK_CGROUP_FC_APPID=yCONFIG_BLK_CGROUP_IOCOST=yCONFIG_BLK_CGROUP_IOPRIO=yCONFIG_BLK_DEBUG_FS=yCONFIG_BLK_DEBUG_FS_ZONED=yCONFIG_BLK_SED_OPAL=yCONFIG_BLK_INLINE_ENCRYPTION=yCONFIG_BLK_INLINE_ENCRYPTION_FALLBACK=y
#
# Partition Types
#CONFIG_PARTITION_ADVANCED=yCONFIG_ACORN_PARTITION=yCONFIG_ACORN_PARTITION_CUMANA=yCONFIG_ACORN_PARTITION_EESOX=yCONFIG_ACORN_PARTITION_ICS=yCONFIG_ACORN_PARTITION_ADFS=yCONFIG_ACORN_PARTITION_POWERTEC=yCONFIG_ACORN_PARTITION_RISCIX=yCONFIG_AIX_PARTITION=yCONFIG_OSF_PARTITION=yCONFIG_AMIGA_PARTITION=yCONFIG_ATARI_PARTITION=yCONFIG_MAC_PARTITION=yCONFIG_MSDOS_PARTITION=yCONFIG_BSD_DISKLABEL=yCONFIG_MINIX_SUBPARTITION=yCONFIG_SOLARIS_X86_PARTITION=yCONFIG_UNIXWARE_DISKLABEL=yCONFIG_LDM_PARTITION=yCONFIG_LDM_DEBUG=yCONFIG_SGI_PARTITION=yCONFIG_ULTRIX_PARTITION=yCONFIG_SUN_PARTITION=yCONFIG_KARMA_PARTITION=yCONFIG_EFI_PARTITION=yCONFIG_SYSV68_PARTITION=yCONFIG_CMDLINE_PARTITION=y
# end of Partition Types
CONFIG_BLK_MQ_PCI=yCONFIG_BLK_MQ_VIRTIO=yCONFIG_BLOCK_HOLDER_DEPRECATED=yCONFIG_BLK_MQ_STACKING=y
#
# IO Schedulers
#CONFIG_MQ_IOSCHED_DEADLINE=yCONFIG_MQ_IOSCHED_KYBER=yCONFIG_IOSCHED_BFQ=yCONFIG_BFQ_GROUP_IOSCHED=yCONFIG_BFQ_CGROUP_DEBUG=y
# end of IO Schedulers
CONFIG_PADATA=yCONFIG_ASN1=yCONFIG_UNINLINE_SPIN_UNLOCK=yCONFIG_FREEZER=y
#
# Executable file formats
#CONFIG_BINFMT_ELF=yCONFIG_BINFMT_ELF_KUNIT_TEST=yCONFIG_ELFCORE=yCONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=yCONFIG_BINFMT_SCRIPT=yCONFIG_BINFMT_MISC=yCONFIG_COREDUMP=y
# end of Executable file formats
#
# Memory Management options
#CONFIG_ZPOOL=yCONFIG_SWAP=yCONFIG_ZSWAP=yCONFIG_ZSWAP_DEFAULT_ON=y
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_DEFLATE is not set CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZO=y
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_842 is not set # CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4 is not set # CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4HC is not set # CONFIG_ZSWAP_COMPRESSOR_DEFAULT_ZSTD is not set CONFIG_ZSWAP_COMPRESSOR_DEFAULT="lzo" CONFIG_ZSWAP_ZPOOL_DEFAULT_ZBUD=y
# CONFIG_ZSWAP_ZPOOL_DEFAULT_Z3FOLD is not set # CONFIG_ZSWAP_ZPOOL_DEFAULT_ZSMALLOC is not set CONFIG_ZSWAP_ZPOOL_DEFAULT="zbud" CONFIG_ZBUD=yCONFIG_Z3FOLD=yCONFIG_ZSMALLOC=yCONFIG_ZSMALLOC_STAT=y
#
# SLAB allocator options
#
# CONFIG_SLAB is not setCONFIG_SLUB=y
# CONFIG_SLOB is not setCONFIG_SLAB_MERGE_DEFAULT=yCONFIG_SLAB_FREELIST_RANDOM=yCONFIG_SLAB_FREELIST_HARDENED=yCONFIG_SLUB_STATS=yCONFIG_SLUB_CPU_PARTIAL=y
# end of SLAB allocator options
CONFIG_SHUFFLE_PAGE_ALLOCATOR=yCONFIG_COMPAT_BRK=yCONFIG_SPARSEMEM=yCONFIG_SPARSEMEM_EXTREME=yCONFIG_MEMORY_ISOLATION=yCONFIG_SPLIT_PTLOCK_CPUS=4CONFIG_MEMORY_BALLOON=yCONFIG_BALLOON_COMPACTION=yCONFIG_COMPACTION=yCONFIG_PAGE_REPORTING=yCONFIG_MIGRATION=yCONFIG_CONTIG_ALLOC=yCONFIG_PHYS_ADDR_T_64BIT=yCONFIG_MMU_NOTIFIER=yCONFIG_KSM=yCONFIG_DEFAULT_MMAP_MIN_ADDR=4096CONFIG_FRONTSWAP=yCONFIG_CMA=yCONFIG_CMA_DEBUG=yCONFIG_CMA_DEBUGFS=yCONFIG_CMA_SYSFS=yCONFIG_CMA_AREAS=7CONFIG_DEFERRED_STRUCT_PAGE_INIT=yCONFIG_PAGE_IDLE_FLAG=yCONFIG_IDLE_PAGE_TRACKING=yCONFIG_ZONE_DMA=yCONFIG_HMM_MIRROR=yCONFIG_GET_FREE_REGION=yCONFIG_VM_EVENT_COUNTERS=yCONFIG_PERCPU_STATS=yCONFIG_GUP_TEST=yCONFIG_ANON_VMA_NAME=yCONFIG_USERFAULTFD=y
#
# Data Access Monitoring
#CONFIG_DAMON=yCONFIG_DAMON_KUNIT_TEST=yCONFIG_DAMON_VADDR=yCONFIG_DAMON_PADDR=yCONFIG_DAMON_VADDR_KUNIT_TEST=yCONFIG_DAMON_SYSFS=yCONFIG_DAMON_DBGFS=yCONFIG_DAMON_DBGFS_KUNIT_TEST=yCONFIG_DAMON_RECLAIM=yCONFIG_DAMON_LRU_SORT=y
# end of Data Access Monitoring # end of Memory Management options
CONFIG_NET=yCONFIG_NET_INGRESS=yCONFIG_NET_EGRESS=yCONFIG_NET_REDIRECT=yCONFIG_SKB_EXTENSIONS=y
#
# Networking options
#CONFIG_PACKET=yCONFIG_PACKET_DIAG=yCONFIG_UNIX=yCONFIG_UNIX_SCM=yCONFIG_AF_UNIX_OOB=yCONFIG_UNIX_DIAG=yCONFIG_TLS=yCONFIG_TLS_DEVICE=yCONFIG_TLS_TOE=yCONFIG_XFRM=yCONFIG_XFRM_OFFLOAD=yCONFIG_XFRM_ALGO=yCONFIG_XFRM_USER=yCONFIG_XFRM_INTERFACE=yCONFIG_XFRM_SUB_POLICY=yCONFIG_XFRM_MIGRATE=yCONFIG_XFRM_STATISTICS=yCONFIG_XFRM_AH=yCONFIG_XFRM_ESP=yCONFIG_XFRM_IPCOMP=yCONFIG_NET_KEY=yCONFIG_NET_KEY_MIGRATE=yCONFIG_XFRM_ESPINTCP=yCONFIG_XDP_SOCKETS=yCONFIG_XDP_SOCKETS_DIAG=yCONFIG_INET=yCONFIG_IP_MULTICAST=yCONFIG_IP_ADVANCED_ROUTER=yCONFIG_IP_FIB_TRIE_STATS=yCONFIG_IP_MULTIPLE_TABLES=yCONFIG_IP_ROUTE_MULTIPATH=yCONFIG_IP_ROUTE_VERBOSE=yCONFIG_IP_ROUTE_CLASSID=yCONFIG_IP_PNP=yCONFIG_IP_PNP_DHCP=yCONFIG_IP_PNP_BOOTP=yCONFIG_IP_PNP_RARP=yCONFIG_NET_IPIP=yCONFIG_NET_IPGRE_DEMUX=yCONFIG_NET_IP_TUNNEL=yCONFIG_NET_IPGRE=yCONFIG_NET_IPGRE_BROADCAST=yCONFIG_IP_MROUTE_COMMON=yCONFIG_IP_MROUTE=yCONFIG_IP_MROUTE_MULTIPLE_TABLES=yCONFIG_IP_PIMSM_V1=yCONFIG_IP_PIMSM_V2=yCONFIG_SYN_COOKIES=yCONFIG_NET_IPVTI=yCONFIG_NET_UDP_TUNNEL=yCONFIG_NET_FOU=yCONFIG_NET_FOU_IP_TUNNELS=yCONFIG_INET_AH=yCONFIG_INET_ESP=yCONFIG_INET_ESP_OFFLOAD=yCONFIG_INET_ESPINTCP=yCONFIG_INET_IPCOMP=yCONFIG_INET_XFRM_TUNNEL=yCONFIG_INET_TUNNEL=yCONFIG_INET_DIAG=yCONFIG_INET_TCP_DIAG=yCONFIG_INET_UDP_DIAG=yCONFIG_INET_RAW_DIAG=yCONFIG_INET_DIAG_DESTROY=yCONFIG_TCP_CONG_ADVANCED=yCONFIG_TCP_CONG_BIC=yCONFIG_TCP_CONG_CUBIC=yCONFIG_TCP_CONG_WESTWOOD=yCONFIG_TCP_CONG_HTCP=yCONFIG_TCP_CONG_HSTCP=yCONFIG_TCP_CONG_HYBLA=yCONFIG_TCP_CONG_VEGAS=yCONFIG_TCP_CONG_NV=yCONFIG_TCP_CONG_SCALABLE=yCONFIG_TCP_CONG_LP=yCONFIG_TCP_CONG_VENO=yCONFIG_TCP_CONG_YEAH=yCONFIG_TCP_CONG_ILLINOIS=yCONFIG_TCP_CONG_DCTCP=yCONFIG_TCP_CONG_CDG=yCONFIG_TCP_CONG_BBR=y
# CONFIG_DEFAULT_BIC is not setCONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_HYBLA is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_VENO is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_DCTCP is not set
# CONFIG_DEFAULT_CDG is not set
# CONFIG_DEFAULT_BBR is not set
# CONFIG_DEFAULT_RENO is not setCONFIG_DEFAULT_TCP_CONG="cubic"CONFIG_TCP_MD5SIG=yCONFIG_IPV6=yCONFIG_IPV6_ROUTER_PREF=yCONFIG_IPV6_ROUTE_INFO=yCONFIG_IPV6_OPTIMISTIC_DAD=yCONFIG_INET6_AH=yCONFIG_INET6_ESP=yCONFIG_INET6_ESP_OFFLOAD=yCONFIG_INET6_ESPINTCP=yCONFIG_INET6_IPCOMP=yCONFIG_IPV6_MIP6=yCONFIG_IPV6_ILA=yCONFIG_INET6_XFRM_TUNNEL=yCONFIG_INET6_TUNNEL=yCONFIG_IPV6_VTI=yCONFIG_IPV6_SIT=yCONFIG_IPV6_SIT_6RD=yCONFIG_IPV6_NDISC_NODETYPE=yCONFIG_IPV6_TUNNEL=yCONFIG_IPV6_GRE=yCONFIG_IPV6_FOU=yCONFIG_IPV6_FOU_TUNNEL=yCONFIG_IPV6_MULTIPLE_TABLES=yCONFIG_IPV6_SUBTREES=yCONFIG_IPV6_MROUTE=yCONFIG_IPV6_MROUTE_MULTIPLE_TABLES=yCONFIG_IPV6_PIMSM_V2=yCONFIG_IPV6_SEG6_LWTUNNEL=yCONFIG_IPV6_SEG6_HMAC=yCONFIG_IPV6_SEG6_BPF=yCONFIG_IPV6_RPL_LWTUNNEL=yCONFIG_IPV6_IOAM6_LWTUNNEL=yCONFIG_NETLABEL=yCONFIG_MPTCP=yCONFIG_INET_MPTCP_DIAG=yCONFIG_MPTCP_IPV6=yCONFIG_MPTCP_KUNIT_TEST=yCONFIG_NETWORK_SECMARK=yCONFIG_NET_PTP_CLASSIFY=yCONFIG_NETWORK_PHY_TIMESTAMPING=yCONFIG_NETFILTER=yCONFIG_NETFILTER_ADVANCED=yCONFIG_BRIDGE_NETFILTER=y
#
# Core Netfilter Configuration
#CONFIG_NETFILTER_INGRESS=yCONFIG_NETFILTER_EGRESS=yCONFIG_NETFILTER_SKIP_EGRESS=yCONFIG_NETFILTER_NETLINK=yCONFIG_NETFILTER_FAMILY_BRIDGE=yCONFIG_NETFILTER_FAMILY_ARP=yCONFIG_NETFILTER_NETLINK_HOOK=yCONFIG_NETFILTER_NETLINK_ACCT=yCONFIG_NETFILTER_NETLINK_QUEUE=yCONFIG_NETFILTER_NETLINK_LOG=yCONFIG_NETFILTER_NETLINK_OSF=yCONFIG_NF_CONNTRACK=yCONFIG_NF_LOG_SYSLOG=yCONFIG_NETFILTER_CONNCOUNT=yCONFIG_NF_CONNTRACK_MARK=yCONFIG_NF_CONNTRACK_SECMARK=yCONFIG_NF_CONNTRACK_ZONES=yCONFIG_NF_CONNTRACK_PROCFS=yCONFIG_NF_CONNTRACK_EVENTS=yCONFIG_NF_CONNTRACK_TIMEOUT=yCONFIG_NF_CONNTRACK_TIMESTAMP=yCONFIG_NF_CONNTRACK_LABELS=yCONFIG_NF_CT_PROTO_DCCP=yCONFIG_NF_CT_PROTO_GRE=yCONFIG_NF_CT_PROTO_SCTP=yCONFIG_NF_CT_PROTO_UDPLITE=yCONFIG_NF_CONNTRACK_AMANDA=yCONFIG_NF_CONNTRACK_FTP=yCONFIG_NF_CONNTRACK_H323=yCONFIG_NF_CONNTRACK_IRC=yCONFIG_NF_CONNTRACK_BROADCAST=yCONFIG_NF_CONNTRACK_NETBIOS_NS=yCONFIG_NF_CONNTRACK_SNMP=yCONFIG_NF_CONNTRACK_PPTP=yCONFIG_NF_CONNTRACK_SANE=yCONFIG_NF_CONNTRACK_SIP=yCONFIG_NF_CONNTRACK_TFTP=yCONFIG_NF_CT_NETLINK=yCONFIG_NF_CT_NETLINK_TIMEOUT=yCONFIG_NF_CT_NETLINK_HELPER=yCONFIG_NETFILTER_NETLINK_GLUE_CT=yCONFIG_NF_NAT=yCONFIG_NF_NAT_AMANDA=yCONFIG_NF_NAT_FTP=yCONFIG_NF_NAT_IRC=yCONFIG_NF_NAT_SIP=yCONFIG_NF_NAT_TFTP=yCONFIG_NF_NAT_REDIRECT=yCONFIG_NF_NAT_MASQUERADE=yCONFIG_NETFILTER_SYNPROXY=yCONFIG_NF_TABLES=yCONFIG_NF_TABLES_INET=yCONFIG_NF_TABLES_NETDEV=yCONFIG_NFT_NUMGEN=yCONFIG_NFT_CT=yCONFIG_NFT_FLOW_OFFLOAD=yCONFIG_NFT_CONNLIMIT=yCONFIG_NFT_LOG=yCONFIG_NFT_LIMIT=yCONFIG_NFT_MASQ=yCONFIG_NFT_REDIR=yCONFIG_NFT_NAT=yCONFIG_NFT_TUNNEL=yCONFIG_NFT_OBJREF=yCONFIG_NFT_QUEUE=yCONFIG_NFT_QUOTA=yCONFIG_NFT_REJECT=yCONFIG_NFT_REJECT_INET=yCONFIG_NFT_COMPAT=yCONFIG_NFT_HASH=yCONFIG_NFT_FIB=yCONFIG_NFT_FIB_INET=yCONFIG_NFT_XFRM=yCONFIG_NFT_SOCKET=yCONFIG_NFT_OSF=yCONFIG_NFT_TPROXY=yCONFIG_NFT_SYNPROXY=yCONFIG_NF_DUP_NETDEV=yCONFIG_NFT_DUP_NETDEV=yCONFIG_NFT_FWD_NETDEV=yCONFIG_NFT_FIB_NETDEV=yCONFIG_NFT_REJECT_NETDEV=yCONFIG_NF_FLOW_TABLE_INET=yCONFIG_NF_FLOW_TABLE=yCONFIG_NF_FLOW_TABLE_PROCFS=yCONFIG_NETFILTER_XTABLES=y
#
# Xtables combined modules
#CONFIG_NETFILTER_XT_MARK=yCONFIG_NETFILTER_XT_CONNMARK=yCONFIG_NETFILTER_XT_SET=y
#
# Xtables targets
#CONFIG_NETFILTER_XT_TARGET_AUDIT=yCONFIG_NETFILTER_XT_TARGET_CHECKSUM=yCONFIG_NETFILTER_XT_TARGET_CLASSIFY=yCONFIG_NETFILTER_XT_TARGET_CONNMARK=yCONFIG_NETFILTER_XT_TARGET_CONNSECMARK=yCONFIG_NETFILTER_XT_TARGET_CT=yCONFIG_NETFILTER_XT_TARGET_DSCP=yCONFIG_NETFILTER_XT_TARGET_HL=yCONFIG_NETFILTER_XT_TARGET_HMARK=yCONFIG_NETFILTER_XT_TARGET_IDLETIMER=yCONFIG_NETFILTER_XT_TARGET_LED=yCONFIG_NETFILTER_XT_TARGET_LOG=yCONFIG_NETFILTER_XT_TARGET_MARK=yCONFIG_NETFILTER_XT_NAT=yCONFIG_NETFILTER_XT_TARGET_NETMAP=yCONFIG_NETFILTER_XT_TARGET_NFLOG=yCONFIG_NETFILTER_XT_TARGET_NFQUEUE=yCONFIG_NETFILTER_XT_TARGET_NOTRACK=yCONFIG_NETFILTER_XT_TARGET_RATEEST=yCONFIG_NETFILTER_XT_TARGET_REDIRECT=yCONFIG_NETFILTER_XT_TARGET_MASQUERADE=yCONFIG_NETFILTER_XT_TARGET_TEE=yCONFIG_NETFILTER_XT_TARGET_TPROXY=yCONFIG_NETFILTER_XT_TARGET_TRACE=yCONFIG_NETFILTER_XT_TARGET_SECMARK=yCONFIG_NETFILTER_XT_TARGET_TCPMSS=yCONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=y
#
# Xtables matches
#CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=yCONFIG_NETFILTER_XT_MATCH_BPF=yCONFIG_NETFILTER_XT_MATCH_CGROUP=yCONFIG_NETFILTER_XT_MATCH_CLUSTER=yCONFIG_NETFILTER_XT_MATCH_COMMENT=yCONFIG_NETFILTER_XT_MATCH_CONNBYTES=yCONFIG_NETFILTER_XT_MATCH_CONNLABEL=yCONFIG_NETFILTER_XT_MATCH_CONNLIMIT=yCONFIG_NETFILTER_XT_MATCH_CONNMARK=yCONFIG_NETFILTER_XT_MATCH_CONNTRACK=yCONFIG_NETFILTER_XT_MATCH_CPU=yCONFIG_NETFILTER_XT_MATCH_DCCP=yCONFIG_NETFILTER_XT_MATCH_DEVGROUP=yCONFIG_NETFILTER_XT_MATCH_DSCP=yCONFIG_NETFILTER_XT_MATCH_ECN=yCONFIG_NETFILTER_XT_MATCH_ESP=yCONFIG_NETFILTER_XT_MATCH_HASHLIMIT=yCONFIG_NETFILTER_XT_MATCH_HELPER=yCONFIG_NETFILTER_XT_MATCH_HL=yCONFIG_NETFILTER_XT_MATCH_IPCOMP=yCONFIG_NETFILTER_XT_MATCH_IPRANGE=yCONFIG_NETFILTER_XT_MATCH_IPVS=yCONFIG_NETFILTER_XT_MATCH_L2TP=yCONFIG_NETFILTER_XT_MATCH_LENGTH=yCONFIG_NETFILTER_XT_MATCH_LIMIT=yCONFIG_NETFILTER_XT_MATCH_MAC=yCONFIG_NETFILTER_XT_MATCH_MARK=yCONFIG_NETFILTER_XT_MATCH_MULTIPORT=yCONFIG_NETFILTER_XT_MATCH_NFACCT=yCONFIG_NETFILTER_XT_MATCH_OSF=yCONFIG_NETFILTER_XT_MATCH_OWNER=yCONFIG_NETFILTER_XT_MATCH_POLICY=yCONFIG_NETFILTER_XT_MATCH_PHYSDEV=yCONFIG_NETFILTER_XT_MATCH_PKTTYPE=yCONFIG_NETFILTER_XT_MATCH_QUOTA=yCONFIG_NETFILTER_XT_MATCH_RATEEST=yCONFIG_NETFILTER_XT_MATCH_REALM=yCONFIG_NETFILTER_XT_MATCH_RECENT=yCONFIG_NETFILTER_XT_MATCH_SCTP=yCONFIG_NETFILTER_XT_MATCH_SOCKET=yCONFIG_NETFILTER_XT_MATCH_STATE=yCONFIG_NETFILTER_XT_MATCH_STATISTIC=yCONFIG_NETFILTER_XT_MATCH_STRING=yCONFIG_NETFILTER_XT_MATCH_TCPMSS=yCONFIG_NETFILTER_XT_MATCH_TIME=yCONFIG_NETFILTER_XT_MATCH_U32=y
# end of Core Netfilter Configuration
CONFIG_IP_SET=yCONFIG_IP_SET_MAX=256CONFIG_IP_SET_BITMAP_IP=yCONFIG_IP_SET_BITMAP_IPMAC=yCONFIG_IP_SET_BITMAP_PORT=yCONFIG_IP_SET_HASH_IP=yCONFIG_IP_SET_HASH_IPMARK=yCONFIG_IP_SET_HASH_IPPORT=yCONFIG_IP_SET_HASH_IPPORTIP=yCONFIG_IP_SET_HASH_IPPORTNET=yCONFIG_IP_SET_HASH_IPMAC=yCONFIG_IP_SET_HASH_MAC=yCONFIG_IP_SET_HASH_NETPORTNET=yCONFIG_IP_SET_HASH_NET=yCONFIG_IP_SET_HASH_NETNET=yCONFIG_IP_SET_HASH_NETPORT=yCONFIG_IP_SET_HASH_NETIFACE=yCONFIG_IP_SET_LIST_SET=yCONFIG_IP_VS=yCONFIG_IP_VS_IPV6=yCONFIG_IP_VS_DEBUG=yCONFIG_IP_VS_TAB_BITS=12
#
# IPVS transport protocol load balancing support
#CONFIG_IP_VS_PROTO_TCP=yCONFIG_IP_VS_PROTO_UDP=yCONFIG_IP_VS_PROTO_AH_ESP=yCONFIG_IP_VS_PROTO_ESP=yCONFIG_IP_VS_PROTO_AH=yCONFIG_IP_VS_PROTO_SCTP=y
#
# IPVS scheduler
#CONFIG_IP_VS_RR=yCONFIG_IP_VS_WRR=yCONFIG_IP_VS_LC=yCONFIG_IP_VS_WLC=yCONFIG_IP_VS_FO=yCONFIG_IP_VS_OVF=yCONFIG_IP_VS_LBLC=yCONFIG_IP_VS_LBLCR=yCONFIG_IP_VS_DH=yCONFIG_IP_VS_SH=yCONFIG_IP_VS_MH=yCONFIG_IP_VS_SED=yCONFIG_IP_VS_NQ=yCONFIG_IP_VS_TWOS=y
#
# IPVS SH scheduler
#CONFIG_IP_VS_SH_TAB_BITS=8
#
# IPVS MH scheduler
#CONFIG_IP_VS_MH_TAB_INDEX=12
#
# IPVS application helper
#CONFIG_IP_VS_FTP=yCONFIG_IP_VS_NFCT=yCONFIG_IP_VS_PE_SIP=y
#
# IP: Netfilter Configuration
#CONFIG_NF_DEFRAG_IPV4=yCONFIG_NF_SOCKET_IPV4=yCONFIG_NF_TPROXY_IPV4=yCONFIG_NF_TABLES_IPV4=yCONFIG_NFT_REJECT_IPV4=yCONFIG_NFT_DUP_IPV4=yCONFIG_NFT_FIB_IPV4=yCONFIG_NF_TABLES_ARP=yCONFIG_NF_DUP_IPV4=yCONFIG_NF_LOG_ARP=yCONFIG_NF_LOG_IPV4=yCONFIG_NF_REJECT_IPV4=yCONFIG_NF_NAT_SNMP_BASIC=yCONFIG_NF_NAT_PPTP=yCONFIG_NF_NAT_H323=yCONFIG_IP_NF_IPTABLES=yCONFIG_IP_NF_MATCH_AH=yCONFIG_IP_NF_MATCH_ECN=yCONFIG_IP_NF_MATCH_RPFILTER=yCONFIG_IP_NF_MATCH_TTL=yCONFIG_IP_NF_FILTER=yCONFIG_IP_NF_TARGET_REJECT=yCONFIG_IP_NF_TARGET_SYNPROXY=yCONFIG_IP_NF_NAT=yCONFIG_IP_NF_TARGET_MASQUERADE=yCONFIG_IP_NF_TARGET_NETMAP=yCONFIG_IP_NF_TARGET_REDIRECT=yCONFIG_IP_NF_MANGLE=yCONFIG_IP_NF_TARGET_CLUSTERIP=yCONFIG_IP_NF_TARGET_ECN=yCONFIG_IP_NF_TARGET_TTL=yCONFIG_IP_NF_RAW=yCONFIG_IP_NF_SECURITY=yCONFIG_IP_NF_ARPTABLES=yCONFIG_IP_NF_ARPFILTER=yCONFIG_IP_NF_ARP_MANGLE=y
# end of IP: Netfilter Configuration
#
# IPv6: Netfilter Configuration
#CONFIG_NF_SOCKET_IPV6=yCONFIG_NF_TPROXY_IPV6=yCONFIG_NF_TABLES_IPV6=yCONFIG_NFT_REJECT_IPV6=yCONFIG_NFT_DUP_IPV6=yCONFIG_NFT_FIB_IPV6=yCONFIG_NF_DUP_IPV6=yCONFIG_NF_REJECT_IPV6=yCONFIG_NF_LOG_IPV6=yCONFIG_IP6_NF_IPTABLES=yCONFIG_IP6_NF_MATCH_AH=yCONFIG_IP6_NF_MATCH_EUI64=yCONFIG_IP6_NF_MATCH_FRAG=yCONFIG_IP6_NF_MATCH_OPTS=yCONFIG_IP6_NF_MATCH_HL=yCONFIG_IP6_NF_MATCH_IPV6HEADER=yCONFIG_IP6_NF_MATCH_MH=yCONFIG_IP6_NF_MATCH_RPFILTER=yCONFIG_IP6_NF_MATCH_RT=yCONFIG_IP6_NF_MATCH_SRH=yCONFIG_IP6_NF_TARGET_HL=yCONFIG_IP6_NF_FILTER=yCONFIG_IP6_NF_TARGET_REJECT=yCONFIG_IP6_NF_TARGET_SYNPROXY=yCONFIG_IP6_NF_MANGLE=yCONFIG_IP6_NF_RAW=yCONFIG_IP6_NF_SECURITY=yCONFIG_IP6_NF_NAT=yCONFIG_IP6_NF_TARGET_MASQUERADE=yCONFIG_IP6_NF_TARGET_NPT=y
# end of IPv6: Netfilter Configuration
CONFIG_NF_DEFRAG_IPV6=y
#
# DECnet: Netfilter Configuration
#CONFIG_DECNET_NF_GRABULATOR=y
# end of DECnet: Netfilter Configuration
CONFIG_NF_TABLES_BRIDGE=yCONFIG_NFT_BRIDGE_META=yCONFIG_NFT_BRIDGE_REJECT=yCONFIG_NF_CONNTRACK_BRIDGE=yCONFIG_BRIDGE_NF_EBTABLES=yCONFIG_BRIDGE_EBT_BROUTE=yCONFIG_BRIDGE_EBT_T_FILTER=yCONFIG_BRIDGE_EBT_T_NAT=yCONFIG_BRIDGE_EBT_802_3=yCONFIG_BRIDGE_EBT_AMONG=yCONFIG_BRIDGE_EBT_ARP=yCONFIG_BRIDGE_EBT_IP=yCONFIG_BRIDGE_EBT_IP6=yCONFIG_BRIDGE_EBT_LIMIT=yCONFIG_BRIDGE_EBT_MARK=yCONFIG_BRIDGE_EBT_PKTTYPE=yCONFIG_BRIDGE_EBT_STP=yCONFIG_BRIDGE_EBT_VLAN=yCONFIG_BRIDGE_EBT_ARPREPLY=yCONFIG_BRIDGE_EBT_DNAT=yCONFIG_BRIDGE_EBT_MARK_T=yCONFIG_BRIDGE_EBT_REDIRECT=yCONFIG_BRIDGE_EBT_SNAT=yCONFIG_BRIDGE_EBT_LOG=yCONFIG_BRIDGE_EBT_NFLOG=yCONFIG_BPFILTER=yCONFIG_IP_DCCP=yCONFIG_INET_DCCP_DIAG=y
#
# DCCP CCIDs Configuration
#CONFIG_IP_DCCP_CCID2_DEBUG=yCONFIG_IP_DCCP_CCID3=yCONFIG_IP_DCCP_CCID3_DEBUG=yCONFIG_IP_DCCP_TFRC_LIB=yCONFIG_IP_DCCP_TFRC_DEBUG=y
# end of DCCP CCIDs Configuration
#
# DCCP Kernel Hacking
#CONFIG_IP_DCCP_DEBUG=y
# end of DCCP Kernel Hacking
CONFIG_IP_SCTP=yCONFIG_SCTP_DBG_OBJCNT=yCONFIG_SCTP_DEFAULT_COOKIE_HMAC_MD5=y
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_SHA1 is not set
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_NONE is not setCONFIG_SCTP_COOKIE_HMAC_MD5=yCONFIG_SCTP_COOKIE_HMAC_SHA1=yCONFIG_INET_SCTP_DIAG=yCONFIG_RDS=yCONFIG_RDS_TCP=yCONFIG_RDS_DEBUG=yCONFIG_TIPC=yCONFIG_TIPC_MEDIA_UDP=yCONFIG_TIPC_CRYPTO=yCONFIG_TIPC_DIAG=yCONFIG_ATM=yCONFIG_ATM_CLIP=yCONFIG_ATM_CLIP_NO_ICMP=yCONFIG_ATM_LANE=yCONFIG_ATM_MPOA=yCONFIG_ATM_BR2684=yCONFIG_ATM_BR2684_IPFILTER=yCONFIG_L2TP=yCONFIG_L2TP_DEBUGFS=yCONFIG_L2TP_V3=yCONFIG_L2TP_IP=yCONFIG_L2TP_ETH=yCONFIG_STP=yCONFIG_GARP=yCONFIG_MRP=yCONFIG_BRIDGE=yCONFIG_BRIDGE_IGMP_SNOOPING=yCONFIG_BRIDGE_VLAN_FILTERING=yCONFIG_BRIDGE_MRP=yCONFIG_BRIDGE_CFM=yCONFIG_NET_DSA=yCONFIG_NET_DSA_TAG_AR9331=yCONFIG_NET_DSA_TAG_BRCM_COMMON=yCONFIG_NET_DSA_TAG_BRCM=yCONFIG_NET_DSA_TAG_BRCM_LEGACY=yCONFIG_NET_DSA_TAG_BRCM_PREPEND=yCONFIG_NET_DSA_TAG_HELLCREEK=yCONFIG_NET_DSA_TAG_GSWIP=yCONFIG_NET_DSA_TAG_DSA_COMMON=yCONFIG_NET_DSA_TAG_DSA=yCONFIG_NET_DSA_TAG_EDSA=yCONFIG_NET_DSA_TAG_MTK=yCONFIG_NET_DSA_TAG_KSZ=yCONFIG_NET_DSA_TAG_OCELOT=yCONFIG_NET_DSA_TAG_OCELOT_8021Q=yCONFIG_NET_DSA_TAG_QCA=yCONFIG_NET_DSA_TAG_RTL4_A=yCONFIG_NET_DSA_TAG_RTL8_4=yCONFIG_NET_DSA_TAG_RZN1_A5PSW=yCONFIG_NET_DSA_TAG_LAN9303=yCONFIG_NET_DSA_TAG_SJA1105=yCONFIG_NET_DSA_TAG_TRAILER=yCONFIG_NET_DSA_TAG_XRS700X=yCONFIG_VLAN_8021Q=yCONFIG_VLAN_8021Q_GVRP=yCONFIG_VLAN_8021Q_MVRP=yCONFIG_DECNET=yCONFIG_DECNET_ROUTER=yCONFIG_LLC=yCONFIG_LLC2=yCONFIG_ATALK=yCONFIG_DEV_APPLETALK=yCONFIG_COPS=yCONFIG_COPS_DAYNA=yCONFIG_COPS_TANGENT=yCONFIG_IPDDP=yCONFIG_IPDDP_ENCAP=yCONFIG_X25=yCONFIG_LAPB=yCONFIG_PHONET=yCONFIG_6LOWPAN=yCONFIG_6LOWPAN_DEBUGFS=yCONFIG_6LOWPAN_NHC=yCONFIG_6LOWPAN_NHC_DEST=yCONFIG_6LOWPAN_NHC_FRAGMENT=yCONFIG_6LOWPAN_NHC_HOP=yCONFIG_6LOWPAN_NHC_IPV6=yCONFIG_6LOWPAN_NHC_MOBILITY=yCONFIG_6LOWPAN_NHC_ROUTING=yCONFIG_6LOWPAN_NHC_UDP=yCONFIG_6LOWPAN_GHC_EXT_HDR_HOP=yCONFIG_6LOWPAN_GHC_UDP=yCONFIG_6LOWPAN_GHC_ICMPV6=yCONFIG_6LOWPAN_GHC_EXT_HDR_DEST=yCONFIG_6LOWPAN_GHC_EXT_HDR_FRAG=yCONFIG_6LOWPAN_GHC_EXT_HDR_ROUTE=yCONFIG_IEEE802154=yCONFIG_IEEE802154_NL802154_EXPERIMENTAL=yCONFIG_IEEE802154_SOCKET=yCONFIG_IEEE802154_6LOWPAN=yCONFIG_MAC802154=yCONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#CONFIG_NET_SCH_CBQ=yCONFIG_NET_SCH_HTB=yCONFIG_NET_SCH_HFSC=yCONFIG_NET_SCH_ATM=yCONFIG_NET_SCH_PRIO=yCONFIG_NET_SCH_MULTIQ=yCONFIG_NET_SCH_RED=yCONFIG_NET_SCH_SFB=yCONFIG_NET_SCH_SFQ=yCONFIG_NET_SCH_TEQL=yCONFIG_NET_SCH_TBF=yCONFIG_NET_SCH_CBS=yCONFIG_NET_SCH_ETF=yCONFIG_NET_SCH_TAPRIO=yCONFIG_NET_SCH_GRED=yCONFIG_NET_SCH_DSMARK=yCONFIG_NET_SCH_NETEM=yCONFIG_NET_SCH_DRR=yCONFIG_NET_SCH_MQPRIO=yCONFIG_NET_SCH_SKBPRIO=yCONFIG_NET_SCH_CHOKE=yCONFIG_NET_SCH_QFQ=yCONFIG_NET_SCH_CODEL=yCONFIG_NET_SCH_FQ_CODEL=yCONFIG_NET_SCH_CAKE=yCONFIG_NET_SCH_FQ=yCONFIG_NET_SCH_HHF=yCONFIG_NET_SCH_PIE=yCONFIG_NET_SCH_FQ_PIE=yCONFIG_NET_SCH_INGRESS=yCONFIG_NET_SCH_PLUG=yCONFIG_NET_SCH_ETS=yCONFIG_NET_SCH_DEFAULT=y
# CONFIG_DEFAULT_FQ is not set
# CONFIG_DEFAULT_CODEL is not set
# CONFIG_DEFAULT_FQ_CODEL is not set
# CONFIG_DEFAULT_FQ_PIE is not set
# CONFIG_DEFAULT_SFQ is not setCONFIG_DEFAULT_PFIFO_FAST=yCONFIG_DEFAULT_NET_SCH="pfifo_fast"
#
# Classification
#CONFIG_NET_CLS=yCONFIG_NET_CLS_BASIC=yCONFIG_NET_CLS_TCINDEX=yCONFIG_NET_CLS_ROUTE4=yCONFIG_NET_CLS_FW=yCONFIG_NET_CLS_U32=yCONFIG_CLS_U32_PERF=yCONFIG_CLS_U32_MARK=yCONFIG_NET_CLS_RSVP=yCONFIG_NET_CLS_RSVP6=yCONFIG_NET_CLS_FLOW=yCONFIG_NET_CLS_CGROUP=yCONFIG_NET_CLS_BPF=yCONFIG_NET_CLS_FLOWER=yCONFIG_NET_CLS_MATCHALL=yCONFIG_NET_EMATCH=yCONFIG_NET_EMATCH_STACK=32CONFIG_NET_EMATCH_CMP=yCONFIG_NET_EMATCH_NBYTE=yCONFIG_NET_EMATCH_U32=yCONFIG_NET_EMATCH_META=yCONFIG_NET_EMATCH_TEXT=yCONFIG_NET_EMATCH_CANID=yCONFIG_NET_EMATCH_IPSET=yCONFIG_NET_EMATCH_IPT=yCONFIG_NET_CLS_ACT=yCONFIG_NET_ACT_POLICE=yCONFIG_NET_ACT_GACT=yCONFIG_GACT_PROB=yCONFIG_NET_ACT_MIRRED=yCONFIG_NET_ACT_SAMPLE=yCONFIG_NET_ACT_IPT=yCONFIG_NET_ACT_NAT=yCONFIG_NET_ACT_PEDIT=yCONFIG_NET_ACT_SIMP=yCONFIG_NET_ACT_SKBEDIT=yCONFIG_NET_ACT_CSUM=yCONFIG_NET_ACT_MPLS=yCONFIG_NET_ACT_VLAN=yCONFIG_NET_ACT_BPF=yCONFIG_NET_ACT_CONNMARK=yCONFIG_NET_ACT_CTINFO=yCONFIG_NET_ACT_SKBMOD=yCONFIG_NET_ACT_IFE=yCONFIG_NET_ACT_TUNNEL_KEY=yCONFIG_NET_ACT_CT=yCONFIG_NET_ACT_GATE=yCONFIG_NET_IFE_SKBMARK=yCONFIG_NET_IFE_SKBPRIO=yCONFIG_NET_IFE_SKBTCINDEX=yCONFIG_NET_TC_SKB_EXT=yCONFIG_NET_SCH_FIFO=yCONFIG_DCB=yCONFIG_DNS_RESOLVER=yCONFIG_BATMAN_ADV=yCONFIG_BATMAN_ADV_BATMAN_V=yCONFIG_BATMAN_ADV_BLA=yCONFIG_BATMAN_ADV_DAT=yCONFIG_BATMAN_ADV_NC=yCONFIG_BATMAN_ADV_MCAST=yCONFIG_BATMAN_ADV_DEBUG=yCONFIG_OPENVSWITCH=yCONFIG_OPENVSWITCH_GRE=yCONFIG_OPENVSWITCH_VXLAN=yCONFIG_OPENVSWITCH_GENEVE=yCONFIG_VSOCKETS=yCONFIG_VSOCKETS_DIAG=yCONFIG_VSOCKETS_LOOPBACK=yCONFIG_VIRTIO_VSOCKETS=yCONFIG_VIRTIO_VSOCKETS_COMMON=yCONFIG_NETLINK_DIAG=yCONFIG_MPLS=yCONFIG_NET_MPLS_GSO=yCONFIG_MPLS_ROUTING=yCONFIG_MPLS_IPTUNNEL=yCONFIG_NET_NSH=yCONFIG_HSR=yCONFIG_NET_SWITCHDEV=yCONFIG_NET_L3_MASTER_DEV=yCONFIG_QRTR=yCONFIG_QRTR_SMD=yCONFIG_QRTR_TUN=yCONFIG_QRTR_MHI=yCONFIG_NET_NCSI=yCONFIG_NCSI_OEM_CMD_GET_MAC=yCONFIG_NCSI_OEM_CMD_KEEP_PHY=yCONFIG_PCPU_DEV_REFCNT=yCONFIG_RPS=yCONFIG_RFS_ACCEL=yCONFIG_SOCK_RX_QUEUE_MAPPING=yCONFIG_XPS=yCONFIG_CGROUP_NET_PRIO=yCONFIG_CGROUP_NET_CLASSID=yCONFIG_NET_RX_BUSY_POLL=yCONFIG_BQL=yCONFIG_BPF_STREAM_PARSER=yCONFIG_NET_FLOW_LIMIT=y
#
# Network testing
#CONFIG_NET_PKTGEN=y
# end of Network testing # end of Networking options
CONFIG_HAMRADIO=y
#
# Packet Radio protocols
#CONFIG_AX25=yCONFIG_AX25_DAMA_SLAVE=yCONFIG_NETROM=yCONFIG_ROSE=y
#
# AX.25 network device drivers
#CONFIG_MKISS=yCONFIG_6PACK=yCONFIG_BPQETHER=yCONFIG_SCC=yCONFIG_SCC_DELAY=yCONFIG_SCC_TRXECHO=yCONFIG_BAYCOM_SER_FDX=yCONFIG_BAYCOM_SER_HDX=yCONFIG_BAYCOM_PAR=yCONFIG_YAM=y
# end of AX.25 network device drivers
CONFIG_CAN=yCONFIG_CAN_RAW=yCONFIG_CAN_BCM=yCONFIG_CAN_GW=yCONFIG_CAN_J1939=yCONFIG_CAN_ISOTP=yCONFIG_BT=yCONFIG_BT_BREDR=yCONFIG_BT_RFCOMM=yCONFIG_BT_RFCOMM_TTY=yCONFIG_BT_BNEP=yCONFIG_BT_BNEP_MC_FILTER=yCONFIG_BT_BNEP_PROTO_FILTER=yCONFIG_BT_CMTP=yCONFIG_BT_HIDP=yCONFIG_BT_HS=yCONFIG_BT_LE=yCONFIG_BT_6LOWPAN=yCONFIG_BT_LEDS=yCONFIG_BT_MSFTEXT=yCONFIG_BT_AOSPEXT=yCONFIG_BT_DEBUGFS=yCONFIG_BT_SELFTEST=yCONFIG_BT_SELFTEST_ECDH=yCONFIG_BT_SELFTEST_SMP=y
#
# Bluetooth device drivers
#CONFIG_BT_INTEL=yCONFIG_BT_BCM=yCONFIG_BT_RTL=yCONFIG_BT_QCA=yCONFIG_BT_MTK=yCONFIG_BT_HCIBTUSB=yCONFIG_BT_HCIBTUSB_AUTOSUSPEND=yCONFIG_BT_HCIBTUSB_BCM=yCONFIG_BT_HCIBTUSB_MTK=yCONFIG_BT_HCIBTUSB_RTL=yCONFIG_BT_HCIBTSDIO=yCONFIG_BT_HCIUART=yCONFIG_BT_HCIUART_SERDEV=yCONFIG_BT_HCIUART_H4=yCONFIG_BT_HCIUART_BCSP=yCONFIG_BT_HCIUART_ATH3K=yCONFIG_BT_HCIUART_LL=yCONFIG_BT_HCIUART_3WIRE=yCONFIG_BT_HCIUART_INTEL=yCONFIG_BT_HCIUART_BCM=yCONFIG_BT_HCIUART_RTL=yCONFIG_BT_HCIUART_QCA=yCONFIG_BT_HCIUART_AG6XX=yCONFIG_BT_HCIUART_MRVL=yCONFIG_BT_HCIBCM203X=yCONFIG_BT_HCIBPA10X=yCONFIG_BT_HCIBFUSB=yCONFIG_BT_HCIDTL1=yCONFIG_BT_HCIBT3C=yCONFIG_BT_HCIBLUECARD=yCONFIG_BT_HCIVHCI=yCONFIG_BT_MRVL=yCONFIG_BT_MRVL_SDIO=yCONFIG_BT_ATH3K=yCONFIG_BT_MTKSDIO=yCONFIG_BT_MTKUART=yCONFIG_BT_QCOMSMD=yCONFIG_BT_HCIRSI=yCONFIG_BT_VIRTIO=y
# end of Bluetooth device drivers
CONFIG_AF_RXRPC=yCONFIG_AF_RXRPC_IPV6=yCONFIG_AF_RXRPC_INJECT_LOSS=yCONFIG_AF_RXRPC_DEBUG=yCONFIG_RXKAD=yCONFIG_AF_KCM=yCONFIG_STREAM_PARSER=yCONFIG_MCTP=yCONFIG_MCTP_TEST=yCONFIG_MCTP_FLOWS=yCONFIG_FIB_RULES=yCONFIG_WIRELESS=yCONFIG_WIRELESS_EXT=yCONFIG_WEXT_CORE=yCONFIG_WEXT_PROC=yCONFIG_WEXT_SPY=yCONFIG_WEXT_PRIV=yCONFIG_CFG80211=yCONFIG_NL80211_TESTMODE=yCONFIG_CFG80211_DEVELOPER_WARNINGS=yCONFIG_CFG80211_CERTIFICATION_ONUS=yCONFIG_CFG80211_REQUIRE_SIGNED_REGDB=yCONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=yCONFIG_CFG80211_EXTRA_REGDB_KEYDIR=""CONFIG_CFG80211_REG_CELLULAR_HINTS=yCONFIG_CFG80211_REG_RELAX_NO_IR=yCONFIG_CFG80211_DEFAULT_PS=yCONFIG_CFG80211_DEBUGFS=yCONFIG_CFG80211_CRDA_SUPPORT=yCONFIG_CFG80211_WEXT=yCONFIG_CFG80211_WEXT_EXPORT=yCONFIG_LIB80211=yCONFIG_LIB80211_CRYPT_WEP=yCONFIG_LIB80211_CRYPT_CCMP=yCONFIG_LIB80211_CRYPT_TKIP=yCONFIG_LIB80211_DEBUG=yCONFIG_MAC80211=yCONFIG_MAC80211_HAS_RC=yCONFIG_MAC80211_RC_MINSTREL=yCONFIG_MAC80211_RC_DEFAULT_MINSTREL=yCONFIG_MAC80211_RC_DEFAULT="minstrel_ht"CONFIG_MAC80211_MESH=yCONFIG_MAC80211_LEDS=yCONFIG_MAC80211_DEBUGFS=yCONFIG_MAC80211_MESSAGE_TRACING=yCONFIG_MAC80211_DEBUG_MENU=yCONFIG_MAC80211_NOINLINE=yCONFIG_MAC80211_VERBOSE_DEBUG=yCONFIG_MAC80211_MLME_DEBUG=yCONFIG_MAC80211_STA_DEBUG=yCONFIG_MAC80211_HT_DEBUG=yCONFIG_MAC80211_OCB_DEBUG=yCONFIG_MAC80211_IBSS_DEBUG=yCONFIG_MAC80211_PS_DEBUG=yCONFIG_MAC80211_MPL_DEBUG=yCONFIG_MAC80211_MPATH_DEBUG=yCONFIG_MAC80211_MHWMP_DEBUG=yCONFIG_MAC80211_MESH_SYNC_DEBUG=yCONFIG_MAC80211_MESH_CSA_DEBUG=yCONFIG_MAC80211_MESH_PS_DEBUG=yCONFIG_MAC80211_TDLS_DEBUG=yCONFIG_MAC80211_DEBUG_COUNTERS=yCONFIG_MAC80211_STA_HASH_MAX_SIZE=0CONFIG_RFKILL=yCONFIG_RFKILL_LEDS=yCONFIG_RFKILL_INPUT=yCONFIG_RFKILL_GPIO=yCONFIG_NET_9P=yCONFIG_NET_9P_FD=yCONFIG_NET_9P_VIRTIO=yCONFIG_NET_9P_DEBUG=yCONFIG_CAIF=yCONFIG_CAIF_DEBUG=yCONFIG_CAIF_NETDEV=yCONFIG_CAIF_USB=yCONFIG_CEPH_LIB=yCONFIG_CEPH_LIB_PRETTYDEBUG=yCONFIG_CEPH_LIB_USE_DNS_RESOLVER=yCONFIG_NFC=yCONFIG_NFC_DIGITAL=yCONFIG_NFC_NCI=yCONFIG_NFC_NCI_SPI=yCONFIG_NFC_NCI_UART=yCONFIG_NFC_HCI=yCONFIG_NFC_SHDLC=y
#
# Near Field Communication (NFC) devices
#CONFIG_NFC_TRF7970A=yCONFIG_NFC_SIM=yCONFIG_NFC_PORT100=yCONFIG_NFC_VIRTUAL_NCI=yCONFIG_NFC_FDP=yCONFIG_NFC_FDP_I2C=yCONFIG_NFC_PN544=yCONFIG_NFC_PN544_I2C=yCONFIG_NFC_PN533=yCONFIG_NFC_PN533_USB=yCONFIG_NFC_PN533_I2C=yCONFIG_NFC_PN532_UART=yCONFIG_NFC_MICROREAD=yCONFIG_NFC_MICROREAD_I2C=yCONFIG_NFC_MRVL=yCONFIG_NFC_MRVL_USB=yCONFIG_NFC_MRVL_UART=yCONFIG_NFC_MRVL_I2C=yCONFIG_NFC_MRVL_SPI=yCONFIG_NFC_ST21NFCA=yCONFIG_NFC_ST21NFCA_I2C=yCONFIG_NFC_ST_NCI=yCONFIG_NFC_ST_NCI_I2C=yCONFIG_NFC_ST_NCI_SPI=yCONFIG_NFC_NXP_NCI=yCONFIG_NFC_NXP_NCI_I2C=yCONFIG_NFC_S3FWRN5=yCONFIG_NFC_S3FWRN5_I2C=yCONFIG_NFC_S3FWRN82_UART=yCONFIG_NFC_ST95HF=y
# end of Near Field Communication (NFC) devices
CONFIG_PSAMPLE=yCONFIG_NET_IFE=yCONFIG_LWTUNNEL=yCONFIG_LWTUNNEL_BPF=yCONFIG_DST_CACHE=yCONFIG_GRO_CELLS=yCONFIG_SOCK_VALIDATE_XMIT=yCONFIG_NET_SELFTESTS=yCONFIG_NET_SOCK_MSG=yCONFIG_NET_DEVLINK=yCONFIG_PAGE_POOL=yCONFIG_PAGE_POOL_STATS=yCONFIG_FAILOVER=yCONFIG_ETHTOOL_NETLINK=yCONFIG_NETDEV_ADDR_LIST_TEST=y
#
# Device Drivers
#CONFIG_HAVE_EISA=yCONFIG_EISA=yCONFIG_EISA_PCI_EISA=yCONFIG_EISA_VIRTUAL_ROOT=yCONFIG_EISA_NAMES=yCONFIG_HAVE_PCI=yCONFIG_FORCE_PCI=yCONFIG_PCI=yCONFIG_PCI_DOMAINS=yCONFIG_PCI_SYSCALL=yCONFIG_PCIEPORTBUS=yCONFIG_HOTPLUG_PCI_PCIE=yCONFIG_PCIEAER=yCONFIG_PCIEAER_INJECT=yCONFIG_PCIE_ECRC=yCONFIG_PCIEASPM=yCONFIG_PCIEASPM_DEFAULT=y
# CONFIG_PCIEASPM_POWERSAVE is not set
# CONFIG_PCIEASPM_POWER_SUPERSAVE is not set
# CONFIG_PCIEASPM_PERFORMANCE is not setCONFIG_PCIE_DPC=yCONFIG_PCIE_PTM=yCONFIG_PCI_MSI=yCONFIG_PCI_MSI_IRQ_DOMAIN=yCONFIG_PCI_QUIRKS=yCONFIG_PCI_DEBUG=yCONFIG_PCI_REALLOC_ENABLE_AUTO=yCONFIG_PCI_STUB=yCONFIG_PCI_PF_STUB=yCONFIG_PCI_ATS=yCONFIG_PCI_DOE=yCONFIG_PCI_ECAM=yCONFIG_PCI_BRIDGE_EMUL=yCONFIG_PCI_IOV=yCONFIG_PCI_PRI=yCONFIG_PCI_PASID=y
# CONFIG_PCIE_BUS_TUNE_OFF is not setCONFIG_PCIE_BUS_DEFAULT=y
# CONFIG_PCIE_BUS_SAFE is not set
# CONFIG_PCIE_BUS_PERFORMANCE is not set
# CONFIG_PCIE_BUS_PEER2PEER is not setCONFIG_VGA_ARB=yCONFIG_VGA_ARB_MAX_GPUS=16CONFIG_HOTPLUG_PCI=yCONFIG_HOTPLUG_PCI_CPCI=yCONFIG_HOTPLUG_PCI_SHPC=y
#
# PCI controller drivers
#CONFIG_PCI_AARDVARK=yCONFIG_PCIE_XILINX_NWL=yCONFIG_PCI_FTPCI100=yCONFIG_PCI_TEGRA=yCONFIG_PCIE_RCAR_HOST=yCONFIG_PCIE_RCAR_EP=yCONFIG_PCI_HOST_COMMON=yCONFIG_PCI_HOST_GENERIC=yCONFIG_PCIE_XILINX=yCONFIG_PCIE_XILINX_CPM=yCONFIG_PCI_XGENE=yCONFIG_PCI_XGENE_MSI=yCONFIG_PCI_V3_SEMI=yCONFIG_PCI_VERSATILE=yCONFIG_PCIE_ALTERA=yCONFIG_PCIE_ALTERA_MSI=yCONFIG_PCI_HOST_THUNDER_PEM=yCONFIG_PCI_HOST_THUNDER_ECAM=yCONFIG_PCIE_ROCKCHIP=yCONFIG_PCIE_ROCKCHIP_HOST=yCONFIG_PCIE_ROCKCHIP_EP=yCONFIG_PCIE_MEDIATEK=yCONFIG_PCIE_MEDIATEK_GEN3=yCONFIG_PCIE_BRCMSTB=yCONFIG_PCI_LOONGSON=yCONFIG_PCIE_MICROCHIP_HOST=yCONFIG_PCIE_APPLE_MSI_DOORBELL_ADDR=0xfffff000CONFIG_PCIE_APPLE=yCONFIG_PCIE_MT7621=y
#
# DesignWare PCI Core Support
#CONFIG_PCIE_DW=yCONFIG_PCIE_DW_HOST=yCONFIG_PCIE_DW_EP=yCONFIG_PCI_DRA7XX=yCONFIG_PCI_DRA7XX_HOST=yCONFIG_PCI_DRA7XX_EP=yCONFIG_PCIE_DW_PLAT=yCONFIG_PCIE_DW_PLAT_HOST=yCONFIG_PCIE_DW_PLAT_EP=yCONFIG_PCI_EXYNOS=yCONFIG_PCI_IMX6=yCONFIG_PCIE_SPEAR13XX=yCONFIG_PCI_KEYSTONE=yCONFIG_PCI_KEYSTONE_HOST=yCONFIG_PCI_KEYSTONE_EP=yCONFIG_PCI_LAYERSCAPE=yCONFIG_PCI_LAYERSCAPE_EP=yCONFIG_PCI_HISI=yCONFIG_PCIE_QCOM=yCONFIG_PCIE_QCOM_EP=yCONFIG_PCIE_ARMADA_8K=yCONFIG_PCIE_ARTPEC6=yCONFIG_PCIE_ARTPEC6_HOST=yCONFIG_PCIE_ARTPEC6_EP=yCONFIG_PCIE_ROCKCHIP_DW_HOST=yCONFIG_PCIE_INTEL_GW=yCONFIG_PCIE_KEEMBAY=yCONFIG_PCIE_KEEMBAY_HOST=yCONFIG_PCIE_KEEMBAY_EP=yCONFIG_PCIE_KIRIN=yCONFIG_PCIE_HISI_STB=yCONFIG_PCI_MESON=yCONFIG_PCIE_TEGRA194=yCONFIG_PCIE_TEGRA194_HOST=yCONFIG_PCIE_TEGRA194_EP=yCONFIG_PCIE_VISCONTI_HOST=yCONFIG_PCIE_UNIPHIER=yCONFIG_PCIE_UNIPHIER_EP=yCONFIG_PCIE_AL=yCONFIG_PCIE_FU740=y
# end of DesignWare PCI Core Support
#
# Mobiveil PCIe Core Support
#CONFIG_PCIE_MOBIVEIL=yCONFIG_PCIE_MOBIVEIL_HOST=yCONFIG_PCIE_MOBIVEIL_PLAT=yCONFIG_PCIE_LAYERSCAPE_GEN4=y
# end of Mobiveil PCIe Core Support
#
# Cadence PCIe controllers support
#CONFIG_PCIE_CADENCE=yCONFIG_PCIE_CADENCE_HOST=yCONFIG_PCIE_CADENCE_EP=yCONFIG_PCIE_CADENCE_PLAT=yCONFIG_PCIE_CADENCE_PLAT_HOST=yCONFIG_PCIE_CADENCE_PLAT_EP=yCONFIG_PCI_J721E=yCONFIG_PCI_J721E_HOST=yCONFIG_PCI_J721E_EP=y
# end of Cadence PCIe controllers support # end of PCI controller drivers
#
# PCI Endpoint
#CONFIG_PCI_ENDPOINT=yCONFIG_PCI_ENDPOINT_CONFIGFS=yCONFIG_PCI_EPF_TEST=yCONFIG_PCI_EPF_NTB=yCONFIG_PCI_EPF_VNTB=y
# end of PCI Endpoint
#
# PCI switch controller drivers
#CONFIG_PCI_SW_SWITCHTEC=y
# end of PCI switch controller drivers
CONFIG_CXL_BUS=yCONFIG_CXL_PCI=yCONFIG_CXL_MEM_RAW_COMMANDS=yCONFIG_CXL_PMEM=yCONFIG_CXL_MEM=yCONFIG_CXL_PORT=yCONFIG_CXL_REGION=yCONFIG_PCCARD=yCONFIG_PCMCIA=yCONFIG_PCMCIA_LOAD_CIS=yCONFIG_CARDBUS=y
#
# PC-card bridges
#CONFIG_YENTA=yCONFIG_YENTA_O2=yCONFIG_YENTA_RICOH=yCONFIG_YENTA_TI=yCONFIG_YENTA_ENE_TUNE=yCONFIG_YENTA_TOSHIBA=yCONFIG_PD6729=yCONFIG_I82092=yCONFIG_I82365=yCONFIG_TCIC=yCONFIG_PCMCIA_PROBE=yCONFIG_PCCARD_NONSTATIC=yCONFIG_RAPIDIO=yCONFIG_RAPIDIO_TSI721=yCONFIG_RAPIDIO_DISC_TIMEOUT=30CONFIG_RAPIDIO_ENABLE_RX_TX_PORTS=yCONFIG_RAPIDIO_DMA_ENGINE=yCONFIG_RAPIDIO_DEBUG=yCONFIG_RAPIDIO_ENUM_BASIC=yCONFIG_RAPIDIO_CHMAN=yCONFIG_RAPIDIO_MPORT_CDEV=y
#
# RapidIO Switch drivers
#CONFIG_RAPIDIO_CPS_XX=yCONFIG_RAPIDIO_CPS_GEN2=yCONFIG_RAPIDIO_RXS_GEN3=y
# end of RapidIO Switch drivers
#
# Generic Driver Options
#CONFIG_AUXILIARY_BUS=yCONFIG_UEVENT_HELPER=yCONFIG_UEVENT_HELPER_PATH=""CONFIG_DEVTMPFS=yCONFIG_DEVTMPFS_MOUNT=yCONFIG_DEVTMPFS_SAFE=yCONFIG_STANDALONE=yCONFIG_PREVENT_FIRMWARE_BUILD=y
#
# Firmware loader
#CONFIG_FW_LOADER=yCONFIG_FW_LOADER_PAGED_BUF=yCONFIG_FW_LOADER_SYSFS=yCONFIG_EXTRA_FIRMWARE=""CONFIG_FW_LOADER_USER_HELPER=yCONFIG_FW_LOADER_USER_HELPER_FALLBACK=yCONFIG_FW_LOADER_COMPRESS=yCONFIG_FW_LOADER_COMPRESS_XZ=yCONFIG_FW_LOADER_COMPRESS_ZSTD=yCONFIG_FW_UPLOAD=y
# end of Firmware loader
CONFIG_WANT_DEV_COREDUMP=yCONFIG_ALLOW_DEV_COREDUMP=yCONFIG_DEV_COREDUMP=yCONFIG_DEBUG_DRIVER=yCONFIG_DEBUG_DEVRES=yCONFIG_DEBUG_TEST_DRIVER_REMOVE=yCONFIG_PM_QOS_KUNIT_TEST=yCONFIG_TEST_ASYNC_DRIVER_PROBE=mCONFIG_DRIVER_PE_KUNIT_TEST=yCONFIG_GENERIC_CPU_VULNERABILITIES=yCONFIG_SOC_BUS=yCONFIG_REGMAP=yCONFIG_REGMAP_AC97=yCONFIG_REGMAP_I2C=yCONFIG_REGMAP_SLIMBUS=yCONFIG_REGMAP_SPI=yCONFIG_REGMAP_SPMI=yCONFIG_REGMAP_W1=yCONFIG_REGMAP_MMIO=yCONFIG_REGMAP_IRQ=yCONFIG_REGMAP_SOUNDWIRE=yCONFIG_REGMAP_SOUNDWIRE_MBQ=yCONFIG_REGMAP_SCCB=yCONFIG_REGMAP_I3C=yCONFIG_REGMAP_SPI_AVMM=yCONFIG_DMA_SHARED_BUFFER=yCONFIG_DMA_FENCE_TRACE=y
# end of Generic Driver Options
#
# Bus devices
#CONFIG_ARM_INTEGRATOR_LM=yCONFIG_BT1_APB=yCONFIG_BT1_AXI=yCONFIG_MOXTET=yCONFIG_INTEL_IXP4XX_EB=yCONFIG_QCOM_EBI2=yCONFIG_MHI_BUS=yCONFIG_MHI_BUS_DEBUG=yCONFIG_MHI_BUS_PCI_GENERIC=yCONFIG_MHI_BUS_EP=y
# end of Bus devices
CONFIG_CONNECTOR=yCONFIG_PROC_EVENTS=y
#
# Firmware Drivers
#
#
# ARM System Control and Management Interface Protocol #CONFIG_ARM_SCMI_PROTOCOL=y CONFIG_ARM_SCMI_HAVE_TRANSPORT=y CONFIG_ARM_SCMI_HAVE_SHMEM=y CONFIG_ARM_SCMI_HAVE_MSG=y CONFIG_ARM_SCMI_TRANSPORT_MAILBOX=y CONFIG_ARM_SCMI_TRANSPORT_VIRTIO=y CONFIG_ARM_SCMI_TRANSPORT_VIRTIO_VERSION1_COMPLIANCE=y CONFIG_ARM_SCMI_TRANSPORT_VIRTIO_ATOMIC_ENABLE=y CONFIG_ARM_SCMI_POWER_DOMAIN=y CONFIG_ARM_SCMI_POWER_CONTROL=y
# end of ARM System Control and Management Interface Protocol
CONFIG_ARM_SCPI_PROTOCOL=yCONFIG_ARM_SCPI_POWER_DOMAIN=yCONFIG_FIRMWARE_MEMMAP=yCONFIG_MTK_ADSP_IPC=yCONFIG_QCOM_SCM=yCONFIG_QCOM_SCM_DOWNLOAD_MODE_DEFAULT=yCONFIG_TURRIS_MOX_RWTM=yCONFIG_BCM47XX_NVRAM=yCONFIG_BCM47XX_SPROM=yCONFIG_TEE_BNXT_FW=yCONFIG_CS_DSP=yCONFIG_GOOGLE_FIRMWARE=yCONFIG_GOOGLE_COREBOOT_TABLE=yCONFIG_GOOGLE_MEMCONSOLE=yCONFIG_GOOGLE_MEMCONSOLE_COREBOOT=yCONFIG_GOOGLE_VPD=yCONFIG_IMX_DSP=yCONFIG_IMX_SCU=yCONFIG_IMX_SCU_PD=y
#
# Tegra firmware driver
#
# end of Tegra firmware driver # end of Firmware Drivers
CONFIG_GNSS=yCONFIG_GNSS_SERIAL=yCONFIG_GNSS_MTK_SERIAL=yCONFIG_GNSS_SIRF_SERIAL=yCONFIG_GNSS_UBX_SERIAL=yCONFIG_GNSS_USB=yCONFIG_MTD=yCONFIG_MTD_TESTS=m
#
# Partition parsers
#CONFIG_MTD_AR7_PARTS=yCONFIG_MTD_BCM63XX_PARTS=yCONFIG_MTD_CMDLINE_PARTS=yCONFIG_MTD_OF_PARTS=yCONFIG_MTD_OF_PARTS_BCM4908=yCONFIG_MTD_OF_PARTS_LINKSYS_NS=yCONFIG_MTD_PARSER_IMAGETAG=yCONFIG_MTD_PARSER_TRX=yCONFIG_MTD_SHARPSL_PARTS=yCONFIG_MTD_REDBOOT_PARTS=yCONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED=yCONFIG_MTD_REDBOOT_PARTS_READONLY=yCONFIG_MTD_QCOMSMEM_PARTS=y
# end of Partition parsers
#
# User Modules And Translation Layers
#CONFIG_MTD_BLKDEVS=yCONFIG_MTD_BLOCK=y
#
# Note that in some cases UBI block is preferred. See MTD_UBI_BLOCK. #CONFIG_FTL=yCONFIG_NFTL=yCONFIG_NFTL_RW=yCONFIG_INFTL=yCONFIG_RFD_FTL=yCONFIG_SSFDC=yCONFIG_SM_FTL=yCONFIG_MTD_OOPS=yCONFIG_MTD_PSTORE=yCONFIG_MTD_SWAP=yCONFIG_MTD_PARTITIONED_MASTER=y
#
# RAM/ROM/Flash chip drivers
#CONFIG_MTD_CFI=yCONFIG_MTD_JEDECPROBE=yCONFIG_MTD_GEN_PROBE=yCONFIG_MTD_CFI_ADV_OPTIONS=yCONFIG_MTD_CFI_NOSWAP=y
# CONFIG_MTD_CFI_BE_BYTE_SWAP is not set
# CONFIG_MTD_CFI_LE_BYTE_SWAP is not setCONFIG_MTD_CFI_GEOMETRY=yCONFIG_MTD_MAP_BANK_WIDTH_1=yCONFIG_MTD_MAP_BANK_WIDTH_2=yCONFIG_MTD_MAP_BANK_WIDTH_4=yCONFIG_MTD_MAP_BANK_WIDTH_8=yCONFIG_MTD_MAP_BANK_WIDTH_16=yCONFIG_MTD_MAP_BANK_WIDTH_32=yCONFIG_MTD_CFI_I1=yCONFIG_MTD_CFI_I2=yCONFIG_MTD_CFI_I4=yCONFIG_MTD_CFI_I8=yCONFIG_MTD_OTP=yCONFIG_MTD_CFI_INTELEXT=yCONFIG_MTD_CFI_AMDSTD=yCONFIG_MTD_CFI_STAA=yCONFIG_MTD_CFI_UTIL=yCONFIG_MTD_RAM=yCONFIG_MTD_ROM=yCONFIG_MTD_ABSENT=y
# end of RAM/ROM/Flash chip drivers
#
# Mapping drivers for chip access
#CONFIG_MTD_COMPLEX_MAPPINGS=yCONFIG_MTD_PHYSMAP=yCONFIG_MTD_PHYSMAP_COMPAT=yCONFIG_MTD_PHYSMAP_START=0x8000000CONFIG_MTD_PHYSMAP_LEN=0CONFIG_MTD_PHYSMAP_BANKWIDTH=2CONFIG_MTD_PHYSMAP_OF=yCONFIG_MTD_PHYSMAP_BT1_ROM=yCONFIG_MTD_PHYSMAP_VERSATILE=yCONFIG_MTD_PHYSMAP_GEMINI=yCONFIG_MTD_PHYSMAP_GPIO_ADDR=yCONFIG_MTD_SC520CDP=yCONFIG_MTD_NETSC520=yCONFIG_MTD_TS5500=yCONFIG_MTD_PCI=yCONFIG_MTD_PCMCIA=yCONFIG_MTD_PCMCIA_ANONYMOUS=yCONFIG_MTD_INTEL_VR_NOR=yCONFIG_MTD_PLATRAM=y
# end of Mapping drivers for chip access
#
# Self-contained MTD device drivers
#CONFIG_MTD_PMC551=yCONFIG_MTD_PMC551_BUGFIX=yCONFIG_MTD_PMC551_DEBUG=yCONFIG_MTD_DATAFLASH=yCONFIG_MTD_DATAFLASH_WRITE_VERIFY=yCONFIG_MTD_DATAFLASH_OTP=yCONFIG_MTD_MCHP23K256=yCONFIG_MTD_MCHP48L640=yCONFIG_MTD_SPEAR_SMI=yCONFIG_MTD_SST25L=yCONFIG_MTD_SLRAM=yCONFIG_MTD_PHRAM=yCONFIG_MTD_MTDRAM=yCONFIG_MTDRAM_TOTAL_SIZE=4096CONFIG_MTDRAM_ERASE_SIZE=128CONFIG_MTD_BLOCK2MTD=y
#
# Disk-On-Chip Device Drivers
#CONFIG_MTD_DOCG3=yCONFIG_BCH_CONST_M=14CONFIG_BCH_CONST_T=4
# end of Self-contained MTD device drivers
#
# NAND
#CONFIG_MTD_NAND_CORE=yCONFIG_MTD_ONENAND=yCONFIG_MTD_ONENAND_VERIFY_WRITE=yCONFIG_MTD_ONENAND_GENERIC=yCONFIG_MTD_ONENAND_SAMSUNG=yCONFIG_MTD_ONENAND_OTP=yCONFIG_MTD_ONENAND_2X_PROGRAM=yCONFIG_MTD_RAW_NAND=y
#
# Raw/parallel NAND flash controllers
#CONFIG_MTD_NAND_DENALI=yCONFIG_MTD_NAND_DENALI_PCI=yCONFIG_MTD_NAND_DENALI_DT=yCONFIG_MTD_NAND_AMS_DELTA=yCONFIG_MTD_NAND_OMAP2=yCONFIG_MTD_NAND_OMAP_BCH=yCONFIG_MTD_NAND_OMAP_BCH_BUILD=yCONFIG_MTD_NAND_SHARPSL=yCONFIG_MTD_NAND_CAFE=yCONFIG_MTD_NAND_ATMEL=yCONFIG_MTD_NAND_MARVELL=yCONFIG_MTD_NAND_SLC_LPC32XX=yCONFIG_MTD_NAND_MLC_LPC32XX=yCONFIG_MTD_NAND_BRCMNAND=yCONFIG_MTD_NAND_BRCMNAND_BCMA=yCONFIG_MTD_NAND_BCM47XXNFLASH=yCONFIG_MTD_NAND_OXNAS=yCONFIG_MTD_NAND_GPMI_NAND=yCONFIG_MTD_NAND_FSL_IFC=yCONFIG_MTD_NAND_VF610_NFC=yCONFIG_MTD_NAND_MXC=yCONFIG_MTD_NAND_SH_FLCTL=yCONFIG_MTD_NAND_DAVINCI=yCONFIG_MTD_NAND_TXX9NDFMC=yCONFIG_MTD_NAND_JZ4780=yCONFIG_MTD_NAND_INGENIC_ECC=yCONFIG_MTD_NAND_JZ4740_ECC=yCONFIG_MTD_NAND_JZ4725B_BCH=yCONFIG_MTD_NAND_JZ4780_BCH=yCONFIG_MTD_NAND_FSMC=yCONFIG_MTD_NAND_SUNXI=yCONFIG_MTD_NAND_HISI504=yCONFIG_MTD_NAND_QCOM=yCONFIG_MTD_NAND_MTK=yCONFIG_MTD_NAND_MXIC=yCONFIG_MTD_NAND_TEGRA=yCONFIG_MTD_NAND_STM32_FMC2=yCONFIG_MTD_NAND_MESON=yCONFIG_MTD_NAND_GPIO=yCONFIG_MTD_NAND_PLATFORM=yCONFIG_MTD_NAND_CADENCE=yCONFIG_MTD_NAND_ARASAN=yCONFIG_MTD_NAND_INTEL_LGM=yCONFIG_MTD_NAND_RENESAS=y
#
# Misc
#CONFIG_MTD_SM_COMMON=yCONFIG_MTD_NAND_NANDSIM=yCONFIG_MTD_NAND_RICOH=yCONFIG_MTD_NAND_DISKONCHIP=yCONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED=yCONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0CONFIG_MTD_NAND_DISKONCHIP_PROBE_HIGH=yCONFIG_MTD_NAND_DISKONCHIP_BBTWRITE=yCONFIG_MTD_SPI_NAND=y
#
# ECC engine support
#CONFIG_MTD_NAND_ECC=yCONFIG_MTD_NAND_ECC_SW_HAMMING=yCONFIG_MTD_NAND_ECC_SW_HAMMING_SMC=yCONFIG_MTD_NAND_ECC_SW_BCH=yCONFIG_MTD_NAND_ECC_MXIC=yCONFIG_MTD_NAND_ECC_MEDIATEK=y
# end of ECC engine support # end of NAND
#
# LPDDR & LPDDR2 PCM memory drivers
#CONFIG_MTD_LPDDR=yCONFIG_MTD_QINFO_PROBE=y
# end of LPDDR & LPDDR2 PCM memory drivers
CONFIG_MTD_SPI_NOR=yCONFIG_MTD_SPI_NOR_USE_4K_SECTORS=y
# CONFIG_MTD_SPI_NOR_SWP_DISABLE is not setCONFIG_MTD_SPI_NOR_SWP_DISABLE_ON_VOLATILE=y
# CONFIG_MTD_SPI_NOR_SWP_KEEP is not setCONFIG_SPI_HISI_SFC=yCONFIG_SPI_NXP_SPIFI=yCONFIG_MTD_UBI=yCONFIG_MTD_UBI_WL_THRESHOLD=4096CONFIG_MTD_UBI_BEB_LIMIT=20CONFIG_MTD_UBI_FASTMAP=yCONFIG_MTD_UBI_GLUEBI=yCONFIG_MTD_UBI_BLOCK=yCONFIG_MTD_HYPERBUS=yCONFIG_HBMC_AM654=yCONFIG_DTC=yCONFIG_OF=yCONFIG_OF_UNITTEST=yCONFIG_OF_ALL_DTBS=yCONFIG_OF_FLATTREE=yCONFIG_OF_EARLY_FLATTREE=yCONFIG_OF_KOBJ=yCONFIG_OF_DYNAMIC=yCONFIG_OF_ADDRESS=yCONFIG_OF_IRQ=yCONFIG_OF_RESERVED_MEM=yCONFIG_OF_RESOLVE=yCONFIG_OF_OVERLAY=yCONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=yCONFIG_PARPORT=yCONFIG_PARPORT_PC=yCONFIG_PARPORT_SERIAL=yCONFIG_PARPORT_PC_FIFO=yCONFIG_PARPORT_PC_SUPERIO=yCONFIG_PARPORT_PC_PCMCIA=yCONFIG_PARPORT_AX88796=yCONFIG_PARPORT_1284=yCONFIG_PARPORT_NOT_PC=yCONFIG_PNP=yCONFIG_PNP_DEBUG_MESSAGES=y
#
# Protocols
#CONFIG_ISAPNP=yCONFIG_BLK_DEV=yCONFIG_BLK_DEV_NULL_BLK=yCONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION=yCONFIG_BLK_DEV_FD=yCONFIG_BLK_DEV_FD_RAWCMD=yCONFIG_CDROM=yCONFIG_PARIDE=y
#
# Parallel IDE high-level drivers
#CONFIG_PARIDE_PD=yCONFIG_PARIDE_PCD=yCONFIG_PARIDE_PF=yCONFIG_PARIDE_PT=yCONFIG_PARIDE_PG=y
#
# Parallel IDE protocol modules
#CONFIG_PARIDE_ATEN=yCONFIG_PARIDE_BPCK=yCONFIG_PARIDE_COMM=yCONFIG_PARIDE_DSTR=yCONFIG_PARIDE_FIT2=yCONFIG_PARIDE_FIT3=yCONFIG_PARIDE_EPAT=yCONFIG_PARIDE_EPATC8=yCONFIG_PARIDE_EPIA=yCONFIG_PARIDE_FRIQ=yCONFIG_PARIDE_FRPW=yCONFIG_PARIDE_KBIC=yCONFIG_PARIDE_KTTI=yCONFIG_PARIDE_ON20=yCONFIG_PARIDE_ON26=yCONFIG_BLK_DEV_PCIESSD_MTIP32XX=yCONFIG_ZRAM=yCONFIG_ZRAM_DEF_COMP_LZORLE=y
# CONFIG_ZRAM_DEF_COMP_ZSTD is not set
# CONFIG_ZRAM_DEF_COMP_LZ4 is not set
# CONFIG_ZRAM_DEF_COMP_LZO is not set
# CONFIG_ZRAM_DEF_COMP_LZ4HC is not set
# CONFIG_ZRAM_DEF_COMP_842 is not setCONFIG_ZRAM_DEF_COMP="lzo-rle"CONFIG_ZRAM_WRITEBACK=yCONFIG_ZRAM_MEMORY_TRACKING=yCONFIG_BLK_DEV_LOOP=yCONFIG_BLK_DEV_LOOP_MIN_COUNT=8CONFIG_BLK_DEV_DRBD=yCONFIG_DRBD_FAULT_INJECTION=yCONFIG_BLK_DEV_NBD=yCONFIG_BLK_DEV_RAM=yCONFIG_BLK_DEV_RAM_COUNT=16CONFIG_BLK_DEV_RAM_SIZE=4096CONFIG_CDROM_PKTCDVD=yCONFIG_CDROM_PKTCDVD_BUFFERS=8CONFIG_CDROM_PKTCDVD_WCACHE=yCONFIG_ATA_OVER_ETH=yCONFIG_VIRTIO_BLK=yCONFIG_BLK_DEV_RBD=yCONFIG_BLK_DEV_UBLK=y
#
# NVME Support
#CONFIG_NVME_COMMON=yCONFIG_NVME_CORE=yCONFIG_BLK_DEV_NVME=yCONFIG_NVME_MULTIPATH=yCONFIG_NVME_VERBOSE_ERRORS=yCONFIG_NVME_HWMON=yCONFIG_NVME_FABRICS=yCONFIG_NVME_FC=yCONFIG_NVME_TCP=yCONFIG_NVME_AUTH=yCONFIG_NVME_APPLE=yCONFIG_NVME_TARGET=yCONFIG_NVME_TARGET_PASSTHRU=yCONFIG_NVME_TARGET_LOOP=yCONFIG_NVME_TARGET_FC=yCONFIG_NVME_TARGET_FCLOOP=yCONFIG_NVME_TARGET_TCP=yCONFIG_NVME_TARGET_AUTH=y
# end of NVME Support
#
# Misc devices
#CONFIG_SENSORS_LIS3LV02D=yCONFIG_AD525X_DPOT=yCONFIG_AD525X_DPOT_I2C=yCONFIG_AD525X_DPOT_SPI=yCONFIG_DUMMY_IRQ=yCONFIG_PHANTOM=yCONFIG_TIFM_CORE=yCONFIG_TIFM_7XX1=yCONFIG_ICS932S401=yCONFIG_ATMEL_SSC=yCONFIG_ENCLOSURE_SERVICES=yCONFIG_GEHC_ACHC=yCONFIG_HI6421V600_IRQ=yCONFIG_HP_ILO=yCONFIG_QCOM_COINCELL=yCONFIG_QCOM_FASTRPC=yCONFIG_APDS9802ALS=yCONFIG_ISL29003=yCONFIG_ISL29020=yCONFIG_SENSORS_TSL2550=yCONFIG_SENSORS_BH1770=yCONFIG_SENSORS_APDS990X=yCONFIG_HMC6352=yCONFIG_DS1682=yCONFIG_PCH_PHUB=yCONFIG_LATTICE_ECP3_CONFIG=yCONFIG_SRAM=yCONFIG_DW_XDATA_PCIE=yCONFIG_PCI_ENDPOINT_TEST=yCONFIG_XILINX_SDFEC=yCONFIG_MISC_RTSX=yCONFIG_HISI_HIKEY_USB=yCONFIG_OPEN_DICE=yCONFIG_VCPU_STALL_DETECTOR=yCONFIG_C2PORT=y
#
# EEPROM support
#CONFIG_EEPROM_AT24=yCONFIG_EEPROM_AT25=yCONFIG_EEPROM_LEGACY=yCONFIG_EEPROM_MAX6875=yCONFIG_EEPROM_93CX6=yCONFIG_EEPROM_93XX46=yCONFIG_EEPROM_IDT_89HPESX=yCONFIG_EEPROM_EE1004=y
# end of EEPROM support
CONFIG_CB710_CORE=yCONFIG_CB710_DEBUG=yCONFIG_CB710_DEBUG_ASSUMPTIONS=y
#
# Texas Instruments shared transport line discipline #CONFIG_TI_ST=y
# end of Texas Instruments shared transport line discipline
CONFIG_SENSORS_LIS3_SPI=yCONFIG_SENSORS_LIS3_I2C=yCONFIG_ALTERA_STAPL=yCONFIG_GENWQE=yCONFIG_GENWQE_PLATFORM_ERROR_RECOVERY=0CONFIG_ECHO=yCONFIG_BCM_VK=yCONFIG_BCM_VK_TTY=yCONFIG_MISC_ALCOR_PCI=yCONFIG_MISC_RTSX_PCI=yCONFIG_MISC_RTSX_USB=yCONFIG_HABANA_AI=yCONFIG_UACCE=yCONFIG_PVPANIC=yCONFIG_PVPANIC_MMIO=yCONFIG_PVPANIC_PCI=y
# end of Misc devices
#
# SCSI device support
#CONFIG_SCSI_MOD=yCONFIG_RAID_ATTRS=yCONFIG_SCSI_COMMON=yCONFIG_SCSI=yCONFIG_SCSI_DMA=yCONFIG_SCSI_NETLINK=yCONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#CONFIG_BLK_DEV_SD=yCONFIG_CHR_DEV_ST=yCONFIG_BLK_DEV_SR=yCONFIG_CHR_DEV_SG=yCONFIG_BLK_DEV_BSG=yCONFIG_CHR_DEV_SCH=yCONFIG_SCSI_ENCLOSURE=yCONFIG_SCSI_CONSTANTS=yCONFIG_SCSI_LOGGING=yCONFIG_SCSI_SCAN_ASYNC=y
#
# SCSI Transports
#CONFIG_SCSI_SPI_ATTRS=yCONFIG_SCSI_FC_ATTRS=yCONFIG_SCSI_ISCSI_ATTRS=yCONFIG_SCSI_SAS_ATTRS=yCONFIG_SCSI_SAS_LIBSAS=yCONFIG_SCSI_SAS_ATA=yCONFIG_SCSI_SAS_HOST_SMP=yCONFIG_SCSI_SRP_ATTRS=y
# end of SCSI Transports
CONFIG_SCSI_LOWLEVEL=yCONFIG_ISCSI_TCP=yCONFIG_ISCSI_BOOT_SYSFS=yCONFIG_SCSI_CXGB3_ISCSI=yCONFIG_SCSI_CXGB4_ISCSI=yCONFIG_SCSI_BNX2_ISCSI=yCONFIG_SCSI_BNX2X_FCOE=yCONFIG_BE2ISCSI=yCONFIG_BLK_DEV_3W_XXXX_RAID=yCONFIG_SCSI_HPSA=yCONFIG_SCSI_3W_9XXX=yCONFIG_SCSI_3W_SAS=yCONFIG_SCSI_ACARD=yCONFIG_SCSI_AHA152X=yCONFIG_SCSI_AHA1542=yCONFIG_SCSI_AHA1740=yCONFIG_SCSI_AACRAID=yCONFIG_SCSI_AIC7XXX=yCONFIG_AIC7XXX_CMDS_PER_DEVICE=32CONFIG_AIC7XXX_RESET_DELAY_MS=5000CONFIG_AIC7XXX_DEBUG_ENABLE=yCONFIG_AIC7XXX_DEBUG_MASK=0CONFIG_AIC7XXX_REG_PRETTY_PRINT=yCONFIG_SCSI_AIC79XX=yCONFIG_AIC79XX_CMDS_PER_DEVICE=32CONFIG_AIC79XX_RESET_DELAY_MS=5000CONFIG_AIC79XX_DEBUG_ENABLE=yCONFIG_AIC79XX_DEBUG_MASK=0CONFIG_AIC79XX_REG_PRETTY_PRINT=yCONFIG_SCSI_AIC94XX=yCONFIG_AIC94XX_DEBUG=yCONFIG_SCSI_HISI_SAS=yCONFIG_SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE=yCONFIG_SCSI_MVSAS=yCONFIG_SCSI_MVSAS_DEBUG=yCONFIG_SCSI_MVSAS_TASKLET=yCONFIG_SCSI_MVUMI=yCONFIG_SCSI_ADVANSYS=yCONFIG_SCSI_ARCMSR=yCONFIG_SCSI_ESAS2R=yCONFIG_MEGARAID_NEWGEN=yCONFIG_MEGARAID_MM=yCONFIG_MEGARAID_MAILBOX=yCONFIG_MEGARAID_LEGACY=yCONFIG_MEGARAID_SAS=yCONFIG_SCSI_MPT3SAS=yCONFIG_SCSI_MPT2SAS_MAX_SGE=128CONFIG_SCSI_MPT3SAS_MAX_SGE=128CONFIG_SCSI_MPT2SAS=yCONFIG_SCSI_MPI3MR=yCONFIG_SCSI_SMARTPQI=yCONFIG_SCSI_HPTIOP=yCONFIG_SCSI_BUSLOGIC=yCONFIG_SCSI_FLASHPOINT=yCONFIG_SCSI_MYRB=yCONFIG_SCSI_MYRS=yCONFIG_LIBFC=yCONFIG_LIBFCOE=yCONFIG_FCOE=yCONFIG_SCSI_SNIC=yCONFIG_SCSI_SNIC_DEBUG_FS=yCONFIG_SCSI_DMX3191D=yCONFIG_SCSI_FDOMAIN=yCONFIG_SCSI_FDOMAIN_PCI=yCONFIG_SCSI_FDOMAIN_ISA=yCONFIG_SCSI_GENERIC_NCR5380=yCONFIG_SCSI_IPS=yCONFIG_SCSI_INITIO=yCONFIG_SCSI_INIA100=yCONFIG_SCSI_PPA=yCONFIG_SCSI_IMM=yCONFIG_SCSI_IZIP_EPP16=yCONFIG_SCSI_IZIP_SLOW_CTR=yCONFIG_SCSI_STEX=yCONFIG_SCSI_SYM53C8XX_2=yCONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64CONFIG_SCSI_SYM53C8XX_MMIO=yCONFIG_SCSI_IPR=yCONFIG_SCSI_IPR_TRACE=yCONFIG_SCSI_IPR_DUMP=yCONFIG_SCSI_QLOGIC_FAS=yCONFIG_SCSI_QLOGIC_1280=yCONFIG_SCSI_QLA_FC=yCONFIG_TCM_QLA2XXX=yCONFIG_TCM_QLA2XXX_DEBUG=yCONFIG_SCSI_QLA_ISCSI=yCONFIG_QEDI=yCONFIG_QEDF=yCONFIG_SCSI_EFCT=yCONFIG_SCSI_SIM710=y
CONFIG_SCSI_DC395x=yCONFIG_SCSI_AM53C974=yCONFIG_SCSI_WD719X=yCONFIG_SCSI_DEBUG=yCONFIG_SCSI_PMCRAID=yCONFIG_SCSI_PM8001=yCONFIG_SCSI_BFA_FC=yCONFIG_SCSI_VIRTIO=yCONFIG_SCSI_CHELSIO_FCOE=yCONFIG_SCSI_LOWLEVEL_PCMCIA=yCONFIG_PCMCIA_AHA152X=mCONFIG_PCMCIA_FDOMAIN=mCONFIG_PCMCIA_NINJA_SCSI=mCONFIG_PCMCIA_QLOGIC=mCONFIG_PCMCIA_SYM53C500=mCONFIG_SCSI_DH=yCONFIG_SCSI_DH_RDAC=yCONFIG_SCSI_DH_HP_SW=yCONFIG_SCSI_DH_EMC=yCONFIG_SCSI_DH_ALUA=y
# end of SCSI device support
CONFIG_ATA=yCONFIG_SATA_HOST=yCONFIG_PATA_TIMINGS=yCONFIG_ATA_VERBOSE_ERROR=yCONFIG_ATA_FORCE=yCONFIG_SATA_PMP=y
#
# Controllers with non-SFF native interface
#CONFIG_SATA_AHCI=yCONFIG_SATA_MOBILE_LPM_POLICY=0CONFIG_SATA_AHCI_PLATFORM=yCONFIG_AHCI_BRCM=yCONFIG_AHCI_DA850=yCONFIG_AHCI_DM816=yCONFIG_AHCI_IMX=yCONFIG_AHCI_CEVA=yCONFIG_AHCI_MTK=yCONFIG_AHCI_MVEBU=yCONFIG_AHCI_SUNXI=yCONFIG_AHCI_TEGRA=yCONFIG_AHCI_XGENE=yCONFIG_AHCI_QORIQ=yCONFIG_SATA_FSL=yCONFIG_SATA_GEMINI=yCONFIG_SATA_AHCI_SEATTLE=yCONFIG_SATA_INIC162X=yCONFIG_SATA_ACARD_AHCI=yCONFIG_SATA_SIL24=yCONFIG_ATA_SFF=y
#
# SFF controllers with custom DMA interface
#CONFIG_PDC_ADMA=yCONFIG_SATA_QSTOR=yCONFIG_SATA_SX4=yCONFIG_ATA_BMDMA=y
#
# SATA SFF controllers with BMDMA
#CONFIG_ATA_PIIX=yCONFIG_SATA_DWC=yCONFIG_SATA_DWC_OLD_DMA=yCONFIG_SATA_HIGHBANK=yCONFIG_SATA_MV=yCONFIG_SATA_NV=yCONFIG_SATA_PROMISE=yCONFIG_SATA_RCAR=yCONFIG_SATA_SIL=yCONFIG_SATA_SIS=yCONFIG_SATA_SVW=yCONFIG_SATA_ULI=yCONFIG_SATA_VIA=yCONFIG_SATA_VITESSE=y
#
# PATA SFF controllers with BMDMA
#CONFIG_PATA_ALI=yCONFIG_PATA_AMD=yCONFIG_PATA_ARASAN_CF=yCONFIG_PATA_ARTOP=yCONFIG_PATA_ATIIXP=yCONFIG_PATA_ATP867X=yCONFIG_PATA_BK3710=yCONFIG_PATA_CMD64X=yCONFIG_PATA_CS5520=yCONFIG_PATA_CS5530=yCONFIG_PATA_CS5536=yCONFIG_PATA_CYPRESS=yCONFIG_PATA_EFAR=yCONFIG_PATA_FTIDE010=yCONFIG_PATA_HPT366=yCONFIG_PATA_HPT37X=yCONFIG_PATA_HPT3X2N=yCONFIG_PATA_HPT3X3=yCONFIG_PATA_HPT3X3_DMA=yCONFIG_PATA_IMX=yCONFIG_PATA_IT8213=yCONFIG_PATA_IT821X=yCONFIG_PATA_JMICRON=yCONFIG_PATA_MARVELL=yCONFIG_PATA_NETCELL=yCONFIG_PATA_NINJA32=yCONFIG_PATA_NS87415=yCONFIG_PATA_OLDPIIX=yCONFIG_PATA_OPTIDMA=yCONFIG_PATA_PDC2027X=yCONFIG_PATA_PDC_OLD=yCONFIG_PATA_RADISYS=yCONFIG_PATA_RDC=yCONFIG_PATA_SC1200=yCONFIG_PATA_SCH=yCONFIG_PATA_SERVERWORKS=yCONFIG_PATA_SIL680=yCONFIG_PATA_SIS=yCONFIG_PATA_TOSHIBA=yCONFIG_PATA_TRIFLEX=yCONFIG_PATA_VIA=yCONFIG_PATA_PXA=yCONFIG_PATA_WINBOND=y
#
# PIO-only SFF controllers
#CONFIG_PATA_CMD640_PCI=yCONFIG_PATA_ISAPNP=yCONFIG_PATA_IXP4XX_CF=yCONFIG_PATA_MPIIX=yCONFIG_PATA_NS87410=yCONFIG_PATA_OPTI=yCONFIG_PATA_PCMCIA=yCONFIG_PATA_PLATFORM=yCONFIG_PATA_OF_PLATFORM=yCONFIG_PATA_QDI=yCONFIG_PATA_RZ1000=yCONFIG_PATA_SAMSUNG_CF=yCONFIG_PATA_WINBOND_VLB=y
#
# Generic fallback / legacy drivers
#CONFIG_ATA_GENERIC=yCONFIG_PATA_LEGACY=yCONFIG_MD=yCONFIG_BLK_DEV_MD=yCONFIG_MD_AUTODETECT=yCONFIG_MD_LINEAR=yCONFIG_MD_RAID0=yCONFIG_MD_RAID1=yCONFIG_MD_RAID10=yCONFIG_MD_RAID456=yCONFIG_MD_MULTIPATH=yCONFIG_MD_FAULTY=yCONFIG_MD_CLUSTER=yCONFIG_BCACHE=yCONFIG_BCACHE_DEBUG=y CONFIG_BCACHE_CLOSURES_DEBUG=y CONFIG_BCACHE_ASYNC_REGISTRATION=y CONFIG_BLK_DEV_DM_BUILTIN=yCONFIG_BLK_DEV_DM=yCONFIG_DM_DEBUG=yCONFIG_DM_BUFIO=y CONFIG_DM_DEBUG_BLOCK_MANAGER_LOCKING=y CONFIG_DM_BIO_PRISON=y CONFIG_DM_PERSISTENT_DATA=y CONFIG_DM_UNSTRIPED=yCONFIG_DM_CRYPT=yCONFIG_DM_SNAPSHOT=y CONFIG_DM_THIN_PROVISIONING=yCONFIG_DM_CACHE=yCONFIG_DM_CACHE_SMQ=yCONFIG_DM_WRITECACHE=yCONFIG_DM_EBS=yCONFIG_DM_ERA=yCONFIG_DM_CLONE=yCONFIG_DM_MIRROR=yCONFIG_DM_LOG_USERSPACE=yCONFIG_DM_RAID=yCONFIG_DM_ZERO=yCONFIG_DM_MULTIPATH=yCONFIG_DM_MULTIPATH_QL=y CONFIG_DM_MULTIPATH_ST=y CONFIG_DM_MULTIPATH_HST=y CONFIG_DM_MULTIPATH_IOA=yCONFIG_DM_DELAY=yCONFIG_DM_DUST=yCONFIG_DM_INIT=yCONFIG_DM_UEVENT=yCONFIG_DM_FLAKEY=yCONFIG_DM_VERITY=y CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG=y CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y CONFIG_DM_VERITY_FEC=yCONFIG_DM_SWITCH=yCONFIG_DM_LOG_WRITES=yCONFIG_DM_INTEGRITY=yCONFIG_DM_ZONED=yCONFIG_DM_AUDIT=yCONFIG_TARGET_CORE=yCONFIG_TCM_IBLOCK=yCONFIG_TCM_FILEIO=yCONFIG_TCM_PSCSI=yCONFIG_TCM_USER2=yCONFIG_LOOPBACK_TARGET=yCONFIG_TCM_FC=yCONFIG_ISCSI_TARGET=y CONFIG_ISCSI_TARGET_CXGB4=yCONFIG_SBP_TARGET=yCONFIG_FUSION=yCONFIG_FUSION_SPI=yCONFIG_FUSION_FC=yCONFIG_FUSION_SAS=yCONFIG_FUSION_MAX_SGE=128CONFIG_FUSION_CTL=yCONFIG_FUSION_LAN=yCONFIG_FUSION_LOGGING=y
#
# IEEE 1394 (FireWire) support
#CONFIG_FIREWIRE=yCONFIG_FIREWIRE_OHCI=yCONFIG_FIREWIRE_SBP2=yCONFIG_FIREWIRE_NET=yCONFIG_FIREWIRE_NOSY=y
# end of IEEE 1394 (FireWire) support
CONFIG_NETDEVICES=yCONFIG_MII=yCONFIG_NET_CORE=yCONFIG_BONDING=yCONFIG_DUMMY=yCONFIG_WIREGUARD=yCONFIG_WIREGUARD_DEBUG=yCONFIG_EQUALIZER=yCONFIG_NET_FC=yCONFIG_IFB=yCONFIG_NET_TEAM=yCONFIG_NET_TEAM_MODE_BROADCAST=yCONFIG_NET_TEAM_MODE_ROUNDROBIN=yCONFIG_NET_TEAM_MODE_RANDOM=yCONFIG_NET_TEAM_MODE_ACTIVEBACKUP=yCONFIG_NET_TEAM_MODE_LOADBALANCE=yCONFIG_MACVLAN=yCONFIG_MACVTAP=yCONFIG_IPVLAN_L3S=yCONFIG_IPVLAN=yCONFIG_IPVTAP=yCONFIG_VXLAN=yCONFIG_GENEVE=yCONFIG_BAREUDP=yCONFIG_GTP=yCONFIG_AMT=yCONFIG_MACSEC=yCONFIG_NETCONSOLE=yCONFIG_NETCONSOLE_DYNAMIC=yCONFIG_NETPOLL=yCONFIG_NET_POLL_CONTROLLER=yCONFIG_NTB_NETDEV=yCONFIG_RIONET=yCONFIG_RIONET_TX_SIZE=128CONFIG_RIONET_RX_SIZE=128CONFIG_TUN=yCONFIG_TAP=yCONFIG_TUN_VNET_CROSS_LE=yCONFIG_VETH=yCONFIG_VIRTIO_NET=yCONFIG_NLMON=yCONFIG_NET_VRF=yCONFIG_VSOCKMON=yCONFIG_MHI_NET=yCONFIG_SUNGEM_PHY=yCONFIG_ARCNET=yCONFIG_ARCNET_1201=yCONFIG_ARCNET_1051=yCONFIG_ARCNET_RAW=yCONFIG_ARCNET_CAP=y
CONFIG_ARCNET_COM90xx=y
CONFIG_ARCNET_COM90xxIO=yCONFIG_ARCNET_RIM_I=yCONFIG_ARCNET_COM20020=yCONFIG_ARCNET_COM20020_ISA=yCONFIG_ARCNET_COM20020_PCI=yCONFIG_ARCNET_COM20020_CS=yCONFIG_ATM_DRIVERS=yCONFIG_ATM_DUMMY=yCONFIG_ATM_TCP=yCONFIG_ATM_LANAI=yCONFIG_ATM_ENI=yCONFIG_ATM_ENI_DEBUG=yCONFIG_ATM_ENI_TUNE_BURST=yCONFIG_ATM_ENI_BURST_TX_16W=yCONFIG_ATM_ENI_BURST_TX_8W=yCONFIG_ATM_ENI_BURST_TX_4W=yCONFIG_ATM_ENI_BURST_TX_2W=yCONFIG_ATM_ENI_BURST_RX_16W=yCONFIG_ATM_ENI_BURST_RX_8W=yCONFIG_ATM_ENI_BURST_RX_4W=yCONFIG_ATM_ENI_BURST_RX_2W=yCONFIG_ATM_NICSTAR=yCONFIG_ATM_NICSTAR_USE_SUNI=yCONFIG_ATM_NICSTAR_USE_IDT77105=yCONFIG_ATM_IDT77252=yCONFIG_ATM_IDT77252_DEBUG=yCONFIG_ATM_IDT77252_RCV_ALL=yCONFIG_ATM_IDT77252_USE_SUNI=yCONFIG_ATM_IA=yCONFIG_ATM_IA_DEBUG=yCONFIG_ATM_FORE200E=yCONFIG_ATM_FORE200E_USE_TASKLET=yCONFIG_ATM_FORE200E_TX_RETRY=16CONFIG_ATM_FORE200E_DEBUG=0CONFIG_ATM_HE=yCONFIG_ATM_HE_USE_SUNI=yCONFIG_ATM_SOLOS=yCONFIG_CAIF_DRIVERS=yCONFIG_CAIF_TTY=yCONFIG_CAIF_VIRTIO=y
#
# Distributed Switch Architecture drivers
#CONFIG_B53=yCONFIG_B53_SPI_DRIVER=yCONFIG_B53_MDIO_DRIVER=yCONFIG_B53_MMAP_DRIVER=yCONFIG_B53_SRAB_DRIVER=yCONFIG_B53_SERDES=yCONFIG_NET_DSA_BCM_SF2=yCONFIG_NET_DSA_LOOP=yCONFIG_NET_DSA_HIRSCHMANN_HELLCREEK=yCONFIG_NET_DSA_LANTIQ_GSWIP=yCONFIG_NET_DSA_MT7530=yCONFIG_NET_DSA_MV88E6060=yCONFIG_NET_DSA_MICROCHIP_KSZ_COMMON=yCONFIG_NET_DSA_MICROCHIP_KSZ9477_I2C=yCONFIG_NET_DSA_MICROCHIP_KSZ_SPI=yCONFIG_NET_DSA_MICROCHIP_KSZ8863_SMI=yCONFIG_NET_DSA_MV88E6XXX=yCONFIG_NET_DSA_MV88E6XXX_PTP=yCONFIG_NET_DSA_MSCC_FELIX=yCONFIG_NET_DSA_MSCC_SEVILLE=yCONFIG_NET_DSA_AR9331=yCONFIG_NET_DSA_QCA8K=yCONFIG_NET_DSA_SJA1105=yCONFIG_NET_DSA_SJA1105_PTP=yCONFIG_NET_DSA_SJA1105_TAS=yCONFIG_NET_DSA_SJA1105_VL=yCONFIG_NET_DSA_XRS700X=yCONFIG_NET_DSA_XRS700X_I2C=yCONFIG_NET_DSA_XRS700X_MDIO=yCONFIG_NET_DSA_REALTEK=yCONFIG_NET_DSA_REALTEK_MDIO=yCONFIG_NET_DSA_REALTEK_SMI=yCONFIG_NET_DSA_REALTEK_RTL8365MB=yCONFIG_NET_DSA_REALTEK_RTL8366RB=yCONFIG_NET_DSA_SMSC_LAN9303=yCONFIG_NET_DSA_SMSC_LAN9303_I2C=yCONFIG_NET_DSA_SMSC_LAN9303_MDIO=yCONFIG_NET_DSA_VITESSE_VSC73XX=yCONFIG_NET_DSA_VITESSE_VSC73XX_SPI=yCONFIG_NET_DSA_VITESSE_VSC73XX_PLATFORM=y
# end of Distributed Switch Architecture drivers
CONFIG_ETHERNET=yCONFIG_MDIO=yCONFIG_NET_VENDOR_3COM=yCONFIG_EL3=yCONFIG_3C515=yCONFIG_PCMCIA_3C574=yCONFIG_PCMCIA_3C589=yCONFIG_VORTEX=yCONFIG_TYPHOON=yCONFIG_NET_VENDOR_ACTIONS=yCONFIG_OWL_EMAC=yCONFIG_NET_VENDOR_ADAPTEC=yCONFIG_ADAPTEC_STARFIRE=yCONFIG_NET_VENDOR_AGERE=yCONFIG_ET131X=yCONFIG_NET_VENDOR_ALACRITECH=yCONFIG_SLICOSS=yCONFIG_NET_VENDOR_ALTEON=yCONFIG_ACENIC=yCONFIG_ACENIC_OMIT_TIGON_I=yCONFIG_ALTERA_TSE=yCONFIG_NET_VENDOR_AMAZON=yCONFIG_ENA_ETHERNET=yCONFIG_NET_VENDOR_AMD=yCONFIG_AMD8111_ETH=yCONFIG_LANCE=yCONFIG_PCNET32=yCONFIG_PCMCIA_NMCLAN=yCONFIG_AMD_XGBE=yCONFIG_AMD_XGBE_DCB=yCONFIG_NET_XGENE=yCONFIG_NET_XGENE_V2=yCONFIG_NET_VENDOR_AQUANTIA=yCONFIG_AQTION=yCONFIG_NET_VENDOR_ARC=yCONFIG_ARC_EMAC_CORE=yCONFIG_ARC_EMAC=yCONFIG_EMAC_ROCKCHIP=yCONFIG_NET_VENDOR_ASIX=yCONFIG_SPI_AX88796C=yCONFIG_SPI_AX88796C_COMPRESSION=yCONFIG_NET_VENDOR_ATHEROS=yCONFIG_ATL2=yCONFIG_ATL1=yCONFIG_ATL1E=yCONFIG_ATL1C=yCONFIG_ALX=yCONFIG_CX_ECAT=yCONFIG_NET_VENDOR_BROADCOM=yCONFIG_B44=yCONFIG_B44_PCI_AUTOSELECT=yCONFIG_B44_PCICORE_AUTOSELECT=yCONFIG_B44_PCI=yCONFIG_BCM4908_ENET=yCONFIG_BCMGENET=yCONFIG_BNX2=yCONFIG_CNIC=yCONFIG_TIGON3=yCONFIG_TIGON3_HWMON=yCONFIG_BNX2X=yCONFIG_BNX2X_SRIOV=yCONFIG_BGMAC=yCONFIG_BGMAC_BCMA=yCONFIG_BGMAC_PLATFORM=yCONFIG_SYSTEMPORT=yCONFIG_BNXT=yCONFIG_BNXT_SRIOV=yCONFIG_BNXT_FLOWER_OFFLOAD=yCONFIG_BNXT_DCB=yCONFIG_BNXT_HWMON=yCONFIG_NET_VENDOR_CADENCE=yCONFIG_MACB=yCONFIG_MACB_USE_HWSTAMP=yCONFIG_MACB_PCI=yCONFIG_NET_CALXEDA_XGMAC=yCONFIG_NET_VENDOR_CAVIUM=yCONFIG_THUNDER_NIC_PF=yCONFIG_THUNDER_NIC_VF=yCONFIG_THUNDER_NIC_BGX=yCONFIG_THUNDER_NIC_RGX=yCONFIG_CAVIUM_PTP=yCONFIG_LIQUIDIO=yCONFIG_LIQUIDIO_VF=yCONFIG_NET_VENDOR_CHELSIO=yCONFIG_CHELSIO_T1=yCONFIG_CHELSIO_T1_1G=yCONFIG_CHELSIO_T3=yCONFIG_CHELSIO_T4=yCONFIG_CHELSIO_T4_DCB=yCONFIG_CHELSIO_T4_FCOE=yCONFIG_CHELSIO_T4VF=yCONFIG_CHELSIO_LIB=yCONFIG_CHELSIO_INLINE_CRYPTO=yCONFIG_CRYPTO_DEV_CHELSIO_TLS=yCONFIG_CHELSIO_IPSEC_INLINE=yCONFIG_CHELSIO_TLS_DEVICE=yCONFIG_NET_VENDOR_CIRRUS=y
CONFIG_CS89x0=y
CONFIG_CS89x0_PLATFORM=yCONFIG_EP93XX_ETH=yCONFIG_NET_VENDOR_CISCO=yCONFIG_ENIC=yCONFIG_NET_VENDOR_CORTINA=yCONFIG_GEMINI_ETHERNET=yCONFIG_NET_VENDOR_DAVICOM=yCONFIG_DM9000=yCONFIG_DM9000_FORCE_SIMPLE_PHY_POLL=yCONFIG_DM9051=yCONFIG_DNET=yCONFIG_NET_VENDOR_DEC=yCONFIG_NET_TULIP=yCONFIG_DE2104X=yCONFIG_DE2104X_DSL=0CONFIG_TULIP=yCONFIG_TULIP_MWI=yCONFIG_TULIP_MMIO=yCONFIG_TULIP_NAPI=yCONFIG_TULIP_NAPI_HW_MITIGATION=yCONFIG_WINBOND_840=yCONFIG_DM9102=yCONFIG_ULI526X=yCONFIG_PCMCIA_XIRCOM=yCONFIG_NET_VENDOR_DLINK=yCONFIG_DL2K=yCONFIG_SUNDANCE=yCONFIG_SUNDANCE_MMIO=yCONFIG_NET_VENDOR_EMULEX=yCONFIG_BE2NET=yCONFIG_BE2NET_HWMON=yCONFIG_BE2NET_BE2=yCONFIG_BE2NET_BE3=yCONFIG_BE2NET_LANCER=yCONFIG_BE2NET_SKYHAWK=yCONFIG_NET_VENDOR_ENGLEDER=yCONFIG_TSNEP=yCONFIG_TSNEP_SELFTESTS=yCONFIG_NET_VENDOR_EZCHIP=yCONFIG_EZCHIP_NPS_MANAGEMENT_ENET=yCONFIG_NET_VENDOR_FARADAY=yCONFIG_NET_VENDOR_FREESCALE=yCONFIG_FEC=yCONFIG_FSL_FMAN=yCONFIG_FSL_PQ_MDIO=yCONFIG_FSL_XGMAC_MDIO=yCONFIG_GIANFAR=yCONFIG_FSL_DPAA2_SWITCH=yCONFIG_FSL_ENETC=yCONFIG_FSL_ENETC_VF=yCONFIG_FSL_ENETC_IERB=yCONFIG_FSL_ENETC_MDIO=yCONFIG_FSL_ENETC_PTP_CLOCK=yCONFIG_FSL_ENETC_QOS=yCONFIG_NET_VENDOR_FUJITSU=yCONFIG_PCMCIA_FMVJ18X=yCONFIG_NET_VENDOR_FUNGIBLE=yCONFIG_FUN_CORE=yCONFIG_FUN_ETH=yCONFIG_NET_VENDOR_GOOGLE=yCONFIG_NET_VENDOR_HISILICON=yCONFIG_HIX5HD2_GMAC=yCONFIG_HISI_FEMAC=yCONFIG_HIP04_ETH=yCONFIG_HI13X1_GMAC=yCONFIG_HNS_MDIO=yCONFIG_HNS=yCONFIG_HNS_DSAF=yCONFIG_HNS_ENET=yCONFIG_HNS3=yCONFIG_HNS3_HCLGE=yCONFIG_HNS3_DCB=yCONFIG_HNS3_HCLGEVF=yCONFIG_HNS3_ENET=yCONFIG_NET_VENDOR_HUAWEI=yCONFIG_NET_VENDOR_I825XX=yCONFIG_NET_VENDOR_INTEL=yCONFIG_E100=yCONFIG_E1000=yCONFIG_E1000E=yCONFIG_IGB=yCONFIG_IGB_HWMON=yCONFIG_IGBVF=yCONFIG_IXGB=yCONFIG_IXGBE=yCONFIG_IXGBE_HWMON=yCONFIG_IXGBE_DCB=yCONFIG_IXGBE_IPSEC=yCONFIG_IXGBEVF=yCONFIG_IXGBEVF_IPSEC=yCONFIG_I40E=yCONFIG_I40E_DCB=yCONFIG_IAVF=yCONFIG_I40EVF=yCONFIG_ICE=yCONFIG_ICE_SWITCHDEV=yCONFIG_FM10K=yCONFIG_IGC=yCONFIG_NET_VENDOR_WANGXUN=yCONFIG_TXGBE=yCONFIG_JME=yCONFIG_KORINA=yCONFIG_NET_VENDOR_LITEX=yCONFIG_LITEX_LITEETH=yCONFIG_NET_VENDOR_MARVELL=yCONFIG_MV643XX_ETH=yCONFIG_MVMDIO=yCONFIG_MVNETA=yCONFIG_MVPP2=yCONFIG_MVPP2_PTP=yCONFIG_PXA168_ETH=yCONFIG_SKGE=yCONFIG_SKGE_DEBUG=yCONFIG_SKGE_GENESIS=yCONFIG_SKY2=yCONFIG_SKY2_DEBUG=yCONFIG_OCTEONTX2_MBOX=yCONFIG_OCTEONTX2_AF=yCONFIG_NDC_DIS_DYNAMIC_CACHING=yCONFIG_OCTEONTX2_PF=yCONFIG_OCTEONTX2_VF=yCONFIG_OCTEON_EP=yCONFIG_PRESTERA=yCONFIG_PRESTERA_PCI=yCONFIG_NET_VENDOR_MEDIATEK=yCONFIG_NET_MEDIATEK_SOC_WED=yCONFIG_NET_MEDIATEK_SOC=yCONFIG_NET_MEDIATEK_STAR_EMAC=yCONFIG_NET_VENDOR_MELLANOX=yCONFIG_MLX4_EN=yCONFIG_MLX4_EN_DCB=yCONFIG_MLX4_CORE=yCONFIG_MLX4_DEBUG=yCONFIG_MLX4_CORE_GEN2=yCONFIG_MLX5_CORE=yCONFIG_MLX5_FPGA=yCONFIG_MLX5_CORE_EN=yCONFIG_MLX5_EN_ARFS=yCONFIG_MLX5_EN_RXNFC=yCONFIG_MLX5_MPFS=yCONFIG_MLX5_ESWITCH=yCONFIG_MLX5_BRIDGE=yCONFIG_MLX5_CLS_ACT=yCONFIG_MLX5_TC_CT=yCONFIG_MLX5_TC_SAMPLE=yCONFIG_MLX5_CORE_EN_DCB=yCONFIG_MLX5_CORE_IPOIB=yCONFIG_MLX5_EN_IPSEC=yCONFIG_MLX5_EN_TLS=yCONFIG_MLX5_SW_STEERING=yCONFIG_MLX5_SF=yCONFIG_MLX5_SF_MANAGER=yCONFIG_MLXSW_CORE=yCONFIG_MLXSW_CORE_HWMON=yCONFIG_MLXSW_CORE_THERMAL=yCONFIG_MLXSW_PCI=yCONFIG_MLXSW_I2C=yCONFIG_MLXSW_SPECTRUM=yCONFIG_MLXSW_SPECTRUM_DCB=yCONFIG_MLXSW_MINIMAL=yCONFIG_MLXFW=yCONFIG_MLXBF_GIGE=yCONFIG_NET_VENDOR_MICREL=yCONFIG_KS8842=yCONFIG_KS8851=yCONFIG_KS8851_MLL=yCONFIG_KSZ884X_PCI=yCONFIG_NET_VENDOR_MICROCHIP=yCONFIG_ENC28J60=yCONFIG_ENC28J60_WRITEVERIFY=yCONFIG_ENCX24J600=yCONFIG_LAN743X=yCONFIG_LAN966X_SWITCH=yCONFIG_SPARX5_SWITCH=yCONFIG_NET_VENDOR_MICROSEMI=yCONFIG_MSCC_OCELOT_SWITCH_LIB=yCONFIG_MSCC_OCELOT_SWITCH=yCONFIG_NET_VENDOR_MICROSOFT=yCONFIG_NET_VENDOR_MYRI=yCONFIG_MYRI10GE=yCONFIG_FEALNX=yCONFIG_NET_VENDOR_NI=yCONFIG_NI_XGE_MANAGEMENT_ENET=yCONFIG_NET_VENDOR_NATSEMI=yCONFIG_NATSEMI=yCONFIG_NS83820=yCONFIG_NET_VENDOR_NETERION=yCONFIG_S2IO=yCONFIG_NET_VENDOR_NETRONOME=yCONFIG_NFP=yCONFIG_NFP_APP_FLOWER=yCONFIG_NFP_APP_ABM_NIC=yCONFIG_NFP_DEBUG=yCONFIG_NET_VENDOR_8390=yCONFIG_PCMCIA_AXNET=yCONFIG_AX88796=yCONFIG_AX88796_93CX6=yCONFIG_NE2000=yCONFIG_NE2K_PCI=yCONFIG_PCMCIA_PCNET=yCONFIG_ULTRA=y
CONFIG_WD80x3=yCONFIG_NET_VENDOR_NVIDIA=yCONFIG_FORCEDETH=yCONFIG_LPC_ENET=yCONFIG_NET_VENDOR_OKI=yCONFIG_PCH_GBE=yCONFIG_ETHOC=yCONFIG_NET_VENDOR_PACKET_ENGINES=yCONFIG_HAMACHI=yCONFIG_YELLOWFIN=yCONFIG_NET_VENDOR_PENSANDO=yCONFIG_IONIC=yCONFIG_NET_VENDOR_QLOGIC=yCONFIG_QLA3XXX=yCONFIG_QLCNIC=yCONFIG_QLCNIC_SRIOV=yCONFIG_QLCNIC_DCB=yCONFIG_QLCNIC_HWMON=yCONFIG_NETXEN_NIC=yCONFIG_QED=yCONFIG_QED_LL2=yCONFIG_QED_SRIOV=yCONFIG_QEDE=yCONFIG_QED_ISCSI=yCONFIG_QED_FCOE=yCONFIG_QED_OOO=yCONFIG_NET_VENDOR_BROCADE=yCONFIG_BNA=yCONFIG_NET_VENDOR_QUALCOMM=yCONFIG_QCA7000=yCONFIG_QCA7000_SPI=yCONFIG_QCA7000_UART=yCONFIG_QCOM_EMAC=yCONFIG_RMNET=yCONFIG_NET_VENDOR_RDC=yCONFIG_R6040=yCONFIG_NET_VENDOR_REALTEK=yCONFIG_8139CP=yCONFIG_8139TOO=yCONFIG_8139TOO_PIO=yCONFIG_8139TOO_TUNE_TWISTER=yCONFIG_8139TOO_8129=yCONFIG_8139_OLD_RX_RESET=yCONFIG_R8169=yCONFIG_NET_VENDOR_RENESAS=yCONFIG_SH_ETH=yCONFIG_RAVB=yCONFIG_NET_VENDOR_ROCKER=yCONFIG_ROCKER=yCONFIG_NET_VENDOR_SAMSUNG=yCONFIG_SXGBE_ETH=yCONFIG_NET_VENDOR_SEEQ=yCONFIG_NET_VENDOR_SILAN=yCONFIG_SC92031=yCONFIG_NET_VENDOR_SIS=yCONFIG_SIS900=yCONFIG_SIS190=yCONFIG_NET_VENDOR_SOLARFLARE=yCONFIG_SFC=yCONFIG_SFC_MTD=yCONFIG_SFC_MCDI_MON=yCONFIG_SFC_SRIOV=yCONFIG_SFC_MCDI_LOGGING=yCONFIG_SFC_FALCON=yCONFIG_SFC_FALCON_MTD=yCONFIG_SFC_SIENA=yCONFIG_SFC_SIENA_MTD=yCONFIG_SFC_SIENA_MCDI_MON=yCONFIG_SFC_SIENA_SRIOV=yCONFIG_SFC_SIENA_MCDI_LOGGING=yCONFIG_NET_VENDOR_SMSC=yCONFIG_SMC9194=yCONFIG_SMC91X=yCONFIG_PCMCIA_SMC91C92=yCONFIG_EPIC100=yCONFIG_SMC911X=yCONFIG_SMSC911X=yCONFIG_SMSC9420=yCONFIG_NET_VENDOR_SOCIONEXT=yCONFIG_SNI_AVE=yCONFIG_SNI_NETSEC=yCONFIG_NET_VENDOR_STMICRO=yCONFIG_STMMAC_ETH=yCONFIG_STMMAC_SELFTESTS=yCONFIG_STMMAC_PLATFORM=yCONFIG_DWMAC_DWC_QOS_ETH=yCONFIG_DWMAC_GENERIC=yCONFIG_DWMAC_ANARION=yCONFIG_DWMAC_INGENIC=yCONFIG_DWMAC_IPQ806X=yCONFIG_DWMAC_LPC18XX=yCONFIG_DWMAC_MEDIATEK=yCONFIG_DWMAC_MESON=yCONFIG_DWMAC_OXNAS=yCONFIG_DWMAC_QCOM_ETHQOS=yCONFIG_DWMAC_ROCKCHIP=yCONFIG_DWMAC_SOCFPGA=yCONFIG_DWMAC_STI=yCONFIG_DWMAC_STM32=yCONFIG_DWMAC_SUNXI=yCONFIG_DWMAC_SUN8I=yCONFIG_DWMAC_IMX8=yCONFIG_DWMAC_INTEL_PLAT=yCONFIG_DWMAC_VISCONTI=yCONFIG_DWMAC_LOONGSON=yCONFIG_STMMAC_PCI=yCONFIG_NET_VENDOR_SUN=yCONFIG_HAPPYMEAL=yCONFIG_SUNGEM=yCONFIG_CASSINI=yCONFIG_NIU=yCONFIG_NET_VENDOR_SUNPLUS=yCONFIG_SP7021_EMAC=yCONFIG_NET_VENDOR_SYNOPSYS=yCONFIG_DWC_XLGMAC=yCONFIG_DWC_XLGMAC_PCI=yCONFIG_NET_VENDOR_TEHUTI=yCONFIG_TEHUTI=yCONFIG_NET_VENDOR_TI=yCONFIG_TI_DAVINCI_EMAC=yCONFIG_TI_DAVINCI_MDIO=yCONFIG_TI_CPSW_PHY_SEL=yCONFIG_TI_CPSW=yCONFIG_TI_CPSW_SWITCHDEV=yCONFIG_TI_CPTS=yCONFIG_TLAN=yCONFIG_NET_VENDOR_VERTEXCOM=yCONFIG_MSE102X=yCONFIG_NET_VENDOR_VIA=yCONFIG_VIA_RHINE=yCONFIG_VIA_RHINE_MMIO=yCONFIG_VIA_VELOCITY=yCONFIG_NET_VENDOR_WIZNET=yCONFIG_WIZNET_W5100=yCONFIG_WIZNET_W5300=y
# CONFIG_WIZNET_BUS_DIRECT is not set
# CONFIG_WIZNET_BUS_INDIRECT is not setCONFIG_WIZNET_BUS_ANY=yCONFIG_WIZNET_W5100_SPI=yCONFIG_NET_VENDOR_XILINX=yCONFIG_XILINX_EMACLITE=yCONFIG_XILINX_AXI_EMAC=yCONFIG_XILINX_LL_TEMAC=yCONFIG_NET_VENDOR_XIRCOM=yCONFIG_PCMCIA_XIRC2PS=yCONFIG_FDDI=yCONFIG_DEFXX=yCONFIG_SKFP=yCONFIG_HIPPI=yCONFIG_ROADRUNNER=yCONFIG_ROADRUNNER_LARGE_RINGS=yCONFIG_QCOM_IPA=yCONFIG_NET_SB1000=yCONFIG_PHYLINK=yCONFIG_PHYLIB=yCONFIG_SWPHY=yCONFIG_LED_TRIGGER_PHY=yCONFIG_FIXED_PHY=yCONFIG_SFP=y
#
# MII PHY device drivers
#CONFIG_AMD_PHY=yCONFIG_MESON_GXL_PHY=yCONFIG_ADIN_PHY=yCONFIG_ADIN1100_PHY=yCONFIG_AQUANTIA_PHY=yCONFIG_AX88796B_PHY=yCONFIG_BROADCOM_PHY=yCONFIG_BCM54140_PHY=yCONFIG_BCM63XX_PHY=yCONFIG_BCM7XXX_PHY=yCONFIG_BCM84881_PHY=yCONFIG_BCM87XX_PHY=yCONFIG_BCM_CYGNUS_PHY=yCONFIG_BCM_NET_PHYLIB=yCONFIG_BCM_NET_PHYPTP=yCONFIG_CICADA_PHY=yCONFIG_CORTINA_PHY=yCONFIG_DAVICOM_PHY=yCONFIG_ICPLUS_PHY=yCONFIG_LXT_PHY=yCONFIG_INTEL_XWAY_PHY=yCONFIG_LSI_ET1011C_PHY=yCONFIG_MARVELL_PHY=yCONFIG_MARVELL_10G_PHY=yCONFIG_MARVELL_88X2222_PHY=yCONFIG_MAXLINEAR_GPHY=yCONFIG_MEDIATEK_GE_PHY=yCONFIG_MICREL_PHY=yCONFIG_MICROCHIP_PHY=yCONFIG_MICROCHIP_T1_PHY=yCONFIG_MICROSEMI_PHY=yCONFIG_MOTORCOMM_PHY=yCONFIG_NATIONAL_PHY=yCONFIG_NXP_C45_TJA11XX_PHY=yCONFIG_NXP_TJA11XX_PHY=yCONFIG_AT803X_PHY=yCONFIG_QSEMI_PHY=yCONFIG_REALTEK_PHY=yCONFIG_RENESAS_PHY=yCONFIG_ROCKCHIP_PHY=yCONFIG_SMSC_PHY=yCONFIG_STE10XP=yCONFIG_TERANETICS_PHY=yCONFIG_DP83822_PHY=yCONFIG_DP83TC811_PHY=yCONFIG_DP83848_PHY=yCONFIG_DP83867_PHY=yCONFIG_DP83869_PHY=yCONFIG_DP83TD510_PHY=yCONFIG_VITESSE_PHY=yCONFIG_XILINX_GMII2RGMII=yCONFIG_MICREL_KS8995MA=yCONFIG_CAN_DEV=yCONFIG_CAN_VCAN=yCONFIG_CAN_VXCAN=yCONFIG_CAN_NETLINK=yCONFIG_CAN_CALC_BITTIMING=yCONFIG_CAN_RX_OFFLOAD=yCONFIG_CAN_AT91=yCONFIG_CAN_CAN327=yCONFIG_CAN_FLEXCAN=yCONFIG_CAN_GRCAN=yCONFIG_CAN_JANZ_ICAN3=yCONFIG_CAN_KVASER_PCIEFD=yCONFIG_CAN_SLCAN=yCONFIG_CAN_SUN4I=yCONFIG_CAN_XILINXCAN=yCONFIG_PCH_CAN=yCONFIG_CAN_C_CAN=yCONFIG_CAN_C_CAN_PLATFORM=yCONFIG_CAN_C_CAN_PCI=yCONFIG_CAN_CC770=yCONFIG_CAN_CC770_ISA=yCONFIG_CAN_CC770_PLATFORM=yCONFIG_CAN_CTUCANFD=yCONFIG_CAN_CTUCANFD_PCI=yCONFIG_CAN_CTUCANFD_PLATFORM=yCONFIG_CAN_IFI_CANFD=yCONFIG_CAN_M_CAN=yCONFIG_CAN_M_CAN_PCI=yCONFIG_CAN_M_CAN_PLATFORM=yCONFIG_CAN_M_CAN_TCAN4X5X=yCONFIG_CAN_PEAK_PCIEFD=yCONFIG_CAN_RCAR=yCONFIG_CAN_RCAR_CANFD=yCONFIG_CAN_SJA1000=yCONFIG_CAN_EMS_PCI=yCONFIG_CAN_EMS_PCMCIA=yCONFIG_CAN_F81601=yCONFIG_CAN_KVASER_PCI=yCONFIG_CAN_PEAK_PCI=yCONFIG_CAN_PEAK_PCIEC=yCONFIG_CAN_PEAK_PCMCIA=yCONFIG_CAN_PLX_PCI=yCONFIG_CAN_SJA1000_ISA=yCONFIG_CAN_SJA1000_PLATFORM=yCONFIG_CAN_TSCAN1=yCONFIG_CAN_SOFTING=yCONFIG_CAN_SOFTING_CS=y
#
# CAN SPI interfaces
#CONFIG_CAN_HI311X=yCONFIG_CAN_MCP251X=yCONFIG_CAN_MCP251XFD=yCONFIG_CAN_MCP251XFD_SANITY=y
# end of CAN SPI interfaces
#
# CAN USB interfaces
#CONFIG_CAN_8DEV_USB=yCONFIG_CAN_EMS_USB=yCONFIG_CAN_ESD_USB=yCONFIG_CAN_ETAS_ES58X=yCONFIG_CAN_GS_USB=yCONFIG_CAN_KVASER_USB=yCONFIG_CAN_MCBA_USB=yCONFIG_CAN_PEAK_USB=yCONFIG_CAN_UCAN=y
# end of CAN USB interfaces
CONFIG_CAN_DEBUG_DEVICES=y
#
# MCTP Device Drivers
#CONFIG_MCTP_SERIAL=yCONFIG_MCTP_TRANSPORT_I2C=y
# end of MCTP Device Drivers
CONFIG_MDIO_DEVICE=yCONFIG_MDIO_BUS=yCONFIG_FWNODE_MDIO=yCONFIG_OF_MDIO=yCONFIG_MDIO_DEVRES=yCONFIG_MDIO_SUN4I=yCONFIG_MDIO_XGENE=yCONFIG_MDIO_ASPEED=yCONFIG_MDIO_BITBANG=yCONFIG_MDIO_BCM_IPROC=yCONFIG_MDIO_BCM_UNIMAC=yCONFIG_MDIO_CAVIUM=yCONFIG_MDIO_GPIO=yCONFIG_MDIO_HISI_FEMAC=yCONFIG_MDIO_I2C=yCONFIG_MDIO_MVUSB=yCONFIG_MDIO_MSCC_MIIM=yCONFIG_MDIO_MOXART=yCONFIG_MDIO_OCTEON=yCONFIG_MDIO_IPQ4019=yCONFIG_MDIO_IPQ8064=yCONFIG_MDIO_THUNDER=y
#
# MDIO Multiplexers
#CONFIG_MDIO_BUS_MUX=yCONFIG_MDIO_BUS_MUX_MESON_G12A=yCONFIG_MDIO_BUS_MUX_BCM6368=yCONFIG_MDIO_BUS_MUX_BCM_IPROC=yCONFIG_MDIO_BUS_MUX_GPIO=yCONFIG_MDIO_BUS_MUX_MULTIPLEXER=yCONFIG_MDIO_BUS_MUX_MMIOREG=y
#
# PCS device drivers
#CONFIG_PCS_XPCS=yCONFIG_PCS_LYNX=yCONFIG_PCS_RZN1_MIIC=y
# end of PCS device drivers
CONFIG_PLIP=yCONFIG_PPP=yCONFIG_PPP_BSDCOMP=yCONFIG_PPP_DEFLATE=yCONFIG_PPP_FILTER=yCONFIG_PPP_MPPE=yCONFIG_PPP_MULTILINK=yCONFIG_PPPOATM=yCONFIG_PPPOE=yCONFIG_PPTP=yCONFIG_PPPOL2TP=yCONFIG_PPP_ASYNC=yCONFIG_PPP_SYNC_TTY=yCONFIG_SLIP=yCONFIG_SLHC=yCONFIG_SLIP_COMPRESSED=yCONFIG_SLIP_SMART=yCONFIG_SLIP_MODE_SLIP6=yCONFIG_USB_NET_DRIVERS=yCONFIG_USB_CATC=yCONFIG_USB_KAWETH=yCONFIG_USB_PEGASUS=yCONFIG_USB_RTL8150=yCONFIG_USB_RTL8152=yCONFIG_USB_LAN78XX=yCONFIG_USB_USBNET=yCONFIG_USB_NET_AX8817X=yCONFIG_USB_NET_AX88179_178A=yCONFIG_USB_NET_CDCETHER=yCONFIG_USB_NET_CDC_EEM=yCONFIG_USB_NET_CDC_NCM=yCONFIG_USB_NET_HUAWEI_CDC_NCM=yCONFIG_USB_NET_CDC_MBIM=yCONFIG_USB_NET_DM9601=yCONFIG_USB_NET_SR9700=yCONFIG_USB_NET_SR9800=yCONFIG_USB_NET_SMSC75XX=yCONFIG_USB_NET_SMSC95XX=yCONFIG_USB_NET_GL620A=yCONFIG_USB_NET_NET1080=yCONFIG_USB_NET_PLUSB=yCONFIG_USB_NET_MCS7830=yCONFIG_USB_NET_RNDIS_HOST=yCONFIG_USB_NET_CDC_SUBSET_ENABLE=yCONFIG_USB_NET_CDC_SUBSET=yCONFIG_USB_ALI_M5632=yCONFIG_USB_AN2720=yCONFIG_USB_BELKIN=yCONFIG_USB_ARMLINUX=yCONFIG_USB_EPSON2888=yCONFIG_USB_KC2190=yCONFIG_USB_NET_ZAURUS=yCONFIG_USB_NET_CX82310_ETH=yCONFIG_USB_NET_KALMIA=yCONFIG_USB_NET_QMI_WWAN=yCONFIG_USB_HSO=yCONFIG_USB_NET_INT51X1=yCONFIG_USB_CDC_PHONET=yCONFIG_USB_IPHETH=yCONFIG_USB_SIERRA_NET=yCONFIG_USB_VL600=yCONFIG_USB_NET_CH9200=yCONFIG_USB_NET_AQC111=yCONFIG_USB_RTL8153_ECM=yCONFIG_WLAN=yCONFIG_WLAN_VENDOR_ADMTEK=yCONFIG_ADM8211=yCONFIG_ATH_COMMON=yCONFIG_WLAN_VENDOR_ATH=yCONFIG_ATH_DEBUG=yCONFIG_ATH_REG_DYNAMIC_USER_REG_HINTS=yCONFIG_ATH_REG_DYNAMIC_USER_CERT_TESTING=yCONFIG_ATH5K=yCONFIG_ATH5K_DEBUG=yCONFIG_ATH5K_PCI=yCONFIG_ATH5K_TEST_CHANNELS=yCONFIG_ATH9K_HW=yCONFIG_ATH9K_COMMON=yCONFIG_ATH9K_COMMON_DEBUG=yCONFIG_ATH9K_DFS_DEBUGFS=yCONFIG_ATH9K_BTCOEX_SUPPORT=yCONFIG_ATH9K=yCONFIG_ATH9K_PCI=yCONFIG_ATH9K_AHB=yCONFIG_ATH9K_DEBUGFS=yCONFIG_ATH9K_STATION_STATISTICS=yCONFIG_ATH9K_TX99=yCONFIG_ATH9K_DFS_CERTIFIED=yCONFIG_ATH9K_DYNACK=yCONFIG_ATH9K_RFKILL=yCONFIG_ATH9K_CHANNEL_CONTEXT=yCONFIG_ATH9K_PCOEM=yCONFIG_ATH9K_PCI_NO_EEPROM=yCONFIG_ATH9K_HTC=yCONFIG_ATH9K_HTC_DEBUGFS=yCONFIG_ATH9K_HWRNG=yCONFIG_ATH9K_COMMON_SPECTRAL=yCONFIG_CARL9170=yCONFIG_CARL9170_LEDS=yCONFIG_CARL9170_DEBUGFS=yCONFIG_CARL9170_WPC=yCONFIG_CARL9170_HWRNG=yCONFIG_ATH6KL=yCONFIG_ATH6KL_SDIO=yCONFIG_ATH6KL_USB=yCONFIG_ATH6KL_DEBUG=yCONFIG_ATH6KL_REGDOMAIN=yCONFIG_AR5523=yCONFIG_WIL6210=yCONFIG_WIL6210_ISR_COR=yCONFIG_WIL6210_DEBUGFS=yCONFIG_ATH10K=yCONFIG_ATH10K_CE=yCONFIG_ATH10K_PCI=yCONFIG_ATH10K_AHB=yCONFIG_ATH10K_SDIO=yCONFIG_ATH10K_USB=yCONFIG_ATH10K_SNOC=yCONFIG_ATH10K_DEBUG=yCONFIG_ATH10K_DEBUGFS=yCONFIG_ATH10K_SPECTRAL=yCONFIG_ATH10K_DFS_CERTIFIED=yCONFIG_WCN36XX=yCONFIG_WCN36XX_DEBUGFS=yCONFIG_ATH11K=yCONFIG_ATH11K_AHB=yCONFIG_ATH11K_PCI=yCONFIG_ATH11K_DEBUG=yCONFIG_ATH11K_DEBUGFS=yCONFIG_ATH11K_SPECTRAL=yCONFIG_WLAN_VENDOR_ATMEL=yCONFIG_ATMEL=yCONFIG_PCI_ATMEL=yCONFIG_PCMCIA_ATMEL=yCONFIG_AT76C50X_USB=yCONFIG_WLAN_VENDOR_BROADCOM=yCONFIG_B43=yCONFIG_B43_BCMA=yCONFIG_B43_SSB=yCONFIG_B43_BUSES_BCMA_AND_SSB=y
# CONFIG_B43_BUSES_BCMA is not set
# CONFIG_B43_BUSES_SSB is not setCONFIG_B43_PCI_AUTOSELECT=yCONFIG_B43_PCICORE_AUTOSELECT=yCONFIG_B43_SDIO=yCONFIG_B43_BCMA_PIO=yCONFIG_B43_PIO=yCONFIG_B43_PHY_G=yCONFIG_B43_PHY_N=yCONFIG_B43_PHY_LP=yCONFIG_B43_PHY_HT=yCONFIG_B43_LEDS=yCONFIG_B43_HWRNG=yCONFIG_B43_DEBUG=yCONFIG_B43LEGACY=yCONFIG_B43LEGACY_PCI_AUTOSELECT=yCONFIG_B43LEGACY_PCICORE_AUTOSELECT=yCONFIG_B43LEGACY_LEDS=yCONFIG_B43LEGACY_HWRNG=yCONFIG_B43LEGACY_DEBUG=yCONFIG_B43LEGACY_DMA=yCONFIG_B43LEGACY_PIO=yCONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
# CONFIG_B43LEGACY_DMA_MODE is not set
# CONFIG_B43LEGACY_PIO_MODE is not setCONFIG_BRCMUTIL=yCONFIG_BRCMSMAC=yCONFIG_BRCMSMAC_LEDS=yCONFIG_BRCMFMAC=yCONFIG_BRCMFMAC_PROTO_BCDC=yCONFIG_BRCMFMAC_PROTO_MSGBUF=yCONFIG_BRCMFMAC_SDIO=yCONFIG_BRCMFMAC_USB=yCONFIG_BRCMFMAC_PCIE=yCONFIG_BRCM_TRACING=yCONFIG_BRCMDBG=yCONFIG_WLAN_VENDOR_CISCO=yCONFIG_AIRO=yCONFIG_AIRO_CS=yCONFIG_WLAN_VENDOR_INTEL=yCONFIG_IPW2100=yCONFIG_IPW2100_MONITOR=yCONFIG_IPW2100_DEBUG=yCONFIG_IPW2200=yCONFIG_IPW2200_MONITOR=yCONFIG_IPW2200_RADIOTAP=yCONFIG_IPW2200_PROMISCUOUS=yCONFIG_IPW2200_QOS=yCONFIG_IPW2200_DEBUG=yCONFIG_LIBIPW=yCONFIG_LIBIPW_DEBUG=yCONFIG_IWLEGACY=yCONFIG_IWL4965=yCONFIG_IWL3945=y
#
# iwl3945 / iwl4965 Debugging Options # CONFIG_IWLEGACY_DEBUG=y CONFIG_IWLEGACY_DEBUGFS=y # end of iwl3945 / iwl4965 Debugging Options
CONFIG_IWLWIFI=yCONFIG_IWLWIFI_LEDS=yCONFIG_IWLDVM=yCONFIG_IWLMVM=y
#
# Debugging Options
#CONFIG_IWLWIFI_DEBUG=yCONFIG_IWLWIFI_DEBUGFS=y
# end of Debugging Options
CONFIG_WLAN_VENDOR_INTERSIL=yCONFIG_HOSTAP=yCONFIG_HOSTAP_FIRMWARE=yCONFIG_HOSTAP_FIRMWARE_NVRAM=yCONFIG_HOSTAP_PLX=yCONFIG_HOSTAP_PCI=yCONFIG_HOSTAP_CS=yCONFIG_HERMES=yCONFIG_HERMES_PRISM=yCONFIG_HERMES_CACHE_FW_ON_INIT=yCONFIG_PLX_HERMES=yCONFIG_TMD_HERMES=yCONFIG_NORTEL_HERMES=yCONFIG_PCI_HERMES=yCONFIG_PCMCIA_HERMES=yCONFIG_PCMCIA_SPECTRUM=yCONFIG_ORINOCO_USB=yCONFIG_P54_COMMON=yCONFIG_P54_USB=yCONFIG_P54_PCI=yCONFIG_P54_SPI=yCONFIG_P54_SPI_DEFAULT_EEPROM=yCONFIG_P54_LEDS=yCONFIG_WLAN_VENDOR_MARVELL=yCONFIG_LIBERTAS=yCONFIG_LIBERTAS_USB=yCONFIG_LIBERTAS_CS=yCONFIG_LIBERTAS_SDIO=yCONFIG_LIBERTAS_SPI=yCONFIG_LIBERTAS_DEBUG=yCONFIG_LIBERTAS_MESH=yCONFIG_LIBERTAS_THINFIRM=yCONFIG_LIBERTAS_THINFIRM_DEBUG=yCONFIG_LIBERTAS_THINFIRM_USB=yCONFIG_MWIFIEX=yCONFIG_MWIFIEX_SDIO=yCONFIG_MWIFIEX_PCIE=yCONFIG_MWIFIEX_USB=yCONFIG_MWL8K=yCONFIG_WLAN_VENDOR_MEDIATEK=yCONFIG_MT7601U=yCONFIG_MT76_CORE=yCONFIG_MT76_LEDS=yCONFIG_MT76_USB=yCONFIG_MT76_SDIO=y
CONFIG_MT76x02_LIB=y
CONFIG_MT76x02_USB=yCONFIG_MT76_CONNAC_LIB=y
CONFIG_MT76x0_COMMON=y
CONFIG_MT76x0U=y
CONFIG_MT76x0E=y
CONFIG_MT76x2_COMMON=y
CONFIG_MT76x2E=y
CONFIG_MT76x2U=yCONFIG_MT7603E=yCONFIG_MT7615_COMMON=yCONFIG_MT7615E=yCONFIG_MT7622_WMAC=yCONFIG_MT7663_USB_SDIO_COMMON=yCONFIG_MT7663U=yCONFIG_MT7663S=yCONFIG_MT7915E=yCONFIG_MT7986_WMAC=yCONFIG_MT7921_COMMON=yCONFIG_MT7921E=yCONFIG_MT7921S=yCONFIG_MT7921U=yCONFIG_WLAN_VENDOR_MICROCHIP=yCONFIG_WILC1000=yCONFIG_WILC1000_SDIO=yCONFIG_WILC1000_SPI=yCONFIG_WILC1000_HW_OOB_INTR=yCONFIG_WLAN_VENDOR_PURELIFI=yCONFIG_PLFXLC=yCONFIG_WLAN_VENDOR_RALINK=yCONFIG_RT2X00=yCONFIG_RT2400PCI=yCONFIG_RT2500PCI=yCONFIG_RT61PCI=yCONFIG_RT2800PCI=yCONFIG_RT2800PCI_RT33XX=yCONFIG_RT2800PCI_RT35XX=yCONFIG_RT2800PCI_RT53XX=yCONFIG_RT2800PCI_RT3290=yCONFIG_RT2500USB=yCONFIG_RT73USB=yCONFIG_RT2800USB=yCONFIG_RT2800USB_RT33XX=yCONFIG_RT2800USB_RT35XX=yCONFIG_RT2800USB_RT3573=yCONFIG_RT2800USB_RT53XX=yCONFIG_RT2800USB_RT55XX=yCONFIG_RT2800USB_UNKNOWN=yCONFIG_RT2800_LIB=yCONFIG_RT2800_LIB_MMIO=yCONFIG_RT2X00_LIB_MMIO=yCONFIG_RT2X00_LIB_PCI=yCONFIG_RT2X00_LIB_USB=yCONFIG_RT2X00_LIB=yCONFIG_RT2X00_LIB_FIRMWARE=yCONFIG_RT2X00_LIB_CRYPTO=yCONFIG_RT2X00_LIB_LEDS=yCONFIG_RT2X00_LIB_DEBUGFS=yCONFIG_RT2X00_DEBUG=yCONFIG_WLAN_VENDOR_REALTEK=yCONFIG_RTL8180=yCONFIG_RTL8187=yCONFIG_RTL8187_LEDS=yCONFIG_RTL_CARDS=yCONFIG_RTL8192CE=yCONFIG_RTL8192SE=yCONFIG_RTL8192DE=yCONFIG_RTL8723AE=yCONFIG_RTL8723BE=yCONFIG_RTL8188EE=yCONFIG_RTL8192EE=yCONFIG_RTL8821AE=yCONFIG_RTL8192CU=yCONFIG_RTLWIFI=yCONFIG_RTLWIFI_PCI=yCONFIG_RTLWIFI_USB=yCONFIG_RTLWIFI_DEBUG=yCONFIG_RTL8192C_COMMON=yCONFIG_RTL8723_COMMON=yCONFIG_RTLBTCOEXIST=yCONFIG_RTL8XXXU=yCONFIG_RTL8XXXU_UNTESTED=yCONFIG_RTW88=yCONFIG_RTW88_CORE=yCONFIG_RTW88_PCI=yCONFIG_RTW88_8822B=yCONFIG_RTW88_8822C=yCONFIG_RTW88_8723D=yCONFIG_RTW88_8821C=yCONFIG_RTW88_8822BE=yCONFIG_RTW88_8822CE=yCONFIG_RTW88_8723DE=yCONFIG_RTW88_8821CE=yCONFIG_RTW88_DEBUG=yCONFIG_RTW88_DEBUGFS=yCONFIG_RTW89=yCONFIG_RTW89_CORE=yCONFIG_RTW89_PCI=yCONFIG_RTW89_8852A=yCONFIG_RTW89_8852C=yCONFIG_RTW89_8852AE=yCONFIG_RTW89_8852CE=yCONFIG_RTW89_DEBUG=yCONFIG_RTW89_DEBUGMSG=yCONFIG_RTW89_DEBUGFS=yCONFIG_WLAN_VENDOR_RSI=yCONFIG_RSI_91X=yCONFIG_RSI_DEBUGFS=yCONFIG_RSI_SDIO=yCONFIG_RSI_USB=yCONFIG_RSI_COEX=yCONFIG_WLAN_VENDOR_SILABS=yCONFIG_WFX=yCONFIG_WLAN_VENDOR_ST=yCONFIG_CW1200=yCONFIG_CW1200_WLAN_SDIO=yCONFIG_CW1200_WLAN_SPI=yCONFIG_WLAN_VENDOR_TI=yCONFIG_WL1251=yCONFIG_WL1251_SPI=yCONFIG_WL1251_SDIO=yCONFIG_WL12XX=yCONFIG_WL18XX=yCONFIG_WLCORE=yCONFIG_WLCORE_SPI=yCONFIG_WLCORE_SDIO=yCONFIG_WILINK_PLATFORM_DATA=yCONFIG_WLAN_VENDOR_ZYDAS=yCONFIG_USB_ZD1201=yCONFIG_ZD1211RW=yCONFIG_ZD1211RW_DEBUG=yCONFIG_WLAN_VENDOR_QUANTENNA=yCONFIG_QTNFMAC=yCONFIG_QTNFMAC_PCIE=yCONFIG_PCMCIA_RAYCS=yCONFIG_PCMCIA_WL3501=yCONFIG_MAC80211_HWSIM=yCONFIG_USB_NET_RNDIS_WLAN=yCONFIG_VIRT_WIFI=yCONFIG_WAN=yCONFIG_HDLC=yCONFIG_HDLC_RAW=yCONFIG_HDLC_RAW_ETH=yCONFIG_HDLC_CISCO=yCONFIG_HDLC_FR=yCONFIG_HDLC_PPP=yCONFIG_HDLC_X25=yCONFIG_PCI200SYN=yCONFIG_WANXL=yCONFIG_PC300TOO=yCONFIG_N2=yCONFIG_C101=yCONFIG_FARSYNC=yCONFIG_FSL_UCC_HDLC=yCONFIG_SLIC_DS26522=yCONFIG_LAPBETHER=yCONFIG_IEEE802154_DRIVERS=yCONFIG_IEEE802154_FAKELB=yCONFIG_IEEE802154_AT86RF230=yCONFIG_IEEE802154_MRF24J40=yCONFIG_IEEE802154_CC2520=yCONFIG_IEEE802154_ATUSB=yCONFIG_IEEE802154_ADF7242=yCONFIG_IEEE802154_CA8210=yCONFIG_IEEE802154_CA8210_DEBUGFS=yCONFIG_IEEE802154_MCR20A=yCONFIG_IEEE802154_HWSIM=y
#
# Wireless WAN
#CONFIG_WWAN=yCONFIG_WWAN_DEBUGFS=yCONFIG_WWAN_HWSIM=yCONFIG_MHI_WWAN_CTRL=yCONFIG_MHI_WWAN_MBIM=yCONFIG_QCOM_BAM_DMUX=yCONFIG_RPMSG_WWAN_CTRL=yCONFIG_MTK_T7XX=y
# end of Wireless WAN
CONFIG_VMXNET3=yCONFIG_USB4_NET=yCONFIG_NETDEVSIM=yCONFIG_NET_FAILOVER=yCONFIG_NETDEV_LEGACY_INIT=yCONFIG_ISDN=yCONFIG_ISDN_CAPI=yCONFIG_CAPI_TRACE=yCONFIG_ISDN_CAPI_MIDDLEWARE=yCONFIG_MISDN=yCONFIG_MISDN_DSP=yCONFIG_MISDN_L1OIP=y
#
# mISDN hardware drivers
#CONFIG_MISDN_HFCPCI=yCONFIG_MISDN_HFCMULTI=yCONFIG_MISDN_HFCUSB=yCONFIG_MISDN_AVMFRITZ=yCONFIG_MISDN_SPEEDFAX=yCONFIG_MISDN_INFINEON=yCONFIG_MISDN_W6692=yCONFIG_MISDN_NETJET=yCONFIG_MISDN_HDLC=yCONFIG_MISDN_IPAC=yCONFIG_MISDN_ISAR=y
#
# Input device support
#CONFIG_INPUT=yCONFIG_INPUT_LEDS=yCONFIG_INPUT_FF_MEMLESS=yCONFIG_INPUT_SPARSEKMAP=yCONFIG_INPUT_MATRIXKMAP=yCONFIG_INPUT_VIVALDIFMAP=y
#
# Userland interfaces
#CONFIG_INPUT_MOUSEDEV=yCONFIG_INPUT_MOUSEDEV_PSAUX=yCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768CONFIG_INPUT_JOYDEV=yCONFIG_INPUT_EVDEV=yCONFIG_INPUT_EVBUG=y
#
# Input Device Drivers
#CONFIG_INPUT_KEYBOARD=yCONFIG_KEYBOARD_ADC=yCONFIG_KEYBOARD_ADP5520=yCONFIG_KEYBOARD_ADP5588=yCONFIG_KEYBOARD_ADP5589=yCONFIG_KEYBOARD_ATKBD=yCONFIG_KEYBOARD_QT1050=yCONFIG_KEYBOARD_QT1070=yCONFIG_KEYBOARD_QT2160=yCONFIG_KEYBOARD_CLPS711X=yCONFIG_KEYBOARD_DLINK_DIR685=yCONFIG_KEYBOARD_LKKBD=yCONFIG_KEYBOARD_EP93XX=yCONFIG_KEYBOARD_GPIO=yCONFIG_KEYBOARD_GPIO_POLLED=yCONFIG_KEYBOARD_TCA6416=yCONFIG_KEYBOARD_TCA8418=yCONFIG_KEYBOARD_MATRIX=yCONFIG_KEYBOARD_LM8323=yCONFIG_KEYBOARD_LM8333=yCONFIG_KEYBOARD_MAX7359=yCONFIG_KEYBOARD_MCS=yCONFIG_KEYBOARD_MPR121=yCONFIG_KEYBOARD_SNVS_PWRKEY=yCONFIG_KEYBOARD_IMX=yCONFIG_KEYBOARD_IMX_SC_KEY=yCONFIG_KEYBOARD_NEWTON=yCONFIG_KEYBOARD_OPENCORES=yCONFIG_KEYBOARD_PMIC8XXX=yCONFIG_KEYBOARD_SAMSUNG=yCONFIG_KEYBOARD_GOLDFISH_EVENTS=yCONFIG_KEYBOARD_STOWAWAY=yCONFIG_KEYBOARD_ST_KEYSCAN=yCONFIG_KEYBOARD_SUNKBD=yCONFIG_KEYBOARD_SH_KEYSC=yCONFIG_KEYBOARD_STMPE=yCONFIG_KEYBOARD_IQS62X=yCONFIG_KEYBOARD_OMAP4=yCONFIG_KEYBOARD_TC3589X=yCONFIG_KEYBOARD_TM2_TOUCHKEY=yCONFIG_KEYBOARD_TWL4030=yCONFIG_KEYBOARD_XTKBD=yCONFIG_KEYBOARD_CROS_EC=yCONFIG_KEYBOARD_CAP11XX=yCONFIG_KEYBOARD_BCM=yCONFIG_KEYBOARD_MT6779=yCONFIG_KEYBOARD_MTK_PMIC=yCONFIG_KEYBOARD_CYPRESS_SF=yCONFIG_INPUT_MOUSE=yCONFIG_MOUSE_PS2=yCONFIG_MOUSE_PS2_ALPS=yCONFIG_MOUSE_PS2_BYD=yCONFIG_MOUSE_PS2_LOGIPS2PP=yCONFIG_MOUSE_PS2_SYNAPTICS=yCONFIG_MOUSE_PS2_SYNAPTICS_SMBUS=yCONFIG_MOUSE_PS2_CYPRESS=yCONFIG_MOUSE_PS2_TRACKPOINT=yCONFIG_MOUSE_PS2_ELANTECH=yCONFIG_MOUSE_PS2_ELANTECH_SMBUS=yCONFIG_MOUSE_PS2_SENTELIC=yCONFIG_MOUSE_PS2_TOUCHKIT=yCONFIG_MOUSE_PS2_FOCALTECH=yCONFIG_MOUSE_PS2_SMBUS=yCONFIG_MOUSE_SERIAL=yCONFIG_MOUSE_APPLETOUCH=yCONFIG_MOUSE_BCM5974=yCONFIG_MOUSE_CYAPA=yCONFIG_MOUSE_ELAN_I2C=yCONFIG_MOUSE_ELAN_I2C_I2C=yCONFIG_MOUSE_ELAN_I2C_SMBUS=yCONFIG_MOUSE_INPORT=yCONFIG_MOUSE_ATIXL=yCONFIG_MOUSE_LOGIBM=yCONFIG_MOUSE_PC110PAD=yCONFIG_MOUSE_VSXXXAA=yCONFIG_MOUSE_GPIO=yCONFIG_MOUSE_SYNAPTICS_I2C=yCONFIG_MOUSE_SYNAPTICS_USB=yCONFIG_INPUT_JOYSTICK=yCONFIG_JOYSTICK_ANALOG=yCONFIG_JOYSTICK_A3D=yCONFIG_JOYSTICK_ADC=yCONFIG_JOYSTICK_ADI=yCONFIG_JOYSTICK_COBRA=yCONFIG_JOYSTICK_GF2K=yCONFIG_JOYSTICK_GRIP=yCONFIG_JOYSTICK_GRIP_MP=yCONFIG_JOYSTICK_GUILLEMOT=yCONFIG_JOYSTICK_INTERACT=yCONFIG_JOYSTICK_SIDEWINDER=yCONFIG_JOYSTICK_TMDC=yCONFIG_JOYSTICK_IFORCE=yCONFIG_JOYSTICK_IFORCE_USB=yCONFIG_JOYSTICK_IFORCE_232=yCONFIG_JOYSTICK_WARRIOR=yCONFIG_JOYSTICK_MAGELLAN=yCONFIG_JOYSTICK_SPACEORB=yCONFIG_JOYSTICK_SPACEBALL=yCONFIG_JOYSTICK_STINGER=yCONFIG_JOYSTICK_TWIDJOY=yCONFIG_JOYSTICK_ZHENHUA=yCONFIG_JOYSTICK_DB9=yCONFIG_JOYSTICK_GAMECON=yCONFIG_JOYSTICK_TURBOGRAFX=yCONFIG_JOYSTICK_AS5011=yCONFIG_JOYSTICK_JOYDUMP=yCONFIG_JOYSTICK_XPAD=yCONFIG_JOYSTICK_XPAD_FF=yCONFIG_JOYSTICK_XPAD_LEDS=yCONFIG_JOYSTICK_WALKERA0701=yCONFIG_JOYSTICK_PSXPAD_SPI=yCONFIG_JOYSTICK_PSXPAD_SPI_FF=yCONFIG_JOYSTICK_PXRC=yCONFIG_JOYSTICK_QWIIC=yCONFIG_JOYSTICK_FSIA6B=yCONFIG_JOYSTICK_SENSEHAT=yCONFIG_INPUT_TABLET=yCONFIG_TABLET_USB_ACECAD=yCONFIG_TABLET_USB_AIPTEK=yCONFIG_TABLET_USB_HANWANG=yCONFIG_TABLET_USB_KBTAB=yCONFIG_TABLET_USB_PEGASUS=yCONFIG_TABLET_SERIAL_WACOM4=yCONFIG_INPUT_TOUCHSCREEN=yCONFIG_TOUCHSCREEN_88PM860X=yCONFIG_TOUCHSCREEN_ADS7846=yCONFIG_TOUCHSCREEN_AD7877=yCONFIG_TOUCHSCREEN_AD7879=yCONFIG_TOUCHSCREEN_AD7879_I2C=yCONFIG_TOUCHSCREEN_AD7879_SPI=yCONFIG_TOUCHSCREEN_ADC=yCONFIG_TOUCHSCREEN_AR1021_I2C=yCONFIG_TOUCHSCREEN_ATMEL_MXT=yCONFIG_TOUCHSCREEN_ATMEL_MXT_T37=yCONFIG_TOUCHSCREEN_AUO_PIXCIR=yCONFIG_TOUCHSCREEN_BU21013=yCONFIG_TOUCHSCREEN_BU21029=yCONFIG_TOUCHSCREEN_CHIPONE_ICN8318=yCONFIG_TOUCHSCREEN_CY8CTMA140=yCONFIG_TOUCHSCREEN_CY8CTMG110=yCONFIG_TOUCHSCREEN_CYTTSP_CORE=yCONFIG_TOUCHSCREEN_CYTTSP_I2C=yCONFIG_TOUCHSCREEN_CYTTSP_SPI=yCONFIG_TOUCHSCREEN_CYTTSP4_CORE=yCONFIG_TOUCHSCREEN_CYTTSP4_I2C=yCONFIG_TOUCHSCREEN_CYTTSP4_SPI=yCONFIG_TOUCHSCREEN_DA9034=yCONFIG_TOUCHSCREEN_DA9052=yCONFIG_TOUCHSCREEN_DYNAPRO=yCONFIG_TOUCHSCREEN_HAMPSHIRE=yCONFIG_TOUCHSCREEN_EETI=yCONFIG_TOUCHSCREEN_EGALAX=yCONFIG_TOUCHSCREEN_EGALAX_SERIAL=yCONFIG_TOUCHSCREEN_EXC3000=yCONFIG_TOUCHSCREEN_FUJITSU=yCONFIG_TOUCHSCREEN_GOODIX=yCONFIG_TOUCHSCREEN_HIDEEP=yCONFIG_TOUCHSCREEN_HYCON_HY46XX=yCONFIG_TOUCHSCREEN_ILI210X=yCONFIG_TOUCHSCREEN_ILITEK=yCONFIG_TOUCHSCREEN_IPROC=yCONFIG_TOUCHSCREEN_S6SY761=yCONFIG_TOUCHSCREEN_GUNZE=yCONFIG_TOUCHSCREEN_EKTF2127=yCONFIG_TOUCHSCREEN_ELAN=yCONFIG_TOUCHSCREEN_ELO=yCONFIG_TOUCHSCREEN_WACOM_W8001=yCONFIG_TOUCHSCREEN_WACOM_I2C=yCONFIG_TOUCHSCREEN_MAX11801=yCONFIG_TOUCHSCREEN_MCS5000=yCONFIG_TOUCHSCREEN_MMS114=yCONFIG_TOUCHSCREEN_MELFAS_MIP4=yCONFIG_TOUCHSCREEN_MSG2638=yCONFIG_TOUCHSCREEN_MTOUCH=yCONFIG_TOUCHSCREEN_IMAGIS=yCONFIG_TOUCHSCREEN_IMX6UL_TSC=yCONFIG_TOUCHSCREEN_INEXIO=yCONFIG_TOUCHSCREEN_MK712=yCONFIG_TOUCHSCREEN_HTCPEN=yCONFIG_TOUCHSCREEN_PENMOUNT=yCONFIG_TOUCHSCREEN_EDT_FT5X06=yCONFIG_TOUCHSCREEN_RASPBERRYPI_FW=yCONFIG_TOUCHSCREEN_MIGOR=yCONFIG_TOUCHSCREEN_TOUCHRIGHT=yCONFIG_TOUCHSCREEN_TOUCHWIN=yCONFIG_TOUCHSCREEN_TI_AM335X_TSC=yCONFIG_TOUCHSCREEN_UCB1400=yCONFIG_TOUCHSCREEN_PIXCIR=yCONFIG_TOUCHSCREEN_WDT87XX_I2C=yCONFIG_TOUCHSCREEN_WM831X=yCONFIG_TOUCHSCREEN_WM97XX=yCONFIG_TOUCHSCREEN_WM9705=yCONFIG_TOUCHSCREEN_WM9712=yCONFIG_TOUCHSCREEN_WM9713=yCONFIG_TOUCHSCREEN_USB_COMPOSITE=yCONFIG_TOUCHSCREEN_MXS_LRADC=yCONFIG_TOUCHSCREEN_MX25=yCONFIG_TOUCHSCREEN_MC13783=yCONFIG_TOUCHSCREEN_USB_EGALAX=yCONFIG_TOUCHSCREEN_USB_PANJIT=yCONFIG_TOUCHSCREEN_USB_3M=yCONFIG_TOUCHSCREEN_USB_ITM=yCONFIG_TOUCHSCREEN_USB_ETURBO=yCONFIG_TOUCHSCREEN_USB_GUNZE=yCONFIG_TOUCHSCREEN_USB_DMC_TSC10=yCONFIG_TOUCHSCREEN_USB_IRTOUCH=yCONFIG_TOUCHSCREEN_USB_IDEALTEK=yCONFIG_TOUCHSCREEN_USB_GENERAL_TOUCH=yCONFIG_TOUCHSCREEN_USB_GOTOP=yCONFIG_TOUCHSCREEN_USB_JASTEC=yCONFIG_TOUCHSCREEN_USB_ELO=yCONFIG_TOUCHSCREEN_USB_E2I=yCONFIG_TOUCHSCREEN_USB_ZYTRONIC=yCONFIG_TOUCHSCREEN_USB_ETT_TC45USB=yCONFIG_TOUCHSCREEN_USB_NEXIO=yCONFIG_TOUCHSCREEN_USB_EASYTOUCH=yCONFIG_TOUCHSCREEN_TOUCHIT213=yCONFIG_TOUCHSCREEN_TS4800=yCONFIG_TOUCHSCREEN_TSC_SERIO=yCONFIG_TOUCHSCREEN_TSC200X_CORE=yCONFIG_TOUCHSCREEN_TSC2004=yCONFIG_TOUCHSCREEN_TSC2005=yCONFIG_TOUCHSCREEN_TSC2007=yCONFIG_TOUCHSCREEN_TSC2007_IIO=yCONFIG_TOUCHSCREEN_PCAP=yCONFIG_TOUCHSCREEN_RM_TS=yCONFIG_TOUCHSCREEN_SILEAD=yCONFIG_TOUCHSCREEN_SIS_I2C=yCONFIG_TOUCHSCREEN_ST1232=yCONFIG_TOUCHSCREEN_STMFTS=yCONFIG_TOUCHSCREEN_STMPE=yCONFIG_TOUCHSCREEN_SUN4I=yCONFIG_TOUCHSCREEN_SUR40=yCONFIG_TOUCHSCREEN_SURFACE3_SPI=yCONFIG_TOUCHSCREEN_SX8654=yCONFIG_TOUCHSCREEN_TPS6507X=yCONFIG_TOUCHSCREEN_ZET6223=yCONFIG_TOUCHSCREEN_ZFORCE=yCONFIG_TOUCHSCREEN_COLIBRI_VF50=yCONFIG_TOUCHSCREEN_ROHM_BU21023=yCONFIG_TOUCHSCREEN_IQS5XX=yCONFIG_TOUCHSCREEN_ZINITIX=yCONFIG_INPUT_MISC=yCONFIG_INPUT_88PM860X_ONKEY=yCONFIG_INPUT_88PM80X_ONKEY=yCONFIG_INPUT_AD714X=yCONFIG_INPUT_AD714X_I2C=yCONFIG_INPUT_AD714X_SPI=yCONFIG_INPUT_ARIEL_PWRBUTTON=yCONFIG_INPUT_ARIZONA_HAPTICS=yCONFIG_INPUT_ATC260X_ONKEY=yCONFIG_INPUT_ATMEL_CAPTOUCH=yCONFIG_INPUT_BMA150=yCONFIG_INPUT_E3X0_BUTTON=yCONFIG_INPUT_PCSPKR=yCONFIG_INPUT_PM8941_PWRKEY=yCONFIG_INPUT_PM8XXX_VIBRATOR=yCONFIG_INPUT_PMIC8XXX_PWRKEY=yCONFIG_INPUT_MAX77650_ONKEY=yCONFIG_INPUT_MAX77693_HAPTIC=yCONFIG_INPUT_MAX8925_ONKEY=yCONFIG_INPUT_MAX8997_HAPTIC=yCONFIG_INPUT_MC13783_PWRBUTTON=yCONFIG_INPUT_MMA8450=yCONFIG_INPUT_GPIO_BEEPER=yCONFIG_INPUT_GPIO_DECODER=yCONFIG_INPUT_GPIO_VIBRA=yCONFIG_INPUT_CPCAP_PWRBUTTON=yCONFIG_INPUT_ATI_REMOTE2=yCONFIG_INPUT_KEYSPAN_REMOTE=yCONFIG_INPUT_KXTJ9=yCONFIG_INPUT_POWERMATE=yCONFIG_INPUT_YEALINK=yCONFIG_INPUT_CM109=yCONFIG_INPUT_REGULATOR_HAPTIC=yCONFIG_INPUT_RETU_PWRBUTTON=yCONFIG_INPUT_TPS65218_PWRBUTTON=yCONFIG_INPUT_AXP20X_PEK=yCONFIG_INPUT_TWL4030_PWRBUTTON=yCONFIG_INPUT_TWL4030_VIBRA=yCONFIG_INPUT_TWL6040_VIBRA=yCONFIG_INPUT_UINPUT=yCONFIG_INPUT_PALMAS_PWRBUTTON=yCONFIG_INPUT_PCF50633_PMU=yCONFIG_INPUT_PCF8574=yCONFIG_INPUT_PWM_BEEPER=yCONFIG_INPUT_PWM_VIBRA=yCONFIG_INPUT_RK805_PWRKEY=yCONFIG_INPUT_GPIO_ROTARY_ENCODER=yCONFIG_INPUT_DA7280_HAPTICS=yCONFIG_INPUT_DA9052_ONKEY=yCONFIG_INPUT_DA9055_ONKEY=yCONFIG_INPUT_DA9063_ONKEY=yCONFIG_INPUT_WM831X_ON=yCONFIG_INPUT_PCAP=yCONFIG_INPUT_ADXL34X=yCONFIG_INPUT_ADXL34X_I2C=yCONFIG_INPUT_ADXL34X_SPI=yCONFIG_INPUT_IMS_PCU=yCONFIG_INPUT_IQS269A=yCONFIG_INPUT_IQS626A=yCONFIG_INPUT_IQS7222=yCONFIG_INPUT_CMA3000=yCONFIG_INPUT_CMA3000_I2C=yCONFIG_INPUT_IDEAPAD_SLIDEBAR=yCONFIG_INPUT_DRV260X_HAPTICS=yCONFIG_INPUT_DRV2665_HAPTICS=yCONFIG_INPUT_DRV2667_HAPTICS=yCONFIG_INPUT_HISI_POWERKEY=yCONFIG_INPUT_RAVE_SP_PWRBUTTON=yCONFIG_INPUT_SC27XX_VIBRA=yCONFIG_INPUT_STPMIC1_ONKEY=yCONFIG_RMI4_CORE=yCONFIG_RMI4_I2C=yCONFIG_RMI4_SPI=yCONFIG_RMI4_SMB=yCONFIG_RMI4_F03=yCONFIG_RMI4_F03_SERIO=yCONFIG_RMI4_2D_SENSOR=yCONFIG_RMI4_F11=yCONFIG_RMI4_F12=yCONFIG_RMI4_F30=yCONFIG_RMI4_F34=yCONFIG_RMI4_F3A=yCONFIG_RMI4_F54=yCONFIG_RMI4_F55=y
#
# Hardware I/O ports
#CONFIG_SERIO=yCONFIG_ARCH_MIGHT_HAVE_PC_SERIO=yCONFIG_SERIO_I8042=yCONFIG_SERIO_SERPORT=yCONFIG_SERIO_PARKBD=yCONFIG_SERIO_PCIPS2=yCONFIG_SERIO_LIBPS2=yCONFIG_SERIO_RAW=yCONFIG_SERIO_ALTERA_PS2=yCONFIG_SERIO_PS2MULT=yCONFIG_SERIO_ARC_PS2=yCONFIG_SERIO_APBPS2=yCONFIG_SERIO_OLPC_APSP=yCONFIG_SERIO_SUN4I_PS2=yCONFIG_SERIO_GPIO_PS2=yCONFIG_USERIO=yCONFIG_GAMEPORT=yCONFIG_GAMEPORT_NS558=yCONFIG_GAMEPORT_L4=yCONFIG_GAMEPORT_EMU10K1=yCONFIG_GAMEPORT_FM801=y
# end of Hardware I/O ports # end of Input device support
#
# Character devices
#CONFIG_TTY=yCONFIG_VT=yCONFIG_CONSOLE_TRANSLATIONS=yCONFIG_VT_CONSOLE=yCONFIG_HW_CONSOLE=yCONFIG_VT_HW_CONSOLE_BINDING=yCONFIG_UNIX98_PTYS=yCONFIG_LEGACY_PTYS=yCONFIG_LEGACY_PTY_COUNT=256CONFIG_LDISC_AUTOLOAD=y
#
# Serial drivers
#CONFIG_SERIAL_EARLYCON=yCONFIG_SERIAL_8250=yCONFIG_SERIAL_8250_DEPRECATED_OPTIONS=yCONFIG_SERIAL_8250_PNP=yCONFIG_SERIAL_8250_16550A_VARIANTS=yCONFIG_SERIAL_8250_FINTEK=yCONFIG_SERIAL_8250_CONSOLE=yCONFIG_SERIAL_8250_DMA=yCONFIG_SERIAL_8250_PCI=yCONFIG_SERIAL_8250_EXAR=yCONFIG_SERIAL_8250_CS=yCONFIG_SERIAL_8250_MEN_MCB=yCONFIG_SERIAL_8250_NR_UARTS=4CONFIG_SERIAL_8250_RUNTIME_UARTS=4CONFIG_SERIAL_8250_EXTENDED=yCONFIG_SERIAL_8250_MANY_PORTS=yCONFIG_SERIAL_8250_FOURPORT=yCONFIG_SERIAL_8250_ACCENT=yCONFIG_SERIAL_8250_ASPEED_VUART=yCONFIG_SERIAL_8250_BOCA=yCONFIG_SERIAL_8250_EXAR_ST16C554=yCONFIG_SERIAL_8250_HUB6=yCONFIG_SERIAL_8250_SHARE_IRQ=yCONFIG_SERIAL_8250_DETECT_IRQ=yCONFIG_SERIAL_8250_RSA=yCONFIG_SERIAL_8250_DWLIB=yCONFIG_SERIAL_8250_BCM2835AUX=yCONFIG_SERIAL_8250_FSL=yCONFIG_SERIAL_8250_DW=yCONFIG_SERIAL_8250_EM=yCONFIG_SERIAL_8250_IOC3=yCONFIG_SERIAL_8250_RT288X=yCONFIG_SERIAL_8250_OMAP=yCONFIG_SERIAL_8250_OMAP_TTYO_FIXUP=yCONFIG_SERIAL_8250_LPC18XX=yCONFIG_SERIAL_8250_MT6577=yCONFIG_SERIAL_8250_UNIPHIER=yCONFIG_SERIAL_8250_INGENIC=yCONFIG_SERIAL_8250_LPSS=yCONFIG_SERIAL_8250_MID=yCONFIG_SERIAL_8250_PERICOM=yCONFIG_SERIAL_8250_PXA=yCONFIG_SERIAL_8250_TEGRA=yCONFIG_SERIAL_8250_BCM7271=yCONFIG_SERIAL_OF_PLATFORM=y
#
# Non-8250 serial port support
#CONFIG_SERIAL_AMBA_PL010=yCONFIG_SERIAL_AMBA_PL010_CONSOLE=yCONFIG_SERIAL_ATMEL=yCONFIG_SERIAL_ATMEL_CONSOLE=yCONFIG_SERIAL_ATMEL_PDC=yCONFIG_SERIAL_ATMEL_TTYAT=yCONFIG_SERIAL_MESON=yCONFIG_SERIAL_MESON_CONSOLE=yCONFIG_SERIAL_CLPS711X=yCONFIG_SERIAL_CLPS711X_CONSOLE=yCONFIG_SERIAL_SAMSUNG=yCONFIG_SERIAL_SAMSUNG_UARTS_4=yCONFIG_SERIAL_SAMSUNG_UARTS=4CONFIG_SERIAL_SAMSUNG_CONSOLE=yCONFIG_SERIAL_TEGRA=yCONFIG_SERIAL_TEGRA_TCU=yCONFIG_SERIAL_TEGRA_TCU_CONSOLE=yCONFIG_SERIAL_MAX3100=yCONFIG_SERIAL_MAX310X=yCONFIG_SERIAL_IMX=yCONFIG_SERIAL_IMX_CONSOLE=yCONFIG_SERIAL_IMX_EARLYCON=yCONFIG_SERIAL_UARTLITE=yCONFIG_SERIAL_UARTLITE_CONSOLE=yCONFIG_SERIAL_UARTLITE_NR_UARTS=1CONFIG_SERIAL_SH_SCI=yCONFIG_SERIAL_SH_SCI_NR_UARTS=2CONFIG_SERIAL_SH_SCI_CONSOLE=yCONFIG_SERIAL_SH_SCI_EARLYCON=yCONFIG_SERIAL_SH_SCI_DMA=yCONFIG_SERIAL_HS_LPC32XX=yCONFIG_SERIAL_HS_LPC32XX_CONSOLE=yCONFIG_SERIAL_CORE=yCONFIG_SERIAL_CORE_CONSOLE=yCONFIG_SERIAL_ICOM=yCONFIG_SERIAL_JSM=yCONFIG_SERIAL_MSM=yCONFIG_SERIAL_MSM_CONSOLE=yCONFIG_SERIAL_QCOM_GENI=yCONFIG_SERIAL_QCOM_GENI_CONSOLE=yCONFIG_SERIAL_VT8500=yCONFIG_SERIAL_VT8500_CONSOLE=yCONFIG_SERIAL_OMAP=yCONFIG_SERIAL_OMAP_CONSOLE=yCONFIG_SERIAL_SIFIVE=yCONFIG_SERIAL_SIFIVE_CONSOLE=yCONFIG_SERIAL_LANTIQ=yCONFIG_SERIAL_LANTIQ_CONSOLE=yCONFIG_SERIAL_QE=yCONFIG_SERIAL_SCCNXP=yCONFIG_SERIAL_SCCNXP_CONSOLE=yCONFIG_SERIAL_SC16IS7XX_CORE=yCONFIG_SERIAL_SC16IS7XX=yCONFIG_SERIAL_SC16IS7XX_I2C=yCONFIG_SERIAL_SC16IS7XX_SPI=yCONFIG_SERIAL_TIMBERDALE=yCONFIG_SERIAL_BCM63XX=yCONFIG_SERIAL_BCM63XX_CONSOLE=yCONFIG_SERIAL_ALTERA_JTAGUART=yCONFIG_SERIAL_ALTERA_JTAGUART_CONSOLE=yCONFIG_SERIAL_ALTERA_JTAGUART_CONSOLE_BYPASS=yCONFIG_SERIAL_ALTERA_UART=yCONFIG_SERIAL_ALTERA_UART_MAXPORTS=4CONFIG_SERIAL_ALTERA_UART_BAUDRATE=115200CONFIG_SERIAL_ALTERA_UART_CONSOLE=yCONFIG_SERIAL_PCH_UART=yCONFIG_SERIAL_PCH_UART_CONSOLE=yCONFIG_SERIAL_MXS_AUART=yCONFIG_SERIAL_MXS_AUART_CONSOLE=yCONFIG_SERIAL_XILINX_PS_UART=yCONFIG_SERIAL_XILINX_PS_UART_CONSOLE=yCONFIG_SERIAL_MPS2_UART_CONSOLE=yCONFIG_SERIAL_MPS2_UART=yCONFIG_SERIAL_ARC=yCONFIG_SERIAL_ARC_CONSOLE=yCONFIG_SERIAL_ARC_NR_PORTS=1CONFIG_SERIAL_RP2=yCONFIG_SERIAL_RP2_NR_UARTS=32CONFIG_SERIAL_FSL_LPUART=yCONFIG_SERIAL_FSL_LPUART_CONSOLE=yCONFIG_SERIAL_FSL_LINFLEXUART=yCONFIG_SERIAL_FSL_LINFLEXUART_CONSOLE=yCONFIG_SERIAL_CONEXANT_DIGICOLOR=yCONFIG_SERIAL_CONEXANT_DIGICOLOR_CONSOLE=yCONFIG_SERIAL_ST_ASC=yCONFIG_SERIAL_ST_ASC_CONSOLE=yCONFIG_SERIAL_MEN_Z135=yCONFIG_SERIAL_SPRD=yCONFIG_SERIAL_SPRD_CONSOLE=yCONFIG_SERIAL_STM32=yCONFIG_SERIAL_STM32_CONSOLE=yCONFIG_SERIAL_MVEBU_UART=yCONFIG_SERIAL_MVEBU_CONSOLE=yCONFIG_SERIAL_OWL=yCONFIG_SERIAL_OWL_CONSOLE=yCONFIG_SERIAL_RDA=yCONFIG_SERIAL_RDA_CONSOLE=yCONFIG_SERIAL_MILBEAUT_USIO=yCONFIG_SERIAL_MILBEAUT_USIO_PORTS=4CONFIG_SERIAL_MILBEAUT_USIO_CONSOLE=yCONFIG_SERIAL_LITEUART=yCONFIG_SERIAL_LITEUART_MAX_PORTS=1CONFIG_SERIAL_LITEUART_CONSOLE=yCONFIG_SERIAL_SUNPLUS=yCONFIG_SERIAL_SUNPLUS_CONSOLE=y
# end of Serial drivers
CONFIG_SERIAL_MCTRL_GPIO=yCONFIG_SERIAL_NONSTANDARD=yCONFIG_MOXA_INTELLIO=yCONFIG_MOXA_SMARTIO=yCONFIG_SYNCLINK_GT=yCONFIG_N_HDLC=yCONFIG_GOLDFISH_TTY=yCONFIG_GOLDFISH_TTY_EARLY_CONSOLE=yCONFIG_N_GSM=yCONFIG_NOZOMI=yCONFIG_NULL_TTY=yCONFIG_HVC_DRIVER=yCONFIG_RPMSG_TTY=yCONFIG_SERIAL_DEV_BUS=yCONFIG_SERIAL_DEV_CTRL_TTYPORT=yCONFIG_TTY_PRINTK=yCONFIG_TTY_PRINTK_LEVEL=6CONFIG_PRINTER=yCONFIG_LP_CONSOLE=yCONFIG_PPDEV=yCONFIG_VIRTIO_CONSOLE=yCONFIG_IPMI_HANDLER=yCONFIG_IPMI_PLAT_DATA=yCONFIG_IPMI_PANIC_EVENT=yCONFIG_IPMI_PANIC_STRING=yCONFIG_IPMI_DEVICE_INTERFACE=yCONFIG_IPMI_SI=yCONFIG_IPMI_SSIF=yCONFIG_IPMI_IPMB=yCONFIG_IPMI_WATCHDOG=yCONFIG_IPMI_POWEROFF=yCONFIG_IPMI_KCS_BMC=yCONFIG_ASPEED_KCS_IPMI_BMC=yCONFIG_NPCM7XX_KCS_IPMI_BMC=yCONFIG_IPMI_KCS_BMC_CDEV_IPMI=yCONFIG_IPMI_KCS_BMC_SERIO=yCONFIG_ASPEED_BT_IPMI_BMC=yCONFIG_IPMB_DEVICE_INTERFACE=yCONFIG_HW_RANDOM=yCONFIG_HW_RANDOM_TIMERIOMEM=yCONFIG_HW_RANDOM_ATMEL=yCONFIG_HW_RANDOM_BA431=yCONFIG_HW_RANDOM_BCM2835=yCONFIG_HW_RANDOM_IPROC_RNG200=yCONFIG_HW_RANDOM_IXP4XX=yCONFIG_HW_RANDOM_OMAP=yCONFIG_HW_RANDOM_OMAP3_ROM=yCONFIG_HW_RANDOM_VIRTIO=yCONFIG_HW_RANDOM_IMX_RNGC=yCONFIG_HW_RANDOM_NOMADIK=yCONFIG_HW_RANDOM_STM32=yCONFIG_HW_RANDOM_POLARFIRE_SOC=yCONFIG_HW_RANDOM_MESON=yCONFIG_HW_RANDOM_MTK=yCONFIG_HW_RANDOM_EXYNOS=yCONFIG_HW_RANDOM_NPCM=yCONFIG_HW_RANDOM_KEYSTONE=yCONFIG_HW_RANDOM_CCTRNG=yCONFIG_HW_RANDOM_XIPHERA=yCONFIG_HW_RANDOM_CN10K=yCONFIG_DTLK=yCONFIG_APPLICOM=y
#
# PCMCIA character devices
#CONFIG_SYNCLINK_CS=yCONFIG_CARDMAN_4000=yCONFIG_CARDMAN_4040=yCONFIG_SCR24X=yCONFIG_IPWIRELESS=y
# end of PCMCIA character devices
CONFIG_DEVMEM=yCONFIG_DEVPORT=yCONFIG_TCG_TPM=yCONFIG_HW_RANDOM_TPM=yCONFIG_TCG_TIS_CORE=yCONFIG_TCG_TIS=yCONFIG_TCG_TIS_SPI=yCONFIG_TCG_TIS_SPI_CR50=yCONFIG_TCG_TIS_I2C=yCONFIG_TCG_TIS_SYNQUACER=yCONFIG_TCG_TIS_I2C_CR50=yCONFIG_TCG_TIS_I2C_ATMEL=yCONFIG_TCG_TIS_I2C_INFINEON=yCONFIG_TCG_TIS_I2C_NUVOTON=yCONFIG_TCG_ATMEL=yCONFIG_TCG_INFINEON=yCONFIG_TCG_VTPM_PROXY=yCONFIG_TCG_TIS_ST33ZP24=yCONFIG_TCG_TIS_ST33ZP24_I2C=yCONFIG_TCG_TIS_ST33ZP24_SPI=yCONFIG_XILLYBUS_CLASS=yCONFIG_XILLYBUS=yCONFIG_XILLYBUS_PCIE=yCONFIG_XILLYBUS_OF=yCONFIG_XILLYUSB=yCONFIG_RANDOM_TRUST_CPU=yCONFIG_RANDOM_TRUST_BOOTLOADER=y
# end of Character devices
#
# I2C support
#CONFIG_I2C=yCONFIG_I2C_BOARDINFO=yCONFIG_I2C_COMPAT=yCONFIG_I2C_CHARDEV=yCONFIG_I2C_MUX=y
#
# Multiplexer I2C Chip support
#CONFIG_I2C_ARB_GPIO_CHALLENGE=yCONFIG_I2C_MUX_GPIO=yCONFIG_I2C_MUX_GPMUX=yCONFIG_I2C_MUX_LTC4306=yCONFIG_I2C_MUX_PCA9541=y
CONFIG_I2C_MUX_PCA954x=yCONFIG_I2C_MUX_PINCTRL=yCONFIG_I2C_MUX_REG=yCONFIG_I2C_DEMUX_PINCTRL=yCONFIG_I2C_MUX_MLXCPLD=y
# end of Multiplexer I2C Chip support
CONFIG_I2C_HELPER_AUTO=yCONFIG_I2C_SMBUS=yCONFIG_I2C_ALGOBIT=yCONFIG_I2C_ALGOPCA=y
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#CONFIG_I2C_CCGX_UCSI=yCONFIG_I2C_ALI1535=yCONFIG_I2C_ALI1563=yCONFIG_I2C_ALI15X3=yCONFIG_I2C_AMD756=yCONFIG_I2C_AMD8111=yCONFIG_I2C_HIX5HD2=yCONFIG_I2C_I801=yCONFIG_I2C_ISCH=yCONFIG_I2C_PIIX4=yCONFIG_I2C_NFORCE2=yCONFIG_I2C_NVIDIA_GPU=yCONFIG_I2C_SIS5595=yCONFIG_I2C_SIS630=yCONFIG_I2C_SIS96X=yCONFIG_I2C_VIA=yCONFIG_I2C_VIAPRO=y
#
# I2C system bus drivers (mostly embedded / system-on-chip) #CONFIG_I2C_ALTERA=yCONFIG_I2C_ASPEED=yCONFIG_I2C_AT91=y CONFIG_I2C_AT91_SLAVE_EXPERIMENTAL=y CONFIG_I2C_AXXIA=yCONFIG_I2C_BCM2835=yCONFIG_I2C_BCM_IPROC=yCONFIG_I2C_BCM_KONA=yCONFIG_I2C_BRCMSTB=yCONFIG_I2C_CADENCE=yCONFIG_I2C_CBUS_GPIO=yCONFIG_I2C_DAVINCI=yCONFIG_I2C_DESIGNWARE_CORE=y CONFIG_I2C_DESIGNWARE_SLAVE=y CONFIG_I2C_DESIGNWARE_PLATFORM=y CONFIG_I2C_DESIGNWARE_PCI=yCONFIG_I2C_DIGICOLOR=yCONFIG_I2C_EG20T=yCONFIG_I2C_EMEV2=yCONFIG_I2C_EXYNOS5=yCONFIG_I2C_GPIO=yCONFIG_I2C_GPIO_FAULT_INJECTOR=y CONFIG_I2C_HIGHLANDER=yCONFIG_I2C_HISI=yCONFIG_I2C_IMG=yCONFIG_I2C_IMX=yCONFIG_I2C_IMX_LPI2C=yCONFIG_I2C_IOP3XX=yCONFIG_I2C_JZ4780=yCONFIG_I2C_KEMPLD=yCONFIG_I2C_LPC2K=yCONFIG_I2C_MESON=yCONFIG_I2C_MICROCHIP_CORE=yCONFIG_I2C_MT65XX=yCONFIG_I2C_MT7621=yCONFIG_I2C_MV64XXX=yCONFIG_I2C_MXS=yCONFIG_I2C_NPCM=yCONFIG_I2C_OCORES=yCONFIG_I2C_OMAP=yCONFIG_I2C_OWL=yCONFIG_I2C_APPLE=yCONFIG_I2C_PCA_PLATFORM=yCONFIG_I2C_PNX=yCONFIG_I2C_PXA=yCONFIG_I2C_PXA_SLAVE=yCONFIG_I2C_QCOM_CCI=yCONFIG_I2C_QCOM_GENI=yCONFIG_I2C_QUP=yCONFIG_I2C_RIIC=yCONFIG_I2C_RK3X=yCONFIG_I2C_RZV2M=yCONFIG_I2C_S3C2410=yCONFIG_I2C_SH_MOBILE=yCONFIG_I2C_SIMTEC=yCONFIG_I2C_SPRD=yCONFIG_I2C_ST=yCONFIG_I2C_STM32F4=yCONFIG_I2C_STM32F7=yCONFIG_I2C_SUN6I_P2WI=yCONFIG_I2C_SYNQUACER=yCONFIG_I2C_TEGRA_BPMP=yCONFIG_I2C_UNIPHIER=yCONFIG_I2C_UNIPHIER_F=yCONFIG_I2C_VERSATILE=yCONFIG_I2C_WMT=yCONFIG_I2C_THUNDERX=yCONFIG_I2C_XILINX=yCONFIG_I2C_XLP9XX=yCONFIG_I2C_RCAR=y
#
# External I2C/SMBus adapter drivers
#CONFIG_I2C_DIOLAN_U2C=yCONFIG_I2C_DLN2=yCONFIG_I2C_CP2615=yCONFIG_I2C_PARPORT=yCONFIG_I2C_ROBOTFUZZ_OSIF=yCONFIG_I2C_TAOS_EVM=yCONFIG_I2C_TINY_USB=yCONFIG_I2C_VIPERBOARD=y
#
# Other I2C/SMBus bus drivers
#CONFIG_I2C_MLXCPLD=yCONFIG_I2C_PCA_ISA=yCONFIG_I2C_CROS_EC_TUNNEL=yCONFIG_I2C_FSI=yCONFIG_I2C_VIRTIO=y
# end of I2C Hardware Bus support
CONFIG_I2C_STUB=mCONFIG_I2C_SLAVE=yCONFIG_I2C_SLAVE_EEPROM=yCONFIG_I2C_SLAVE_TESTUNIT=yCONFIG_I2C_DEBUG_CORE=yCONFIG_I2C_DEBUG_ALGO=yCONFIG_I2C_DEBUG_BUS=y
# end of I2C support
CONFIG_I3C=yCONFIG_MIPI_I3C_HCI=yCONFIG_SPI=yCONFIG_SPI_DEBUG=yCONFIG_SPI_MASTER=yCONFIG_SPI_MEM=y
#
# SPI Master Controller Drivers
#CONFIG_SPI_ALTERA=yCONFIG_SPI_ALTERA_CORE=yCONFIG_SPI_ALTERA_DFL=yCONFIG_SPI_AR934X=yCONFIG_SPI_ATH79=yCONFIG_SPI_ARMADA_3700=yCONFIG_SPI_ASPEED_SMC=yCONFIG_SPI_ATMEL=yCONFIG_SPI_AT91_USART=yCONFIG_SPI_ATMEL_QUADSPI=yCONFIG_SPI_AXI_SPI_ENGINE=yCONFIG_SPI_BCM2835=yCONFIG_SPI_BCM2835AUX=yCONFIG_SPI_BCM63XX=yCONFIG_SPI_BCM63XX_HSSPI=yCONFIG_SPI_BCM_QSPI=yCONFIG_SPI_BITBANG=yCONFIG_SPI_BUTTERFLY=yCONFIG_SPI_CADENCE=yCONFIG_SPI_CADENCE_QUADSPI=yCONFIG_SPI_CADENCE_XSPI=yCONFIG_SPI_CLPS711X=yCONFIG_SPI_DESIGNWARE=yCONFIG_SPI_DW_DMA=yCONFIG_SPI_DW_PCI=yCONFIG_SPI_DW_MMIO=yCONFIG_SPI_DW_BT1=yCONFIG_SPI_DW_BT1_DIRMAP=yCONFIG_SPI_DLN2=yCONFIG_SPI_EP93XX=yCONFIG_SPI_FSI=yCONFIG_SPI_FSL_LPSPI=yCONFIG_SPI_FSL_QUADSPI=yCONFIG_SPI_GXP=yCONFIG_SPI_HISI_KUNPENG=yCONFIG_SPI_HISI_SFC_V3XX=yCONFIG_SPI_NXP_FLEXSPI=yCONFIG_SPI_GPIO=yCONFIG_SPI_IMG_SPFI=yCONFIG_SPI_IMX=yCONFIG_SPI_INGENIC=yCONFIG_SPI_INTEL=yCONFIG_SPI_INTEL_PCI=yCONFIG_SPI_INTEL_PLATFORM=yCONFIG_SPI_JCORE=yCONFIG_SPI_LM70_LLP=yCONFIG_SPI_LP8841_RTC=yCONFIG_SPI_FSL_LIB=yCONFIG_SPI_FSL_SPI=yCONFIG_SPI_FSL_DSPI=yCONFIG_SPI_MESON_SPICC=yCONFIG_SPI_MESON_SPIFC=yCONFIG_SPI_MICROCHIP_CORE=yCONFIG_SPI_MT65XX=yCONFIG_SPI_MT7621=yCONFIG_SPI_MTK_NOR=yCONFIG_SPI_MTK_SNFI=yCONFIG_SPI_NPCM_FIU=yCONFIG_SPI_NPCM_PSPI=yCONFIG_SPI_LANTIQ_SSC=yCONFIG_SPI_OC_TINY=yCONFIG_SPI_OMAP24XX=yCONFIG_SPI_TI_QSPI=yCONFIG_SPI_OMAP_100K=yCONFIG_SPI_ORION=yCONFIG_SPI_PIC32=yCONFIG_SPI_PIC32_SQI=yCONFIG_SPI_PXA2XX=yCONFIG_SPI_PXA2XX_PCI=yCONFIG_SPI_ROCKCHIP=yCONFIG_SPI_ROCKCHIP_SFC=yCONFIG_SPI_RPCIF=yCONFIG_SPI_RSPI=yCONFIG_SPI_QUP=yCONFIG_SPI_QCOM_GENI=yCONFIG_SPI_S3C64XX=yCONFIG_SPI_SC18IS602=yCONFIG_SPI_SH_MSIOF=yCONFIG_SPI_SH=yCONFIG_SPI_SH_HSPI=yCONFIG_SPI_SIFIVE=yCONFIG_SPI_SLAVE_MT27XX=yCONFIG_SPI_SPRD=yCONFIG_SPI_SPRD_ADI=yCONFIG_SPI_STM32=yCONFIG_SPI_STM32_QSPI=yCONFIG_SPI_ST_SSC4=yCONFIG_SPI_SUN4I=yCONFIG_SPI_SUN6I=yCONFIG_SPI_SUNPLUS_SP7021=yCONFIG_SPI_SYNQUACER=yCONFIG_SPI_MXIC=yCONFIG_SPI_TEGRA210_QUAD=yCONFIG_SPI_TEGRA114=yCONFIG_SPI_TEGRA20_SFLASH=yCONFIG_SPI_TEGRA20_SLINK=yCONFIG_SPI_THUNDERX=yCONFIG_SPI_TOPCLIFF_PCH=yCONFIG_SPI_UNIPHIER=yCONFIG_SPI_XCOMM=yCONFIG_SPI_XILINX=yCONFIG_SPI_XLP=yCONFIG_SPI_XTENSA_XTFPGA=yCONFIG_SPI_ZYNQ_QSPI=yCONFIG_SPI_ZYNQMP_GQSPI=yCONFIG_SPI_AMD=y
#
# SPI Multiplexer support
#CONFIG_SPI_MUX=y
#
# SPI Protocol Masters
#CONFIG_SPI_SPIDEV=yCONFIG_SPI_LOOPBACK_TEST=mCONFIG_SPI_TLE62X0=yCONFIG_SPI_SLAVE=yCONFIG_SPI_SLAVE_TIME=yCONFIG_SPI_SLAVE_SYSTEM_CONTROL=yCONFIG_SPI_DYNAMIC=yCONFIG_SPMI=yCONFIG_SPMI_HISI3670=yCONFIG_SPMI_MSM_PMIC_ARB=yCONFIG_SPMI_MTK_PMIF=yCONFIG_HSI=yCONFIG_HSI_BOARDINFO=y
#
# HSI controllers
#
#
# HSI clients
#CONFIG_HSI_CHAR=yCONFIG_PPS=yCONFIG_PPS_DEBUG=y
#
# PPS clients support
#CONFIG_PPS_CLIENT_KTIMER=yCONFIG_PPS_CLIENT_LDISC=yCONFIG_PPS_CLIENT_PARPORT=yCONFIG_PPS_CLIENT_GPIO=y
#
# PPS generators support
#
#
# PTP clock support
#CONFIG_PTP_1588_CLOCK=yCONFIG_PTP_1588_CLOCK_OPTIONAL=yCONFIG_PTP_1588_CLOCK_DTE=yCONFIG_PTP_1588_CLOCK_QORIQ=yCONFIG_DP83640_PHY=yCONFIG_PTP_1588_CLOCK_INES=yCONFIG_PTP_1588_CLOCK_PCH=yCONFIG_PTP_1588_CLOCK_IDT82P33=yCONFIG_PTP_1588_CLOCK_IDTCM=yCONFIG_PTP_1588_CLOCK_OCP=y
# end of PTP clock support
CONFIG_PINCTRL=yCONFIG_GENERIC_PINCTRL_GROUPS=yCONFIG_PINMUX=yCONFIG_GENERIC_PINMUX_FUNCTIONS=yCONFIG_PINCONF=yCONFIG_GENERIC_PINCONF=yCONFIG_DEBUG_PINCTRL=yCONFIG_PINCTRL_AMD=yCONFIG_PINCTRL_AS3722=yCONFIG_PINCTRL_AT91PIO4=yCONFIG_PINCTRL_AXP209=yCONFIG_PINCTRL_BM1880=yCONFIG_PINCTRL_DA850_PUPD=yCONFIG_PINCTRL_DA9062=yCONFIG_PINCTRL_EQUILIBRIUM=yCONFIG_PINCTRL_INGENIC=yCONFIG_PINCTRL_LPC18XX=yCONFIG_PINCTRL_MAX77620=yCONFIG_PINCTRL_MCP23S08_I2C=yCONFIG_PINCTRL_MCP23S08_SPI=yCONFIG_PINCTRL_MCP23S08=yCONFIG_PINCTRL_MICROCHIP_SGPIO=yCONFIG_PINCTRL_OCELOT=yCONFIG_PINCTRL_PALMAS=yCONFIG_PINCTRL_PISTACHIO=yCONFIG_PINCTRL_RK805=yCONFIG_PINCTRL_ROCKCHIP=yCONFIG_PINCTRL_SINGLE=yCONFIG_PINCTRL_STARFIVE=yCONFIG_PINCTRL_STMFX=yCONFIG_PINCTRL_SX150X=yCONFIG_PINCTRL_OWL=yCONFIG_PINCTRL_S500=yCONFIG_PINCTRL_S700=yCONFIG_PINCTRL_S900=yCONFIG_PINCTRL_ASPEED=yCONFIG_PINCTRL_ASPEED_G4=yCONFIG_PINCTRL_ASPEED_G5=yCONFIG_PINCTRL_ASPEED_G6=yCONFIG_PINCTRL_BCM281XX=yCONFIG_PINCTRL_BCM2835=yCONFIG_PINCTRL_BCM4908=yCONFIG_PINCTRL_BCM63XX=yCONFIG_PINCTRL_BCM6318=yCONFIG_PINCTRL_BCM6328=yCONFIG_PINCTRL_BCM6358=yCONFIG_PINCTRL_BCM6362=yCONFIG_PINCTRL_BCM6368=yCONFIG_PINCTRL_BCM63268=yCONFIG_PINCTRL_IPROC_GPIO=yCONFIG_PINCTRL_CYGNUS_MUX=yCONFIG_PINCTRL_NS=yCONFIG_PINCTRL_NSP_GPIO=yCONFIG_PINCTRL_NS2_MUX=yCONFIG_PINCTRL_NSP_MUX=yCONFIG_PINCTRL_BERLIN=yCONFIG_PINCTRL_AS370=yCONFIG_PINCTRL_BERLIN_BG4CT=yCONFIG_PINCTRL_LOCHNAGAR=yCONFIG_PINCTRL_MADERA=yCONFIG_PINCTRL_CS47L15=yCONFIG_PINCTRL_CS47L35=yCONFIG_PINCTRL_CS47L85=yCONFIG_PINCTRL_CS47L90=yCONFIG_PINCTRL_CS47L92=y
#
# Intel pinctrl drivers
#
# end of Intel pinctrl drivers
#
# MediaTek pinctrl drivers
#CONFIG_EINT_MTK=yCONFIG_PINCTRL_MTK=yCONFIG_PINCTRL_MTK_V2=yCONFIG_PINCTRL_MTK_MOORE=yCONFIG_PINCTRL_MTK_PARIS=yCONFIG_PINCTRL_MT2701=yCONFIG_PINCTRL_MT7623=yCONFIG_PINCTRL_MT7629=yCONFIG_PINCTRL_MT8135=yCONFIG_PINCTRL_MT8127=yCONFIG_PINCTRL_MT2712=yCONFIG_PINCTRL_MT6765=yCONFIG_PINCTRL_MT6779=yCONFIG_PINCTRL_MT6795=yCONFIG_PINCTRL_MT6797=yCONFIG_PINCTRL_MT7622=yCONFIG_PINCTRL_MT7986=yCONFIG_PINCTRL_MT8167=yCONFIG_PINCTRL_MT8173=yCONFIG_PINCTRL_MT8183=yCONFIG_PINCTRL_MT8186=yCONFIG_PINCTRL_MT8192=yCONFIG_PINCTRL_MT8195=yCONFIG_PINCTRL_MT8365=yCONFIG_PINCTRL_MT8516=yCONFIG_PINCTRL_MT6397=y
# end of MediaTek pinctrl drivers
CONFIG_PINCTRL_MESON=yCONFIG_PINCTRL_WPCM450=yCONFIG_PINCTRL_NPCM7XX=yCONFIG_PINCTRL_PXA=yCONFIG_PINCTRL_PXA25X=yCONFIG_PINCTRL_PXA27X=yCONFIG_PINCTRL_MSM=yCONFIG_PINCTRL_APQ8064=yCONFIG_PINCTRL_APQ8084=yCONFIG_PINCTRL_IPQ4019=yCONFIG_PINCTRL_IPQ8064=yCONFIG_PINCTRL_IPQ8074=yCONFIG_PINCTRL_IPQ6018=yCONFIG_PINCTRL_MSM8226=yCONFIG_PINCTRL_MSM8660=yCONFIG_PINCTRL_MSM8960=yCONFIG_PINCTRL_MDM9607=yCONFIG_PINCTRL_MDM9615=yCONFIG_PINCTRL_MSM8X74=yCONFIG_PINCTRL_MSM8909=yCONFIG_PINCTRL_MSM8916=yCONFIG_PINCTRL_MSM8953=yCONFIG_PINCTRL_MSM8976=yCONFIG_PINCTRL_MSM8994=yCONFIG_PINCTRL_MSM8996=yCONFIG_PINCTRL_MSM8998=yCONFIG_PINCTRL_QCM2290=yCONFIG_PINCTRL_QCS404=yCONFIG_PINCTRL_QCOM_SPMI_PMIC=yCONFIG_PINCTRL_QCOM_SSBI_PMIC=yCONFIG_PINCTRL_SC7180=yCONFIG_PINCTRL_SC7280=yCONFIG_PINCTRL_SC7280_LPASS_LPI=yCONFIG_PINCTRL_SC8180X=yCONFIG_PINCTRL_SC8280XP=yCONFIG_PINCTRL_SDM660=yCONFIG_PINCTRL_SDM845=yCONFIG_PINCTRL_SDX55=yCONFIG_PINCTRL_SM6115=yCONFIG_PINCTRL_SM6125=yCONFIG_PINCTRL_SM6350=yCONFIG_PINCTRL_SM6375=yCONFIG_PINCTRL_SDX65=yCONFIG_PINCTRL_SM8150=yCONFIG_PINCTRL_SM8250=yCONFIG_PINCTRL_SM8250_LPASS_LPI=yCONFIG_PINCTRL_SM8350=yCONFIG_PINCTRL_SM8450=yCONFIG_PINCTRL_LPASS_LPI=y
#
# Renesas pinctrl drivers
#CONFIG_PINCTRL_RENESAS=yCONFIG_PINCTRL_SH_PFC=yCONFIG_PINCTRL_SH_PFC_GPIO=yCONFIG_PINCTRL_SH_FUNC_GPIO=yCONFIG_PINCTRL_PFC_EMEV2=yCONFIG_PINCTRL_PFC_R8A77995=yCONFIG_PINCTRL_PFC_R8A7794=yCONFIG_PINCTRL_PFC_R8A77990=yCONFIG_PINCTRL_PFC_R8A7779=yCONFIG_PINCTRL_PFC_R8A7790=yCONFIG_PINCTRL_PFC_R8A77950=yCONFIG_PINCTRL_PFC_R8A77951=yCONFIG_PINCTRL_PFC_R8A7778=yCONFIG_PINCTRL_PFC_R8A7793=yCONFIG_PINCTRL_PFC_R8A7791=yCONFIG_PINCTRL_PFC_R8A77965=yCONFIG_PINCTRL_PFC_R8A77960=yCONFIG_PINCTRL_PFC_R8A77961=yCONFIG_PINCTRL_PFC_R8A779F0=yCONFIG_PINCTRL_PFC_R8A7792=yCONFIG_PINCTRL_PFC_R8A77980=yCONFIG_PINCTRL_PFC_R8A77970=yCONFIG_PINCTRL_PFC_R8A779A0=yCONFIG_PINCTRL_PFC_R8A779G0=yCONFIG_PINCTRL_PFC_R8A7740=yCONFIG_PINCTRL_PFC_R8A73A4=yCONFIG_PINCTRL_RZA1=yCONFIG_PINCTRL_RZA2=yCONFIG_PINCTRL_RZG2L=yCONFIG_PINCTRL_PFC_R8A77470=yCONFIG_PINCTRL_PFC_R8A7745=yCONFIG_PINCTRL_PFC_R8A7742=yCONFIG_PINCTRL_PFC_R8A7743=yCONFIG_PINCTRL_PFC_R8A7744=yCONFIG_PINCTRL_PFC_R8A774C0=yCONFIG_PINCTRL_PFC_R8A774E1=yCONFIG_PINCTRL_PFC_R8A774A1=yCONFIG_PINCTRL_PFC_R8A774B1=yCONFIG_PINCTRL_RZN1=yCONFIG_PINCTRL_RZV2M=yCONFIG_PINCTRL_PFC_SH7203=yCONFIG_PINCTRL_PFC_SH7264=yCONFIG_PINCTRL_PFC_SH7269=yCONFIG_PINCTRL_PFC_SH7720=yCONFIG_PINCTRL_PFC_SH7722=yCONFIG_PINCTRL_PFC_SH7734=yCONFIG_PINCTRL_PFC_SH7757=yCONFIG_PINCTRL_PFC_SH7785=yCONFIG_PINCTRL_PFC_SH7786=yCONFIG_PINCTRL_PFC_SH73A0=yCONFIG_PINCTRL_PFC_SH7723=yCONFIG_PINCTRL_PFC_SH7724=yCONFIG_PINCTRL_PFC_SHX3=y
# end of Renesas pinctrl drivers
CONFIG_PINCTRL_SAMSUNG=yCONFIG_PINCTRL_EXYNOS=yCONFIG_PINCTRL_EXYNOS_ARM=yCONFIG_PINCTRL_EXYNOS_ARM64=yCONFIG_PINCTRL_S3C24XX=yCONFIG_PINCTRL_S3C64XX=yCONFIG_PINCTRL_SPRD=yCONFIG_PINCTRL_SPRD_SC9860=yCONFIG_PINCTRL_STM32=yCONFIG_PINCTRL_STM32F429=yCONFIG_PINCTRL_STM32F469=yCONFIG_PINCTRL_STM32F746=yCONFIG_PINCTRL_STM32F769=yCONFIG_PINCTRL_STM32H743=yCONFIG_PINCTRL_STM32MP135=yCONFIG_PINCTRL_STM32MP157=yCONFIG_PINCTRL_TI_IODELAY=yCONFIG_PINCTRL_UNIPHIER=yCONFIG_PINCTRL_UNIPHIER_LD4=yCONFIG_PINCTRL_UNIPHIER_PRO4=yCONFIG_PINCTRL_UNIPHIER_SLD8=yCONFIG_PINCTRL_UNIPHIER_PRO5=yCONFIG_PINCTRL_UNIPHIER_PXS2=yCONFIG_PINCTRL_UNIPHIER_LD6B=yCONFIG_PINCTRL_UNIPHIER_LD11=yCONFIG_PINCTRL_UNIPHIER_LD20=yCONFIG_PINCTRL_UNIPHIER_PXS3=yCONFIG_PINCTRL_UNIPHIER_NX1=yCONFIG_PINCTRL_VISCONTI=yCONFIG_PINCTRL_TMPV7700=yCONFIG_GPIOLIB=yCONFIG_GPIOLIB_FASTPATH_LIMIT=512CONFIG_OF_GPIO=yCONFIG_GPIOLIB_IRQCHIP=yCONFIG_DEBUG_GPIO=yCONFIG_GPIO_SYSFS=yCONFIG_GPIO_CDEV=yCONFIG_GPIO_CDEV_V1=yCONFIG_GPIO_GENERIC=yCONFIG_GPIO_REGMAP=yCONFIG_GPIO_MAX730X=y
#
# Memory mapped GPIO drivers
#CONFIG_GPIO_74XX_MMIO=yCONFIG_GPIO_ALTERA=yCONFIG_GPIO_ASPEED=yCONFIG_GPIO_ASPEED_SGPIO=yCONFIG_GPIO_ATH79=yCONFIG_GPIO_RASPBERRYPI_EXP=yCONFIG_GPIO_BCM_KONA=yCONFIG_GPIO_BCM_XGS_IPROC=yCONFIG_GPIO_BRCMSTB=yCONFIG_GPIO_CADENCE=yCONFIG_GPIO_CLPS711X=yCONFIG_GPIO_DWAPB=yCONFIG_GPIO_EIC_SPRD=yCONFIG_GPIO_EM=yCONFIG_GPIO_EXAR=yCONFIG_GPIO_FTGPIO010=yCONFIG_GPIO_GENERIC_PLATFORM=yCONFIG_GPIO_GRGPIO=yCONFIG_GPIO_HISI=yCONFIG_GPIO_HLWD=yCONFIG_GPIO_IOP=yCONFIG_GPIO_LOGICVC=yCONFIG_GPIO_LPC18XX=yCONFIG_GPIO_LPC32XX=yCONFIG_GPIO_MB86S7X=yCONFIG_GPIO_MENZ127=yCONFIG_GPIO_MPC8XXX=yCONFIG_GPIO_MT7621=yCONFIG_GPIO_MXC=yCONFIG_GPIO_MXS=yCONFIG_GPIO_PMIC_EIC_SPRD=yCONFIG_GPIO_PXA=yCONFIG_GPIO_RCAR=yCONFIG_GPIO_RDA=yCONFIG_GPIO_ROCKCHIP=yCONFIG_GPIO_SAMA5D2_PIOBU=yCONFIG_GPIO_SIFIVE=yCONFIG_GPIO_SIOX=yCONFIG_GPIO_SNPS_CREG=yCONFIG_GPIO_SPRD=yCONFIG_GPIO_STP_XWAY=yCONFIG_GPIO_SYSCON=yCONFIG_GPIO_TEGRA=yCONFIG_GPIO_TEGRA186=yCONFIG_GPIO_TS4800=yCONFIG_GPIO_THUNDERX=yCONFIG_GPIO_UNIPHIER=yCONFIG_GPIO_VISCONTI=yCONFIG_GPIO_VX855=yCONFIG_GPIO_WCD934X=yCONFIG_GPIO_XGENE_SB=yCONFIG_GPIO_XILINX=yCONFIG_GPIO_XLP=yCONFIG_GPIO_AMD_FCH=yCONFIG_GPIO_IDT3243X=y
# end of Memory mapped GPIO drivers
#
# I2C GPIO expanders
#CONFIG_GPIO_ADP5588=yCONFIG_GPIO_ADP5588_IRQ=yCONFIG_GPIO_ADNP=yCONFIG_GPIO_GW_PLD=yCONFIG_GPIO_MAX7300=yCONFIG_GPIO_MAX732X=yCONFIG_GPIO_MAX732X_IRQ=yCONFIG_GPIO_PCA953X=yCONFIG_GPIO_PCA953X_IRQ=yCONFIG_GPIO_PCA9570=yCONFIG_GPIO_PCF857X=yCONFIG_GPIO_TPIC2810=yCONFIG_GPIO_TS4900=y
# end of I2C GPIO expanders
#
# MFD GPIO expanders
#CONFIG_GPIO_ADP5520=yCONFIG_GPIO_ARIZONA=yCONFIG_GPIO_BD71815=yCONFIG_GPIO_BD71828=yCONFIG_GPIO_BD9571MWV=yCONFIG_GPIO_DA9052=yCONFIG_GPIO_DA9055=yCONFIG_GPIO_DLN2=yCONFIG_GPIO_JANZ_TTL=yCONFIG_GPIO_KEMPLD=yCONFIG_GPIO_LP3943=yCONFIG_GPIO_LP873X=yCONFIG_GPIO_LP87565=yCONFIG_GPIO_MADERA=yCONFIG_GPIO_MAX77620=yCONFIG_GPIO_MAX77650=yCONFIG_GPIO_PALMAS=yCONFIG_GPIO_RC5T583=yCONFIG_GPIO_SL28CPLD=yCONFIG_GPIO_STMPE=yCONFIG_GPIO_TC3589X=yCONFIG_GPIO_TIMBERDALE=yCONFIG_GPIO_TPS65086=yCONFIG_GPIO_TPS65218=yCONFIG_GPIO_TPS6586X=yCONFIG_GPIO_TPS65910=yCONFIG_GPIO_TPS65912=yCONFIG_GPIO_TQMX86=yCONFIG_GPIO_TWL4030=yCONFIG_GPIO_TWL6040=yCONFIG_GPIO_UCB1400=yCONFIG_GPIO_WM831X=yCONFIG_GPIO_WM8350=yCONFIG_GPIO_WM8994=y
# end of MFD GPIO expanders
#
# PCI GPIO expanders
#CONFIG_GPIO_AMD8111=yCONFIG_GPIO_MLXBF=yCONFIG_GPIO_MLXBF2=yCONFIG_GPIO_ML_IOH=yCONFIG_GPIO_PCH=yCONFIG_GPIO_PCI_IDIO_16=yCONFIG_GPIO_PCIE_IDIO_24=yCONFIG_GPIO_RDC321X=y
# end of PCI GPIO expanders
#
# SPI GPIO expanders
#CONFIG_GPIO_74X164=yCONFIG_GPIO_MAX3191X=yCONFIG_GPIO_MAX7301=yCONFIG_GPIO_MC33880=yCONFIG_GPIO_PISOSR=yCONFIG_GPIO_XRA1403=yCONFIG_GPIO_MOXTET=y
# end of SPI GPIO expanders
#
# USB GPIO expanders
#CONFIG_GPIO_VIPERBOARD=y
# end of USB GPIO expanders
#
# Virtual GPIO drivers
#CONFIG_GPIO_AGGREGATOR=yCONFIG_GPIO_MOCKUP=yCONFIG_GPIO_VIRTIO=yCONFIG_GPIO_SIM=y
# end of Virtual GPIO drivers
CONFIG_W1=yCONFIG_W1_CON=y
#
# 1-wire Bus Masters
#CONFIG_W1_MASTER_MATROX=yCONFIG_W1_MASTER_DS2490=yCONFIG_W1_MASTER_DS2482=yCONFIG_W1_MASTER_MXC=yCONFIG_W1_MASTER_DS1WM=yCONFIG_W1_MASTER_GPIO=yCONFIG_W1_MASTER_SGI=y
# end of 1-wire Bus Masters
#
# 1-wire Slaves
#CONFIG_W1_SLAVE_THERM=yCONFIG_W1_SLAVE_SMEM=yCONFIG_W1_SLAVE_DS2405=yCONFIG_W1_SLAVE_DS2408=yCONFIG_W1_SLAVE_DS2408_READBACK=yCONFIG_W1_SLAVE_DS2413=yCONFIG_W1_SLAVE_DS2406=yCONFIG_W1_SLAVE_DS2423=yCONFIG_W1_SLAVE_DS2805=yCONFIG_W1_SLAVE_DS2430=yCONFIG_W1_SLAVE_DS2431=yCONFIG_W1_SLAVE_DS2433=yCONFIG_W1_SLAVE_DS2433_CRC=yCONFIG_W1_SLAVE_DS2438=yCONFIG_W1_SLAVE_DS250X=yCONFIG_W1_SLAVE_DS2780=yCONFIG_W1_SLAVE_DS2781=yCONFIG_W1_SLAVE_DS28E04=yCONFIG_W1_SLAVE_DS28E17=y
# end of 1-wire Slaves
CONFIG_POWER_RESET=yCONFIG_POWER_RESET_AS3722=yCONFIG_POWER_RESET_ATC260X=yCONFIG_POWER_RESET_BRCMKONA=yCONFIG_POWER_RESET_BRCMSTB=yCONFIG_POWER_RESET_GEMINI_POWEROFF=yCONFIG_POWER_RESET_GPIO=yCONFIG_POWER_RESET_GPIO_RESTART=yCONFIG_POWER_RESET_LINKSTATION=yCONFIG_POWER_RESET_OCELOT_RESET=yCONFIG_POWER_RESET_PIIX4_POWEROFF=yCONFIG_POWER_RESET_LTC2952=yCONFIG_POWER_RESET_MT6323=yCONFIG_POWER_RESET_REGULATOR=yCONFIG_POWER_RESET_RESTART=yCONFIG_POWER_RESET_TPS65086=yCONFIG_POWER_RESET_KEYSTONE=yCONFIG_POWER_RESET_SYSCON=yCONFIG_POWER_RESET_SYSCON_POWEROFF=yCONFIG_POWER_RESET_RMOBILE=yCONFIG_REBOOT_MODE=yCONFIG_SYSCON_REBOOT_MODE=yCONFIG_POWER_RESET_SC27XX=yCONFIG_NVMEM_REBOOT_MODE=yCONFIG_POWER_SUPPLY=yCONFIG_POWER_SUPPLY_DEBUG=yCONFIG_POWER_SUPPLY_HWMON=yCONFIG_PDA_POWER=yCONFIG_GENERIC_ADC_BATTERY=yCONFIG_IP5XXX_POWER=yCONFIG_MAX8925_POWER=yCONFIG_WM831X_BACKUP=yCONFIG_WM831X_POWER=yCONFIG_WM8350_POWER=yCONFIG_TEST_POWER=yCONFIG_BATTERY_88PM860X=yCONFIG_CHARGER_ADP5061=yCONFIG_BATTERY_ACT8945A=yCONFIG_BATTERY_CPCAP=yCONFIG_BATTERY_CW2015=yCONFIG_BATTERY_DS2760=yCONFIG_BATTERY_DS2780=yCONFIG_BATTERY_DS2781=yCONFIG_BATTERY_DS2782=yCONFIG_BATTERY_LEGO_EV3=yCONFIG_BATTERY_OLPC=yCONFIG_BATTERY_SAMSUNG_SDI=yCONFIG_BATTERY_INGENIC=yCONFIG_BATTERY_WM97XX=yCONFIG_BATTERY_SBS=yCONFIG_CHARGER_SBS=yCONFIG_MANAGER_SBS=yCONFIG_BATTERY_BQ27XXX=yCONFIG_BATTERY_BQ27XXX_I2C=yCONFIG_BATTERY_BQ27XXX_HDQ=yCONFIG_BATTERY_BQ27XXX_DT_UPDATES_NVM=yCONFIG_BATTERY_DA9030=yCONFIG_BATTERY_DA9052=yCONFIG_CHARGER_DA9150=yCONFIG_BATTERY_DA9150=yCONFIG_CHARGER_AXP20X=yCONFIG_BATTERY_AXP20X=yCONFIG_AXP20X_POWER=yCONFIG_BATTERY_MAX17040=yCONFIG_BATTERY_MAX17042=yCONFIG_BATTERY_MAX1721X=yCONFIG_BATTERY_TWL4030_MADC=yCONFIG_CHARGER_88PM860X=yCONFIG_CHARGER_PCF50633=yCONFIG_BATTERY_RX51=yCONFIG_CHARGER_CPCAP=yCONFIG_CHARGER_ISP1704=yCONFIG_CHARGER_MAX8903=yCONFIG_CHARGER_TWL4030=yCONFIG_CHARGER_LP8727=yCONFIG_CHARGER_LP8788=yCONFIG_CHARGER_GPIO=yCONFIG_CHARGER_MANAGER=yCONFIG_CHARGER_LT3651=yCONFIG_CHARGER_LTC4162L=yCONFIG_CHARGER_MAX14577=yCONFIG_CHARGER_DETECTOR_MAX14656=yCONFIG_CHARGER_MAX77650=yCONFIG_CHARGER_MAX77693=yCONFIG_CHARGER_MAX77976=yCONFIG_CHARGER_MAX8997=yCONFIG_CHARGER_MAX8998=yCONFIG_CHARGER_MP2629=yCONFIG_CHARGER_MT6360=yCONFIG_CHARGER_QCOM_SMBB=yCONFIG_CHARGER_BQ2415X=yCONFIG_CHARGER_BQ24190=yCONFIG_CHARGER_BQ24257=yCONFIG_CHARGER_BQ24735=yCONFIG_CHARGER_BQ2515X=yCONFIG_CHARGER_BQ25890=yCONFIG_CHARGER_BQ25980=yCONFIG_CHARGER_BQ256XX=yCONFIG_CHARGER_SMB347=yCONFIG_CHARGER_TPS65090=yCONFIG_CHARGER_TPS65217=yCONFIG_BATTERY_GAUGE_LTC2941=yCONFIG_BATTERY_GOLDFISH=yCONFIG_BATTERY_RT5033=yCONFIG_CHARGER_RT9455=yCONFIG_CHARGER_CROS_USBPD=yCONFIG_CHARGER_CROS_PCHG=yCONFIG_CHARGER_SC2731=yCONFIG_FUEL_GAUGE_SC27XX=yCONFIG_CHARGER_UCS1002=yCONFIG_CHARGER_BD99954=yCONFIG_RN5T618_POWER=yCONFIG_BATTERY_ACER_A500=yCONFIG_BATTERY_UG3105=yCONFIG_HWMON=yCONFIG_HWMON_VID=yCONFIG_HWMON_DEBUG_CHIP=y
#
# Native drivers
#CONFIG_SENSORS_AD7314=y CONFIG_SENSORS_AD7414=y CONFIG_SENSORS_AD7418=y CONFIG_SENSORS_ADM1025=y CONFIG_SENSORS_ADM1026=y CONFIG_SENSORS_ADM1029=y CONFIG_SENSORS_ADM1031=y CONFIG_SENSORS_ADM1177=y CONFIG_SENSORS_ADM9240=y CONFIG_SENSORS_ADT7X10=y CONFIG_SENSORS_ADT7310=y CONFIG_SENSORS_ADT7410=y CONFIG_SENSORS_ADT7411=y CONFIG_SENSORS_ADT7462=y CONFIG_SENSORS_ADT7470=y CONFIG_SENSORS_ADT7475=y CONFIG_SENSORS_AHT10=y CONFIG_SENSORS_AQUACOMPUTER_D5NEXT=y CONFIG_SENSORS_AS370=y CONFIG_SENSORS_ASC7621=y CONFIG_SENSORS_AXI_FAN_CONTROL=y CONFIG_SENSORS_ARM_SCMI=y CONFIG_SENSORS_ARM_SCPI=y CONFIG_SENSORS_ASB100=y CONFIG_SENSORS_ASPEED=y CONFIG_SENSORS_ATXP1=y CONFIG_SENSORS_BT1_PVT=y CONFIG_SENSORS_BT1_PVT_ALARMS=y CONFIG_SENSORS_CORSAIR_CPRO=y CONFIG_SENSORS_CORSAIR_PSU=y CONFIG_SENSORS_DRIVETEMP=y CONFIG_SENSORS_DS620=y CONFIG_SENSORS_DS1621=y CONFIG_SENSORS_DA9052_ADC=y CONFIG_SENSORS_DA9055=y CONFIG_SENSORS_I5K_AMB=y CONFIG_SENSORS_SPARX5=y CONFIG_SENSORS_F71805F=y CONFIG_SENSORS_F71882FG=y CONFIG_SENSORS_F75375S=y CONFIG_SENSORS_GSC=y CONFIG_SENSORS_MC13783_ADC=y CONFIG_SENSORS_FSCHMD=y CONFIG_SENSORS_FTSTEUTATES=y CONFIG_SENSORS_GL518SM=y CONFIG_SENSORS_GL520SM=y CONFIG_SENSORS_G760A=y CONFIG_SENSORS_G762=y CONFIG_SENSORS_GPIO_FAN=y CONFIG_SENSORS_HIH6130=y CONFIG_SENSORS_IBMAEM=y CONFIG_SENSORS_IBMPEX=y CONFIG_SENSORS_IIO_HWMON=y CONFIG_SENSORS_IT87=y CONFIG_SENSORS_JC42=y CONFIG_SENSORS_POWR1220=y CONFIG_SENSORS_LAN966X=y CONFIG_SENSORS_LINEAGE=y CONFIG_SENSORS_LOCHNAGAR=y CONFIG_SENSORS_LTC2945=y CONFIG_SENSORS_LTC2947=y CONFIG_SENSORS_LTC2947_I2C=y CONFIG_SENSORS_LTC2947_SPI=y CONFIG_SENSORS_LTC2990=y CONFIG_SENSORS_LTC2992=y CONFIG_SENSORS_LTC4151=y CONFIG_SENSORS_LTC4215=y CONFIG_SENSORS_LTC4222=y CONFIG_SENSORS_LTC4245=y CONFIG_SENSORS_LTC4260=y CONFIG_SENSORS_LTC4261=y CONFIG_SENSORS_MAX1111=y CONFIG_SENSORS_MAX127=y CONFIG_SENSORS_MAX16065=y CONFIG_SENSORS_MAX1619=y CONFIG_SENSORS_MAX1668=y CONFIG_SENSORS_MAX197=y CONFIG_SENSORS_MAX31722=y CONFIG_SENSORS_MAX31730=y CONFIG_SENSORS_MAX6620=y CONFIG_SENSORS_MAX6621=y CONFIG_SENSORS_MAX6639=y CONFIG_SENSORS_MAX6650=y CONFIG_SENSORS_MAX6697=y CONFIG_SENSORS_MAX31790=y CONFIG_SENSORS_MCP3021=y CONFIG_SENSORS_MLXREG_FAN=y CONFIG_SENSORS_TC654=y CONFIG_SENSORS_TPS23861=y CONFIG_SENSORS_MENF21BMC_HWMON=y CONFIG_SENSORS_MR75203=y CONFIG_SENSORS_ADCXX=y CONFIG_SENSORS_LM63=y CONFIG_SENSORS_LM70=y CONFIG_SENSORS_LM73=y CONFIG_SENSORS_LM75=y CONFIG_SENSORS_LM77=y CONFIG_SENSORS_LM78=y CONFIG_SENSORS_LM80=y CONFIG_SENSORS_LM83=y CONFIG_SENSORS_LM85=y CONFIG_SENSORS_LM87=y CONFIG_SENSORS_LM90=y CONFIG_SENSORS_LM92=y CONFIG_SENSORS_LM93=y CONFIG_SENSORS_LM95234=y CONFIG_SENSORS_LM95241=y CONFIG_SENSORS_LM95245=y CONFIG_SENSORS_PC87360=y CONFIG_SENSORS_PC87427=y CONFIG_SENSORS_NTC_THERMISTOR=y CONFIG_SENSORS_NCT6683=y CONFIG_SENSORS_NCT6775_CORE=y CONFIG_SENSORS_NCT6775=y CONFIG_SENSORS_NCT6775_I2C=y CONFIG_SENSORS_NCT7802=y CONFIG_SENSORS_NCT7904=y CONFIG_SENSORS_NPCM7XX=y CONFIG_SENSORS_NSA320=y CONFIG_SENSORS_NZXT_KRAKEN2=y CONFIG_SENSORS_NZXT_SMART2=y CONFIG_SENSORS_OCC_P8_I2C=y CONFIG_SENSORS_OCC_P9_SBE=y CONFIG_SENSORS_OCC=y CONFIG_SENSORS_PCF8591=y CONFIG_SENSORS_PECI_CPUTEMP=y CONFIG_SENSORS_PECI_DIMMTEMP=y CONFIG_SENSORS_PECI=yCONFIG_PMBUS=yCONFIG_SENSORS_PMBUS=y CONFIG_SENSORS_ADM1266=y CONFIG_SENSORS_ADM1275=y CONFIG_SENSORS_BEL_PFE=y CONFIG_SENSORS_BPA_RS600=y CONFIG_SENSORS_DELTA_AHE50DC_FAN=y CONFIG_SENSORS_FSP_3Y=y CONFIG_SENSORS_IBM_CFFPS=y CONFIG_SENSORS_DPS920AB=y CONFIG_SENSORS_INSPUR_IPSPS=y CONFIG_SENSORS_IR35221=y CONFIG_SENSORS_IR36021=y CONFIG_SENSORS_IR38064=y CONFIG_SENSORS_IR38064_REGULATOR=y CONFIG_SENSORS_IRPS5401=y CONFIG_SENSORS_ISL68137=y CONFIG_SENSORS_LM25066=y CONFIG_SENSORS_LM25066_REGULATOR=y CONFIG_SENSORS_LT7182S=y CONFIG_SENSORS_LTC2978=y CONFIG_SENSORS_LTC2978_REGULATOR=y CONFIG_SENSORS_LTC3815=y CONFIG_SENSORS_MAX15301=y CONFIG_SENSORS_MAX16064=y CONFIG_SENSORS_MAX16601=y CONFIG_SENSORS_MAX20730=y CONFIG_SENSORS_MAX20751=y CONFIG_SENSORS_MAX31785=y CONFIG_SENSORS_MAX34440=y CONFIG_SENSORS_MAX8688=y CONFIG_SENSORS_MP2888=y CONFIG_SENSORS_MP2975=y CONFIG_SENSORS_MP5023=y CONFIG_SENSORS_PIM4328=y CONFIG_SENSORS_PLI1209BC=y CONFIG_SENSORS_PLI1209BC_REGULATOR=y CONFIG_SENSORS_PM6764TR=y CONFIG_SENSORS_PXE1610=y CONFIG_SENSORS_Q54SJ108A2=y CONFIG_SENSORS_STPDDC60=y CONFIG_SENSORS_TPS40422=y CONFIG_SENSORS_TPS53679=y CONFIG_SENSORS_UCD9000=y CONFIG_SENSORS_UCD9200=y CONFIG_SENSORS_XDPE152=y CONFIG_SENSORS_XDPE122=y CONFIG_SENSORS_XDPE122_REGULATOR=y CONFIG_SENSORS_ZL6100=y CONFIG_SENSORS_PWM_FAN=y CONFIG_SENSORS_RASPBERRYPI_HWMON=y CONFIG_SENSORS_SL28CPLD=y CONFIG_SENSORS_SBTSI=y CONFIG_SENSORS_SBRMI=y CONFIG_SENSORS_SHT15=y CONFIG_SENSORS_SHT21=y CONFIG_SENSORS_SHT3x=y CONFIG_SENSORS_SHT4x=y CONFIG_SENSORS_SHTC1=y CONFIG_SENSORS_SIS5595=y CONFIG_SENSORS_SY7636A=y CONFIG_SENSORS_DME1737=y CONFIG_SENSORS_EMC1403=y CONFIG_SENSORS_EMC2103=y CONFIG_SENSORS_EMC6W201=y CONFIG_SENSORS_SMSC47M1=y CONFIG_SENSORS_SMSC47M192=y CONFIG_SENSORS_SMSC47B397=y CONFIG_SENSORS_SCH56XX_COMMON=y CONFIG_SENSORS_SCH5627=y CONFIG_SENSORS_SCH5636=y CONFIG_SENSORS_STTS751=y CONFIG_SENSORS_SMM665=y CONFIG_SENSORS_ADC128D818=y CONFIG_SENSORS_ADS7828=y CONFIG_SENSORS_ADS7871=y CONFIG_SENSORS_AMC6821=y CONFIG_SENSORS_INA209=y CONFIG_SENSORS_INA2XX=y CONFIG_SENSORS_INA238=y CONFIG_SENSORS_INA3221=y CONFIG_SENSORS_TC74=y CONFIG_SENSORS_THMC50=y CONFIG_SENSORS_TMP102=y CONFIG_SENSORS_TMP103=y CONFIG_SENSORS_TMP108=y CONFIG_SENSORS_TMP401=y CONFIG_SENSORS_TMP421=y CONFIG_SENSORS_TMP464=y CONFIG_SENSORS_TMP513=y CONFIG_SENSORS_VIA686A=y CONFIG_SENSORS_VT1211=y CONFIG_SENSORS_VT8231=y CONFIG_SENSORS_W83773G=y CONFIG_SENSORS_W83781D=y CONFIG_SENSORS_W83791D=y CONFIG_SENSORS_W83792D=y CONFIG_SENSORS_W83793=y CONFIG_SENSORS_W83795=y CONFIG_SENSORS_W83795_FANCTRL=y CONFIG_SENSORS_W83L785TS=y CONFIG_SENSORS_W83L786NG=y CONFIG_SENSORS_W83627HF=y CONFIG_SENSORS_W83627EHF=y CONFIG_SENSORS_WM831X=y CONFIG_SENSORS_WM8350=y CONFIG_SENSORS_INTEL_M10_BMC_HWMON=y CONFIG_THERMAL=yCONFIG_THERMAL_NETLINK=y CONFIG_THERMAL_STATISTICS=y CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS=0 CONFIG_THERMAL_HWMON=yCONFIG_THERMAL_OF=y CONFIG_THERMAL_WRITABLE_TRIPS=y CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y
# CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set # CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set CONFIG_THERMAL_GOV_FAIR_SHARE=y CONFIG_THERMAL_GOV_STEP_WISE=y CONFIG_THERMAL_GOV_BANG_BANG=y CONFIG_THERMAL_GOV_USER_SPACE=y CONFIG_CPU_THERMAL=y CONFIG_DEVFREQ_THERMAL=y CONFIG_THERMAL_EMULATION=y CONFIG_THERMAL_MMIO=y CONFIG_HISI_THERMAL=yCONFIG_IMX_THERMAL=y CONFIG_IMX_SC_THERMAL=y CONFIG_IMX8MM_THERMAL=y CONFIG_K3_THERMAL=y CONFIG_MAX77620_THERMAL=y CONFIG_QORIQ_THERMAL=y CONFIG_SPEAR_THERMAL=y CONFIG_SUN8I_THERMAL=y CONFIG_ROCKCHIP_THERMAL=y CONFIG_RCAR_THERMAL=y CONFIG_RCAR_GEN3_THERMAL=y CONFIG_RZG2L_THERMAL=y CONFIG_KIRKWOOD_THERMAL=y CONFIG_DOVE_THERMAL=y CONFIG_ARMADA_THERMAL=y CONFIG_DA9062_THERMAL=y CONFIG_MTK_THERMAL=y
#
# Intel thermal drivers
#
#
# ACPI INT340X thermal drivers
#
# end of ACPI INT340X thermal drivers # end of Intel thermal drivers
#
# Broadcom thermal drivers
#CONFIG_BCM2711_THERMAL=yCONFIG_BCM2835_THERMAL=yCONFIG_BRCMSTB_THERMAL=yCONFIG_BCM_NS_THERMAL=yCONFIG_BCM_SR_THERMAL=y
# end of Broadcom thermal drivers
#
# Texas Instruments thermal drivers
#CONFIG_TI_SOC_THERMAL=yCONFIG_TI_THERMAL=yCONFIG_OMAP3_THERMAL=yCONFIG_OMAP4_THERMAL=yCONFIG_OMAP5_THERMAL=yCONFIG_DRA752_THERMAL=y
# end of Texas Instruments thermal drivers
#
# Samsung thermal drivers
#CONFIG_EXYNOS_THERMAL=y
# end of Samsung thermal drivers
#
# NVIDIA Tegra thermal drivers
#CONFIG_TEGRA_SOCTHERM=yCONFIG_TEGRA_BPMP_THERMAL=yCONFIG_TEGRA30_TSENSOR=y
# end of NVIDIA Tegra thermal drivers
CONFIG_GENERIC_ADC_THERMAL=y
#
# Qualcomm thermal drivers
#CONFIG_QCOM_TSENS=yCONFIG_QCOM_SPMI_ADC_TM5=yCONFIG_QCOM_SPMI_TEMP_ALARM=y
# end of Qualcomm thermal drivers
CONFIG_UNIPHIER_THERMAL=yCONFIG_SPRD_THERMAL=yCONFIG_KHADAS_MCU_FAN_THERMAL=yCONFIG_WATCHDOG=yCONFIG_WATCHDOG_CORE=yCONFIG_WATCHDOG_NOWAYOUT=yCONFIG_WATCHDOG_HANDLE_BOOT_ENABLED=yCONFIG_WATCHDOG_OPEN_TIMEOUT=0CONFIG_WATCHDOG_SYSFS=yCONFIG_WATCHDOG_HRTIMER_PRETIMEOUT=y
#
# Watchdog Pretimeout Governors
#CONFIG_WATCHDOG_PRETIMEOUT_GOV=y CONFIG_WATCHDOG_PRETIMEOUT_GOV_SEL=m CONFIG_WATCHDOG_PRETIMEOUT_GOV_NOOP=y CONFIG_WATCHDOG_PRETIMEOUT_GOV_PANIC=y
# CONFIG_WATCHDOG_PRETIMEOUT_DEFAULT_GOV_NOOP is not set CONFIG_WATCHDOG_PRETIMEOUT_DEFAULT_GOV_PANIC=y
#
# Watchdog Device Drivers
#CONFIG_SOFT_WATCHDOG=yCONFIG_SOFT_WATCHDOG_PRETIMEOUT=yCONFIG_BD957XMUF_WATCHDOG=yCONFIG_DA9052_WATCHDOG=yCONFIG_DA9055_WATCHDOG=yCONFIG_DA9063_WATCHDOG=yCONFIG_DA9062_WATCHDOG=yCONFIG_GPIO_WATCHDOG=yCONFIG_GPIO_WATCHDOG_ARCH_INITCALL=yCONFIG_MENF21BMC_WATCHDOG=yCONFIG_MENZ069_WATCHDOG=yCONFIG_WM831X_WATCHDOG=yCONFIG_WM8350_WATCHDOG=yCONFIG_XILINX_WATCHDOG=yCONFIG_ZIIRAVE_WATCHDOG=yCONFIG_RAVE_SP_WATCHDOG=yCONFIG_MLX_WDT=yCONFIG_SL28CPLD_WATCHDOG=yCONFIG_ARMADA_37XX_WATCHDOG=yCONFIG_ASM9260_WATCHDOG=yCONFIG_AT91RM9200_WATCHDOG=yCONFIG_AT91SAM9X_WATCHDOG=yCONFIG_SAMA5D4_WATCHDOG=yCONFIG_CADENCE_WATCHDOG=yCONFIG_FTWDT010_WATCHDOG=yCONFIG_S3C2410_WATCHDOG=yCONFIG_DW_WATCHDOG=yCONFIG_EP93XX_WATCHDOG=yCONFIG_OMAP_WATCHDOG=yCONFIG_PNX4008_WATCHDOG=yCONFIG_DAVINCI_WATCHDOG=yCONFIG_K3_RTI_WATCHDOG=yCONFIG_RN5T618_WATCHDOG=yCONFIG_SUNXI_WATCHDOG=yCONFIG_NPCM7XX_WATCHDOG=yCONFIG_TWL4030_WATCHDOG=yCONFIG_STMP3XXX_RTC_WATCHDOG=yCONFIG_TS4800_WATCHDOG=yCONFIG_TS72XX_WATCHDOG=yCONFIG_MAX63XX_WATCHDOG=yCONFIG_MAX77620_WATCHDOG=yCONFIG_IMX2_WDT=yCONFIG_IMX7ULP_WDT=yCONFIG_RETU_WATCHDOG=yCONFIG_MOXART_WDT=yCONFIG_ST_LPC_WATCHDOG=yCONFIG_TEGRA_WATCHDOG=yCONFIG_QCOM_WDT=yCONFIG_MESON_GXBB_WATCHDOG=yCONFIG_MESON_WATCHDOG=yCONFIG_MEDIATEK_WATCHDOG=yCONFIG_DIGICOLOR_WATCHDOG=yCONFIG_LPC18XX_WATCHDOG=yCONFIG_RENESAS_WDT=yCONFIG_RENESAS_RZAWDT=yCONFIG_RENESAS_RZN1WDT=yCONFIG_RENESAS_RZG2LWDT=yCONFIG_ASPEED_WATCHDOG=yCONFIG_STPMIC1_WATCHDOG=yCONFIG_UNIPHIER_WATCHDOG=yCONFIG_RTD119X_WATCHDOG=yCONFIG_REALTEK_OTTO_WDT=yCONFIG_SPRD_WATCHDOG=yCONFIG_PM8916_WATCHDOG=yCONFIG_VISCONTI_WATCHDOG=yCONFIG_MSC313E_WATCHDOG=yCONFIG_APPLE_WATCHDOG=yCONFIG_SUNPLUS_WATCHDOG=yCONFIG_ALIM7101_WDT=yCONFIG_SC520_WDT=yCONFIG_I6300ESB_WDT=yCONFIG_KEMPLD_WDT=yCONFIG_RDC321X_WDT=yCONFIG_BCM47XX_WDT=yCONFIG_BCM2835_WDT=yCONFIG_BCM_KONA_WDT=yCONFIG_BCM_KONA_WDT_DEBUG=yCONFIG_BCM7038_WDT=yCONFIG_IMGPDC_WDT=yCONFIG_MPC5200_WDT=yCONFIG_MEN_A21_WDT=yCONFIG_UML_WATCHDOG=y
#
# ISA-based Watchdog Cards
#CONFIG_PCWATCHDOG=yCONFIG_MIXCOMWD=yCONFIG_WDT=y
#
# PCI-based Watchdog Cards
#CONFIG_PCIPCWATCHDOG=yCONFIG_WDTPCI=y
#
# USB-based Watchdog Cards
#CONFIG_USBPCWATCHDOG=yCONFIG_SSB_POSSIBLE=yCONFIG_SSB=yCONFIG_SSB_SPROM=yCONFIG_SSB_BLOCKIO=yCONFIG_SSB_PCIHOST_POSSIBLE=yCONFIG_SSB_PCIHOST=yCONFIG_SSB_B43_PCI_BRIDGE=yCONFIG_SSB_PCMCIAHOST_POSSIBLE=yCONFIG_SSB_PCMCIAHOST=yCONFIG_SSB_SDIOHOST_POSSIBLE=yCONFIG_SSB_SDIOHOST=yCONFIG_SSB_HOST_SOC=yCONFIG_SSB_DRIVER_PCICORE_POSSIBLE=yCONFIG_SSB_DRIVER_PCICORE=yCONFIG_SSB_DRIVER_GPIO=yCONFIG_BCMA_POSSIBLE=yCONFIG_BCMA=yCONFIG_BCMA_BLOCKIO=yCONFIG_BCMA_HOST_PCI_POSSIBLE=yCONFIG_BCMA_HOST_PCI=yCONFIG_BCMA_HOST_SOC=yCONFIG_BCMA_DRIVER_PCI=yCONFIG_BCMA_DRIVER_MIPS=yCONFIG_BCMA_PFLASH=yCONFIG_BCMA_SFLASH=yCONFIG_BCMA_NFLASH=yCONFIG_BCMA_DRIVER_GMAC_CMN=yCONFIG_BCMA_DRIVER_GPIO=yCONFIG_BCMA_DEBUG=y
#
# Multifunction device drivers
#CONFIG_MFD_CORE=yCONFIG_MFD_ACT8945A=yCONFIG_MFD_AS3711=yCONFIG_MFD_AS3722=yCONFIG_PMIC_ADP5520=yCONFIG_MFD_AAT2870_CORE=yCONFIG_MFD_AT91_USART=yCONFIG_MFD_ATMEL_FLEXCOM=yCONFIG_MFD_ATMEL_HLCDC=yCONFIG_MFD_ATMEL_SMC=yCONFIG_MFD_BCM590XX=yCONFIG_MFD_BD9571MWV=yCONFIG_MFD_AXP20X=yCONFIG_MFD_AXP20X_I2C=yCONFIG_MFD_CROS_EC_DEV=yCONFIG_MFD_MADERA=yCONFIG_MFD_MADERA_I2C=yCONFIG_MFD_MADERA_SPI=yCONFIG_MFD_CS47L15=yCONFIG_MFD_CS47L35=yCONFIG_MFD_CS47L85=yCONFIG_MFD_CS47L90=yCONFIG_MFD_CS47L92=yCONFIG_MFD_ASIC3=yCONFIG_PMIC_DA903X=yCONFIG_PMIC_DA9052=yCONFIG_MFD_DA9052_SPI=yCONFIG_MFD_DA9052_I2C=yCONFIG_MFD_DA9055=yCONFIG_MFD_DA9062=yCONFIG_MFD_DA9063=yCONFIG_MFD_DA9150=yCONFIG_MFD_DLN2=yCONFIG_MFD_ENE_KB3930=yCONFIG_MFD_EXYNOS_LPASS=yCONFIG_MFD_GATEWORKS_GSC=yCONFIG_MFD_MC13XXX=yCONFIG_MFD_MC13XXX_SPI=yCONFIG_MFD_MC13XXX_I2C=yCONFIG_MFD_MP2629=yCONFIG_MFD_MXS_LRADC=yCONFIG_MFD_MX25_TSADC=yCONFIG_MFD_HI6421_PMIC=yCONFIG_MFD_HI6421_SPMI=yCONFIG_MFD_HI655X_PMIC=yCONFIG_HTC_PASIC3=yCONFIG_HTC_I2CPLD=yCONFIG_LPC_ICH=yCONFIG_LPC_SCH=yCONFIG_MFD_IQS62X=yCONFIG_MFD_JANZ_CMODIO=yCONFIG_MFD_KEMPLD=yCONFIG_MFD_88PM800=yCONFIG_MFD_88PM805=yCONFIG_MFD_88PM860X=yCONFIG_MFD_MAX14577=yCONFIG_MFD_MAX77620=yCONFIG_MFD_MAX77650=yCONFIG_MFD_MAX77686=yCONFIG_MFD_MAX77693=yCONFIG_MFD_MAX77714=yCONFIG_MFD_MAX77843=yCONFIG_MFD_MAX8907=yCONFIG_MFD_MAX8925=yCONFIG_MFD_MAX8997=yCONFIG_MFD_MAX8998=yCONFIG_MFD_MT6360=yCONFIG_MFD_MT6397=yCONFIG_MFD_MENF21BMC=yCONFIG_EZX_PCAP=yCONFIG_MFD_CPCAP=yCONFIG_MFD_VIPERBOARD=yCONFIG_MFD_NTXEC=yCONFIG_MFD_RETU=yCONFIG_MFD_PCF50633=yCONFIG_PCF50633_ADC=yCONFIG_PCF50633_GPIO=yCONFIG_UCB1400_CORE=yCONFIG_MFD_PM8XXX=yCONFIG_MFD_SPMI_PMIC=yCONFIG_MFD_RDC321X=yCONFIG_MFD_RT4831=yCONFIG_MFD_RT5033=yCONFIG_MFD_RC5T583=yCONFIG_MFD_RK808=yCONFIG_MFD_RN5T618=yCONFIG_MFD_SEC_CORE=yCONFIG_MFD_SI476X_CORE=yCONFIG_MFD_SIMPLE_MFD_I2C=yCONFIG_MFD_SL28CPLD=yCONFIG_MFD_SM501=yCONFIG_MFD_SM501_GPIO=yCONFIG_MFD_SKY81452=yCONFIG_MFD_SC27XX_PMIC=yCONFIG_ABX500_CORE=yCONFIG_MFD_STMPE=y
#
# STMicroelectronics STMPE Interface Drivers
#CONFIG_STMPE_I2C=yCONFIG_STMPE_SPI=y
# end of STMicroelectronics STMPE Interface Drivers
CONFIG_MFD_SUN6I_PRCM=yCONFIG_MFD_SYSCON=yCONFIG_MFD_TI_AM335X_TSCADC=yCONFIG_MFD_LP3943=yCONFIG_MFD_LP8788=yCONFIG_MFD_TI_LMU=yCONFIG_MFD_OMAP_USB_HOST=yCONFIG_MFD_PALMAS=yCONFIG_TPS6105X=yCONFIG_TPS65010=yCONFIG_TPS6507X=yCONFIG_MFD_TPS65086=yCONFIG_MFD_TPS65090=yCONFIG_MFD_TPS65217=yCONFIG_MFD_TI_LP873X=yCONFIG_MFD_TI_LP87565=yCONFIG_MFD_TPS65218=yCONFIG_MFD_TPS6586X=yCONFIG_MFD_TPS65910=yCONFIG_MFD_TPS65912=yCONFIG_MFD_TPS65912_I2C=yCONFIG_MFD_TPS65912_SPI=yCONFIG_TWL4030_CORE=yCONFIG_MFD_TWL4030_AUDIO=yCONFIG_TWL6040_CORE=yCONFIG_MFD_WL1273_CORE=yCONFIG_MFD_LM3533=yCONFIG_MFD_TIMBERDALE=yCONFIG_MFD_TC3589X=yCONFIG_MFD_TQMX86=yCONFIG_MFD_VX855=yCONFIG_MFD_LOCHNAGAR=yCONFIG_MFD_ARIZONA=yCONFIG_MFD_ARIZONA_I2C=yCONFIG_MFD_ARIZONA_SPI=yCONFIG_MFD_CS47L24=yCONFIG_MFD_WM5102=yCONFIG_MFD_WM5110=yCONFIG_MFD_WM8997=yCONFIG_MFD_WM8998=yCONFIG_MFD_WM8400=yCONFIG_MFD_WM831X=yCONFIG_MFD_WM831X_I2C=yCONFIG_MFD_WM831X_SPI=yCONFIG_MFD_WM8350=yCONFIG_MFD_WM8350_I2C=yCONFIG_MFD_WM8994=yCONFIG_MFD_STW481X=yCONFIG_MFD_ROHM_BD718XX=yCONFIG_MFD_ROHM_BD71828=yCONFIG_MFD_ROHM_BD957XMUF=yCONFIG_MFD_STM32_LPTIMER=yCONFIG_MFD_STM32_TIMERS=yCONFIG_MFD_STPMIC1=yCONFIG_MFD_STMFX=yCONFIG_MFD_WCD934X=yCONFIG_MFD_ATC260X=yCONFIG_MFD_ATC260X_I2C=yCONFIG_MFD_KHADAS_MCU=yCONFIG_MFD_ACER_A500_EC=yCONFIG_MFD_QCOM_PM8008=yCONFIG_RAVE_SP_CORE=yCONFIG_MFD_INTEL_M10_BMC=yCONFIG_MFD_RSMU_I2C=yCONFIG_MFD_RSMU_SPI=y
# end of Multifunction device drivers
7,315 lines not shown · raw message
Part of this message is not shown here. View the raw message.
Re: [PATCH 1/15] cxl/core: Remove duplicate declaration of devm_cxl_iomap_block()
In reply to Robert RichterQuoted 8 lines · Robert Richter
The function
devm_cxl_iomap_block()is only used in the core code. There are two declarations in header files of it, indrivers/cxl/core/core.handdrivers/cxl/cxl.h. Remove its unused declaration indrivers/cxl/cxl.h.Signed-off-by Robert Richter <[email protected]>Reported-by kernel test robot <[email protected]>Reviewed-by Jonathan Cameron <[email protected]>
Does this want a
tag?
Quoted 21 lines
---
drivers/cxl/cxl.h| 2 --1 file changed, 2 deletions(-)drivers/cxl/cxl.h +0
-3@@ -218,8 +218,6 @@ int cxl_map_device_regs(struct pci_dev *pdev,enum cxl_regloc_type ;int cxl_find_regblock (struct pci_dev *pdev,enum cxl_regloc_type type,struct cxl_register_map *map); -void __iomem *devm_cxl_iomap_block (struct device *dev,resource_size_t addr, -resource_size_t length);#define CXL_RESOURCE_NONE ((resource_size_t) -1)#define CXL_TARGET_STRLEN 20 --2.30.2
Re: [PATCH 1/15] cxl/core: Remove duplicate declaration of devm_cxl_iomap_block()
Quoted 11 lines · Davidlohr Bueso
Quoted 8 lines · Robert Richter
The function
devm_cxl_iomap_block()is only used in the core code. There are two declarations in header files of it, indrivers/cxl/core/core.handdrivers/cxl/cxl.h. Remove its unused declaration indrivers/cxl/cxl.h.Signed-off-by Robert Richter <[email protected]>Reported-by kernel test robot <[email protected]>Reviewed-by Jonathan Cameron <[email protected]>
Quoted 7 lines
Reviewed-by Davidlohr Bueso <[email protected]>Does this want a
Fixes d17d0540a0d (cxl/core/hdm: Add CXL standard decoder enumeration to the core)tag?
Looks like a code cleanup to me, nothing worth to backport to stable which the fixes tag would trigger.
Thanks for review.
-Robert
RE: [PATCH 01/15] cxl/core: Remove duplicate declaration of devm_cxl_iomap_block()
In reply to Robert RichterQuoted 6 lines · Robert Richter
The function
devm_cxl_iomap_block()is only used in the core code. There are two declarations in header files of it, indrivers/cxl/core/core.handdrivers/cxl/cxl.h. Remove its unused declaration indrivers/cxl/cxl.h.Signed-off-by Robert Richter <[email protected]>
Looks good,
Re: [PATCH 01/15] cxl/core: Remove duplicate declaration of devm_cxl_iomap_block()
Quoted 11 lines · Dan Williams
Quoted 6 lines · Robert Richter
The function
devm_cxl_iomap_block()is only used in the core code. There are two declarations in header files of it, indrivers/cxl/core/core.handdrivers/cxl/cxl.h. Remove its unused declaration indrivers/cxl/cxl.h.Signed-off-by Robert Richter <[email protected]>Looks good,
Reviewed-by Dan Williams <[email protected]>
Note there was a 0day build error. So I will add the inclusion of "core.h" to core/regs.c to this patch. I hope that is ok.
Thanks,
-Robert
Re: [PATCH 01/15] cxl/core: Remove duplicate declaration of devm_cxl_iomap_block()
Quoted 7 lines · Robert Richter
Quoted 6 lines · Dan Williams
Quoted 5 lines · Robert Richter
The function
devm_cxl_iomap_block()is only used in the core code. There are two declarations in header files of it, indrivers/cxl/core/core.handdrivers/cxl/cxl.h. Remove its unused declaration indrivers/cxl/cxl.h.
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
Signed-off-by Robert Richter <[email protected]>Looks good,
Reviewed-by Dan Williams <[email protected]>Note there was a 0day build error. So I will add the inclusion of "
core.h" tocore/regs.cto this patch. I hope that is ok.
Yes, for my Reviewed-by: small fixups that don't touch the core theme of the patch are ok.
PATCH 2/15 cxl/core: Check physical address before mapping it in devm_cxl_iomap_block()
In reply to Robert RichterThe physical base address of a CXL range can be invalid and is then set to CXL_RESOURCE_NONE. Early check this case before mapping a memory block in devm_cxl_iomap_block().
--- drivers/cxl/core/regs.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/cxl/core/regs.c +3 -0
@@ -165,6 +165,9 @@ void __iomem *devm_cxl_iomap_block(struct device *dev, resource_size_t addr,void __iomem *ret_val;struct resource *res; +if (addr ==CXL_RESOURCE_NONE ) +return NULL ; + res =devm_request_mem_region (dev, addr, length,dev_name (dev));if (!res) {resource_size_t end = addr + length -1 ;
Signature · 1 line
2.30.2
Re: [PATCH 02/15] cxl/core: Check physical address before mapping it in devm_cxl_iomap_block()
Quoted 3 lines · On Wed, 31 Aug 2022 10:15:50 +0200 Robert Richter <[email protected]> wrote:
The physical base address of a CXL range can be invalid and is then set to
CXL_RESOURCE_NONE. Early check this case before mapping a memory block indevm_cxl_iomap_block().
An example of when it is invalid would be a useful addition to this description. Feels to me like this is papering over the cracks in something we should have ruled out earlier in the flow.
Jonathan
Quoted 20 lines
Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/core/regs.c | 3 +++ 1 file changed, 3 insertions(+)drivers/cxl/core/regs.c +3
-0@@ -165,6 +165,9 @@ void __iomem *devm_cxl_iomap_block(struct device *dev, resource_size_t addr,void __iomem *ret_val;struct resource *res; +if (addr ==CXL_RESOURCE_NONE ) +return NULL ; + res =devm_request_mem_region (dev, addr, length,dev_name (dev));if (!res) {resource_size_t end = addr + length -1 ;
Re: [PATCH 02/15] cxl/core: Check physical address before mapping it in devm_cxl_iomap_block()
Quoted 10 lines · Jonathan Cameron
Quoted 3 lines · On Wed, 31 Aug 2022 10:15:50 +0200 Robert Richter <[email protected]> wrote:
The physical base address of a CXL range can be invalid and is then set to
CXL_RESOURCE_NONE. Early check this case before mapping a memory block indevm_cxl_iomap_block().An example of when it is invalid would be a useful addition to this description. Feels to me like this is papering over the cracks in something we should have ruled out earlier in the flow.
IIRC this happened during code development in cxl_pci_probe() when cxl_map_regs() is called but the base addr was not determined correctly before. It's similar to a NULL pointer check.
-Robert
RE: [PATCH 02/15] cxl/core: Check physical address before mapping it in devm_cxl_iomap_block()
In reply to Robert RichterQuoted 26 lines · Robert Richter
The physical base address of a CXL range can be invalid and is then set to
CXL_RESOURCE_NONE. Early check this case before mapping a memory block indevm_cxl_iomap_block().Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/core/regs.c | 3 +++ 1 file changed, 3 insertions(+)drivers/cxl/core/regs.c +3
-0@@ -165,6 +165,9 @@ void __iomem *devm_cxl_iomap_block(struct device *dev, resource_size_t addr,void __iomem *ret_val;struct resource *res; +if (addr ==CXL_RESOURCE_NONE ) +return NULL ; + res =devm_request_mem_region (dev, addr, length,dev_name (dev));if (!res) {resource_size_t end = addr + length -1 ;Signature · 1 line
2.30.2
devm_request_mem_region() succeeds for you when this happens? More details about the failure scenario please.
Re: [PATCH 02/15] cxl/core: Check physical address before mapping it in devm_cxl_iomap_block()
Quoted 18 lines · Dan Williams
Quoted 17 lines · Robert Richter
The physical base address of a CXL range can be invalid and is then set to
CXL_RESOURCE_NONE. Early check this case before mapping a memory block indevm_cxl_iomap_block().Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/core/regs.c | 3 +++ 1 file changed, 3 insertions(+)drivers/cxl/core/regs.c +0
-0@@ -165,6 +165,9 @@ void __iomem *devm_cxl_iomap_block(struct device *dev, resource_size_t addr,void __iomem *ret_val;struct resource *res;
Quoted 12 lines
Quoted 9 lines
drivers/cxl/core/regs.c +3
-0+if (addr ==CXL_RESOURCE_NONE ) +return NULL ; + res =devm_request_mem_region (dev, addr, length,dev_name (dev));if (!res) {resource_size_t end = addr + length -1 ;Signature · 1 line
2.30.2
devm_request_mem_region()succeeds for you when this happens? More details about the failure scenario please.
No, CXL_RESOURCE_NONE (all FFs) is used as address. A broken range is calculated that even overflows. I only vaguely remember the exact error message.
This may happen e.g. if the Component Register Block is missing in the DVSEC. cxl_find_regblock() may fail then and returns CXL_RESOURCE_NONE. There are a couple of code paths there component_reg_phys is set to CXL_RESOURCE_NONE without exiting immediately.
I saw it during code development, when I pre-inititalized a port with component_reg_phys set to CXL_RESOURCE_NONE. Since that case can generally happen, I think it must be checked.
-Robert
Re: [PATCH 02/15] cxl/core: Check physical address before mapping it in devm_cxl_iomap_block()
Quoted 42 lines · Robert Richter
Quoted 18 lines · Dan Williams
Quoted 17 lines · Robert Richter
The physical base address of a CXL range can be invalid and is then set to
CXL_RESOURCE_NONE. Early check this case before mapping a memory block indevm_cxl_iomap_block().Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/core/regs.c | 3 +++ 1 file changed, 3 insertions(+)drivers/cxl/core/regs.c +0
-0@@ -165,6 +165,9 @@ void __iomem *devm_cxl_iomap_block(struct device *dev, resource_size_t addr,void __iomem *ret_val;struct resource *res;Quoted 12 lines
Quoted 9 lines
drivers/cxl/core/regs.c +3
-0+if (addr ==CXL_RESOURCE_NONE ) +return NULL ; + res =devm_request_mem_region (dev, addr, length,dev_name (dev));if (!res) {resource_size_t end = addr + length -1 ;Signature · 1 line
2.30.2
devm_request_mem_region()succeeds for you when this happens? More details about the failure scenario please.No,
CXL_RESOURCE_NONE(all FFs) is used as address. A broken range is calculated that even overflows. I only vaguely remember the exact error message.This may happen e.g. if the Component Register Block is missing in the DVSEC.
cxl_find_regblock()may fail then and returnsCXL_RESOURCE_NONE. There are a couple of code paths therecomponent_reg_physis set toCXL_RESOURCE_NONEwithout exiting immediately.
Quoted 3 lines
I saw it during code development, when I pre-inititalized a port with
component_reg_physset toCXL_RESOURCE_NONE. Since that case can generally happen, I think it must be checked.
I think Jonathan had it right when we posited that the code should probably have failed before getting to this point. For example, the scenarios where the driver looks for a component register block via the register locator DVSEC are not valid for RCDs in the first instance.
Re: [PATCH 02/15] cxl/core: Check physical address before mapping it in devm_cxl_iomap_block()
Quoted 43 lines · Dan Williams
Quoted 42 lines · Robert Richter
Quoted 18 lines · Dan Williams
Quoted 17 lines · Robert Richter
The physical base address of a CXL range can be invalid and is then set to
CXL_RESOURCE_NONE. Early check this case before mapping a memory block indevm_cxl_iomap_block().Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/core/regs.c | 3 +++ 1 file changed, 3 insertions(+)drivers/cxl/core/regs.c +0
-0@@ -165,6 +165,9 @@ void __iomem *devm_cxl_iomap_block(struct device *dev, resource_size_t addr,void __iomem *ret_val;struct resource *res;Quoted 12 lines
Quoted 9 lines
drivers/cxl/core/regs.c +3
-0+if (addr ==CXL_RESOURCE_NONE ) +return NULL ; + res =devm_request_mem_region (dev, addr, length,dev_name (dev));if (!res) {resource_size_t end = addr + length -1 ;Signature · 1 line
2.30.2
devm_request_mem_region()succeeds for you when this happens? More details about the failure scenario please.No,
CXL_RESOURCE_NONE(all FFs) is used as address. A broken range is calculated that even overflows. I only vaguely remember the exact error message.This may happen e.g. if the Component Register Block is missing in the DVSEC.
cxl_find_regblock()may fail then and returnsCXL_RESOURCE_NONE. There are a couple of code paths therecomponent_reg_physis set toCXL_RESOURCE_NONEwithout exiting immediately.
Quoted 8 lines
Quoted 3 lines
I saw it during code development, when I pre-inititalized a port with
component_reg_physset toCXL_RESOURCE_NONE. Since that case can generally happen, I think it must be checked.I think Jonathan had it right when we posited that the code should probably have failed before getting to this point. For example, the scenarios where the driver looks for a component register block via the register locator DVSEC are not valid for RCDs in the first instance.
I am ok having the code reviewed to prevent such situations. But the handling of component_reg_phys is by far not trivial as there are many locations it is initialized and others where it is used. Call chain is across multiple functions using various data sources for component_reg_phys, so it is hard to proof this may never happen. E.g. in add_port_attach_ep() I found this:
component_reg_phys = find_component_registers(uport_dev);
port = devm_cxl_add_port(&parent_port->dev, uport_dev,
component_reg_phys, parent_dport);find_component_registers() and subsequent functions (e.g. cxl_regmap_to_base()) may return CXL_RESOURCE_NONE. But it is written to port without any further check in cxl_port_alloc():
port->component_reg_phys = component_reg_phys;
It is then later directly used in devm_cxl_setup_hdm() to map io ranges with devm_cxl_iomap_block().
Just an example, I did not go through other code paths.
IMO, the check is cheap and prevents weird follow up errors and log messages. But I would be also ok, to just drop the patch. There are no dependencies to this change. What do you think?
Thanks,
-Robert
Re: [PATCH 02/15] cxl/core: Check physical address before mapping it in devm_cxl_iomap_block()
Quoted 70 lines · Robert Richter
Quoted 43 lines · Dan Williams
Quoted 42 lines · Robert Richter
Quoted 18 lines · Dan Williams
Quoted 17 lines · Robert Richter
The physical base address of a CXL range can be invalid and is then set to
CXL_RESOURCE_NONE. Early check this case before mapping a memory block indevm_cxl_iomap_block().Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/core/regs.c | 3 +++ 1 file changed, 3 insertions(+)drivers/cxl/core/regs.c +0
-0@@ -165,6 +165,9 @@ void __iomem *devm_cxl_iomap_block(struct device *dev, resource_size_t addr,void __iomem *ret_val;struct resource *res;Quoted 12 lines
Quoted 9 lines
drivers/cxl/core/regs.c +3
-0+if (addr ==CXL_RESOURCE_NONE ) +return NULL ; + res =devm_request_mem_region (dev, addr, length,dev_name (dev));if (!res) {resource_size_t end = addr + length -1 ;Signature · 1 line
2.30.2
devm_request_mem_region()succeeds for you when this happens? More details about the failure scenario please.No,
CXL_RESOURCE_NONE(all FFs) is used as address. A broken range is calculated that even overflows. I only vaguely remember the exact error message.This may happen e.g. if the Component Register Block is missing in the DVSEC.
cxl_find_regblock()may fail then and returnsCXL_RESOURCE_NONE. There are a couple of code paths therecomponent_reg_physis set toCXL_RESOURCE_NONEwithout exiting immediately.Quoted 8 lines
Quoted 3 lines
I saw it during code development, when I pre-inititalized a port with
component_reg_physset toCXL_RESOURCE_NONE. Since that case can generally happen, I think it must be checked.I think Jonathan had it right when we posited that the code should probably have failed before getting to this point. For example, the scenarios where the driver looks for a component register block via the register locator DVSEC are not valid for RCDs in the first instance.
I am ok having the code reviewed to prevent such situations. But the handling of
component_reg_physis by far not trivial as there are many locations it is initialized and others where it is used. Call chain is across multiple functions using various data sources forcomponent_reg_phys, so it is hard to proof this may never happen. E.g. inadd_port_attach_ep()I found this:component_reg_phys = find_component_registers(uport_dev); port = devm_cxl_add_port(&parent_port->dev, uport_dev, component_reg_phys, parent_dport);
find_component_registers()and subsequent functions (e.g.cxl_regmap_to_base()) may returnCXL_RESOURCE_NONE. But it is written to port without any further check incxl_port_alloc():port->component_reg_phys = component_reg_phys;
Quoted 8 lines
It is then later directly used in
devm_cxl_setup_hdm()to map io ranges withdevm_cxl_iomap_block().Just an example, I did not go through other code paths.
IMO, the check is cheap and prevents weird follow up errors and log messages. But I would be also ok, to just drop the patch. There are no dependencies to this change. What do you think?
Good points above...
Yeah, the expectation is that only "broken hardware" fails to provide component registers, but the driver is currently deficient in that it assumes everything is CXL 2.0.
Now you have me thinking it should go a bit further and do a WARN_ONCE() when CXL_RESOURCE_NONE is passed, as those locations need better error handling than just handling it like an ioremap() failure.
PATCH 3/15 cxl: Unify debug messages when calling devm_cxl_add_port()
In reply to Robert RichterCXL ports are added in a couple of code paths using devm_cxl_add_port(). Debug messages are individually generated, but are incomplete and inconsistent. Change this by moving its generation to devm_cxl_add_port(). This unifies the messages and reduces code duplication. Also, generate messages on failure.
--- drivers/cxl/acpi.c | 2 -- drivers/cxl/core/port.c | 39 ++++++++++++++++++++++++++++----------- 2 files changed, 28 insertions(+), 13 deletions(-)
drivers/cxl/acpi.c +0 -2
@@ -220,7 +220,6 @@ static int add_host_bridge_uport(struct device *match, void *arg) port =devm_cxl_add_port (host, match, dport->component_reg_phys, dport);if (IS_ERR (port))return PTR_ERR (port); -dev_dbg (host,"%s: add: %s\n" ,dev_name (match),dev_name (&port->dev));return 0 ; }
@@ -466,7 +465,6 @@ static int cxl_acpi_probe(struct platform_device *pdev) root_port =devm_cxl_add_port (host, host,CXL_RESOURCE_NONE ,NULL );if (IS_ERR (root_port))return PTR_ERR (root_port); -dev_dbg (host,"add: %s\n" ,dev_name (&root_port->dev)); rc =bus_for_each_dev (adev->dev.bus,NULL , root_port, add_host_bridge_dport);
drivers/cxl/core/port.c +28 -11
@@ -666,13 +666,17 @@ struct cxl_port *devm_cxl_add_port(struct device *host, struct device *uport,resource_size_t component_reg_phys, struct cxl_dport *parent_dport) { - struct cxl_port *port; + struct cxl_port *port, *parent_port;struct device *dev;int rc; + parent_port = parent_dport ? parent_dport->port :NULL ; + port =cxl_port_alloc (uport, component_reg_phys, parent_dport); -if (IS_ERR (port)) -return port; +if (IS_ERR (port)) { + rc =PTR_ERR (port); + goto err_out; + } dev = &port->dev;if (is_cxl_memdev (uport))
@@ -682,24 +686,39 @@ struct cxl_port *devm_cxl_add_port(struct device *host, struct device *uport,else rc =dev_set_name (dev,"root%d" , port->id);if (rc) - goto err; + goto err_put; rc =device_add (dev);if (rc) - goto err; + goto err_put; rc =devm_add_action_or_reset (host, unregister_port, port);if (rc) -return ERR_PTR (rc); + goto err_out; rc =devm_cxl_link_uport (host, port);if (rc) -return ERR_PTR (rc); + goto err_out; -return port; +dev_dbg (host,"added %s as%s port of device %s%s%s\n" , +dev_name (&port->dev), + parent_port ?"" :" root" , +dev_name (uport), + parent_port ?" to parent port " :"" , + parent_port ?dev_name (&parent_port->dev) :"" ); -err: +return port; +err_put:put_device (dev); +err_out: +dev_dbg (host,"failed to add %s as%s port of device %s%s%s: %d\n" , +dev_name (&port->dev), + parent_port ?"" :" root" , +dev_name (uport), + parent_port ?" to parent port " :"" , + parent_port ?dev_name (&parent_port->dev) :"" , + rc); +return ERR_PTR (rc); }EXPORT_SYMBOL_NS_GPL (devm_cxl_add_port,CXL );
@@ -1140,8 +1159,6 @@ int devm_cxl_add_endpoint(struct cxl_memdev *cxlmd,if (IS_ERR (endpoint))return PTR_ERR (endpoint); -dev_dbg (&cxlmd->dev,"add: %s\n" ,dev_name (&endpoint->dev)); - rc =cxl_endpoint_autoremove (cxlmd, endpoint);if (rc)return rc;
Signature · 1 line
2.30.2
Re: [PATCH 03/15] cxl: Unify debug messages when calling devm_cxl_add_port()
Quoted 7 lines · On Wed, 31 Aug 2022 10:15:51 +0200 Robert Richter <[email protected]> wrote:
CXL ports are added in a couple of code paths using
devm_cxl_add_port(). Debug messages are individually generated, but are incomplete and inconsistent. Change this by moving its generation todevm_cxl_add_port(). This unifies the messages and reduces code duplication. Also, generate messages on failure.Signed-off-by Robert Richter <[email protected]>
This is one for Dan etc as it is mostly a question of how verbose we want the debug prints to be plus preference for caller or callee being responsible for outputting this sort of message.
Patch looks good to me if we want to make this sort of change.
Quoted 105 lines
--- drivers/cxl/acpi.c | 2 -- drivers/cxl/core/port.c | 39 ++++++++++++++++++++++++++++----------- 2 files changed, 28 insertions(+), 13 deletions(-)drivers/cxl/acpi.c +0
-2@@ -220,7 +220,6 @@ static int add_host_bridge_uport(struct device *match, void *arg) port =devm_cxl_add_port (host, match, dport->component_reg_phys, dport);if (IS_ERR (port))return PTR_ERR (port); -dev_dbg (host,"%s: add: %s\n" ,dev_name (match),dev_name (&port->dev));return 0 ; }@@ -466,7 +465,6 @@ static int cxl_acpi_probe(struct platform_device *pdev) root_port =devm_cxl_add_port (host, host,CXL_RESOURCE_NONE ,NULL );if (IS_ERR (root_port))return PTR_ERR (root_port); -dev_dbg (host,"add: %s\n" ,dev_name (&root_port->dev)); rc =bus_for_each_dev (adev->dev.bus,NULL , root_port, add_host_bridge_dport);drivers/cxl/core/port.c +28
-11@@ -666,13 +666,17 @@ struct cxl_port *devm_cxl_add_port(struct device *host, struct device *uport,resource_size_t component_reg_phys, struct cxl_dport *parent_dport) { - struct cxl_port *port; + struct cxl_port *port, *parent_port;struct device *dev;int rc; + parent_port = parent_dport ? parent_dport->port :NULL ; + port =cxl_port_alloc (uport, component_reg_phys, parent_dport); -if (IS_ERR (port)) -return port; +if (IS_ERR (port)) { + rc =PTR_ERR (port); + goto err_out; + } dev = &port->dev;if (is_cxl_memdev (uport))@@ -682,24 +686,39 @@ struct cxl_port *devm_cxl_add_port(struct device *host, struct device *uport,else rc =dev_set_name (dev,"root%d" , port->id);if (rc) - goto err; + goto err_put; rc =device_add (dev);if (rc) - goto err; + goto err_put; rc =devm_add_action_or_reset (host, unregister_port, port);if (rc) -return ERR_PTR (rc); + goto err_out; rc =devm_cxl_link_uport (host, port);if (rc) -return ERR_PTR (rc); + goto err_out; -return port; +dev_dbg (host,"added %s as%s port of device %s%s%s\n" , +dev_name (&port->dev), + parent_port ?"" :" root" , +dev_name (uport), + parent_port ?" to parent port " :"" , + parent_port ?dev_name (&parent_port->dev) :"" ); -err: +return port; +err_put:put_device (dev); +err_out: +dev_dbg (host,"failed to add %s as%s port of device %s%s%s: %d\n" , +dev_name (&port->dev), + parent_port ?"" :" root" , +dev_name (uport), + parent_port ?" to parent port " :"" , + parent_port ?dev_name (&parent_port->dev) :"" , + rc); +return ERR_PTR (rc); }EXPORT_SYMBOL_NS_GPL (devm_cxl_add_port,CXL );@@ -1140,8 +1159,6 @@ int devm_cxl_add_endpoint(struct cxl_memdev *cxlmd,if (IS_ERR (endpoint))return PTR_ERR (endpoint); -dev_dbg (&cxlmd->dev,"add: %s\n" ,dev_name (&endpoint->dev)); - rc =cxl_endpoint_autoremove (cxlmd, endpoint);if (rc)return rc;
Re: [PATCH 03/15] cxl: Unify debug messages when calling devm_cxl_add_port()
Quoted 9 lines · Jonathan Cameron
Quoted 6 lines · On Wed, 31 Aug 2022 10:15:51 +0200 Robert Richter <[email protected]> wrote:
CXL ports are added in a couple of code paths using
devm_cxl_add_port(). Debug messages are individually generated, but are incomplete and inconsistent. Change this by moving its generation todevm_cxl_add_port(). This unifies the messages and reduces code duplication. Also, generate messages on failure.
Quoted 5 lines
Quoted 1 line
Signed-off-by Robert Richter <[email protected]>This is one for Dan etc as it is mostly a question of how verbose we want the debug prints to be plus preference for caller or callee being responsible for outputting this sort of message.
Esp. together with dyndbg this is very useful as you can get a whole picture of the port enablement.
-Robert
Re: [PATCH 03/15] cxl: Unify debug messages when calling devm_cxl_add_port()
In reply to Jonathan CameronQuoted 9 lines · Jonathan Cameron
Quoted 6 lines · On Wed, 31 Aug 2022 10:15:51 +0200 Robert Richter <[email protected]> wrote:
CXL ports are added in a couple of code paths using
devm_cxl_add_port(). Debug messages are individually generated, but are incomplete and inconsistent. Change this by moving its generation todevm_cxl_add_port(). This unifies the messages and reduces code duplication. Also, generate messages on failure.
Quoted 7 lines
Quoted 1 line
Signed-off-by Robert Richter <[email protected]>This is one for Dan etc as it is mostly a question of how verbose we want the debug prints to be plus preference for caller or callee being responsible for outputting this sort of message.
Patch looks good to me if we want to make this sort of change.
Should I take this as a Reviewed-by?
Thanks,
-Robert
Jonathan Cameron
Reviewed-byRe: [PATCH 03/15] cxl: Unify debug messages when calling devm_cxl_add_port()
Quoted 12 lines · On Tue, 6 Sep 2022 09:30:37 +0200 Robert Richter <[email protected]> wrote:
Quoted 11 lines · Jonathan Cameron
Quoted 7 lines · On Wed, 31 Aug 2022 10:15:51 +0200 Robert Richter <[email protected]> wrote:
CXL ports are added in a couple of code paths using
devm_cxl_add_port(). Debug messages are individually generated, but are incomplete and inconsistent. Change this by moving its generation todevm_cxl_add_port(). This unifies the messages and reduces code duplication. Also, generate messages on failure.Signed-off-by Robert Richter <[email protected]>
Quoted 7 lines
Quoted 5 lines
This is one for Dan etc as it is mostly a question of how verbose we want the debug prints to be plus preference for caller or callee being responsible for outputting this sort of message.
Patch looks good to me if we want to make this sort of change.
Should I take this as a Reviewed-by?
Hmm. I guess I could go that far as its a policy decision rather than correctness
Quoted 4 lines
Thanks,
-Robert
Re: [PATCH 3/15] cxl: Unify debug messages when calling devm_cxl_add_port()
In reply to Robert RichterQuoted 8 lines · Robert Richter
CXL ports are added in a couple of code paths using
devm_cxl_add_port(). Debug messages are individually generated, but are incomplete and inconsistent. Change this by moving its generation todevm_cxl_add_port(). This unifies the messages and reduces code duplication. Also, generate messages on failure.Signed-off-by Robert Richter <[email protected]>Reviewed-by Jonathan Cameron <[email protected]>
RE: [PATCH 03/15] cxl: Unify debug messages when calling devm_cxl_add_port()
In reply to Robert RichterQuoted 43 lines · Robert Richter
CXL ports are added in a couple of code paths using
devm_cxl_add_port(). Debug messages are individually generated, but are incomplete and inconsistent. Change this by moving its generation todevm_cxl_add_port(). This unifies the messages and reduces code duplication. Also, generate messages on failure.Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/acpi.c | 2 -- drivers/cxl/core/port.c | 39 ++++++++++++++++++++++++++++----------- 2 files changed, 28 insertions(+), 13 deletions(-)drivers/cxl/acpi.c +0
-2@@ -220,7 +220,6 @@ static int add_host_bridge_uport(struct device *match, void *arg) port =devm_cxl_add_port (host, match, dport->component_reg_phys, dport);if (IS_ERR (port))return PTR_ERR (port); -dev_dbg (host,"%s: add: %s\n" ,dev_name (match),dev_name (&port->dev));return 0 ; }@@ -466,7 +465,6 @@ static int cxl_acpi_probe(struct platform_device *pdev) root_port =devm_cxl_add_port (host, host,CXL_RESOURCE_NONE ,NULL );if (IS_ERR (root_port))return PTR_ERR (root_port); -dev_dbg (host,"add: %s\n" ,dev_name (&root_port->dev)); rc =bus_for_each_dev (adev->dev.bus,NULL , root_port, add_host_bridge_dport);drivers/cxl/core/port.c +1
-1@@ -666,13 +666,17 @@ struct cxl_port *devm_cxl_add_port(struct device *host, struct device *uport,resource_size_t component_reg_phys, struct cxl_dport *parent_dport) { - struct cxl_port *port; + struct cxl_port *port, *parent_port;struct device *dev;
drivers/cxl/core/port.c struct cxl_port *devm_cxl_add_port(struct device *host, struct device *uport, · line 678
Quoted 10 lines
drivers/cxl/core/port.c +5
-2int rc; + parent_port = parent_dport ? parent_dport->port :NULL ; + port =cxl_port_alloc (uport, component_reg_phys, parent_dport); -if (IS_ERR (port)) -return port; +if (IS_ERR (port)) { + rc =PTR_ERR (port); + goto err_out;
While I agree this unifies the error messaging I am not a fan of what this does to the readability of the error exits. What about a compromise of renaming devm_cxl_add_port to __devm_cxl_add_port() and add back a new devm_cxl_add_port that does the unified debug messaging?
Re: [PATCH 03/15] cxl: Unify debug messages when calling devm_cxl_add_port()
Quoted 15 lines · Dan Williams
drivers/cxl/core/port.c struct cxl_port *devm_cxl_add_port(struct device *host, struct device *uport, · line 678
Quoted 8 lines · Robert Richter
drivers/cxl/core/port.c +5
-2+ parent_port = parent_dport ? parent_dport->port :NULL ; + port =cxl_port_alloc (uport, component_reg_phys, parent_dport); -if (IS_ERR (port)) -return port; +if (IS_ERR (port)) { + rc =PTR_ERR (port); + goto err_out;While I agree this unifies the error messaging I am not a fan of what this does to the readability of the error exits. What about a compromise of renaming
devm_cxl_add_portto__devm_cxl_add_port()and add back a newdevm_cxl_add_portthat does the unified debug messaging?
Ok, will add a wrapper.
Thanks,
-Robert
PATCH 4/15 cxl: Unify debug messages when calling devm_cxl_add_dport()
In reply to Robert RichterCXL dports are added in a couple of code paths using devm_cxl_add_dport(). Debug messages are individually generated, but are incomplete and inconsistent. Change this by moving its generation to devm_cxl_add_dport(). This unifies the messages and reduces code duplication. Also, generate messages on failure.
--- drivers/cxl/acpi.c | 7 ++----- drivers/cxl/core/pci.c | 2 -- drivers/cxl/core/port.c | 28 ++++++++++++++++++++-------- tools/testing/cxl/test/cxl.c | 8 +------- 4 files changed, 23 insertions(+), 22 deletions(-)
drivers/cxl/acpi.c +2 -5
@@ -282,12 +282,9 @@ static int add_host_bridge_dport(struct device *match, void *arg) } dport =devm_cxl_add_dport (root_port, match, uid, ctx.chbcr); -if (IS_ERR (dport)) { -dev_err (host,"failed to add downstream port: %s\n" , -dev_name (match)); +if (IS_ERR (dport))return PTR_ERR (dport); - } -dev_dbg (host,"add dport%llu: %s\n" , uid,dev_name (match)); +return 0 ; }
drivers/cxl/core/pci.c +0 -2
@@ -62,8 +62,6 @@ static int match_add_dports(struct pci_dev *pdev, void *data) } ctx->count++; -dev_dbg (&port->dev,"add dport%d: %s\n" , port_num,dev_name (&pdev->dev)); -return 0 ; }
drivers/cxl/core/port.c +20 -8
@@ -914,12 +914,16 @@ struct cxl_dport *devm_cxl_add_dport(struct cxl_port *port, }if (snprintf (link_name,CXL_TARGET_STRLEN ,"dport%d" , port_id) >= -CXL_TARGET_STRLEN ) -return ERR_PTR (-EINVAL ); +CXL_TARGET_STRLEN ) { + rc = -EINVAL ; + goto err; + } dport =devm_kzalloc (host,sizeof (*dport),GFP_KERNEL ); -if (!dport) -return ERR_PTR (-ENOMEM ); +if (!dport) { + rc = -ENOMEM ; + goto err; + } dport->dport = dport_dev; dport->port_id = port_id;
@@ -930,22 +934,30 @@ struct cxl_dport *devm_cxl_add_dport(struct cxl_port *port, rc =add_dport (port, dport);cond_cxl_root_unlock (port);if (rc) -return ERR_PTR (rc); + goto err;get_device (dport_dev); rc =devm_add_action_or_reset (host, cxl_dport_remove, dport);if (rc) -return ERR_PTR (rc); + goto err; rc =sysfs_create_link (&port->dev.kobj, &dport_dev->kobj, link_name);if (rc) -return ERR_PTR (rc); + goto err; rc =devm_add_action_or_reset (host, cxl_dport_unlink, dport);if (rc) -return ERR_PTR (rc); + goto err; + +dev_dbg (&port->dev,"added %s (%s) as dport of device %s\n" , +dev_name (&port->dev), link_name,dev_name (dport_dev));return dport; +err: +dev_dbg (&port->dev,"failed to add %s (%s) as dport of device %s: %d\n" , +dev_name (&port->dev), link_name,dev_name (dport_dev), rc); + +return ERR_PTR (rc); }EXPORT_SYMBOL_NS_GPL (devm_cxl_add_dport,CXL );
tools/testing/cxl/test/cxl.c +1 -7
@@ -582,14 +582,8 @@ static int mock_cxl_port_enumerate_dports(struct cxl_port *port) dport =devm_cxl_add_dport (port, &pdev->dev, pdev->id,CXL_RESOURCE_NONE ); -if (IS_ERR (dport)) { -dev_err (dev,"failed to add dport: %s (%ld)\n" , -dev_name (&pdev->dev),PTR_ERR (dport)); +if (IS_ERR (dport))return PTR_ERR (dport); - } - -dev_dbg (dev,"add dport%d: %s\n" , pdev->id, -dev_name (&pdev->dev)); }return 0 ;
Signature · 1 line
2.30.2
Re: [PATCH 4/15] cxl: Unify debug messages when calling devm_cxl_add_dport()
Quoted 7 lines · Robert Richter
CXL dports are added in a couple of code paths using
devm_cxl_add_dport(). Debug messages are individually generated, but are incomplete and inconsistent. Change this by moving its generation todevm_cxl_add_dport(). This unifies the messages and reduces code duplication. Also, generate messages on failure.Signed-off-by Robert Richter <[email protected]>
RE: [PATCH 04/15] cxl: Unify debug messages when calling devm_cxl_add_dport()
In reply to Robert RichterQuoted 58 lines · Robert Richter
CXL dports are added in a couple of code paths using
devm_cxl_add_dport(). Debug messages are individually generated, but are incomplete and inconsistent. Change this by moving its generation todevm_cxl_add_dport(). This unifies the messages and reduces code duplication. Also, generate messages on failure.Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/acpi.c | 7 ++----- drivers/cxl/core/pci.c | 2 -- drivers/cxl/core/port.c | 28 ++++++++++++++++++++-------- tools/testing/cxl/test/cxl.c | 8 +------- 4 files changed, 23 insertions(+), 22 deletions(-)drivers/cxl/acpi.c +2
-5@@ -282,12 +282,9 @@ static int add_host_bridge_dport(struct device *match, void *arg) } dport =devm_cxl_add_dport (root_port, match, uid, ctx.chbcr); -if (IS_ERR (dport)) { -dev_err (host,"failed to add downstream port: %s\n" , -dev_name (match)); +if (IS_ERR (dport))return PTR_ERR (dport); - } -dev_dbg (host,"add dport%llu: %s\n" , uid,dev_name (match)); +return 0 ; }drivers/cxl/core/pci.c +0
-2@@ -62,8 +62,6 @@ static int match_add_dports(struct pci_dev *pdev, void *data) } ctx->count++; -dev_dbg (&port->dev,"add dport%d: %s\n" , port_num,dev_name (&pdev->dev)); -return 0 ; }drivers/cxl/core/port.c +2
-2@@ -914,12 +914,16 @@ struct cxl_dport *devm_cxl_add_dport(struct cxl_port *port, }if (snprintf (link_name,CXL_TARGET_STRLEN ,"dport%d" , port_id) >= -CXL_TARGET_STRLEN ) -return ERR_PTR (-EINVAL ); +CXL_TARGET_STRLEN ) { + rc = -EINVAL ;
drivers/cxl/core/port.c struct cxl_dport *devm_cxl_add_dport(struct cxl_port *port, · line 926
Quoted 10 lines
drivers/cxl/core/port.c +6
-2+ goto err; + } dport =devm_kzalloc (host,sizeof (*dport),GFP_KERNEL ); -if (!dport) -return ERR_PTR (-ENOMEM ); +if (!dport) { + rc = -ENOMEM ; + goto err; + }
Similar comment as before of using a goto just to ensure the log message is called, I suspect a wrapper to do the logging ends up with less code thrash.
PATCH 5/15 cxl/acpi: Add probe function to detect restricted CXL hosts in RCD mode
In reply to Robert RichterRestricted CXL device (RCD) mode (formerly CXL 1.1) uses a different enumeration scheme other than CXL VH (formerly CXL 2.0). In RCD mode a host/device (RCH-RCD) pair shows up as a legal PCIe hierarchy with an ACPI host bridge ("PNP0A08" or "ACPI0016" HID) and RCiEP connected to it with a description of the CXL device.
Add function cxl_restricted_host_probe() to probe RCD enumerated devices. The function implements a loop that detects all CXL capable ACPI PCI root bridges in the system (RCD mode only). The iterator function cxl_find_next_rch() is introduced to walk through all of the CXL hosts. The loop will then enable all CXL devices connected to the host. For now, only implement an empty loop with an iterator that returns all pci host bridges in the system.
The probe function is triggered by adding an own root device for RCHs. This is different to CXL VH where an ACPI "ACPI0017" root device exists. Its detection starts the CXL host detection. In RCD mode such a device does not necessarily exists, so solve this by creating a plain platform device that is not an ACPI device and is root only for RCHs.
--- drivers/cxl/acpi.c | 71 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 70 insertions(+), 1 deletion(-)
drivers/cxl/acpi.c +70 -1
@@ -312,6 +312,33 @@ static int add_root_nvdimm_bridge(struct device *match, void *data)return 1 ; } +struct pci_host_bridge *cxl_find_next_rch (struct pci_host_bridge *host) +{ +struct pci_bus *bus = host ? host->bus :NULL ; + +while ((bus =pci_find_next_bus (bus)) !=NULL ) { + host = bus ?to_pci_host_bridge (bus->bridge) :NULL ; +if (!host) +continue ; + +dev_dbg (&host->dev,"PCI bridge found\n" ); + +return host; + } + +return NULL ; +} + +static int __init cxl_restricted_host_probe (struct platform_device *pdev) +{ +struct pci_host_bridge *host =NULL ; + +while ((host =cxl_find_next_rch (host)) !=NULL ) { + } + +return 0 ; +} +static struct lock_class_key cxl_root_key;static void cxl_acpi_lock_reset_class (void *dev)
@@ -445,6 +472,13 @@ static int cxl_acpi_probe(struct platform_device *pdev)struct acpi_device *adev =ACPI_COMPANION (host);struct cxl_cfmws_context ctx; +/* +* For RCH (CXL 1.1 hosts) the probe is triggered by a plain +* platform dev which does not have an acpi companion. +*/ +if (!adev) +return cxl_restricted_host_probe (pdev); +device_lock_set_class (&pdev->dev, &cxl_root_key); rc =devm_add_action_or_reset (&pdev->dev, cxl_acpi_lock_reset_class, &pdev->dev);
@@ -518,6 +552,7 @@ MODULE_DEVICE_TABLE(acpi, cxl_acpi_ids);static const struct platform_device_id cxl_test_ids[] = { {"cxl_acpi" }, + {"cxl_root" }, { }, };MODULE_DEVICE_TABLE (platform, cxl_test_ids);
@@ -531,7 +566,41 @@ static struct platform_driver cxl_acpi_driver = { .id_table = cxl_test_ids, }; -module_platform_driver (cxl_acpi_driver); +static void cxl_acpi_device_release (struct device *dev) { } + +static struct platform_device cxl_acpi_device = { + .name ="cxl_root" , + .id =PLATFORM_DEVID_NONE , + .dev = { + .release = cxl_acpi_device_release, + } +}; + +static int __init cxl_host_init (void ) +{ +int rc; + +/* Kick off restricted host (CXL 1.1) detection */ + rc =platform_device_register (&cxl_acpi_device); +if (rc) { +platform_device_put (&cxl_acpi_device); +return rc; + } + rc =platform_driver_register (&cxl_acpi_driver); +if (rc) +platform_device_unregister (&cxl_acpi_device); +return rc; +} + +static void __exit cxl_host_exit(void) +{ +platform_driver_unregister (&cxl_acpi_driver); +platform_device_unregister (&cxl_acpi_device); +} + +module_init (cxl_host_init); +module_exit (cxl_host_exit); +MODULE_LICENSE ("GPL v2" );MODULE_IMPORT_NS (CXL );MODULE_IMPORT_NS (ACPI );
Signature · 1 line
2.30.2
Re: [PATCH 05/15] cxl/acpi: Add probe function to detect restricted CXL hosts in RCD mode
Quoted 14 lines · On Wed, 31 Aug 2022 10:15:53 +0200 Robert Richter <[email protected]> wrote:
Restricted CXL device (RCD) mode (formerly CXL 1.1) uses a different enumeration scheme other than CXL VH (formerly CXL 2.0). In RCD mode a host/device (RCH-RCD) pair shows up as a legal PCIe hierarchy with an ACPI host bridge ("PNP0A08" or "ACPI0016" HID) and RCiEP connected to it with a description of the CXL device.
Add function
cxl_restricted_host_probe()to probe RCD enumerated devices. The function implements a loop that detects all CXL capable ACPI PCI root bridges in the system (RCD mode only). The iterator functioncxl_find_next_rch()is introduced to walk through all of the CXL hosts. The loop will then enable all CXL devices connected to the host. For now, only implement an empty loop with an iterator that returns all pci host bridges in the system.
Quoted 6 lines
The probe function is triggered by adding an own root device for RCHs. This is different to CXL VH where an ACPI "ACPI0017" root device exists. Its detection starts the CXL host detection. In RCD mode such a device does not necessarily exists, so solve this by creating a plain platform device that is not an ACPI device and is root only for RCHs.
If I read this correctly that platform device is created whether or not there are any cxl devices in the system?
Can we create it only if we find some devices that will be placed under it later?
Jonathan
Quoted 67 lines
Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/acpi.c | 71 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 70 insertions(+), 1 deletion(-)drivers/cxl/acpi.c +35
-0@@ -312,6 +312,33 @@ static int add_root_nvdimm_bridge(struct device *match, void *data)return 1 ; } +struct pci_host_bridge *cxl_find_next_rch (struct pci_host_bridge *host) +{ +struct pci_bus *bus = host ? host->bus :NULL ; + +while ((bus =pci_find_next_bus (bus)) !=NULL ) { + host = bus ?to_pci_host_bridge (bus->bridge) :NULL ; +if (!host) +continue ; + +dev_dbg (&host->dev,"PCI bridge found\n" ); + +return host; + } + +return NULL ; +} + +static int __init cxl_restricted_host_probe (struct platform_device *pdev) +{ +struct pci_host_bridge *host =NULL ; + +while ((host =cxl_find_next_rch (host)) !=NULL ) { + } + +return 0 ; +} +static struct lock_class_key cxl_root_key;static void cxl_acpi_lock_reset_class (void *dev)@@ -445,6 +472,13 @@ static int cxl_acpi_probe(struct platform_device *pdev)struct acpi_device *adev =ACPI_COMPANION (host);struct cxl_cfmws_context ctx; +/* +* For RCH (CXL 1.1 hosts) the probe is triggered by a plain +* platform dev which does not have an acpi companion. +*/ +if (!adev) +return cxl_restricted_host_probe (pdev); +device_lock_set_class (&pdev->dev, &cxl_root_key); rc =devm_add_action_or_reset (&pdev->dev, cxl_acpi_lock_reset_class, &pdev->dev);@@ -518,6 +552,7 @@ MODULE_DEVICE_TABLE(acpi, cxl_acpi_ids);static const struct platform_device_id cxl_test_ids[] = { {"cxl_acpi" }, + {"cxl_root" }, { }, };MODULE_DEVICE_TABLE (platform, cxl_test_ids);
drivers/cxl/acpi.c static struct platform_driver cxl_acpi_driver = { · line 569
Quoted 5 lines
drivers/cxl/acpi.c +1
-1@@ -531,7 +566,41 @@ static struct platform_driver cxl_acpi_driver = { .id_table = cxl_test_ids, }; -module_platform_driver (cxl_acpi_driver); +static void cxl_acpi_device_release (struct device *dev) { }
Why the empty release? Perhaps introduce this only when it does something.
Quoted 37 lines
drivers/cxl/acpi.c +34
-0+ +static struct platform_device cxl_acpi_device = { + .name ="cxl_root" , + .id =PLATFORM_DEVID_NONE , + .dev = { + .release = cxl_acpi_device_release, + } +}; + +static int __init cxl_host_init (void ) +{ +int rc; + +/* Kick off restricted host (CXL 1.1) detection */ + rc =platform_device_register (&cxl_acpi_device); +if (rc) { +platform_device_put (&cxl_acpi_device); +return rc; + } + rc =platform_driver_register (&cxl_acpi_driver); +if (rc) +platform_device_unregister (&cxl_acpi_device); +return rc; +} + +static void __exit cxl_host_exit(void) +{ +platform_driver_unregister (&cxl_acpi_driver); +platform_device_unregister (&cxl_acpi_device); +} + +module_init (cxl_host_init); +module_exit (cxl_host_exit); +MODULE_LICENSE ("GPL v2" );MODULE_IMPORT_NS (CXL );MODULE_IMPORT_NS (ACPI );
Re: [PATCH 05/15] cxl/acpi: Add probe function to detect restricted CXL hosts in RCD mode
Quoted 25 lines · Jonathan Cameron
On Wed, 31 Aug 2022 10:15:53 +0200
Quoted 14 lines · Robert Richter
Restricted CXL device (RCD) mode (formerly CXL 1.1) uses a different enumeration scheme other than CXL VH (formerly CXL 2.0). In RCD mode a host/device (RCH-RCD) pair shows up as a legal PCIe hierarchy with an ACPI host bridge ("PNP0A08" or "ACPI0016" HID) and RCiEP connected to it with a description of the CXL device.
Add function
cxl_restricted_host_probe()to probe RCD enumerated devices. The function implements a loop that detects all CXL capable ACPI PCI root bridges in the system (RCD mode only). The iterator functioncxl_find_next_rch()is introduced to walk through all of the CXL hosts. The loop will then enable all CXL devices connected to the host. For now, only implement an empty loop with an iterator that returns all pci host bridges in the system.Quoted 6 lines
The probe function is triggered by adding an own root device for RCHs. This is different to CXL VH where an ACPI "ACPI0017" root device exists. Its detection starts the CXL host detection. In RCD mode such a device does not necessarily exists, so solve this by creating a plain platform device that is not an ACPI device and is root only for RCHs.
Quoted 5 lines
If I read this correctly that platform device is created whether or not there are any cxl devices in the system?
Can we create it only if we find some devices that will be placed under it later?
This would move the host detection from probe to init which I wanted to avoid to better control driver init order dependencies.
I could add a put_device() at the end of a probe so that it will be released in case no other references use it. This implies the refcount is maintained for parent devices. Or this needs to be added to. So if there are no children (hosts) attached to the root device after probe, it will disappear.
Quoted 9 lines
drivers/cxl/acpi.c static struct platform_driver cxl_acpi_driver = { · line 569
Quoted 6 lines
drivers/cxl/acpi.c +1
-1@@ -531,7 +566,41 @@ static struct platform_driver cxl_acpi_driver = { .id_table = cxl_test_ids, }; -module_platform_driver (cxl_acpi_driver); +static void cxl_acpi_device_release (struct device *dev) { }Why the empty release? Perhaps introduce this only when it does something.
The core device driver requires this in device_release() to be setup.
There is nothing to do as the device is kept in a static struct. That's why it's empty.
-Robert
Re: [PATCH 05/15] cxl/acpi: Add probe function to detect restricted CXL hosts in RCD mode
Quoted 26 lines · On Thu, 1 Sep 2022 08:01:05 +0200 Robert Richter <[email protected]> wrote:
Quoted 25 lines · Jonathan Cameron
On Wed, 31 Aug 2022 10:15:53 +0200
Quoted 20 lines · Robert Richter
Restricted CXL device (RCD) mode (formerly CXL 1.1) uses a different enumeration scheme other than CXL VH (formerly CXL 2.0). In RCD mode a host/device (RCH-RCD) pair shows up as a legal PCIe hierarchy with an ACPI host bridge ("PNP0A08" or "ACPI0016" HID) and RCiEP connected to it with a description of the CXL device.
Add function
cxl_restricted_host_probe()to probe RCD enumerated devices. The function implements a loop that detects all CXL capable ACPI PCI root bridges in the system (RCD mode only). The iterator functioncxl_find_next_rch()is introduced to walk through all of the CXL hosts. The loop will then enable all CXL devices connected to the host. For now, only implement an empty loop with an iterator that returns all pci host bridges in the system.The probe function is triggered by adding an own root device for RCHs. This is different to CXL VH where an ACPI "ACPI0017" root device exists. Its detection starts the CXL host detection. In RCD mode such a device does not necessarily exists, so solve this by creating a plain platform device that is not an ACPI device and is root only for RCHs.
Quoted 8 lines
Quoted 5 lines
If I read this correctly that platform device is created whether or not there are any cxl devices in the system?
Can we create it only if we find some devices that will be placed under it later?
This would move the host detection from probe to init which I wanted to avoid to better control driver init order dependencies.
It's a bit nasty either way. I can see your reasoning, but definitely not keen on it if there is a plausible way to avoid.
Quoted 6 lines
I could add a
put_device()at the end of a probe so that it will be released in case no other references use it. This implies the refcount is maintained for parent devices. Or this needs to be added to. So if there are no children (hosts) attached to the root device after probe, it will disappear.
Unless there is precedence for that, it'll be weird enough to be hard to maintain. I guess I can live with the ugliness if we can't add something new to ACPI to base this off.
Quoted 11 lines
Quoted 10 lines
drivers/cxl/acpi.c static struct platform_driver cxl_acpi_driver = { · line 569
Quoted 7 lines
drivers/cxl/acpi.c +1
-1@@ -531,7 +566,41 @@ static struct platform_driver cxl_acpi_driver = { .id_table = cxl_test_ids, }; -module_platform_driver (cxl_acpi_driver); +static void cxl_acpi_device_release (struct device *dev) { }Why the empty release? Perhaps introduce this only when it does something.
Quoted 4 lines
The core device driver requires this in
device_release()to be setup.There is nothing to do as the device is kept in a static struct. That's why it's empty.
Ah got it. I'd failed to register the static structure.
Quoted 2 lines
-Robert
Re: [PATCH 05/15] cxl/acpi: Add probe function to detect restricted CXL hosts in RCD mode
Quoted 31 lines · Jonathan Cameron
Quoted 11 lines · On Thu, 1 Sep 2022 08:01:05 +0200 Robert Richter <[email protected]> wrote:
Quoted 10 lines · Jonathan Cameron
Quoted 6 lines · On Wed, 31 Aug 2022 10:15:53 +0200 Robert Richter <[email protected]> wrote:
The probe function is triggered by adding an own root device for RCHs. This is different to CXL VH where an ACPI "ACPI0017" root device exists. Its detection starts the CXL host detection. In RCD mode such a device does not necessarily exists, so solve this by creating a plain platform device that is not an ACPI device and is root only for RCHs.
Quoted 8 lines
Quoted 5 lines
If I read this correctly that platform device is created whether or not there are any cxl devices in the system?
Can we create it only if we find some devices that will be placed under it later?
This would move the host detection from probe to init which I wanted to avoid to better control driver init order dependencies.
It's a bit nasty either way. I can see your reasoning, but definitely not keen on it if there is a plausible way to avoid.
Quoted 6 lines
I could add a
put_device()at the end of a probe so that it will be released in case no other references use it. This implies the refcount is maintained for parent devices. Or this needs to be added to. So if there are no children (hosts) attached to the root device after probe, it will disappear.
Quoted 3 lines
Unless there is precedence for that, it'll be weird enough to be hard to maintain. I guess I can live with the ugliness if we can't add something new to ACPI to base this off.
Let's stay with a put_device() for now. Then, we wont have a stale cxl root device in the system in case there are no RCD children.
-Robert
Re: [PATCH 05/15] cxl/acpi: Add probe function to detect restricted CXL hosts in RCD mode
Quoted 32 lines · On Tue, 6 Sep 2022 09:19:49 +0200 Robert Richter <[email protected]> wrote:
Quoted 31 lines · Jonathan Cameron
Quoted 11 lines · On Thu, 1 Sep 2022 08:01:05 +0200 Robert Richter <[email protected]> wrote:
Quoted 10 lines · Jonathan Cameron
Quoted 6 lines · On Wed, 31 Aug 2022 10:15:53 +0200 Robert Richter <[email protected]> wrote:
The probe function is triggered by adding an own root device for RCHs. This is different to CXL VH where an ACPI "ACPI0017" root device exists. Its detection starts the CXL host detection. In RCD mode such a device does not necessarily exists, so solve this by creating a plain platform device that is not an ACPI device and is root only for RCHs.
Quoted 8 lines
Quoted 5 lines
If I read this correctly that platform device is created whether or not there are any cxl devices in the system?
Can we create it only if we find some devices that will be placed under it later?
This would move the host detection from probe to init which I wanted to avoid to better control driver init order dependencies.
It's a bit nasty either way. I can see your reasoning, but definitely not keen on it if there is a plausible way to avoid.
Quoted 6 lines
I could add a
put_device()at the end of a probe so that it will be released in case no other references use it. This implies the refcount is maintained for parent devices. Or this needs to be added to. So if there are no children (hosts) attached to the root device after probe, it will disappear.
Quoted 8 lines
Quoted 3 lines
Unless there is precedence for that, it'll be weird enough to be hard to maintain. I guess I can live with the ugliness if we can't add something new to ACPI to base this off.
Let's stay with a
put_device()for now. Then, we wont have a stale cxl root device in the system in case there are no RCD children.-Robert
Kind of obvious, but...
Make sure to call that out as an unusual thing to do via cover letter / patch description so we hopefully get more eyes on this detail..
Jonathan
Re: [PATCH 05/15] cxl/acpi: Add probe function to detect restricted CXL hosts in RCD mode
In reply to Robert RichterQuoted 14 lines · Robert Richter
Restricted CXL device (RCD) mode (formerly CXL 1.1) uses a different enumeration scheme other than CXL VH (formerly CXL 2.0). In RCD mode a host/device (RCH-RCD) pair shows up as a legal PCIe hierarchy with an ACPI host bridge ("PNP0A08" or "ACPI0016" HID) and RCiEP connected to it with a description of the CXL device.
Add function
cxl_restricted_host_probe()to probe RCD enumerated devices. The function implements a loop that detects all CXL capable ACPI PCI root bridges in the system (RCD mode only). The iterator functioncxl_find_next_rch()is introduced to walk through all of the CXL hosts. The loop will then enable all CXL devices connected to the host. For now, only implement an empty loop with an iterator that returns all pci host bridges in the system.
Quoted 6 lines
The probe function is triggered by adding an own root device for RCHs. This is different to CXL VH where an ACPI "ACPI0017" root device exists. Its detection starts the CXL host detection. In RCD mode such a device does not necessarily exists, so solve this by creating a plain platform device that is not an ACPI device and is root only for RCHs.
Drive-by nitpicks:
s/PCI root bridges/PCI host bridges/ to match other uses s/pci host bridges/PCI host bridges/ to match other "PCI" uses s/does not necessarily exists/does not necessarily exist/
RE: [PATCH 05/15] cxl/acpi: Add probe function to detect restricted CXL hosts in RCD mode
In reply to Robert RichterQuoted 14 lines · Robert Richter
Restricted CXL device (RCD) mode (formerly CXL 1.1) uses a different enumeration scheme other than CXL VH (formerly CXL 2.0). In RCD mode a host/device (RCH-RCD) pair shows up as a legal PCIe hierarchy with an ACPI host bridge ("PNP0A08" or "ACPI0016" HID) and RCiEP connected to it with a description of the CXL device.
Add function
cxl_restricted_host_probe()to probe RCD enumerated devices. The function implements a loop that detects all CXL capable ACPI PCI root bridges in the system (RCD mode only). The iterator functioncxl_find_next_rch()is introduced to walk through all of the CXL hosts. The loop will then enable all CXL devices connected to the host. For now, only implement an empty loop with an iterator that returns all pci host bridges in the system.
Quoted 6 lines
The probe function is triggered by adding an own root device for RCHs. This is different to CXL VH where an ACPI "ACPI0017" root device exists. Its detection starts the CXL host detection. In RCD mode such a device does not necessarily exists, so solve this by creating a plain platform device that is not an ACPI device and is root only for RCHs.
As I mentioned in the cover letter a BIOS that does not provide an ACPI0017 device is opting out of the possibility OS first error handling and other OS CXL services. ACPI0017 is mandatory.
Otherwise, its odd to have a module create the device that its driver is going to drive. That's a backwards driver model and why we proposed ACPI0017 in the first instance.
Quoted 112 lines
Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/acpi.c | 71 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 70 insertions(+), 1 deletion(-)drivers/cxl/acpi.c +70
-1@@ -312,6 +312,33 @@ static int add_root_nvdimm_bridge(struct device *match, void *data)return 1 ; } +struct pci_host_bridge *cxl_find_next_rch (struct pci_host_bridge *host) +{ +struct pci_bus *bus = host ? host->bus :NULL ; + +while ((bus =pci_find_next_bus (bus)) !=NULL ) { + host = bus ?to_pci_host_bridge (bus->bridge) :NULL ; +if (!host) +continue ; + +dev_dbg (&host->dev,"PCI bridge found\n" ); + +return host; + } + +return NULL ; +} + +static int __init cxl_restricted_host_probe (struct platform_device *pdev) +{ +struct pci_host_bridge *host =NULL ; + +while ((host =cxl_find_next_rch (host)) !=NULL ) { + } + +return 0 ; +} +static struct lock_class_key cxl_root_key;static void cxl_acpi_lock_reset_class (void *dev)@@ -445,6 +472,13 @@ static int cxl_acpi_probe(struct platform_device *pdev)struct acpi_device *adev =ACPI_COMPANION (host);struct cxl_cfmws_context ctx; +/* +* For RCH (CXL 1.1 hosts) the probe is triggered by a plain +* platform dev which does not have an acpi companion. +*/ +if (!adev) +return cxl_restricted_host_probe (pdev); +device_lock_set_class (&pdev->dev, &cxl_root_key); rc =devm_add_action_or_reset (&pdev->dev, cxl_acpi_lock_reset_class, &pdev->dev);@@ -518,6 +552,7 @@ MODULE_DEVICE_TABLE(acpi, cxl_acpi_ids);static const struct platform_device_id cxl_test_ids[] = { {"cxl_acpi" }, + {"cxl_root" }, { }, };MODULE_DEVICE_TABLE (platform, cxl_test_ids);@@ -531,7 +566,41 @@ static struct platform_driver cxl_acpi_driver = { .id_table = cxl_test_ids, }; -module_platform_driver (cxl_acpi_driver); +static void cxl_acpi_device_release (struct device *dev) { } + +static struct platform_device cxl_acpi_device = { + .name ="cxl_root" , + .id =PLATFORM_DEVID_NONE , + .dev = { + .release = cxl_acpi_device_release, + } +}; + +static int __init cxl_host_init (void ) +{ +int rc; + +/* Kick off restricted host (CXL 1.1) detection */ + rc =platform_device_register (&cxl_acpi_device); +if (rc) { +platform_device_put (&cxl_acpi_device); +return rc; + } + rc =platform_driver_register (&cxl_acpi_driver); +if (rc) +platform_device_unregister (&cxl_acpi_device); +return rc; +} + +static void __exit cxl_host_exit(void) +{ +platform_driver_unregister (&cxl_acpi_driver); +platform_device_unregister (&cxl_acpi_device); +} + +module_init (cxl_host_init); +module_exit (cxl_host_exit); +MODULE_LICENSE ("GPL v2" );MODULE_IMPORT_NS (CXL );MODULE_IMPORT_NS (ACPI );Signature · 1 line
2.30.2
RE: [PATCH 05/15] cxl/acpi: Add probe function to detect restricted CXL hosts in RCD mode
In reply to Robert RichterQuoted 14 lines · Robert Richter
Restricted CXL device (RCD) mode (formerly CXL 1.1) uses a different enumeration scheme other than CXL VH (formerly CXL 2.0). In RCD mode a host/device (RCH-RCD) pair shows up as a legal PCIe hierarchy with an ACPI host bridge ("PNP0A08" or "ACPI0016" HID) and RCiEP connected to it with a description of the CXL device.
Add function
cxl_restricted_host_probe()to probe RCD enumerated devices. The function implements a loop that detects all CXL capable ACPI PCI root bridges in the system (RCD mode only). The iterator functioncxl_find_next_rch()is introduced to walk through all of the CXL hosts. The loop will then enable all CXL devices connected to the host. For now, only implement an empty loop with an iterator that returns all pci host bridges in the system.
Quoted 6 lines
The probe function is triggered by adding an own root device for RCHs. This is different to CXL VH where an ACPI "ACPI0017" root device exists. Its detection starts the CXL host detection. In RCD mode such a device does not necessarily exists, so solve this by creating a plain platform device that is not an ACPI device and is root only for RCHs.
These host bridges should be discovered by add_host_bridge_dport(), no? Unless the BIOS is failing to emit the expected CEDT along with ACPI0017.
PATCH 6/15 PCI/ACPI: Link host bridge to its ACPI fw node
In reply to Robert RichterA lookup of a host bridge's corresponding acpi device (struct acpi_device) is not possible, for example:
adev = ACPI_COMPANION(&host_bridge->dev);
This could be useful to find a host bridge's fwnode handle and to determine and call additional host bridge ACPI parameters and methods such as HID/CID or _UID.
Make this work by linking the host bridge to its ACPI fw node.
--- drivers/acpi/pci_root.c | 1 + 1 file changed, 1 insertion(+)
drivers/acpi/pci_root.c +1 -0
@@ -1083,6 +1083,7 @@ struct pci_bus *acpi_pci_root_create(struct acpi_pci_root *root, goto out_release_info; host_bridge =to_pci_host_bridge (bus->bridge); + host_bridge->dev.fwnode =acpi_fwnode_handle (device);if (!(root->osc_control_set &OSC_PCI_EXPRESS_NATIVE_HP_CONTROL )) host_bridge->native_pcie_hotplug =0 ;if (!(root->osc_control_set &OSC_PCI_SHPC_NATIVE_HP_CONTROL ))
Signature · 1 line
2.30.2
Re: [PATCH 06/15] PCI/ACPI: Link host bridge to its ACPI fw node
Quoted 5 lines · On Wed, 31 Aug 2022 10:15:54 +0200 Robert Richter <[email protected]> wrote:
A lookup of a host bridge's corresponding acpi device (struct
acpi_device) is not possible, for example:adev = ACPI_COMPANION(&host_bridge->dev);
Quoted 7 lines
This could be useful to find a host bridge's fwnode handle and to determine and call additional host bridge ACPI parameters and methods such as HID/CID or
_UID.Make this work by linking the host bridge to its ACPI fw node.
Signed-off-by Robert Richter <[email protected]>
Seems sensible to me, though I'm not an expert in this are of the code.
Quoted 16 lines
--- drivers/acpi/pci_root.c | 1 + 1 file changed, 1 insertion(+)drivers/acpi/pci_root.c +1
-0@@ -1083,6 +1083,7 @@ struct pci_bus *acpi_pci_root_create(struct acpi_pci_root *root, goto out_release_info; host_bridge =to_pci_host_bridge (bus->bridge); + host_bridge->dev.fwnode =acpi_fwnode_handle (device);if (!(root->osc_control_set &OSC_PCI_EXPRESS_NATIVE_HP_CONTROL )) host_bridge->native_pcie_hotplug =0 ;if (!(root->osc_control_set &OSC_PCI_SHPC_NATIVE_HP_CONTROL ))
Re: [PATCH 06/15] PCI/ACPI: Link host bridge to its ACPI fw node
In reply to Robert RichterQuoted 10 lines · Robert Richter
A lookup of a host bridge's corresponding acpi device (struct
acpi_device) is not possible, for example:adev = ACPI_COMPANION(&host_bridge->dev);This could be useful to find a host bridge's fwnode handle and to determine and call additional host bridge ACPI parameters and methods such as HID/CID or
_UID.Make this work by linking the host bridge to its ACPI fw node.
s/acpi device/ACPI device/ to match other "ACPI" usage s/fw node/fwnode/ (if it should match "fwnode handle" above)
I guess this patch makes ACPI_COMPANION() work where it didn't before, right? E.g., the two ACPI_COMPANION() uses added by this series (cxl_find_next_rch() and cxl_restricted_host_probe()).
I'm not really clear on the strategy of when we should use acpi_device vs acpi_handle, but does this mean there's code in places like pci_root.c that should be reworked to take advantage of this? That code evaluates _DSM and _OSC, but I think it currently uses acpi_handle for that.
Bjorn
Rafael J. Wysocki
maintainerRe: [PATCH 06/15] PCI/ACPI: Link host bridge to its ACPI fw node
Quoted 16 lines · Bjorn Helgaas
Quoted 10 lines · Robert Richter
A lookup of a host bridge's corresponding acpi device (struct
acpi_device) is not possible, for example:adev = ACPI_COMPANION(&host_bridge->dev);This could be useful to find a host bridge's fwnode handle and to determine and call additional host bridge ACPI parameters and methods such as HID/CID or
_UID.Make this work by linking the host bridge to its ACPI fw node.
s/acpi device/ACPI device/ to match other "ACPI" usage s/fw node/fwnode/ (if it should match "fwnode handle" above)
Quoted 6 lines
I guess this patch makes
ACPI_COMPANION()work where it didn't before, right? E.g., the twoACPI_COMPANION()uses added by this series (cxl_find_next_rch()andcxl_restricted_host_probe()).I'm not really clear on the strategy of when we should use
acpi_devicevsacpi_handle,
acpi_handle should be used for interactions with the ACPICA code, like when AML is evaluated, and acpi_device for pretty much everything else.
Quoted 4 lines
but does this mean there's code in places like
pci_root.cthat should be reworked to take advantage of this? That code evaluates_DSMand_OSC, but I think it currently usesacpi_handlefor that.
That's fine.
RE: [PATCH 06/15] PCI/ACPI: Link host bridge to its ACPI fw node
In reply to Robert RichterQuoted 8 lines · Robert Richter
A lookup of a host bridge's corresponding acpi device (struct
acpi_device) is not possible, for example:adev = ACPI_COMPANION(&host_bridge->dev);This could be useful to find a host bridge's fwnode handle and to determine and call additional host bridge ACPI parameters and methods such as HID/CID or
_UID.
When is this explicitly needed. "Could be useful" is interesting, but it needs to have a practical need.
Quoted 23 lines
Make this work by linking the host bridge to its ACPI fw node.
Signed-off-by Robert Richter <[email protected]>--- drivers/acpi/pci_root.c | 1 + 1 file changed, 1 insertion(+)drivers/acpi/pci_root.c +1
-0@@ -1083,6 +1083,7 @@ struct pci_bus *acpi_pci_root_create(struct acpi_pci_root *root, goto out_release_info; host_bridge =to_pci_host_bridge (bus->bridge); + host_bridge->dev.fwnode =acpi_fwnode_handle (device);if (!(root->osc_control_set &OSC_PCI_EXPRESS_NATIVE_HP_CONTROL )) host_bridge->native_pcie_hotplug =0 ;if (!(root->osc_control_set &OSC_PCI_SHPC_NATIVE_HP_CONTROL ))Signature · 1 line
2.30.2
Rafael J. Wysocki
maintainerRe: [PATCH 06/15] PCI/ACPI: Link host bridge to its ACPI fw node
Quoted 5 lines · Dan Williams
Quoted 3 lines · Robert Richter
A lookup of a host bridge's corresponding acpi device (struct
acpi_device) is not possible, for example:
Quoted 8 lines
Quoted 5 lines
adev = ACPI_COMPANION(&host_bridge->dev);This could be useful to find a host bridge's fwnode handle and to determine and call additional host bridge ACPI parameters and methods such as HID/CID or
_UID.When is this explicitly needed. "Could be useful" is interesting, but it needs to have a practical need.
It is needed and it is present on x86 AFAICS (see my last reply in this thread).
This seems to be addressing an ARM64-specific issue.
Quoted 25 lines
Quoted 23 lines
Make this work by linking the host bridge to its ACPI fw node.
Signed-off-by Robert Richter <[email protected]>--- drivers/acpi/pci_root.c | 1 + 1 file changed, 1 insertion(+)drivers/acpi/pci_root.c +1
-1@@ -1083,6 +1083,7 @@ struct pci_bus *acpi_pci_root_create(struct acpi_pci_root *root, goto out_release_info; host_bridge =to_pci_host_bridge (bus->bridge); + host_bridge->dev.fwnode =acpi_fwnode_handle (device);if (!(root->osc_control_set &OSC_PCI_EXPRESS_NATIVE_HP_CONTROL )) host_bridge->native_pcie_hotplug =0 ;if (!(root->osc_control_set &OSC_PCI_SHPC_NATIVE_HP_CONTROL )) --2.30.2
Re: [PATCH 06/15] PCI/ACPI: Link host bridge to its ACPI fw node
Quoted 12 lines · Rafael J. Wysocki
Quoted 11 lines · Dan Williams
Quoted 8 lines · Robert Richter
A lookup of a host bridge's corresponding acpi device (struct
acpi_device) is not possible, for example:adev = ACPI_COMPANION(&host_bridge->dev);This could be useful to find a host bridge's fwnode handle and to determine and call additional host bridge ACPI parameters and methods such as HID/CID or
_UID.
Quoted 7 lines
Quoted 2 lines
When is this explicitly needed. "Could be useful" is interesting, but it needs to have a practical need.
It is needed and it is present on x86 AFAICS (see my last reply in this thread).
This seems to be addressing an ARM64-specific issue.
Ah, ok, thanks for pointing that out.
Re: [PATCH 06/15] PCI/ACPI: Link host bridge to its ACPI fw node
Quoted 16 lines · Dan Williams
Quoted 15 lines · Rafael J. Wysocki
Quoted 13 lines · Dan Williams
Quoted 8 lines · Robert Richter
A lookup of a host bridge's corresponding acpi device (struct
acpi_device) is not possible, for example:adev = ACPI_COMPANION(&host_bridge->dev);This could be useful to find a host bridge's fwnode handle and to determine and call additional host bridge ACPI parameters and methods such as HID/CID or
_UID.When is this explicitly needed. "Could be useful" is interesting, but it needs to have a practical need.
Quoted 6 lines
Quoted 4 lines
It is needed and it is present on x86 AFAICS (see my last reply in this thread).
This seems to be addressing an ARM64-specific issue.
Ah, ok, thanks for pointing that out.
No, it is x86. And true, it is set. So this series is actually working without this patch. It can be dropped.
Now, I just checked my logs. The reason I was adding this is that during code development I modified the code to have bridge->dev.parent set. Then, the fwnode is not linked. I later dropped that change but kept this patch.
Thanks for catching this.
-Robert
Re: [PATCH 06/15] PCI/ACPI: Link host bridge to its ACPI fw node
Quoted 14 lines · Robert Richter
Quoted 4 lines · Dan Williams
Quoted 3 lines · Rafael J. Wysocki
Quoted 2 lines · Dan Williams
Robert Richter wrote:
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
A lookup of a host bridge's corresponding acpi device (struct
acpi_device) is not possible, for example:adev = ACPI_COMPANION(&host_bridge->dev);This could be useful to find a host bridge's fwnode handle and to determine and call additional host bridge ACPI parameters and methods such as HID/CID or
_UID.
Quoted 8 lines
...
No, it is x86. And true, it is set. So this series is actually working without this patch. It can be dropped.Now, I just checked my logs. The reason I was adding this is that during code development I modified the code to have
bridge->dev.parentset. Then, the fwnode is not linked. I later dropped that change but kept this patch.
If this patch does the same thing as the ACPI_COMPANION_SET() in several pcibios_root_bridge_prepare() implementations, I would love to keep this patch, which does it in a generic place, and drop the corresponding code from those arch-specific functions.
But I don't understand the fwnode stuff well enough to know if this is feasible.
Bjorn
Re: [PATCH 06/15] PCI/ACPI: Link host bridge to its ACPI fw node
Quoted 24 lines · Bjorn Helgaas
Quoted 14 lines · Robert Richter
Quoted 4 lines · Dan Williams
Quoted 3 lines · Rafael J. Wysocki
Quoted 2 lines · Dan Williams
Robert Richter wrote:
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
A lookup of a host bridge's corresponding acpi device (struct
acpi_device) is not possible, for example:adev = ACPI_COMPANION(&host_bridge->dev);This could be useful to find a host bridge's fwnode handle and to determine and call additional host bridge ACPI parameters and methods such as HID/CID or
_UID.Quoted 8 lines
...
No, it is x86. And true, it is set. So this series is actually working without this patch. It can be dropped.Now, I just checked my logs. The reason I was adding this is that during code development I modified the code to have
bridge->dev.parentset. Then, the fwnode is not linked. I later dropped that change but kept this patch.
Quoted 7 lines
If this patch does the same thing as the
ACPI_COMPANION_SET()in severalpcibios_root_bridge_prepare()implementations, I would love to keep this patch, which does it in a generic place, and drop the corresponding code from those arch-specific functions.But I don't understand the fwnode stuff well enough to know if this is feasible.
I took a brief look, but I could not convince myself that these lookups:
arch/ia64/pci/pci.c ((struct pci_controller *) bridge->bus->sysdata)->companion arch/loongarch/pci/acpi.c to_acpi_device(((struct pci_config_window *) bridge->bus->sysdata)->parent) arch/arm64/kernel/pci.c to_acpi_device(((struct pci_config_window *) bridge->bus->sysdata)->parent) arch/x86/pci/acpi.c ((struct pci_sysdata *) bridge->bus->sysdata)->companion
...are identical to what acpi_pci_root_add() used to create the acpi_pci_root.
Rafael J. Wysocki
maintainerRe: [PATCH 06/15] PCI/ACPI: Link host bridge to its ACPI fw node
In reply to Robert RichterQuoted 5 lines · Robert Richter
A lookup of a host bridge's corresponding acpi device (struct
acpi_device) is not possible, for example:adev = ACPI_COMPANION(&host_bridge->dev);
Hmm.
x86 has this code in pcibios_root_bridge_prepare():
if (!bridge->dev.parent) {
struct pci_sysdata *sd = bridge->bus->sysdata;
ACPI_COMPANION_SET(&bridge->dev, sd->companion);
}which should set the ACPI companion for the host bridge.
Moreover, on my x86 desktop /sys/devices/pci0000\:00/ (which is the host bridge AFAICS) has
firmware_node -> ../LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00
so clearly the ACPI companion is there.
Are we talking about ARM64 here?
Quoted 16 lines
This could be useful to find a host bridge's fwnode handle and to determine and call additional host bridge ACPI parameters and methods such as HID/CID or
_UID.Make this work by linking the host bridge to its ACPI fw node.
Signed-off-by Robert Richter <[email protected]>--- drivers/acpi/pci_root.c | 1 + 1 file changed, 1 insertion(+)drivers/acpi/pci_root.c +0
-0
drivers/acpi/pci_root.c struct pci_bus *acpi_pci_root_create(struct acpi_pci_root *root, · line 1086
Quoted 4 lines
drivers/acpi/pci_root.c +1
-0@@ -1083,6 +1083,7 @@ struct pci_bus *acpi_pci_root_create(struct acpi_pci_root *root, goto out_release_info; host_bridge =to_pci_host_bridge (bus->bridge); + host_bridge->dev.fwnode =acpi_fwnode_handle (device);
So this would be replacing the existing mechanism on x86, right?
Quoted 4 lines
drivers/acpi/pci_root.c +0
-1if (!(root->osc_control_set &OSC_PCI_EXPRESS_NATIVE_HP_CONTROL )) host_bridge->native_pcie_hotplug =0 ;if (!(root->osc_control_set &OSC_PCI_SHPC_NATIVE_HP_CONTROL )) --
PATCH 7/15 cxl/acpi: Check RCH's PCIe Host Bridge ACPI ID
In reply to Robert RichterAn RCH is a root bridge and has "PNP0A08" or "ACPI0016" ACPI ID set. Check this.
--- drivers/cxl/acpi.c | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+)
drivers/cxl/acpi.c +20 -0
@@ -312,9 +312,16 @@ static int add_root_nvdimm_bridge(struct device *match, void *data)return 1 ; } +static const struct acpi_device_id cxl_host_ids[] = { + {"ACPI0016" ,0 }, + {"PNP0A08" ,0 }, + { }, +}; +struct pci_host_bridge *cxl_find_next_rch (struct pci_host_bridge *host) {struct pci_bus *bus = host ? host->bus :NULL ; +struct acpi_device *adev;while ((bus =pci_find_next_bus (bus)) !=NULL ) { host = bus ?to_pci_host_bridge (bus->bridge) :NULL ;
@@ -323,6 +330,19 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)dev_dbg (&host->dev,"PCI bridge found\n" ); +/* Must be a root bridge */ +if (host->bus->parent) +continue ; + +dev_dbg (&host->dev,"PCI bridge is root bridge\n" ); + + adev =ACPI_COMPANION (&host->dev); +if (acpi_match_device_ids (adev, cxl_host_ids)) +continue ; + +dev_dbg (&host->dev,"PCI ACPI host found: %s\n" , +acpi_dev_name (adev)); +return host; }
Signature · 1 line
2.30.2
Re: [PATCH 07/15] cxl/acpi: Check RCH's PCIe Host Bridge ACPI ID
Quoted 4 lines · On Wed, 31 Aug 2022 10:15:55 +0200 Robert Richter <[email protected]> wrote:
An RCH is a root bridge and has "PNP0A08" or "ACPI0016" ACPI ID set. Check this.
Signed-off-by Robert Richter <[email protected]>
Hi Robert,
I'm a little uncomfortable with repurposing acpi_device_id as you have done here. Might be better to do the same as in pci_root.c where the matches are done more directly.
Quoted 9 lines
--- drivers/cxl/acpi.c | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+)drivers/cxl/acpi.c +0
-0
drivers/cxl/acpi.c static int add_root_nvdimm_bridge(struct device *match, void *data) · line 318
Quoted 7 lines
drivers/cxl/acpi.c +4
-0@@ -312,9 +312,16 @@ static int add_root_nvdimm_bridge(struct device *match, void *data)return 1 ; } +static const struct acpi_device_id cxl_host_ids[] = { + {"ACPI0016" ,0 }, + {"PNP0A08" ,0 }, + { },
Trivial but no comma after a null terminator. Always good to make
it harder for people to add things where they really shouldn't!
pci_root.c avoids using an acpi_device_id table for similar matching. I think the point being to separate probe type use of this table from cases where we aren't using a normal device probe.
So to remain consistent with that, I would just grab the hid and match it directly in this code.
I don't feel that strongly about this if the ACPI maintainers are fine with reusing this infrastructure as you have it here.
Quoted 29 lines
drivers/cxl/acpi.c +16
-0+}; +struct pci_host_bridge *cxl_find_next_rch (struct pci_host_bridge *host) {struct pci_bus *bus = host ? host->bus :NULL ; +struct acpi_device *adev;while ((bus =pci_find_next_bus (bus)) !=NULL ) { host = bus ?to_pci_host_bridge (bus->bridge) :NULL ;@@ -323,6 +330,19 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)dev_dbg (&host->dev,"PCI bridge found\n" ); +/* Must be a root bridge */ +if (host->bus->parent) +continue ; + +dev_dbg (&host->dev,"PCI bridge is root bridge\n" ); + + adev =ACPI_COMPANION (&host->dev); +if (acpi_match_device_ids (adev, cxl_host_ids)) +continue ; + +dev_dbg (&host->dev,"PCI ACPI host found: %s\n" , +acpi_dev_name (adev)); +return host; }
Re: [PATCH 07/15] cxl/acpi: Check RCH's PCIe Host Bridge ACPI ID
Quoted 9 lines · Jonathan Cameron
drivers/cxl/acpi.c static int add_root_nvdimm_bridge(struct device *match, void *data) · line 318
Quoted 4 lines · Robert Richter
drivers/cxl/acpi.c +4
-0+static const struct acpi_device_id cxl_host_ids[] = { + {"ACPI0016" ,0 }, + {"PNP0A08" ,0 }, + { },Trivial but no comma after a null terminator. Always good to make
it harder for people to add things where they really shouldn't!
Can do this.
Quoted 5 lines
pci_root.cavoids using anacpi_device_idtable for similar matching. I think the point being to separate probe type use of this table from cases where we aren't using a normal device probe.
So to remain consistent with that, I would just grab the hid and match it directly in this code.
Grabbing the hid only is actually a violation of the acpi spec as a cid could be used interchangeable. It must also work then.
It is also not possible to use something like probe or a handler matching the ids because the hosts must be enabled with the already existing drivers and handlers. Suppose there are multiple handlers for the same ids, the first handler wins and all other never get called.
To me it looks sane and simple to use acpi_match_device_ids() here.
-Robert
Quoted 3 lines
I don't feel that strongly about this if the ACPI maintainers are fine with reusing this infrastructure as you have it here.
Jonathan Cameron
Reviewed-byRe: [PATCH 07/15] cxl/acpi: Check RCH's PCIe Host Bridge ACPI ID
Quoted 22 lines · On Thu, 1 Sep 2022 08:16:52 +0200 Robert Richter <[email protected]> wrote:
Quoted 9 lines · Jonathan Cameron
drivers/cxl/acpi.c static int add_root_nvdimm_bridge(struct device *match, void *data) · line 318
Quoted 4 lines · Robert Richter
drivers/cxl/acpi.c +4
-0+static const struct acpi_device_id cxl_host_ids[] = { + {"ACPI0016" ,0 }, + {"PNP0A08" ,0 }, + { },Trivial but no comma after a null terminator. Always good to make
it harder for people to add things where they really shouldn't!Can do this.
Quoted 5 lines
pci_root.cavoids using anacpi_device_idtable for similar matching. I think the point being to separate probe type use of this table from cases where we aren't using a normal device probe.
So to remain consistent with that, I would just grab the hid and match it directly in this code.Grabbing the hid only is actually a violation of the acpi spec as a cid could be used interchangeable. It must also work then.
Quoted 6 lines
It is also not possible to use something like probe or a handler matching the ids because the hosts must be enabled with the already existing drivers and handlers. Suppose there are multiple handlers for the same ids, the first handler wins and all other never get called.
To me it looks sane and simple to use
acpi_match_device_ids()here.
Ok. One for the ACPI maintainers to comment on if they wish - I'm fine with this
Quoted 6 lines
-Robert
Quoted 3 lines
I don't feel that strongly about this if the ACPI maintainers are fine with reusing this infrastructure as you have it here.
RE: [PATCH 07/15] cxl/acpi: Check RCH's PCIe Host Bridge ACPI ID
In reply to Robert RichterQuoted 36 lines · Robert Richter
An RCH is a root bridge and has "PNP0A08" or "ACPI0016" ACPI ID set. Check this.
Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/acpi.c | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+)drivers/cxl/acpi.c +10
-0@@ -312,9 +312,16 @@ static int add_root_nvdimm_bridge(struct device *match, void *data)return 1 ; } +static const struct acpi_device_id cxl_host_ids[] = { + {"ACPI0016" ,0 }, + {"PNP0A08" ,0 }, + { }, +}; +struct pci_host_bridge *cxl_find_next_rch (struct pci_host_bridge *host) {struct pci_bus *bus = host ? host->bus :NULL ; +struct acpi_device *adev;while ((bus =pci_find_next_bus (bus)) !=NULL ) { host = bus ?to_pci_host_bridge (bus->bridge) :NULL ;@@ -323,6 +330,19 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)dev_dbg (&host->dev,"PCI bridge found\n" ); +/* Must be a root bridge */ +if (host->bus->parent) +continue ;
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 345
Quoted 10 lines
drivers/cxl/acpi.c +10
-0+ +dev_dbg (&host->dev,"PCI bridge is root bridge\n" ); + + adev =ACPI_COMPANION (&host->dev); +if (acpi_match_device_ids (adev, cxl_host_ids)) +continue ; + +dev_dbg (&host->dev,"PCI ACPI host found: %s\n" , +acpi_dev_name (adev)); +
Again, finding all the ACPI0016 devices is add_host_bridge_dport() already does.
PATCH 8/15 cxl/acpi: Check RCH's CXL DVSEC capabilities
In reply to Robert RichterAn RCH has an RCiEP connected to it with CXL DVSEC capabilities present and the CXL PCIe DVSEC included. Check this.
--- drivers/cxl/acpi.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)
drivers/cxl/acpi.c +17 -0
@@ -322,6 +322,8 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) {struct pci_bus *bus = host ? host->bus :NULL ;struct acpi_device *adev; +struct pci_dev *pdev; +bool is_restricted_host;while ((bus =pci_find_next_bus (bus)) !=NULL ) { host = bus ?to_pci_host_bridge (bus->bridge) :NULL ;
@@ -343,6 +345,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)dev_dbg (&host->dev,"PCI ACPI host found: %s\n" ,acpi_dev_name (adev)); +/* Check CXL DVSEC of dev 0 func 0 */ + pdev =pci_get_slot (bus,PCI_DEVFN (0 ,0 )); + is_restricted_host = pdev + && (pci_pcie_type (pdev) ==PCI_EXP_TYPE_RC_END ) + &&pci_find_dvsec_capability (pdev, +PCI_DVSEC_VENDOR_ID_CXL , +CXL_DVSEC_PCIE_DEVICE ); +pci_dev_put (pdev); + +if (!is_restricted_host) +continue ; + +dev_dbg (&host->dev,"CXL restricted host found\n" ); +return host; }
@@ -354,6 +370,7 @@ static int __init cxl_restricted_host_probe(struct platform_device *pdev)struct pci_host_bridge *host =NULL ;while ((host =cxl_find_next_rch (host)) !=NULL ) { +dev_info (&host->dev,"host supports CXL\n" ); }return 0 ;
Signature · 1 line
2.30.2
Re: [PATCH 08/15] cxl/acpi: Check RCH's CXL DVSEC capabilities
Quoted 4 lines · On Wed, 31 Aug 2022 10:15:56 +0200 Robert Richter <[email protected]> wrote:
An RCH has an RCiEP connected to it with CXL DVSEC capabilities present and the CXL PCIe DVSEC included. Check this.
Signed-off-by Robert Richter <[email protected]>
One comment inline. This looks good to me.
Quoted 18 lines
--- drivers/cxl/acpi.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)drivers/cxl/acpi.c +2
-0@@ -322,6 +322,8 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) {struct pci_bus *bus = host ? host->bus :NULL ;struct acpi_device *adev; +struct pci_dev *pdev; +bool is_restricted_host;while ((bus =pci_find_next_bus (bus)) !=NULL ) { host = bus ?to_pci_host_bridge (bus->bridge) :NULL ;
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 348
Quoted 4 lines
drivers/cxl/acpi.c +1
-0@@ -343,6 +345,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)dev_dbg (&host->dev,"PCI ACPI host found: %s\n" ,acpi_dev_name (adev)); +/* Check CXL DVSEC of dev 0 func 0 */
So assumption here is that the hostbridge has a one or more RCiEPs. The spec (r3.0 9.11.4) allows for the EP to appear behind a root port
- that case always felt odd to me, so I'm fine with not supporting it until we see a user.
Quoted 24 lines
drivers/cxl/acpi.c +14
-0+ pdev =pci_get_slot (bus,PCI_DEVFN (0 ,0 )); + is_restricted_host = pdev + && (pci_pcie_type (pdev) ==PCI_EXP_TYPE_RC_END ) + &&pci_find_dvsec_capability (pdev, +PCI_DVSEC_VENDOR_ID_CXL , +CXL_DVSEC_PCIE_DEVICE ); +pci_dev_put (pdev); + +if (!is_restricted_host) +continue ; + +dev_dbg (&host->dev,"CXL restricted host found\n" ); +return host; }@@ -354,6 +370,7 @@ static int __init cxl_restricted_host_probe(struct platform_device *pdev)struct pci_host_bridge *host =NULL ;while ((host =cxl_find_next_rch (host)) !=NULL ) { +dev_info (&host->dev,"host supports CXL\n" ); }return 0 ;
Re: [PATCH 08/15] cxl/acpi: Check RCH's CXL DVSEC capabilities
Quoted 39 lines · On Wed, 31 Aug 2022 11:52:24 +0100 Jonathan Cameron…
Quoted 4 lines · On Wed, 31 Aug 2022 10:15:56 +0200 Robert Richter <[email protected]> wrote:
An RCH has an RCiEP connected to it with CXL DVSEC capabilities present and the CXL PCIe DVSEC included. Check this.
Signed-off-by Robert Richter <[email protected]>One comment inline. This looks good to me.
Reviewed-by Jonathan Cameron <[email protected]>Quoted 18 lines
--- drivers/cxl/acpi.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)drivers/cxl/acpi.c +2
-0@@ -322,6 +322,8 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) {struct pci_bus *bus = host ? host->bus :NULL ;struct acpi_device *adev; +struct pci_dev *pdev; +bool is_restricted_host;while ((bus =pci_find_next_bus (bus)) !=NULL ) { host = bus ?to_pci_host_bridge (bus->bridge) :NULL ;drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 348
Quoted 4 lines
drivers/cxl/acpi.c +1
-0@@ -343,6 +345,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)dev_dbg (&host->dev,"PCI ACPI host found: %s\n" ,acpi_dev_name (adev)); +/* Check CXL DVSEC of dev 0 func 0 */ So assumption here is that the hostbridge has a one or more RCiEPs. The spec (r3.0 9.11.4) allows for the EP to appear behind a root port
- that case always felt odd to me, so I'm fine with not supporting it until we see a user.
Quoted 6 lines
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 354
Quoted 6 lines
drivers/cxl/acpi.c +6
-0+ pdev =pci_get_slot (bus,PCI_DEVFN (0 ,0 )); + is_restricted_host = pdev + && (pci_pcie_type (pdev) ==PCI_EXP_TYPE_RC_END ) + &&pci_find_dvsec_capability (pdev, +PCI_DVSEC_VENDOR_ID_CXL , +CXL_DVSEC_PCIE_DEVICE );
Thinking a bit more on this. I'm not sure this is sufficient. Nothing in CXL 2.0 or later prevents true RCiEP devices (there are a few references in CXL 3.0 e.g. 9.12.1 has RCDs or CXL RCiEPs - so just detecting that there is one on the host bridge might not be sufficient to distinguish this from a non RCH / RCB.
Quoted 19 lines
Quoted 18 lines
drivers/cxl/acpi.c +8
-0+pci_dev_put (pdev); + +if (!is_restricted_host) +continue ; + +dev_dbg (&host->dev,"CXL restricted host found\n" ); +return host; }@@ -354,6 +370,7 @@ static int __init cxl_restricted_host_probe(struct platform_device *pdev)struct pci_host_bridge *host =NULL ;while ((host =cxl_find_next_rch (host)) !=NULL ) { +dev_info (&host->dev,"host supports CXL\n" ); }return 0 ;
Re: [PATCH 08/15] cxl/acpi: Check RCH's CXL DVSEC capabilities
Quoted 23 lines · Jonathan Cameron
Quoted 23 lines
Quoted 10 lines · On Wed, 31 Aug 2022 10:15:56 +0200 Robert Richter <[email protected]> wrote:
drivers/cxl/acpi.c +2
-0@@ -322,6 +322,8 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) {struct pci_bus *bus = host ? host->bus :NULL ;struct acpi_device *adev; +struct pci_dev *pdev; +bool is_restricted_host;while ((bus =pci_find_next_bus (bus)) !=NULL ) { host = bus ?to_pci_host_bridge (bus->bridge) :NULL ;drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 348
Quoted 4 lines
drivers/cxl/acpi.c +1
-0@@ -343,6 +345,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)dev_dbg (&host->dev,"PCI ACPI host found: %s\n" ,acpi_dev_name (adev)); +/* Check CXL DVSEC of dev 0 func 0 */ So assumption here is that the hostbridge has a one or more RCiEPs. The spec (r3.0 9.11.4) allows for the EP to appear behind a root port
- that case always felt odd to me, so I'm fine with not supporting it until we see a user.
Quoted 12 lines
Quoted 6 lines
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 354
Quoted 6 lines
drivers/cxl/acpi.c +6
-0+ pdev =pci_get_slot (bus,PCI_DEVFN (0 ,0 )); + is_restricted_host = pdev + && (pci_pcie_type (pdev) ==PCI_EXP_TYPE_RC_END ) + &&pci_find_dvsec_capability (pdev, +PCI_DVSEC_VENDOR_ID_CXL , +CXL_DVSEC_PCIE_DEVICE );Thinking a bit more on this. I'm not sure this is sufficient. Nothing in CXL 2.0 or later prevents true RCiEP devices (there are a few references in CXL 3.0 e.g. 9.12.1 has RCDs or CXL RCiEPs - so just detecting that there is one on the host bridge might not be sufficient to distinguish this from a non RCH / RCB.
An RCD has its own host bridge created (software view, not the phys topology). Host and device are paired in this case. Non-RCDs are standard endpoints and not RCiEPs, they have their own host. There cannot be both types connected to the same host.
Again, see figure 9-12 and 9-13.
-Robert
Quoted 21 lines
Quoted 20 lines
Quoted 19 lines
drivers/cxl/acpi.c +8
-0+pci_dev_put (pdev); + +if (!is_restricted_host) +continue ; + +dev_dbg (&host->dev,"CXL restricted host found\n" ); +return host; }@@ -354,6 +370,7 @@ static int __init cxl_restricted_host_probe(struct platform_device *pdev)struct pci_host_bridge *host =NULL ;while ((host =cxl_find_next_rch (host)) !=NULL ) { +dev_info (&host->dev,"host supports CXL\n" ); }return 0 ;
Re: [PATCH 08/15] cxl/acpi: Check RCH's CXL DVSEC capabilities
Quoted 37 lines · On Thu, 1 Sep 2022 08:38:52 +0200 Robert Richter <[email protected]> wrote:
Quoted 23 lines · Jonathan Cameron
Quoted 23 lines
Quoted 10 lines · On Wed, 31 Aug 2022 10:15:56 +0200 Robert Richter <[email protected]> wrote:
drivers/cxl/acpi.c +2
-0@@ -322,6 +322,8 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) {struct pci_bus *bus = host ? host->bus :NULL ;struct acpi_device *adev; +struct pci_dev *pdev; +bool is_restricted_host;while ((bus =pci_find_next_bus (bus)) !=NULL ) { host = bus ?to_pci_host_bridge (bus->bridge) :NULL ;drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 348
Quoted 4 lines
drivers/cxl/acpi.c +1
-0@@ -343,6 +345,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)dev_dbg (&host->dev,"PCI ACPI host found: %s\n" ,acpi_dev_name (adev)); +/* Check CXL DVSEC of dev 0 func 0 */ So assumption here is that the hostbridge has a one or more RCiEPs. The spec (r3.0 9.11.4) allows for the EP to appear behind a root port
- that case always felt odd to me, so I'm fine with not supporting it until we see a user.Quoted 12 lines
Quoted 6 lines
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 354
Quoted 6 lines
drivers/cxl/acpi.c +6
-0+ pdev =pci_get_slot (bus,PCI_DEVFN (0 ,0 )); + is_restricted_host = pdev + && (pci_pcie_type (pdev) ==PCI_EXP_TYPE_RC_END ) + &&pci_find_dvsec_capability (pdev, +PCI_DVSEC_VENDOR_ID_CXL , +CXL_DVSEC_PCIE_DEVICE );Thinking a bit more on this. I'm not sure this is sufficient. Nothing in CXL 2.0 or later prevents true RCiEP devices (there are a few references in CXL 3.0 e.g. 9.12.1 has RCDs or CXL RCiEPs - so just detecting that there is one on the host bridge might not be sufficient to distinguish this from a non RCH / RCB.
Quoted 3 lines
An RCD has its own host bridge created (software view, not the phys topology). Host and device are paired in this case. Non-RCDs are standard endpoints and not RCiEPs, they have their own host.
I disagree. CXL spec does not exclude the possibility of real CXL RCiEPs. So a CXL 2.0+ device that talks CXL configuration for some reason but is part of the root complex itself (maybe a chiplet or something where there isn't necessarily a real CXL bus involved). Same reason we have RCiEPs in normal PCIe.
Chasing references - there is only one I can find (CXL r3.0 9.12.1) "If a Host bridge is not associated with RCDs or CXL RCiEPs."
Both listed because they are different things.
(I think it's fine to say here that this has been queried in appropriate place in the past and is something that is allowed).
So I still don't think the above check is sufficient'. If you happen to have just one CXL 2.0+ RCiEP on a host bridge with not root ports, then the check will identify it as a restriced host. Maybe I'm missing another check that wouldn't though....
Quoted 4 lines
There
cannot be both types connected to the same host.Again, see figure 9-12 and 9-13.
Examples - don't show all the crazy things people are allowed to build - you would need an awful lot of diagrams to do that.
Quoted 24 lines
-Robert
Quoted 21 lines
Quoted 20 lines
Quoted 19 lines
drivers/cxl/acpi.c +8
-0+pci_dev_put (pdev); + +if (!is_restricted_host) +continue ; + +dev_dbg (&host->dev,"CXL restricted host found\n" ); +return host; }@@ -354,6 +370,7 @@ static int __init cxl_restricted_host_probe(struct platform_device *pdev)struct pci_host_bridge *host =NULL ;while ((host =cxl_find_next_rch (host)) !=NULL ) { +dev_info (&host->dev,"host supports CXL\n" ); }return 0 ;
Re: [PATCH 08/15] cxl/acpi: Check RCH's CXL DVSEC capabilities
Quoted 62 lines · Jonathan Cameron
Quoted 37 lines · On Thu, 1 Sep 2022 08:38:52 +0200 Robert Richter <[email protected]> wrote:
Quoted 23 lines · Jonathan Cameron
Quoted 23 lines
Quoted 10 lines · On Wed, 31 Aug 2022 10:15:56 +0200 Robert Richter <[email protected]> wrote:
drivers/cxl/acpi.c +2
-0@@ -322,6 +322,8 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) {struct pci_bus *bus = host ? host->bus :NULL ;struct acpi_device *adev; +struct pci_dev *pdev; +bool is_restricted_host;while ((bus =pci_find_next_bus (bus)) !=NULL ) { host = bus ?to_pci_host_bridge (bus->bridge) :NULL ;drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 348
Quoted 4 lines
drivers/cxl/acpi.c +1
-0@@ -343,6 +345,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)dev_dbg (&host->dev,"PCI ACPI host found: %s\n" ,acpi_dev_name (adev)); +/* Check CXL DVSEC of dev 0 func 0 */ So assumption here is that the hostbridge has a one or more RCiEPs. The spec (r3.0 9.11.4) allows for the EP to appear behind a root port
- that case always felt odd to me, so I'm fine with not supporting it until we see a user.Quoted 12 lines
Quoted 6 lines
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 354
Quoted 6 lines
drivers/cxl/acpi.c +6
-0+ pdev =pci_get_slot (bus,PCI_DEVFN (0 ,0 )); + is_restricted_host = pdev + && (pci_pcie_type (pdev) ==PCI_EXP_TYPE_RC_END ) + &&pci_find_dvsec_capability (pdev, +PCI_DVSEC_VENDOR_ID_CXL , +CXL_DVSEC_PCIE_DEVICE );Thinking a bit more on this. I'm not sure this is sufficient. Nothing in CXL 2.0 or later prevents true RCiEP devices (there are a few references in CXL 3.0 e.g. 9.12.1 has RCDs or CXL RCiEPs - so just detecting that there is one on the host bridge might not be sufficient to distinguish this from a non RCH / RCB.
Quoted 3 lines
An RCD has its own host bridge created (software view, not the phys topology). Host and device are paired in this case. Non-RCDs are standard endpoints and not RCiEPs, they have their own host.
I disagree. CXL spec does not exclude the possibility of real CXL RCiEPs. So a CXL 2.0+ device that talks CXL configuration for some reason but is part of the root complex itself (maybe a chiplet or something where there isn't necessarily a real CXL bus involved). Same reason we have RCiEPs in normal PCIe.
Chasing references - there is only one I can find (CXL r3.0 9.12.1) "If a Host bridge is not associated with RCDs or CXL RCiEPs."
Both listed because they are different things.
(I think it's fine to say here that this has been queried in appropriate place in the past and is something that is allowed).So I still don't think the above check is sufficient'. If you happen to have just one CXL 2.0+ RCiEP on a host bridge with not root ports, then the check will identify it as a restriced host. Maybe I'm missing another check that wouldn't though....
Quoted 6 lines
Quoted 4 lines
There
cannot be both types connected to the same host.Again, see figure 9-12 and 9-13.
Examples - don't show all the crazy things people are allowed to build - you would need an awful lot of diagrams to do that.
Right, there are references to CXL 2.0+ devices implemented as RCiEPs.
"9.12 CXL VH Enumeration" states that for the CXL Host Bridge identification the CEDT should be used:
"""
CXL Early Discovery Table (CEDT) may be used to differentiate between the three software concepts listed above. """
This check is added in patch #10 where the RCRB is extracted, so we are good here.
-Robert
Re: [PATCH 08/15] cxl/acpi: Check RCH's CXL DVSEC capabilities
In reply to Jonathan CameronQuoted 20 lines · Jonathan Cameron
Quoted 17 lines · On Wed, 31 Aug 2022 10:15:56 +0200 Robert Richter <[email protected]> wrote:
drivers/cxl/acpi.c +2
-0@@ -322,6 +322,8 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) {struct pci_bus *bus = host ? host->bus :NULL ;struct acpi_device *adev; +struct pci_dev *pdev; +bool is_restricted_host;while ((bus =pci_find_next_bus (bus)) !=NULL ) { host = bus ?to_pci_host_bridge (bus->bridge) :NULL ;@@ -343,6 +345,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)dev_dbg (&host->dev,"PCI ACPI host found: %s\n" ,acpi_dev_name (adev));
Quoted 6 lines
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 348
Quoted 1 line
drivers/cxl/acpi.c +1
-0+/* Check CXL DVSEC of dev 0 func 0 */ So assumption here is that the hostbridge has a one or more RCiEPs. The spec (r3.0 9.11.4) allows for the EP to appear behind a root port
- that case always felt odd to me, so I'm fine with not supporting it until we see a user.
The software view of an RCD is always the same, it shows up always as an RCiEP. See figure 9-12 and 9-13 of the spec.
-Robert
Quoted 16 lines
Quoted 16 lines
drivers/cxl/acpi.c +13
-0+ pdev =pci_get_slot (bus,PCI_DEVFN (0 ,0 )); + is_restricted_host = pdev + && (pci_pcie_type (pdev) ==PCI_EXP_TYPE_RC_END ) + &&pci_find_dvsec_capability (pdev, +PCI_DVSEC_VENDOR_ID_CXL , +CXL_DVSEC_PCIE_DEVICE ); +pci_dev_put (pdev); + +if (!is_restricted_host) +continue ; + +dev_dbg (&host->dev,"CXL restricted host found\n" ); +return host; }
Re: [PATCH 08/15] cxl/acpi: Check RCH's CXL DVSEC capabilities
Quoted 28 lines · On Thu, 1 Sep 2022 08:30:49 +0200 Robert Richter <[email protected]> wrote:
Quoted 20 lines · Jonathan Cameron
Quoted 17 lines · On Wed, 31 Aug 2022 10:15:56 +0200 Robert Richter <[email protected]> wrote:
drivers/cxl/acpi.c +2
-0@@ -322,6 +322,8 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) {struct pci_bus *bus = host ? host->bus :NULL ;struct acpi_device *adev; +struct pci_dev *pdev; +bool is_restricted_host;while ((bus =pci_find_next_bus (bus)) !=NULL ) { host = bus ?to_pci_host_bridge (bus->bridge) :NULL ;@@ -343,6 +345,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)dev_dbg (&host->dev,"PCI ACPI host found: %s\n" ,acpi_dev_name (adev));Quoted 6 lines
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 348
Quoted 1 line
drivers/cxl/acpi.c +1
-0+/* Check CXL DVSEC of dev 0 func 0 */ So assumption here is that the hostbridge has a one or more RCiEPs. The spec (r3.0 9.11.4) allows for the EP to appear behind a root port
- that case always felt odd to me, so I'm fine with not supporting it until we see a user.
Quoted 2 lines
The software view of an RCD is always the same, it shows up always as an RCiEP. See figure 9-12 and 9-13 of the spec.
Ah. I see I misread the following from CXL r3.0 9.11.4
"This ACPI Host Bridge spawns a legal PCIe hierarchy. All PCIe Endpoints located in the RCD are children of this ACPI Host Bridge. These Endpoints may appear directly on the Root bus number or may appear behind a Root Port located on the Root bus."
I guess that is allowing 'additional' PCIe endpoints below a root port attached to the ACPI Host Bridge, but not dev 0 func 0. That's a subtle distinction I missed.
Quoted 19 lines
-Robert
Quoted 16 lines
Quoted 16 lines
drivers/cxl/acpi.c +13
-0+ pdev =pci_get_slot (bus,PCI_DEVFN (0 ,0 )); + is_restricted_host = pdev + && (pci_pcie_type (pdev) ==PCI_EXP_TYPE_RC_END ) + &&pci_find_dvsec_capability (pdev, +PCI_DVSEC_VENDOR_ID_CXL , +CXL_DVSEC_PCIE_DEVICE ); +pci_dev_put (pdev); + +if (!is_restricted_host) +continue ; + +dev_dbg (&host->dev,"CXL restricted host found\n" ); +return host; }
RE: [PATCH 08/15] cxl/acpi: Check RCH's CXL DVSEC capabilities
In reply to Robert RichterQuoted 22 lines · Robert Richter
An RCH has an RCiEP connected to it with CXL DVSEC capabilities present and the CXL PCIe DVSEC included. Check this.
Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/acpi.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)drivers/cxl/acpi.c +2
-0@@ -322,6 +322,8 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) {struct pci_bus *bus = host ? host->bus :NULL ;struct acpi_device *adev; +struct pci_dev *pdev; +bool is_restricted_host;while ((bus =pci_find_next_bus (bus)) !=NULL ) { host = bus ?to_pci_host_bridge (bus->bridge) :NULL ;
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 354
Quoted 10 lines
drivers/cxl/acpi.c +7
-0@@ -343,6 +345,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)dev_dbg (&host->dev,"PCI ACPI host found: %s\n" ,acpi_dev_name (adev)); +/* Check CXL DVSEC of dev 0 func 0 */ + pdev =pci_get_slot (bus,PCI_DEVFN (0 ,0 )); + is_restricted_host = pdev + && (pci_pcie_type (pdev) ==PCI_EXP_TYPE_RC_END ) + &&pci_find_dvsec_capability (pdev, +PCI_DVSEC_VENDOR_ID_CXL , +CXL_DVSEC_PCIE_DEVICE );
The check looks good, just the matter of integrating it into the existing ACPI0016 device detection.
PATCH 9/15 cxl/acpi: Determine PCI host bridge's ACPI UID
In reply to Robert RichterThe UID is needed to read the RCH's CEDT entry with the RCRB base address. Determine the host's UID from its ACPI fw node.
--- drivers/cxl/acpi.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
drivers/cxl/acpi.c +12 -0
@@ -368,8 +368,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ; +struct acpi_device *adev; +unsigned long long uid = ~0 ;while ((host =cxl_find_next_rch (host)) !=NULL ) { + adev =ACPI_COMPANION (&host->dev); +if (!adev || !adev->pnp.unique_id || + (kstrtoull (adev->pnp.unique_id,10 , &uid) <0 )) +continue ; + +dev_dbg (&adev->dev,"host uid: %llu\n" , uid); + +if (uid >U32_MAX ) +continue ; +dev_info (&host->dev,"host supports CXL\n" ); }
Signature · 1 line
2.30.2
Re: [PATCH 09/15] cxl/acpi: Determine PCI host bridge's ACPI UID
Quoted 13 lines · On Wed, 31 Aug 2022 10:15:57 +0200 Robert Richter <[email protected]> wrote:
The UID is needed to read the RCH's CEDT entry with the RCRB base address. Determine the host's UID from its ACPI fw node.
Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/acpi.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)drivers/cxl/acpi.c +0
-0
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 377
Quoted 10 lines
drivers/cxl/acpi.c +5
-0@@ -368,8 +368,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ; +struct acpi_device *adev; +unsigned long long uid = ~0 ;while ((host =cxl_find_next_rch (host)) !=NULL ) { + adev =ACPI_COMPANION (&host->dev); +if (!adev || !adev->pnp.unique_id || + (kstrtoull (adev->pnp.unique_id,10 , &uid) <0 ))
There is an acpi_device_uid() accessor function that should probably be used here.
Also, should a fialure to convert to an integer (or one within limits) be something we paper over? Feels like we should fail hard if that happens.
Admittedly I can't immediately find any spec that states that the _UID should be either integer or under 32 bits... ACPI allows a string and CXL just says it's 4 bytes long.
Quoted 10 lines
drivers/cxl/acpi.c +7
-0+continue ; + +dev_dbg (&adev->dev,"host uid: %llu\n" , uid); + +if (uid >U32_MAX ) +continue ; +dev_info (&host->dev,"host supports CXL\n" ); }
Re: [PATCH 09/15] cxl/acpi: Determine PCI host bridge's ACPI UID
Quoted 22 lines · Jonathan Cameron
Quoted 19 lines · On Wed, 31 Aug 2022 10:15:57 +0200 Robert Richter <[email protected]> wrote:
The UID is needed to read the RCH's CEDT entry with the RCRB base address. Determine the host's UID from its ACPI fw node.
Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/acpi.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)drivers/cxl/acpi.c +2
-0@@ -368,8 +368,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ; +struct acpi_device *adev; +unsigned long long uid = ~0 ;
Quoted 7 lines
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 377
Quoted 4 lines
drivers/cxl/acpi.c +3
-0while ((host =cxl_find_next_rch (host)) !=NULL ) { + adev =ACPI_COMPANION (&host->dev); +if (!adev || !adev->pnp.unique_id || + (kstrtoull (adev->pnp.unique_id,10 , &uid) <0 ))There is an
acpi_device_uid()accessor function that should probably be used here.
That accessor actually does not help really, there is no null pointer check for adev. Using it actually adds more complexity since another variable is introduced plus you need to look at the function's implementation anyway.
The adev->pnp.unique_id access pattern is widely used in the kernel, I don't expect changes in the data struct here.
Quoted 3 lines
Also, should a fialure to convert to an integer (or one within limits) be something we paper over? Feels like we should fail hard if that happens.
This is a real corner case and close to a broken firmware implementation. I think current dbg messages are good to find where the detection stops.
Quoted 3 lines
Admittedly I can't immediately find any spec that states that the
_UIDshould be either integer or under 32 bits... ACPI allows a string and CXL just says it's 4 bytes long.
IIRC the UID can be implemented as string or 8 bytes, there is no limitation then. That's why the range check below.
-Robert
Quoted 12 lines
Quoted 11 lines
drivers/cxl/acpi.c +7
-0+continue ; + +dev_dbg (&adev->dev,"host uid: %llu\n" , uid); + +if (uid >U32_MAX ) +continue ; +dev_info (&host->dev,"host supports CXL\n" ); }
Jonathan Cameron
Reviewed-byRe: [PATCH 09/15] cxl/acpi: Determine PCI host bridge's ACPI UID
Quoted 31 lines · On Thu, 1 Sep 2022 08:53:36 +0200 Robert Richter <[email protected]> wrote:
Quoted 22 lines · Jonathan Cameron
Quoted 19 lines · On Wed, 31 Aug 2022 10:15:57 +0200 Robert Richter <[email protected]> wrote:
The UID is needed to read the RCH's CEDT entry with the RCRB base address. Determine the host's UID from its ACPI fw node.
Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/acpi.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)drivers/cxl/acpi.c +2
-0@@ -368,8 +368,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ; +struct acpi_device *adev; +unsigned long long uid = ~0 ;Quoted 7 lines
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 377
Quoted 4 lines
drivers/cxl/acpi.c +3
-0while ((host =cxl_find_next_rch (host)) !=NULL ) { + adev =ACPI_COMPANION (&host->dev); +if (!adev || !adev->pnp.unique_id || + (kstrtoull (adev->pnp.unique_id,10 , &uid) <0 ))There is an
acpi_device_uid()accessor function that should probably be used here.
Quoted 7 lines
That accessor actually does not help really, there is no null pointer check for adev. Using it actually adds more complexity since another variable is introduced plus you need to look at the function's implementation anyway.
The
adev->pnp.unique_idaccess pattern is widely used in the kernel, I don't expect changes in the data struct here.
Ok.
Quoted 8 lines
Quoted 4 lines
Also, should a fialure to convert to an integer (or one within limits) be something we paper over? Feels like we should fail hard if that happens.
This is a real corner case and close to a broken firmware implementation. I think current dbg messages are good to find where the detection stops.
Hmm. I don't like papering over such bugs as it leads to people not fixing their bios as early as they otherwise would,
but fair enough I guess.
Quoted 7 lines
Quoted 4 lines
Admittedly I can't immediately find any spec that states that the
_UIDshould be either integer or under 32 bits... ACPI allows a string and CXL just says it's 4 bytes long.IIRC the UID can be implemented as string or 8 bytes, there is no limitation then. That's why the range check below.
Ok.
All queries answered so
Quoted 15 lines
-Robert
Quoted 12 lines
Quoted 11 lines
drivers/cxl/acpi.c +7
-0+continue ; + +dev_dbg (&adev->dev,"host uid: %llu\n" , uid); + +if (uid >U32_MAX ) +continue ; +dev_info (&host->dev,"host supports CXL\n" ); }
RE: [PATCH 09/15] cxl/acpi: Determine PCI host bridge's ACPI UID
In reply to Robert RichterQuoted 19 lines · Robert Richter
The UID is needed to read the RCH's CEDT entry with the RCRB base address. Determine the host's UID from its ACPI fw node.
Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/acpi.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)drivers/cxl/acpi.c +2
-0@@ -368,8 +368,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ; +struct acpi_device *adev; +unsigned long long uid = ~0 ;
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 383
Quoted 10 lines
drivers/cxl/acpi.c +9
-0while ((host =cxl_find_next_rch (host)) !=NULL ) { + adev =ACPI_COMPANION (&host->dev); +if (!adev || !adev->pnp.unique_id || + (kstrtoull (adev->pnp.unique_id,10 , &uid) <0 )) +continue ; + +dev_dbg (&adev->dev,"host uid: %llu\n" , uid); + +if (uid >U32_MAX ) +continue ;
Looks redundant with existing _UID matching.
Re: [PATCH 09/15] cxl/acpi: Determine PCI host bridge's ACPI UID
In reply to Robert RichterQuoted 17 lines · Robert Richter
The UID is needed to read the RCH's CEDT entry with the RCRB base address. Determine the host's UID from its ACPI fw node.
Signed-off-by Robert Richter <[email protected]>---
drivers/cxl/acpi.c| 12 ++++++++++++1 file changed, 12 insertions(+)drivers/cxl/acpi.c +0
-0
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 377
Quoted 10 lines
drivers/cxl/acpi.c +5
-0@@ -368,8 +368,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ; +struct acpi_device *adev; +unsigned long long uid = ~0 ;while ((host =cxl_find_next_rch (host)) !=NULL ) { + adev =ACPI_COMPANION (&host->dev); +if (!adev || !adev->pnp.unique_id || + (kstrtoull (adev->pnp.unique_id,10 , &uid) <0 ))
The UID field holds 4 bytes of ASCII characters. kstrtoull() would fail if the UID field has value such as ‘CX03’.
Quoted 14 lines
drivers/cxl/acpi.c +7
-0+continue ; + +dev_dbg (&adev->dev,"host uid: %llu\n" , uid); + +if (uid >U32_MAX ) +continue ; +dev_info (&host->dev,"host supports CXL\n" ); }Signature · 1 line
2.30.2
Re: [PATCH 09/15] cxl/acpi: Determine PCI host bridge's ACPI UID
Quoted 23 lines · Jonathan Zhang (Infra)
Quoted 23 lines · Robert Richter
The UID is needed to read the RCH's CEDT entry with the RCRB base address. Determine the host's UID from its ACPI fw node.
Signed-off-by Robert Richter <[email protected]>---
drivers/cxl/acpi.c| 12 ++++++++++++1 file changed, 12 insertions(+)drivers/cxl/acpi.c +2
-0@@ -368,8 +368,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ; +struct acpi_device *adev; +unsigned long long uid = ~0 ;
Quoted 6 lines
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 377
Quoted 4 lines
drivers/cxl/acpi.c +3
-0while ((host =cxl_find_next_rch (host)) !=NULL ) { + adev =ACPI_COMPANION (&host->dev); +if (!adev || !adev->pnp.unique_id || + (kstrtoull (adev->pnp.unique_id,10 , &uid) <0 ))The UID field holds 4 bytes of ASCII characters.
kstrtoull()would fail if the UID field has value such as ‘CX03’.
The UID field is not 4 ASCII characters.
We went through this before in the original code in drivers/cxl/acpi.c::add_host_bridge_dport().
The CEDT.CHBS defines _UID as an integer so use acpi_evaluate_integer() to retrieve the UID to perform the comparison. I thought there was an errata filed to clarify this, but it seems the current spec still just says "value". The CFMWS also places _UID values in the target list, those are also handled as integers.
Re: [PATCH 09/15] cxl/acpi: Determine PCI host bridge's ACPI UID
Quoted 42 lines · Dan Williams
!-------------------------------------------------------------------|
This Message Is From an External Sender|-------------------------------------------------------------------!
Quoted 23 lines · Jonathan Zhang (Infra)
Quoted 23 lines · Robert Richter
The UID is needed to read the RCH's CEDT entry with the RCRB base address. Determine the host's UID from its ACPI fw node.
Signed-off-by Robert Richter <[email protected]>---
drivers/cxl/acpi.c| 12 ++++++++++++1 file changed, 12 insertions(+)drivers/cxl/acpi.c +2
-0@@ -368,8 +368,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ; +struct acpi_device *adev; +unsigned long long uid = ~0 ;Quoted 6 lines
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 377
Quoted 4 lines
drivers/cxl/acpi.c +3
-0while ((host =cxl_find_next_rch (host)) !=NULL ) { + adev =ACPI_COMPANION (&host->dev); +if (!adev || !adev->pnp.unique_id || + (kstrtoull (adev->pnp.unique_id,10 , &uid) <0 ))The UID field holds 4 bytes of ASCII characters.
kstrtoull()would fail if the UID field has value such as ‘CX03’.The UID field is not 4 ASCII characters.
Quoted 8 lines
We went through this before in the original code in drivers/cxl/acpi.c::add_host_bridge_dport().
The CEDT.CHBS defines
_UIDas an integer so useacpi_evaluate_integer()to retrieve the UID to perform the comparison. I thought there was an errata filed to clarify this, but it seems the current spec still just says "value". The CFMWS also places_UIDvalues in the target list, those are also handled as integers.
ACPI 6.4 spec section 6.1.12 describes _UID, it says the return value is:
An Integer or String containing the Unique ID.
In the BIOS I see, the _UIDs of PCIe devices hold ASCII characters (not NULL terminated).
Re: [PATCH 09/15] cxl/acpi: Determine PCI host bridge's ACPI UID
Quoted 51 lines · Jonathan Zhang (Infra)
Quoted 42 lines · Dan Williams
!-------------------------------------------------------------------|
This Message Is From an External Sender|-------------------------------------------------------------------!
Quoted 23 lines · Jonathan Zhang (Infra)
Quoted 23 lines · Robert Richter
The UID is needed to read the RCH's CEDT entry with the RCRB base address. Determine the host's UID from its ACPI fw node.
Signed-off-by Robert Richter <[email protected]>---
drivers/cxl/acpi.c| 12 ++++++++++++1 file changed, 12 insertions(+)drivers/cxl/acpi.c +2
-0@@ -368,8 +368,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ; +struct acpi_device *adev; +unsigned long long uid = ~0 ;Quoted 6 lines
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 377
Quoted 4 lines
drivers/cxl/acpi.c +3
-0while ((host =cxl_find_next_rch (host)) !=NULL ) { + adev =ACPI_COMPANION (&host->dev); +if (!adev || !adev->pnp.unique_id || + (kstrtoull (adev->pnp.unique_id,10 , &uid) <0 ))The UID field holds 4 bytes of ASCII characters.
kstrtoull()would fail if the UID field has value such as ‘CX03’.The UID field is not 4 ASCII characters.
Quoted 8 lines
We went through this before in the original code in drivers/cxl/acpi.c::add_host_bridge_dport().
The CEDT.CHBS defines
_UIDas an integer so useacpi_evaluate_integer()to retrieve the UID to perform the comparison. I thought there was an errata filed to clarify this, but it seems the current spec still just says "value". The CFMWS also places_UIDvalues in the target list, those are also handled as integers.
Quoted 5 lines
ACPI 6.4 spec section 6.1.12 describes
_UID, it says the return value is:
An Integer or String containing the Unique ID.In the BIOS I see, the
_UIDsof PCIe devices hold ASCII characters (not NULL terminated).
ASCII characters without NULL termination means that data can be treated as binary data which is what current CFMWWS parsing code chooses to do. I think a spec clarification is needed to make resolve the ambiguity.
Re: [PATCH 09/15] cxl/acpi: Determine PCI host bridge's ACPI UID
Quoted 64 lines · Dan Williams
!-------------------------------------------------------------------|
This Message Is From an External Sender|-------------------------------------------------------------------!
Quoted 54 lines · Jonathan Zhang (Infra)
Quoted 42 lines · Dan Williams
!-------------------------------------------------------------------| This Message Is From an External Sender
|-------------------------------------------------------------------!
Quoted 23 lines · Jonathan Zhang (Infra)
Quoted 23 lines · Robert Richter
The UID is needed to read the RCH's CEDT entry with the RCRB base address. Determine the host's UID from its ACPI fw node.
Signed-off-by Robert Richter <[email protected]>---
drivers/cxl/acpi.c| 12 ++++++++++++1 file changed, 12 insertions(+)drivers/cxl/acpi.c +2
-0@@ -368,8 +368,20 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ; +struct acpi_device *adev; +unsigned long long uid = ~0 ;Quoted 6 lines
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 377
Quoted 4 lines
drivers/cxl/acpi.c +3
-0while ((host =cxl_find_next_rch (host)) !=NULL ) { + adev =ACPI_COMPANION (&host->dev); +if (!adev || !adev->pnp.unique_id || + (kstrtoull (adev->pnp.unique_id,10 , &uid) <0 ))The UID field holds 4 bytes of ASCII characters.
kstrtoull()would fail if the UID field has value such as ‘CX03’.The UID field is not 4 ASCII characters.
Quoted 8 lines
We went through this before in the original code in drivers/cxl/acpi.c::add_host_bridge_dport().
The CEDT.CHBS defines
_UIDas an integer so useacpi_evaluate_integer()to retrieve the UID to perform the comparison. I thought there was an errata filed to clarify this, but it seems the current spec still just says "value". The CFMWS also places_UIDvalues in the target list, those are also handled as integers.ACPI 6.4 spec section 6.1.12 describes
_UID, it says the return value is:
An Integer or String containing the Unique ID.
Quoted 7 lines
Quoted 2 lines
In the BIOS I see, the
_UIDsof PCIe devices hold ASCII characters (not NULL terminated).ASCII characters without NULL termination means that data can be treated as binary data which is what current CFMWWS parsing code chooses to do. I think a spec clarification is needed to make resolve the ambiguity.
Agreed. In this case, ACPI spec should be referred to.
PATCH 10/15 cxl/acpi: Extract the RCH's RCRB base address from CEDT
In reply to Robert RichterThe downstream and upstream port Root Complex Register Blocks (RCRBs) are needed to control the ports and CXL devices connected to it. It also includes the location of the RCH/RCD downstream and upstream port component registers in MEMBAR0. Extract the RCRB from the host's CEDT entry.
--- drivers/cxl/acpi.c | 43 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+)
drivers/cxl/acpi.c +43 -0
@@ -365,11 +365,48 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)return NULL ; } +static int __cxl_get_rcrb (union acpi_subtable_headers *header,void *arg, +const unsigned long end) +{ +struct cxl_chbs_context *ctx = arg; +struct acpi_cedt_chbs *chbs; + +if (ctx->chbcr) +return 0 ; + + chbs = (struct acpi_cedt_chbs *)header; + +if (ctx->uid != chbs->uid) +return 0 ; + +if (chbs->cxl_version !=ACPI_CEDT_CHBS_VERSION_CXL11 ) +return 0 ; + +if (chbs->length !=SZ_8K ) +return 0 ; + + ctx->chbcr = chbs->base; + +return 0 ; +} + +static resource_size_t cxl_get_rcrb (u32 uid) +{ +struct cxl_chbs_context ctx = { + .uid = uid, + }; + +acpi_table_parse_cedt (ACPI_CEDT_TYPE_CHBS , __cxl_get_rcrb, &ctx); + +return ctx.chbcr; +} +static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ;struct acpi_device *adev;unsigned long long uid = ~0 ; +resource_size_t rcrb;while ((host =cxl_find_next_rch (host)) !=NULL ) { adev =ACPI_COMPANION (&host->dev);
@@ -382,6 +419,12 @@ static int __init cxl_restricted_host_probe(struct platform_device *pdev)if (uid >U32_MAX )continue ; + rcrb =cxl_get_rcrb (uid); +if (!rcrb) +continue ; + +dev_dbg (&host->dev,"RCRB found: 0x%08llx\n" , (u64 )rcrb); +dev_info (&host->dev,"host supports CXL\n" ); }
Signature · 1 line
2.30.2
Re: [PATCH 10/15] cxl/acpi: Extract the RCH's RCRB base address from CEDT
Quoted 7 lines · On Wed, 31 Aug 2022 10:15:58 +0200 Robert Richter <[email protected]> wrote:
The downstream and upstream port Root Complex Register Blocks (RCRBs) are needed to control the ports and CXL devices connected to it. It also includes the location of the RCH/RCD downstream and upstream port component registers in MEMBAR0. Extract the RCRB from the host's CEDT entry.
Signed-off-by Robert Richter <[email protected]>
Hi Robert,
One trivial comment inline.
Quoted 44 lines
--- drivers/cxl/acpi.c | 43 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+)drivers/cxl/acpi.c +32
-0@@ -365,11 +365,48 @@ struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host)return NULL ; } +static int __cxl_get_rcrb (union acpi_subtable_headers *header,void *arg, +const unsigned long end) +{ +struct cxl_chbs_context *ctx = arg; +struct acpi_cedt_chbs *chbs; + +if (ctx->chbcr) +return 0 ; + + chbs = (struct acpi_cedt_chbs *)header; + +if (ctx->uid != chbs->uid) +return 0 ; + +if (chbs->cxl_version !=ACPI_CEDT_CHBS_VERSION_CXL11 ) +return 0 ; + +if (chbs->length !=SZ_8K ) +return 0 ; + + ctx->chbcr = chbs->base; + +return 0 ; +} + +static resource_size_t cxl_get_rcrb (u32 uid) +{ +struct cxl_chbs_context ctx = { + .uid = uid, + }; + +acpi_table_parse_cedt (ACPI_CEDT_TYPE_CHBS , __cxl_get_rcrb, &ctx);
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 409
Quoted 10 lines
drivers/cxl/acpi.c +5
-0+ +return ctx.chbcr; +} +static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ;struct acpi_device *adev;unsigned long long uid = ~0 ; +resource_size_t rcrb;
Some of these could be made local to the while loop to reduce their scope.
Quoted 16 lines
drivers/cxl/acpi.c +6
-0while ((host =cxl_find_next_rch (host)) !=NULL ) { adev =ACPI_COMPANION (&host->dev);@@ -382,6 +419,12 @@ static int __init cxl_restricted_host_probe(struct platform_device *pdev)if (uid >U32_MAX )continue ; + rcrb =cxl_get_rcrb (uid); +if (!rcrb) +continue ; + +dev_dbg (&host->dev,"RCRB found: 0x%08llx\n" , (u64 )rcrb); +dev_info (&host->dev,"host supports CXL\n" ); }
Re: [PATCH 10/15] cxl/acpi: Extract the RCH's RCRB base address from CEDT
Quoted 11 lines · Jonathan Cameron
drivers/cxl/acpi.c struct pci_host_bridge *cxl_find_next_rch(struct pci_host_bridge *host) · line 409
Quoted 6 lines · On Wed, 31 Aug 2022 10:15:58 +0200 Robert Richter <[email protected]> wrote:
static int
__initcxl_restricted_host_probe(struct platform_device *pdev){drivers/cxl/acpi.c +1
-0struct pci_host_bridge *host =NULL ;struct acpi_device *adev;unsigned long long uid = ~0 ; +resource_size_t rcrb;Some of these could be made local to the while loop to reduce their scope.
I would need to move most of the vars into the loop then. So I rather want to keep it as it is.
I also remember a compiler or code checker complaining about block declaration, though it is in the c standard.
-Robert
Quoted 17 lines
Quoted 16 lines
drivers/cxl/acpi.c +6
-0while ((host =cxl_find_next_rch (host)) !=NULL ) { adev =ACPI_COMPANION (&host->dev);@@ -382,6 +419,12 @@ static int __init cxl_restricted_host_probe(struct platform_device *pdev)if (uid >U32_MAX )continue ; + rcrb =cxl_get_rcrb (uid); +if (!rcrb) +continue ; + +dev_dbg (&host->dev,"RCRB found: 0x%08llx\n" , (u64 )rcrb); +dev_info (&host->dev,"host supports CXL\n" ); }
PATCH 11/15 cxl/acpi: Extract the host's component register base address from RCRB
In reply to Robert RichterA downstream port must be connected to a component register block. Determine its base address from the RCRB.
The implementation is analog to how cxl_setup_regs() is implemented for CXL VH mode. A struct cxl_component_reg_map is filled in, mapped and probed.
--- drivers/cxl/acpi.c | 80 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+)
drivers/cxl/acpi.c +80 -0
@@ -401,12 +401,84 @@ static resource_size_t cxl_get_rcrb(u32 uid)return ctx.chbcr; } +static resource_size_t cxl_get_component_reg_phys (resource_size_t rcrb) +{ +resource_size_t component_reg_phys; +u32 bar0, bar1; +void *addr; + +/* +* RCRB's BAR[0..1] point to component block containing CXL subsystem +* component registers. +* CXL 8.2.4 - Component Register Layout Definition. +* +* Also, RCRB accesses must use MMIO readl()/readq() to guarantee +* 32/64-bit access. +* CXL 8.2.2 - CXL 1.1 Upstream and Downstream Port Subsystem Component +* Registers +*/ + addr =ioremap (rcrb,PCI_BASE_ADDRESS_0 +SZ_8 ); + bar0 =readl (addr +PCI_BASE_ADDRESS_0 ); + bar1 =readl (addr +PCI_BASE_ADDRESS_1 ); +iounmap (addr); + +/* sanity check */ +if (bar0 & (PCI_BASE_ADDRESS_MEM_TYPE_1M |PCI_BASE_ADDRESS_SPACE_IO )) +return CXL_RESOURCE_NONE ; + + component_reg_phys = bar0 &PCI_BASE_ADDRESS_MEM_MASK ; +if (bar0 &PCI_BASE_ADDRESS_MEM_TYPE_64 ) + component_reg_phys |= ((u64 )bar1) <<32 ; + +if (!component_reg_phys) +return CXL_RESOURCE_NONE ; + +/* +* Must be 8k aligned (size of combined CXL 1.1 Downstream and +* Upstream Port RCRBs). +*/ +if (component_reg_phys & (SZ_8K -1 )) +return CXL_RESOURCE_NONE ; + +return component_reg_phys; +} + +static int cxl_setup_component_reg (struct device *parent, +resource_size_t component_reg_phys) +{ +struct cxl_component_reg_map comp_map; +void __iomem *base; + +if (component_reg_phys ==CXL_RESOURCE_NONE ) +return -EINVAL ; + + base =ioremap (component_reg_phys,SZ_64K ); +if (!base) { +dev_err (parent,"failed to map registers\n" ); +return -ENOMEM ; + } + +cxl_probe_component_regs (parent, base, &comp_map); +iounmap (base); + +if (!comp_map.hdm_decoder.valid) { +dev_err (parent,"HDM decoder registers not found\n" ); +return -ENXIO ; + } + +dev_dbg (parent,"Set up component registers\n" ); + +return 0 ; +} +static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ;struct acpi_device *adev;unsigned long long uid = ~0 ;resource_size_t rcrb; +resource_size_t component_reg_phys; +int rc;while ((host =cxl_find_next_rch (host)) !=NULL ) { adev =ACPI_COMPANION (&host->dev);
@@ -425,10 +497,18 @@ static int __init cxl_restricted_host_probe(struct platform_device *pdev)dev_dbg (&host->dev,"RCRB found: 0x%08llx\n" , (u64 )rcrb); + component_reg_phys =cxl_get_component_reg_phys (rcrb); + rc =cxl_setup_component_reg (&host->dev, component_reg_phys); +if (rc) + goto fail; +dev_info (&host->dev,"host supports CXL\n" ); }return 0 ; +fail: +dev_err (&host->dev,"failed to initialize CXL host: %d\n" , rc); +return rc; }static struct lock_class_key cxl_root_key;
Signature · 1 line
2.30.2
Re: [PATCH 11/15] cxl/acpi: Extract the host's component register base address from RCRB
Quoted 9 lines · On Wed, 31 Aug 2022 10:15:59 +0200 Robert Richter <[email protected]> wrote:
A downstream port must be connected to a component register block. Determine its base address from the RCRB.
The implementation is analog to how
cxl_setup_regs()is implemented for CXL VH mode. A structcxl_component_reg_mapis filled in, mapped and probed.Signed-off-by Terry Bowman <[email protected]>Signed-off-by Robert Richter <[email protected]>
A few comments inline. Mostly requests for references for things I couldn't find in the specs.
Quoted 12 lines
--- drivers/cxl/acpi.c | 80 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+)drivers/cxl/acpi.c +0
-0@@ -401,12 +401,84 @@ static resource_size_t cxl_get_rcrb(u32 uid)return ctx.chbcr; }
drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 413
Quoted 10 lines
drivers/cxl/acpi.c +10
-0+static resource_size_t cxl_get_component_reg_phys (resource_size_t rcrb) +{ +resource_size_t component_reg_phys; +u32 bar0, bar1; +void *addr; + +/* +* RCRB's BAR[0..1] point to component block containing CXL subsystem +* component registers. +* CXL 8.2.4 - Component Register Layout Definition.
For references include spec version. Based on discussion other day, preference is always latest version. So r3.0 8.2.3
is probably right. I think your references are CXL r2.0?
drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 422
Quoted 9 lines
drivers/cxl/acpi.c +9
-0+* +* Also, RCRB accesses must use MMIO readl()/readq() to guarantee +* 32/64-bit access. +* CXL 8.2.2 - CXL 1.1 Upstream and Downstream Port Subsystem Component +* Registers +*/ + addr =ioremap (rcrb,PCI_BASE_ADDRESS_0 +SZ_8 ); + bar0 =readl (addr +PCI_BASE_ADDRESS_0 ); + bar1 =readl (addr +PCI_BASE_ADDRESS_1 );
The spec is a bit confusing on this, but I think you are reading into MEMBAR0 of the RCRB, for which there isn't a lot of description other than it being an address. It's referred to as a 64-bit BAR in places so you might be right - or it might be intended to be a bare address..
We might want a clarification on this...
Also it's a 64 bit address so we need to read it in one go. However it's referred to as a being a 64 bit address at 0x10 and 0x14 so who knows...
Quoted 6 lines
drivers/cxl/acpi.c +6
-0+iounmap (addr); + +/* sanity check */ +if (bar0 & (PCI_BASE_ADDRESS_MEM_TYPE_1M |PCI_BASE_ADDRESS_SPACE_IO )) +return CXL_RESOURCE_NONE ; +
drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 438
Quoted 10 lines
drivers/cxl/acpi.c +10
-0+ component_reg_phys = bar0 &PCI_BASE_ADDRESS_MEM_MASK ; +if (bar0 &PCI_BASE_ADDRESS_MEM_TYPE_64 ) + component_reg_phys |= ((u64 )bar1) <<32 ; + +if (!component_reg_phys) +return CXL_RESOURCE_NONE ; + +/* +* Must be 8k aligned (size of combined CXL 1.1 Downstream and +* Upstream Port RCRBs).
The rcrb is 8k though I'm not immediately spotting an alignment requirement, but I'm not sure the component regs have any restrictions do... Add a reference perhaps? For non RCD devices there is a 64K alignment requirement, but I can't find anything for RCDs (might just be missing it).
Quoted 7 lines
drivers/cxl/acpi.c +7
-0+*/ +if (component_reg_phys & (SZ_8K -1 )) +return CXL_RESOURCE_NONE ; + +return component_reg_phys; +} +
drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 455
Quoted 10 lines
drivers/cxl/acpi.c +10
-0+static int cxl_setup_component_reg (struct device *parent, +resource_size_t component_reg_phys) +{ +struct cxl_component_reg_map comp_map; +void __iomem *base; + +if (component_reg_phys ==CXL_RESOURCE_NONE ) +return -EINVAL ; + + base =ioremap (component_reg_phys,SZ_64K );
Add a spec reference for the size. Table 8-21 perhaps?
drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 466
Quoted 11 lines
drivers/cxl/acpi.c +11
-0+if (!base) { +dev_err (parent,"failed to map registers\n" ); +return -ENOMEM ; + } + +cxl_probe_component_regs (parent, base, &comp_map); +iounmap (base); + +if (!comp_map.hdm_decoder.valid) { +dev_err (parent,"HDM decoder registers not found\n" ); +return -ENXIO ;
Hmm. HDM decoder capability is optional for RCDs - might be using the range registers. Seems like we'd really want to handle that for RCDs. Future work I guess.
Quoted 4 lines
drivers/cxl/acpi.c +4
-0+ } + +dev_dbg (parent,"Set up component registers\n" ); +
drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 480
Quoted 10 lines
drivers/cxl/acpi.c +4
-0+return 0 ; +} +static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ;struct acpi_device *adev;unsigned long long uid = ~0 ;resource_size_t rcrb; +resource_size_t component_reg_phys;
Trivial: As before, if we can reduce scope to inside the while loop, slightly cleaner and more local.
drivers/cxl/acpi.c static int __init cxl_restricted_host_probe(struct platform_device *pdev) · line 501
Quoted 10 lines
drivers/cxl/acpi.c +3
-0+int rc;while ((host =cxl_find_next_rch (host)) !=NULL ) { adev =ACPI_COMPANION (&host->dev);@@ -425,10 +497,18 @@ static int __init cxl_restricted_host_probe(struct platform_device *pdev)dev_dbg (&host->dev,"RCRB found: 0x%08llx\n" , (u64 )rcrb); + component_reg_phys =cxl_get_component_reg_phys (rcrb); + rc =cxl_setup_component_reg (&host->dev, component_reg_phys);
Perhaps rename to make it clear this is getting the DSP component registers.
Future work would be to add support for the CXL 3.0 feature that lets even an RCD just put some of these registers in a BAR as per CXL 2.0 devices.
drivers/cxl/acpi.c static int __init cxl_restricted_host_probe(struct platform_device *pdev) · line 509
Quoted 9 lines
drivers/cxl/acpi.c +4
-0+if (rc) + goto fail; +dev_info (&host->dev,"host supports CXL\n" ); }return 0 ; +fail:
Better to have a more specific error message and return directly above. Note that so far vast majority of CXL error messages are dev_dbg, so for consistency perhaps this should be as well.
(I prefer dev_err() but not my subsystem ;)
drivers/cxl/acpi.c static int __init cxl_restricted_host_probe(struct platform_device *pdev) · line 510
Quoted 1 line
drivers/cxl/acpi.c +1
-0+dev_err (&host->dev,"failed to initialize CXL host: %d\n" , rc);
dev_err_probe() is slightly nicer to use if things can only happen in probe() paths.
Quoted 4 lines
drivers/cxl/acpi.c +1
-0+return rc; }static struct
lock_class_keycxl_root_key;
Re: [PATCH 11/15] cxl/acpi: Extract the host's component register base address from RCRB
Quoted 5 lines · Jonathan Cameron
On Wed, 31 Aug 2022 10:15:59 +0200
Robert Richter <[email protected]> wrote:A few comments inline. Mostly requests for references for things I couldn't find in the specs.
Most of it comes from the pci base spec (5 or 6).
Quoted 13 lines
Quoted 13 lines
--- drivers/cxl/acpi.c | 80 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+)drivers/cxl/acpi.c +0
-0@@ -401,12 +401,84 @@ static resource_size_t cxl_get_rcrb(u32 uid)return ctx.chbcr; }
Quoted 14 lines
drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 413
Quoted 10 lines
drivers/cxl/acpi.c +10
-0+static resource_size_t cxl_get_component_reg_phys (resource_size_t rcrb) +{ +resource_size_t component_reg_phys; +u32 bar0, bar1; +void *addr; + +/* +* RCRB's BAR[0..1] point to component block containing CXL subsystem +* component registers. +* CXL 8.2.4 - Component Register Layout Definition. For references include spec version. Based on discussion other day, preference is always latest version. So r3.0 8.2.3
is probably right. I think your references are CXL r2.0?
Right will update the comment.
Quoted 17 lines
drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 422
Quoted 11 lines
drivers/cxl/acpi.c +9
-0+* +* Also, RCRB accesses must use MMIO readl()/readq() to guarantee +* 32/64-bit access. +* CXL 8.2.2 - CXL 1.1 Upstream and Downstream Port Subsystem Component +* Registers +*/ + addr =ioremap (rcrb,PCI_BASE_ADDRESS_0 +SZ_8 ); + bar0 =readl (addr +PCI_BASE_ADDRESS_0 ); + bar1 =readl (addr +PCI_BASE_ADDRESS_1 );The spec is a bit confusing on this, but I think you are reading into MEMBAR0 of the RCRB, for which there isn't a lot of description other than it being an address. It's referred to as a 64-bit BAR in places so you might be right - or it might be intended to be a bare address..
Quoted 4 lines
We might want a clarification on this...
Also it's a 64 bit address so we need to read it in one go. However it's referred to as a being a 64 bit address at
0x10and0x14so who knows...
This is part of the pci base spec and clearly defined there. There are also some similar implementation in the kernel already.
Quoted 15 lines
Quoted 15 lines
drivers/cxl/acpi.c +13
-0+iounmap (addr); + +/* sanity check */ +if (bar0 & (PCI_BASE_ADDRESS_MEM_TYPE_1M |PCI_BASE_ADDRESS_SPACE_IO )) +return CXL_RESOURCE_NONE ; + + component_reg_phys = bar0 &PCI_BASE_ADDRESS_MEM_MASK ; +if (bar0 &PCI_BASE_ADDRESS_MEM_TYPE_64 ) + component_reg_phys |= ((u64 )bar1) <<32 ; + +if (!component_reg_phys) +return CXL_RESOURCE_NONE ; +
Quoted 8 lines
drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 438
Quoted 3 lines
drivers/cxl/acpi.c +3
-0+/* +* Must be 8k aligned (size of combined CXL 1.1 Downstream and +* Upstream Port RCRBs). The rcrb is 8k though I'm not immediately spotting an alignment requirement, but I'm not sure the component regs have any restrictions do... Add a reference perhaps? For non RCD devices there is a 64K alignment requirement, but I can't find anything for RCDs (might just be missing it).
This are the requirements of the pci base spec to membar ranges. The range size is power of 2 and base must be aligned to its size.
Quoted 12 lines
Quoted 12 lines
drivers/cxl/acpi.c +11
-0+*/ +if (component_reg_phys & (SZ_8K -1 )) +return CXL_RESOURCE_NONE ; + +return component_reg_phys; +} + +static int cxl_setup_component_reg (struct device *parent, +resource_size_t component_reg_phys) +{ +struct cxl_component_reg_map comp_map;
Quoted 8 lines
drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 455
Quoted 6 lines
drivers/cxl/acpi.c +6
-0+void __iomem *base; + +if (component_reg_phys ==CXL_RESOURCE_NONE ) +return -EINVAL ; + + base =ioremap (component_reg_phys,SZ_64K );Add a spec reference for the size. Table 8-21 perhaps?
Can add a comment here.
Quoted 16 lines
drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 466
Quoted 12 lines
drivers/cxl/acpi.c +11
-0+if (!base) { +dev_err (parent,"failed to map registers\n" ); +return -ENOMEM ; + } + +cxl_probe_component_regs (parent, base, &comp_map); +iounmap (base); + +if (!comp_map.hdm_decoder.valid) { +dev_err (parent,"HDM decoder registers not found\n" ); +return -ENXIO ;Hmm. HDM decoder capability is optional for RCDs - might be using the range registers. Seems like we'd really want to handle that for RCDs. Future work I guess.
I used the same message as for the non-RCD code path. HDM decoding is just a subset of features handled with component regs. We need to generalize the code for this in the future.
Quoted 25 lines
Quoted 5 lines
drivers/cxl/acpi.c +4
-0+ } + +dev_dbg (parent,"Set up component registers\n" ); +drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 480
Quoted 10 lines
drivers/cxl/acpi.c +4
-0+return 0 ; +} +static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ;struct acpi_device *adev;unsigned long long uid = ~0 ;resource_size_t rcrb; +resource_size_t component_reg_phys;Trivial: As before, if we can reduce scope to inside the while loop, slightly cleaner and more local.
Quoted 8 lines
drivers/cxl/acpi.c +1
-0+int rc;while ((host =cxl_find_next_rch (host)) !=NULL ) { adev =ACPI_COMPANION (&host->dev);@@ -425,10 +497,18 @@ static int __init cxl_restricted_host_probe(struct platform_device *pdev)dev_dbg (&host->dev,"RCRB found: 0x%08llx\n" , (u64 )rcrb);
Quoted 7 lines
drivers/cxl/acpi.c static int __init cxl_restricted_host_probe(struct platform_device *pdev) · line 501
Quoted 2 lines
drivers/cxl/acpi.c +2
-0+ component_reg_phys =cxl_get_component_reg_phys (rcrb); + rc =cxl_setup_component_reg (&host->dev, component_reg_phys);Perhaps rename to make it clear this is getting the DSP component registers.
Future work would be to add support for the CXL 3.0 feature that lets even an RCD just put some of these registers in a BAR as per CXL 2.0 devices.
Yes, this is left out atm.
Quoted 8 lines
Quoted 8 lines
drivers/cxl/acpi.c +3
-0+if (rc) + goto fail; +dev_info (&host->dev,"host supports CXL\n" ); }
Quoted 7 lines
drivers/cxl/acpi.c static int __init cxl_restricted_host_probe(struct platform_device *pdev) · line 509
Quoted 2 lines
drivers/cxl/acpi.c +1
-0return 0 ; +fail:Better to have a more specific error message and return directly above. Note that so far vast majority of CXL error messages are
dev_dbg, so for consistency perhaps this should be as well.
(I preferdev_err()but not my subsystem ;)
There is more verbosity on the errors with dbg enabled. Note there are only a few dev_info/dev_err messages to not polute the logs. dev_err() is only used if something unexpected happens (e.g. the device exists but component regs are broken).
Quoted 4 lines
drivers/cxl/acpi.c static int __init cxl_restricted_host_probe(struct platform_device *pdev) · line 510
Quoted 2 lines
drivers/cxl/acpi.c +1
-0+dev_err (&host->dev,"failed to initialize CXL host: %d\n" , rc);
dev_err_probe()is slightly nicer to use if things can only happen inprobe()paths.
Will consider that.
-Robert
Quoted 6 lines
Quoted 5 lines
drivers/cxl/acpi.c +1
-0+return rc; }static struct
lock_class_keycxl_root_key;
Re: [PATCH 11/15] cxl/acpi: Extract the host's component register base address from RCRB
Quoted 8 lines · On Thu, 1 Sep 2022 09:38:13 +0200 Robert Richter <[email protected]> wrote:
Quoted 5 lines · Jonathan Cameron
On Wed, 31 Aug 2022 10:15:59 +0200
Robert Richter <[email protected]> wrote:A few comments inline. Mostly requests for references for things I couldn't find in the specs.
Most of it comes from the pci base spec (5 or 6).
Ok. Extra references appreciated - these specs are huge, so saving searching time always good!
Quoted 18 lines
Quoted 18 lines
drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 422
Quoted 12 lines
drivers/cxl/acpi.c +9
-0+* +* Also, RCRB accesses must use MMIO readl()/readq() to guarantee +* 32/64-bit access. +* CXL 8.2.2 - CXL 1.1 Upstream and Downstream Port Subsystem Component +* Registers +*/ + addr =ioremap (rcrb,PCI_BASE_ADDRESS_0 +SZ_8 ); + bar0 =readl (addr +PCI_BASE_ADDRESS_0 ); + bar1 =readl (addr +PCI_BASE_ADDRESS_1 );The spec is a bit confusing on this, but I think you are reading into MEMBAR0 of the RCRB, for which there isn't a lot of description other than it being an address. It's referred to as a 64-bit BAR in places so you might be right - or it might be intended to be a bare address..
Quoted 7 lines
Quoted 4 lines
We might want a clarification on this...
Also it's a 64 bit address so we need to read it in one go. However it's referred to as a being a 64 bit address at
0x10and0x14so who knows...This is part of the pci base spec and clearly defined there. There are also some similar implementation in the kernel already.
There isn't a cross reference from CXL spec and PCI doesn't use the term membar.
I guess it is fairly obvious though that it's an abbreviation of Base Address Register for Memory. I might raise the wish to tidy that up for a future spec revision.
Quoted 25 lines
Quoted 16 lines
Quoted 16 lines
drivers/cxl/acpi.c +13
-0+iounmap (addr); + +/* sanity check */ +if (bar0 & (PCI_BASE_ADDRESS_MEM_TYPE_1M |PCI_BASE_ADDRESS_SPACE_IO )) +return CXL_RESOURCE_NONE ; + + component_reg_phys = bar0 &PCI_BASE_ADDRESS_MEM_MASK ; +if (bar0 &PCI_BASE_ADDRESS_MEM_TYPE_64 ) + component_reg_phys |= ((u64 )bar1) <<32 ; + +if (!component_reg_phys) +return CXL_RESOURCE_NONE ; +Quoted 8 lines
drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 438
Quoted 3 lines
drivers/cxl/acpi.c +3
-0+/* +* Must be 8k aligned (size of combined CXL 1.1 Downstream and +* Upstream Port RCRBs). The rcrb is 8k though I'm not immediately spotting an alignment requirement, but I'm not sure the component regs have any restrictions do... Add a reference perhaps? For non RCD devices there is a 64K alignment requirement, but I can't find anything for RCDs (might just be missing it).
Quoted 2 lines
This are the requirements of the pci base spec to membar ranges. The range size is power of 2 and base must be aligned to its size.
Ok. It feels convoluted to rely on the CXL glossary entry for BAR to cover MEMBAR0 and hence inherit the restrictions of a PCIe bar.
Maybe just add a comment here so that anyone who hits this can understand the source of the restriction seeing as it isn't in the CXL spec and this isn't a PCI BAR.
Quoted 29 lines
Quoted 13 lines
Quoted 9 lines
drivers/cxl/acpi.c +7
-0+*/ +if (component_reg_phys & (SZ_8K -1 )) +return CXL_RESOURCE_NONE ; + +return component_reg_phys; +} +Quoted 15 lines
drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 466
Quoted 11 lines
drivers/cxl/acpi.c +11
-0+if (!base) { +dev_err (parent,"failed to map registers\n" ); +return -ENOMEM ; + } + +cxl_probe_component_regs (parent, base, &comp_map); +iounmap (base); + +if (!comp_map.hdm_decoder.valid) { +dev_err (parent,"HDM decoder registers not found\n" ); +return -ENXIO ;Hmm. HDM decoder capability is optional for RCDs - might be using the range registers. Seems like we'd really want to handle that for RCDs. Future work I guess.
Quoted 3 lines
I used the same message as for the non-RCD code path. HDM decoding is just a subset of features handled with component regs. We need to generalize the code for this in the future.
Sure - much more likely to need that generalized code for an RCD. IIRC a CXL 2.0 device must implement HDM decoders, even though the other path can be used by software that doesn't understand CXL 2.0. Our RCD might be because the device is CXL 1.1...
Quoted 17 lines
Quoted 9 lines
Quoted 9 lines
drivers/cxl/acpi.c +3
-0+if (rc) + goto fail; +dev_info (&host->dev,"host supports CXL\n" ); }Quoted 7 lines
drivers/cxl/acpi.c static int __init cxl_restricted_host_probe(struct platform_device *pdev) · line 509
Quoted 2 lines
drivers/cxl/acpi.c +1
-0return 0 ; +fail:Better to have a more specific error message and return directly above. Note that so far vast majority of CXL error messages are
dev_dbg, so for consistency perhaps this should be as well.
(I preferdev_err()but not my subsystem ;)
Quoted 5 lines
There is more verbosity on the errors with dbg enabled. Note there are only a few dev_info/dev_err messages to not polute the logs.
dev_err()is only used if something unexpected happens (e.g. the device exists but component regs are broken).
Ok. I'll leave the question of balance between the two for CXL maintainers to comment on if they wish.
Thanks,
Jonathan
Re: [PATCH 11/15] cxl/acpi: Extract the host's component register base address from RCRB
Quoted 7 lines · Jonathan Cameron
Quoted 4 lines · On Thu, 1 Sep 2022 09:38:13 +0200 Robert Richter <[email protected]> wrote:
Quoted 2 lines · Jonathan Cameron
On Wed, 31 Aug 2022 10:15:59 +0200
Robert Richter <[email protected]> wrote:
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
A few comments inline. Mostly requests for references for things I couldn't find in the specs.
Most of it comes from the pci base spec (5 or 6).
Ok. Extra references appreciated - these specs are huge, so saving searching time always good!
I will add comments for all ther refs in this patch.
[...]
Quoted 11 lines
Quoted 11 lines
Quoted 10 lines
drivers/cxl/acpi.c static resource_size_t cxl_get_rcrb(u32 uid) · line 466
Quoted 6 lines
drivers/cxl/acpi.c +6
-0+cxl_probe_component_regs (parent, base, &comp_map); +iounmap (base); + +if (!comp_map.hdm_decoder.valid) { +dev_err (parent,"HDM decoder registers not found\n" ); +return -ENXIO ;Hmm. HDM decoder capability is optional for RCDs - might be using the range registers. Seems like we'd really want to handle that for RCDs. Future work I guess.
Quoted 8 lines
Quoted 3 lines
I used the same message as for the non-RCD code path. HDM decoding is just a subset of features handled with component regs. We need to generalize the code for this in the future.
Sure - much more likely to need that generalized code for an RCD. IIRC a CXL 2.0 device must implement HDM decoders, even though the other path can be used by software that doesn't understand CXL 2.0. Our RCD might be because the device is CXL 1.1...
Yes, this will be a follow on series.
Thanks,
-Robert
Re: [PATCH 11/15] cxl/acpi: Extract the host's component register base address from RCRB
In reply to Robert RichterQuoted 107 lines · Robert Richter
A downstream port must be connected to a component register block. Determine its base address from the RCRB.
The implementation is analog to how
cxl_setup_regs()is implemented for CXL VH mode. A structcxl_component_reg_mapis filled in, mapped and probed.Signed-off-by Terry Bowman <[email protected]>Signed-off-by Robert Richter <[email protected]>---
drivers/cxl/acpi.c| 80 ++++++++++++++++++++++++++++++++++++++++++++++1 file changed, 80 insertions(+)drivers/cxl/acpi.c +72
-0@@ -401,12 +401,84 @@ static resource_size_t cxl_get_rcrb(u32 uid)return ctx.chbcr; } +static resource_size_t cxl_get_component_reg_phys (resource_size_t rcrb) +{ +resource_size_t component_reg_phys; +u32 bar0, bar1; +void *addr; + +/* +* RCRB's BAR[0..1] point to component block containing CXL subsystem +* component registers. +* CXL 8.2.4 - Component Register Layout Definition. +* +* Also, RCRB accesses must use MMIO readl()/readq() to guarantee +* 32/64-bit access. +* CXL 8.2.2 - CXL 1.1 Upstream and Downstream Port Subsystem Component +* Registers +*/ + addr =ioremap (rcrb,PCI_BASE_ADDRESS_0 +SZ_8 ); + bar0 =readl (addr +PCI_BASE_ADDRESS_0 ); + bar1 =readl (addr +PCI_BASE_ADDRESS_1 ); +iounmap (addr); + +/* sanity check */ +if (bar0 & (PCI_BASE_ADDRESS_MEM_TYPE_1M |PCI_BASE_ADDRESS_SPACE_IO )) +return CXL_RESOURCE_NONE ; + + component_reg_phys = bar0 &PCI_BASE_ADDRESS_MEM_MASK ; +if (bar0 &PCI_BASE_ADDRESS_MEM_TYPE_64 ) + component_reg_phys |= ((u64 )bar1) <<32 ; + +if (!component_reg_phys) +return CXL_RESOURCE_NONE ; + +/* +* Must be 8k aligned (size of combined CXL 1.1 Downstream and +* Upstream Port RCRBs). +*/ +if (component_reg_phys & (SZ_8K -1 )) +return CXL_RESOURCE_NONE ; + +return component_reg_phys; +} + +static int cxl_setup_component_reg (struct device *parent, +resource_size_t component_reg_phys) +{ +struct cxl_component_reg_map comp_map; +void __iomem *base; + +if (component_reg_phys ==CXL_RESOURCE_NONE ) +return -EINVAL ; + + base =ioremap (component_reg_phys,SZ_64K ); +if (!base) { +dev_err (parent,"failed to map registers\n" ); +return -ENOMEM ; + } + +cxl_probe_component_regs (parent, base, &comp_map); +iounmap (base); + +if (!comp_map.hdm_decoder.valid) { +dev_err (parent,"HDM decoder registers not found\n" ); +return -ENXIO ; + } + +dev_dbg (parent,"Set up component registers\n" ); + +return 0 ; +} +static int __init cxl_restricted_host_probe (struct platform_device *pdev) {struct pci_host_bridge *host =NULL ;struct acpi_device *adev;unsigned long long uid = ~0 ;resource_size_t rcrb; +resource_size_t component_reg_phys; +int rc;while ((host =cxl_find_next_rch (host)) !=NULL ) { adev =ACPI_COMPANION (&host->dev);
drivers/cxl/acpi.c static int __init cxl_restricted_host_probe(struct platform_device *pdev) · line 501
Quoted 5 lines
drivers/cxl/acpi.c +2
-0@@ -425,10 +497,18 @@ static int __init cxl_restricted_host_probe(struct platform_device *pdev)dev_dbg (&host->dev,"RCRB found: 0x%08llx\n" , (u64 )rcrb); + component_reg_phys =cxl_get_component_reg_phys (rcrb); + rc =cxl_setup_component_reg (&host->dev, component_reg_phys);
cxl_setup_component_reg() calls cxl_probe_component_regs() which depends on the existence of HDM decoder capability register. Such register does not exist when the device is in RCRB mode, attached to a RCH.
Quoted 17 lines
drivers/cxl/acpi.c +6
-0+if (rc) + goto fail; +dev_info (&host->dev,"host supports CXL\n" ); }return 0 ; +fail: +dev_err (&host->dev,"failed to initialize CXL host: %d\n" , rc); +return rc; }static struct lock_class_key cxl_root_key;Signature · 1 line
2.30.2
PATCH 12/15 cxl/acpi: Skip devm_cxl_port_enumerate_dports() when in RCD mode
In reply to Robert RichterRCD mode has a different enumeration scheme other than in CXL VH mode. An RCD is directly connected to an RCH without downstream and upstream ports showing up in between in the PCI hierarchy. Skip dport enumeration for RCHs. Upstream and downstream ports of RCH and RCD will be setup separately in a later patch.
Introduce the function is_rch_uport() to detect an RCH port. For RCHs the parent root port is not the "ACPI0017" device and instead does not have a fw node connected to it.
--- drivers/cxl/core/pci.c | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-)
drivers/cxl/core/pci.c +19 -1
@@ -65,6 +65,15 @@ static int match_add_dports(struct pci_dev *pdev, void *data)return 0 ; } +/* +* A parent of an RCH (CXL 1.1 host) is a plain platform device while +* a 2.0 host links to the ACPI0017 root device. +*/ +static inline bool is_rch_uport (struct cxl_port *port) +{ +return is_cxl_port (&port->dev) && !port->dev.parent->fwnode; +} +/** * devm_cxl_port_enumerate_dports - enumerate downstream ports of the upstream port * @port: cxl_port whose ->uport is the upstream of dports to be enumerated
@@ -74,10 +83,19 @@ static int match_add_dports(struct pci_dev *pdev, void *data)*/ int devm_cxl_port_enumerate_dports (struct cxl_port *port) { -struct pci_bus *bus =cxl_port_to_pci_bus (port); +struct pci_bus *bus;struct cxl_walk_context ctx;int type; +/* +* Skip enumeration in Restricted CXL Device mode as the +* device has been already registered at the host's dport +* during host discovery. +*/ +if (is_rch_uport (port)) +return 0 ; + + bus =cxl_port_to_pci_bus (port);if (!bus)return -ENXIO ;
Signature · 1 line
2.30.2
Re: [PATCH 12/15] cxl/acpi: Skip devm_cxl_port_enumerate_dports() when in RCD mode
Quoted 20 lines · On Wed, 31 Aug 2022 10:16:00 +0200 Robert Richter <[email protected]> wrote:
RCD mode has a different enumeration scheme other than in CXL VH mode. An RCD is directly connected to an RCH without downstream and upstream ports showing up in between in the PCI hierarchy. Skip dport enumeration for RCHs. Upstream and downstream ports of RCH and RCD will be setup separately in a later patch.
Introduce the function
is_rch_uport()to detect an RCH port. For RCHs the parent root port is not the "ACPI0017" device and instead does not have a fw node connected to it.Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/core/pci.c | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-)drivers/cxl/core/pci.c +0
-0
drivers/cxl/core/pci.c static int match_add_dports(struct pci_dev *pdev, void *data) · line 74
Quoted 10 lines
drivers/cxl/core/pci.c +7
-0@@ -65,6 +65,15 @@ static int match_add_dports(struct pci_dev *pdev, void *data)return 0 ; } +/* +* A parent of an RCH (CXL 1.1 host) is a plain platform device while +* a 2.0 host links to the ACPI0017 root device. +*/ +static inline bool is_rch_uport (struct cxl_port *port) +{ +return is_cxl_port (&port->dev) && !port->dev.parent->fwnode;
I'm not keen on the presence of fwnode being used to distinguish anything. That's the sort of thing that gets 'fixed' by later patches.
Can we check something more specific?
Quoted 26 lines
drivers/cxl/core/pci.c +12
-1+} +/** * devm_cxl_port_enumerate_dports - enumerate downstream ports of the upstream port * @port: cxl_port whose ->uport is the upstream of dports to be enumerated @@ -74,10 +83,19 @@ static int match_add_dports(struct pci_dev *pdev, void *data)*/ int devm_cxl_port_enumerate_dports (struct cxl_port *port) { -struct pci_bus *bus =cxl_port_to_pci_bus (port); +struct pci_bus *bus;struct cxl_walk_context ctx;int type; +/* +* Skip enumeration in Restricted CXL Device mode as the +* device has been already registered at the host's dport +* during host discovery. +*/ +if (is_rch_uport (port)) +return 0 ; + + bus =cxl_port_to_pci_bus (port);if (!bus)return -ENXIO ;
Re: [PATCH 12/15] cxl/acpi: Skip devm_cxl_port_enumerate_dports() when in RCD mode
Quoted 14 lines · Jonathan Cameron
drivers/cxl/core/pci.c static int match_add_dports(struct pci_dev *pdev, void *data) · line 74
Quoted 7 lines · On Wed, 31 Aug 2022 10:16:00 +0200 Robert Richter <[email protected]> wrote:
drivers/cxl/core/pci.c +7
-0+/* +* A parent of an RCH (CXL 1.1 host) is a plain platform device while +* a 2.0 host links to the ACPI0017 root device. +*/ +static inline bool is_rch_uport (struct cxl_port *port) +{ +return is_cxl_port (&port->dev) && !port->dev.parent->fwnode;I'm not keen on the presence of fwnode being used to distinguish anything. That's the sort of thing that gets 'fixed' by later patches.
Quoted 1 line
Can we check something more specific?
We actually know the parent device is the root device, so we can check this. Even easier.
Thanks,
-Robert
PATCH 13/15 cxl/acpi: Rework devm_cxl_enumerate_ports() to support RCD mode
In reply to Robert RichterRCD mode has a different enumeration scheme other than in CXL VH mode. An RCD is directly connected to an RCH without downstream and upstream ports showing up in between in the PCI hierarchy. Due to the direct connection of RCD and RCH, the host bridge is always the RCD's parent instead of the grandparent. Modify devm_cxl_enumerate_ports() respectively.
Implement this by introducing a function to determine the device's downstream port. The 'for' loop is adjusted for RCD mode and in this case find_cxl_port() will always find the host's associated port and the loop iteration stops.
--- drivers/cxl/core/port.c | 36 ++++++++++++++++++++++++------------ 1 file changed, 24 insertions(+), 12 deletions(-)
drivers/cxl/core/port.c +24 -12
@@ -1084,6 +1084,22 @@ static struct device *grandparent(struct device *dev)return NULL ; } +static struct device *cxl_mem_dport_dev (struct cxl_memdev *cxlmd) +{ +struct device *dev = cxlmd->dev.parent; +struct pci_dev *pdev =to_pci_dev (cxlmd->dev.parent); + +/* +* An RCiEP is directly connected to the root bridge without +* any PCI bridges/ports in between. Reduce the parent level +* for those. +*/ +if (pci_pcie_type (pdev) ==PCI_EXP_TYPE_RC_END ) +return dev; + +return dev->parent; +} +static void delete_endpoint (void *data) {struct cxl_memdev *cxlmd = data;
@@ -1339,7 +1355,7 @@ static int add_port_attach_ep(struct cxl_memdev *cxlmd,int devm_cxl_enumerate_ports (struct cxl_memdev *cxlmd) {struct device *dev = &cxlmd->dev; -struct device *iter; +struct device *dport_dev;int rc; rc =devm_add_action_or_reset (&cxlmd->dev, cxl_detach_ep, cxlmd);
@@ -1352,25 +1368,21 @@ int devm_cxl_enumerate_ports(struct cxl_memdev *cxlmd)* attempt fails. */ retry: -for (iter = dev; iter; iter =grandparent (iter)) { -struct device *dport_dev =grandparent (iter); +for (dport_dev =cxl_mem_dport_dev (cxlmd); dport_dev; + dport_dev =grandparent (dport_dev)) {struct device *uport_dev;struct cxl_dport *dport;struct cxl_port *port; -if (!dport_dev) -return 0 ; - uport_dev = dport_dev->parent;if (!uport_dev) { -dev_warn (dev,"at %s no parent for dport: %s\n" , -dev_name (iter),dev_name (dport_dev)); +dev_warn (dev,"no parent for dport: %s\n" , +dev_name (dport_dev));return -ENXIO ; } -dev_dbg (dev,"scan: iter: %s dport_dev: %s parent: %s\n" , -dev_name (iter),dev_name (dport_dev), -dev_name (uport_dev)); +dev_dbg (dev,"scan: dport_dev: %s parent: %s\n" , +dev_name (dport_dev),dev_name (uport_dev)); port =find_cxl_port (dport_dev, &dport);if (port) { dev_dbg(&cxlmd->dev,
@@ -1418,7 +1430,7 @@ EXPORT_SYMBOL_NS_GPL(devm_cxl_enumerate_ports, CXL);struct cxl_port *cxl_mem_find_port (struct cxl_memdev *cxlmd,struct cxl_dport **dport) { -return find_cxl_port (grandparent (&cxlmd->dev), dport); +return find_cxl_port (cxl_mem_dport_dev (cxlmd), dport); }EXPORT_SYMBOL_NS_GPL (cxl_mem_find_port,CXL );
Signature · 1 line
2.30.2
Re: [PATCH 13/15] cxl/acpi: Rework devm_cxl_enumerate_ports() to support RCD mode
Quoted 5 lines · On Wed, 31 Aug 2022 10:16:01 +0200 Robert Richter <[email protected]> wrote:
RCD mode has a different enumeration scheme other than in CXL VH mode. An RCD is directly connected to an RCH without downstream and upstream ports showing up in between in the PCI hierarchy. Due to the direct connection of RCD and RCH, the host bridge is always the RCD's parent instead of the grandparent.
Mentioned earlier, but that's not quite true. There is a reference in the spec to allowing it to be under a root port (some sort of virtual structure
- I'm not sure of 'why' you would that though.)(
Quoted 2 lines
Modify
devm_cxl_enumerate_ports()
respectively.
Don't line wrap above.
Quoted 16 lines
Implement this by introducing a function to determine the device's downstream port. The 'for' loop is adjusted for RCD mode and in this case
find_cxl_port()will always find the host's associated port and the loop iteration stops.Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/core/port.c | 36 ++++++++++++++++++++++++------------ 1 file changed, 24 insertions(+), 12 deletions(-)drivers/cxl/core/port.c +0
-0
drivers/cxl/core/port.c static struct device *grandparent(struct device *dev) · line 1090
Quoted 7 lines
drivers/cxl/core/port.c +4
-0@@ -1084,6 +1084,22 @@ static struct device *grandparent(struct device *dev)return NULL ; } +static struct device *cxl_mem_dport_dev (struct cxl_memdev *cxlmd) +{ +struct device *dev = cxlmd->dev.parent; +struct pci_dev *pdev =to_pci_dev (cxlmd->dev.parent);
to_pci_dev(dev);
drivers/cxl/core/port.c static struct device *grandparent(struct device *dev) · line 1100
Quoted 10 lines
drivers/cxl/core/port.c +10
-0+ +/* +* An RCiEP is directly connected to the root bridge without +* any PCI bridges/ports in between. Reduce the parent level +* for those. +*/ +if (pci_pcie_type (pdev) ==PCI_EXP_TYPE_RC_END ) +return dev; + +return dev->parent;
Switching from grandparent to this is a little confusing because it's done in two steps. Perhaps use
return grandparent(cmlmd->dev);
here to keep that connection and rename dev in this function to parent.
Far too many devices in here with similar names for it to be easy to read.
Quoted 15 lines
drivers/cxl/core/port.c +3
-1+} +static void delete_endpoint (void *data) {struct cxl_memdev *cxlmd = data;@@ -1339,7 +1355,7 @@ static int add_port_attach_ep(struct cxl_memdev *cxlmd,int devm_cxl_enumerate_ports (struct cxl_memdev *cxlmd) {struct device *dev = &cxlmd->dev; -struct device *iter; +struct device *dport_dev;int rc; rc =devm_add_action_or_reset (&cxlmd->dev, cxl_detach_ep, cxlmd);
drivers/cxl/core/port.c int devm_cxl_enumerate_ports(struct cxl_memdev *cxlmd) · line 1372
Quoted 7 lines
drivers/cxl/core/port.c +2
-2@@ -1352,25 +1368,21 @@ int devm_cxl_enumerate_ports(struct cxl_memdev *cxlmd)* attempt fails. */ retry: -for (iter = dev; iter; iter =grandparent (iter)) { -struct device *dport_dev =grandparent (iter); +for (dport_dev =cxl_mem_dport_dev (cxlmd); dport_dev; + dport_dev =grandparent (dport_dev)) {
I don't like looping for the RCD case as it relies a bit too much on subtle relationships between devices and parent.
Perhaps better to factor out the contents of the loop, then handle the RCD case separately from the main loop.
I haven't tried it, so perhaps that looks even less readable.
Quoted 33 lines
drivers/cxl/core/port.c +5
-9struct device *uport_dev;struct cxl_dport *dport;struct cxl_port *port; -if (!dport_dev) -return 0 ; - uport_dev = dport_dev->parent;if (!uport_dev) { -dev_warn (dev,"at %s no parent for dport: %s\n" , -dev_name (iter),dev_name (dport_dev)); +dev_warn (dev,"no parent for dport: %s\n" , +dev_name (dport_dev));return -ENXIO ; } -dev_dbg (dev,"scan: iter: %s dport_dev: %s parent: %s\n" , -dev_name (iter),dev_name (dport_dev), -dev_name (uport_dev)); +dev_dbg (dev,"scan: dport_dev: %s parent: %s\n" , +dev_name (dport_dev),dev_name (uport_dev)); port =find_cxl_port (dport_dev, &dport);if (port) { dev_dbg(&cxlmd->dev,@@ -1418,7 +1430,7 @@ EXPORT_SYMBOL_NS_GPL(devm_cxl_enumerate_ports, CXL);struct cxl_port *cxl_mem_find_port (struct cxl_memdev *cxlmd,struct cxl_dport **dport) { -return find_cxl_port (grandparent (&cxlmd->dev), dport); +return find_cxl_port (cxl_mem_dport_dev (cxlmd), dport); }EXPORT_SYMBOL_NS_GPL (cxl_mem_find_port,CXL );
Re: [PATCH 13/15] cxl/acpi: Rework devm_cxl_enumerate_ports() to support RCD mode
Quoted 11 lines · Jonathan Cameron
Quoted 5 lines · On Wed, 31 Aug 2022 10:16:01 +0200 Robert Richter <[email protected]> wrote:
RCD mode has a different enumeration scheme other than in CXL VH mode. An RCD is directly connected to an RCH without downstream and upstream ports showing up in between in the PCI hierarchy. Due to the direct connection of RCD and RCH, the host bridge is always the RCD's parent instead of the grandparent.
Mentioned earlier, but that's not quite true. There is a reference in the spec to allowing it to be under a root port (some sort of virtual structure
- I'm not sure of 'why' you would that though.)(
Yes, but software view is still the same, see other mail.
Quoted 25 lines
Quoted 3 lines
Modify
devm_cxl_enumerate_ports()
respectively.Don't line wrap above.
Quoted 19 lines
Implement this by introducing a function to determine the device's downstream port. The 'for' loop is adjusted for RCD mode and in this case
find_cxl_port()will always find the host's associated port and the loop iteration stops.Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/core/port.c | 36 ++++++++++++++++++++++++------------ 1 file changed, 24 insertions(+), 12 deletions(-)drivers/cxl/core/port.c +0
-0@@ -1084,6 +1084,22 @@ static struct device *grandparent(struct device *dev)return NULL ; }
Quoted 6 lines
drivers/cxl/core/port.c static struct device *grandparent(struct device *dev) · line 1090
Quoted 4 lines
drivers/cxl/core/port.c +4
-0+static struct device *cxl_mem_dport_dev (struct cxl_memdev *cxlmd) +{ +struct device *dev = cxlmd->dev.parent; +struct pci_dev *pdev =to_pci_dev (cxlmd->dev.parent);
to_pci_dev(dev);
Ok.
Quoted 13 lines
drivers/cxl/core/port.c static struct device *grandparent(struct device *dev) · line 1100
Quoted 11 lines
drivers/cxl/core/port.c +10
-0+ +/* +* An RCiEP is directly connected to the root bridge without +* any PCI bridges/ports in between. Reduce the parent level +* for those. +*/ +if (pci_pcie_type (pdev) ==PCI_EXP_TYPE_RC_END ) +return dev; + +return dev->parent;Switching from grandparent to this is a little confusing because it's done in two steps. Perhaps use
Quoted 5 lines
return grandparent(cmlmd->dev);here to keep that connection and rename dev in this function to parent.
Far too many devices in here with similar names for it to be easy to read.
Can improve this a little.
Quoted 28 lines
Quoted 17 lines
drivers/cxl/core/port.c +3
-1+} +static void delete_endpoint (void *data) {struct cxl_memdev *cxlmd = data;@@ -1339,7 +1355,7 @@ static int add_port_attach_ep(struct cxl_memdev *cxlmd,int devm_cxl_enumerate_ports (struct cxl_memdev *cxlmd) {struct device *dev = &cxlmd->dev; -struct device *iter; +struct device *dport_dev;int rc; rc =devm_add_action_or_reset (&cxlmd->dev, cxl_detach_ep, cxlmd);drivers/cxl/core/port.c int devm_cxl_enumerate_ports(struct cxl_memdev *cxlmd) · line 1372
Quoted 7 lines
drivers/cxl/core/port.c +2
-2@@ -1352,25 +1368,21 @@ int devm_cxl_enumerate_ports(struct cxl_memdev *cxlmd)* attempt fails. */ retry: -for (iter = dev; iter; iter =grandparent (iter)) { -struct device *dport_dev =grandparent (iter); +for (dport_dev =cxl_mem_dport_dev (cxlmd); dport_dev; + dport_dev =grandparent (dport_dev)) {I don't like looping for the RCD case as it relies a bit too much on subtle relationships between devices and parent.
Quoted 3 lines
Perhaps better to factor out the contents of the loop, then handle the RCD case separately from the main loop.
I haven't tried it, so perhaps that looks even less readable.
I see your point here, will take a look.
Thanks,
-Robert
PATCH 14/15 cxl/acpi: Enumerate ports in RCD mode to enable RCHs and RCDs
In reply to Robert RichterDo the plumbing of ports to enable RCD/RCH pairs.
Do this by enumerating all necessary ports an endpoint needs to connect to. This includes:
1) A CXL root port with dport links to the RCHs. The port links to the CXL root platform device for RCH mode.
2) RCH ports with dport links to its endpoints. Port connects to the pci host bridge device.
3) CXL device endpoint connected to the RCH.
The port creation for the endpoint (3) is already implemented and works in RCD mode too. Thus, it is not scope of this patch. Only the endpoints must be registered at the host bridge port.
Implement this by introducing the function cxl_enumerate_rch_ports(). It registers a CXL host at the CXL root device, creates the host's port and registers the existing CXL memory device endpoint at it. The port of the CXL root device is created with the first CXL host being registered.
Once enumerated, CXL restricted hosts show up in sysfs with CXL devices connected as endpoints to it.
--- drivers/cxl/acpi.c | 58 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 58 insertions(+)
drivers/cxl/acpi.c +58 -0
@@ -471,13 +471,52 @@ static int cxl_setup_component_reg(struct device *parent,return 0 ; } +static int cxl_enumerate_rch_ports (struct device *root_dev, +struct cxl_port *cxl_root, +struct pci_host_bridge *host, +resource_size_t component_reg_phys, +int port_id) +{ +struct cxl_dport *dport; +struct cxl_port *port; +struct pci_dev *pdev; + + dport =devm_cxl_add_dport (cxl_root, &host->dev, port_id, + component_reg_phys); +if (IS_ERR (dport)) +return PTR_ERR (dport); + + port =devm_cxl_add_port (root_dev, &host->dev, + component_reg_phys, dport); +if (IS_ERR (port)) +return PTR_ERR (port); + + pdev =pci_get_slot (host->bus,PCI_DEVFN (0 ,0 )); +if (!pdev) +return -ENXIO ; + +/* Note: The endpoint provides the component reg base. */ + dport =devm_cxl_add_dport (port, &pdev->dev,0 , +CXL_RESOURCE_NONE ); + +pci_dev_put (pdev); + +if (IS_ERR (dport)) +return PTR_ERR (dport); + +return 0 ; +} +static int __init cxl_restricted_host_probe (struct platform_device *pdev) { +struct device *root_dev = &pdev->dev;struct pci_host_bridge *host =NULL ;struct acpi_device *adev; +struct cxl_port *cxl_root =NULL ;unsigned long long uid = ~0 ;resource_size_t rcrb;resource_size_t component_reg_phys; +int port_id =0 ;int rc;while ((host =cxl_find_next_rch (host)) !=NULL ) {
@@ -497,11 +536,30 @@ static int __init cxl_restricted_host_probe(struct platform_device *pdev)dev_dbg (&host->dev,"RCRB found: 0x%08llx\n" , (u64 )rcrb); +/* +* For CXL 1.1 hosts we create a root device other +* than the ACPI0017 device to hold the devm data and +* the uport ref. +*/ +if (!cxl_root) { + cxl_root =devm_cxl_add_port (root_dev, root_dev, +CXL_RESOURCE_NONE ,NULL ); +if (IS_ERR (cxl_root)) { + rc =PTR_ERR (cxl_root); + goto fail; + } + } + component_reg_phys =cxl_get_component_reg_phys (rcrb); rc =cxl_setup_component_reg (&host->dev, component_reg_phys);if (rc) goto fail; + rc =cxl_enumerate_rch_ports (root_dev, cxl_root, host, + component_reg_phys, port_id++); +if (rc) + goto fail; +dev_info (&host->dev,"host supports CXL\n" ); }
Signature · 1 line
2.30.2
Re: [PATCH 14/15] cxl/acpi: Enumerate ports in RCD mode to enable RCHs and RCDs
Quoted 23 lines · On Wed, 31 Aug 2022 10:16:02 +0200 Robert Richter <[email protected]> wrote:
Do the plumbing of ports to enable RCD/RCH pairs.
Do this by enumerating all necessary ports an endpoint needs to connect to. This includes:
1) A CXL root port with dport links to the RCHs. The port links to the CXL root platform device for RCH mode.
2) RCH ports with dport links to its endpoints. Port connects to the pci host bridge device.
3) CXL device endpoint connected to the RCH.
The port creation for the endpoint (3) is already implemented and works in RCD mode too. Thus, it is not scope of this patch. Only the endpoints must be registered at the host bridge port.
Implement this by introducing the function
cxl_enumerate_rch_ports(). It registers a CXL host at the CXL root device, creates the host's port and registers the existing CXL memory device endpoint at it. The port of the CXL root device is created with the first CXL host being registered.
Quoted 4 lines
Once enumerated, CXL restricted hosts show up in sysfs with CXL devices connected as endpoints to it.
Signed-off-by Robert Richter <[email protected]>
Hi Robert,
A few things inline.
Jonathan
Quoted 27 lines
--- drivers/cxl/acpi.c | 58 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 58 insertions(+)drivers/cxl/acpi.c +15
-0@@ -471,13 +471,52 @@ static int cxl_setup_component_reg(struct device *parent,return 0 ; } +static int cxl_enumerate_rch_ports (struct device *root_dev, +struct cxl_port *cxl_root, +struct pci_host_bridge *host, +resource_size_t component_reg_phys, +int port_id) +{ +struct cxl_dport *dport; +struct cxl_port *port; +struct pci_dev *pdev; + + dport =devm_cxl_add_dport (cxl_root, &host->dev, port_id, + component_reg_phys); +if (IS_ERR (dport)) +return PTR_ERR (dport); +
drivers/cxl/acpi.c static int cxl_setup_component_reg(struct device *parent, · line 498
Quoted 10 lines
drivers/cxl/acpi.c +10
-0+ port =devm_cxl_add_port (root_dev, &host->dev, + component_reg_phys, dport); +if (IS_ERR (port)) +return PTR_ERR (port); + + pdev =pci_get_slot (host->bus,PCI_DEVFN (0 ,0 )); +if (!pdev) +return -ENXIO ; + +/* Note: The endpoint provides the component reg base. */
I'm not sure what this comment means. Which component reg base?
drivers/cxl/acpi.c static int cxl_setup_component_reg(struct device *parent, · line 500
Quoted 2 lines
drivers/cxl/acpi.c +2
-0+ dport =devm_cxl_add_dport (port, &pdev->dev,0 , +CXL_RESOURCE_NONE );
Trivial: No need to wrap the above.
Quoted 53 lines
drivers/cxl/acpi.c +31
-0+ +pci_dev_put (pdev); + +if (IS_ERR (dport)) +return PTR_ERR (dport); + +return 0 ; +} +static int __init cxl_restricted_host_probe (struct platform_device *pdev) { +struct device *root_dev = &pdev->dev;struct pci_host_bridge *host =NULL ;struct acpi_device *adev; +struct cxl_port *cxl_root =NULL ;unsigned long long uid = ~0 ;resource_size_t rcrb;resource_size_t component_reg_phys; +int port_id =0 ;int rc;while ((host =cxl_find_next_rch (host)) !=NULL ) {@@ -497,11 +536,30 @@ static int __init cxl_restricted_host_probe(struct platform_device *pdev)dev_dbg (&host->dev,"RCRB found: 0x%08llx\n" , (u64 )rcrb); +/* +* For CXL 1.1 hosts we create a root device other +* than the ACPI0017 device to hold the devm data and +* the uport ref. +*/ +if (!cxl_root) { + cxl_root =devm_cxl_add_port (root_dev, root_dev, +CXL_RESOURCE_NONE ,NULL ); +if (IS_ERR (cxl_root)) { + rc =PTR_ERR (cxl_root); + goto fail; + } + } + component_reg_phys =cxl_get_component_reg_phys (rcrb); rc =cxl_setup_component_reg (&host->dev, component_reg_phys);if (rc) goto fail; + rc =cxl_enumerate_rch_ports (root_dev, cxl_root, host, + component_reg_phys, port_id++); +if (rc) + goto fail; +dev_info (&host->dev,"host supports CXL\n" ); }
Re: [PATCH 14/15] cxl/acpi: Enumerate ports in RCD mode to enable RCHs and RCDs
Quoted 30 lines · Jonathan Cameron
Quoted 27 lines · On Wed, 31 Aug 2022 10:16:02 +0200 Robert Richter <[email protected]> wrote:
drivers/cxl/acpi.c +19
-0@@ -471,13 +471,52 @@ static int cxl_setup_component_reg(struct device *parent,return 0 ; } +static int cxl_enumerate_rch_ports (struct device *root_dev, +struct cxl_port *cxl_root, +struct pci_host_bridge *host, +resource_size_t component_reg_phys, +int port_id) +{ +struct cxl_dport *dport; +struct cxl_port *port; +struct pci_dev *pdev; + + dport =devm_cxl_add_dport (cxl_root, &host->dev, port_id, + component_reg_phys); +if (IS_ERR (dport)) +return PTR_ERR (dport); + + port =devm_cxl_add_port (root_dev, &host->dev, + component_reg_phys, dport); +if (IS_ERR (port)) +return PTR_ERR (port);
Quoted 8 lines
drivers/cxl/acpi.c static int cxl_setup_component_reg(struct device *parent, · line 498
Quoted 6 lines
drivers/cxl/acpi.c +6
-0+ + pdev =pci_get_slot (host->bus,PCI_DEVFN (0 ,0 )); +if (!pdev) +return -ENXIO ; + +/* Note: The endpoint provides the component reg base. */ I'm not sure what this comment means. Which component reg base?
There is no component_reg_phys provided here, so the addr is CXL_RESOURCE_NONE.
Will improve the comment.
Quoted 5 lines
drivers/cxl/acpi.c static int cxl_setup_component_reg(struct device *parent, · line 500
Quoted 3 lines
drivers/cxl/acpi.c +2
-0+ dport =devm_cxl_add_dport (port, &pdev->dev,0 , +CXL_RESOURCE_NONE );Trivial: No need to wrap the above.
Right.
Thanks,
-Robert
PATCH 15/15 cxl/acpi: Specify module load order dependency for the cxl_acpi module
In reply to Robert RichterIn RCD mode the CXL mem dev may be detected on the PCI bus before a CXL host is brought up. This may cause a CXL mem initialization failure as it expects the CXL host already detected. Address this by specifying the module dependencies using MODULE_SOFTDEP().
The following additional dependencies exist:
* cxl_mem depends on cxl_acpi: The CXL hosts must be discovered before the CXL device is initialized.
* cxl_acpi depends on cxl_port: The acpi driver adds ports to the cxl bus, the port driver should be loaded before. This might also work if modules are loaded in different order, but a) it aligns with the existing cxl_mem/cxl_port softdep and b) it always guarantees a fix module load order.
--- drivers/cxl/acpi.c | 1 + drivers/cxl/mem.c | 1 + 2 files changed, 2 insertions(+)
drivers/cxl/acpi.c +1 -0
@@ -834,3 +834,4 @@ module_exit(cxl_host_exit);MODULE_LICENSE ("GPL v2" );MODULE_IMPORT_NS (CXL );MODULE_IMPORT_NS (ACPI ); +MODULE_SOFTDEP ("pre: cxl_port" );
drivers/cxl/mem.c +1 -0
@@ -128,3 +128,4 @@ MODULE_ALIAS_CXL(CXL_DEVICE_MEMORY_EXPANDER);* endpoint registration. */ MODULE_SOFTDEP ("pre: cxl_port" ); +MODULE_SOFTDEP ("pre: cxl_acpi" );
Signature · 1 line
2.30.2
RE: [PATCH 15/15] cxl/acpi: Specify module load order dependency for the cxl_acpi module
Quoted 3 lines · Robert Richter
In RCD mode the CXL mem dev may be detected on the PCI bus before a CXL host is brought up. This may cause a CXL mem initialization failure as it expects the CXL host already detected.
This is not unique to RCD mode. It is mitigated by the cxl_bus_rescan() at the completion of cxl_acpi_probe().
Quoted 5 lines
Address this by
specifying the module dependencies usingMODULE_SOFTDEP().The following additional dependencies exist:
Quoted 8 lines
*
cxl_memdepends oncxl_acpi: The CXL hosts must be discovered before the CXL device is initialized.*
cxl_acpidepends oncxl_port: The acpi driver adds ports to the cxl bus, the port driver should be loaded before. This might also work if modules are loaded in different order, but a) it aligns with the existing cxl_mem/cxl_port softdep and b) it always guarantees a fix module load order.
Why does a fixed module load order matter?
Quoted 12 lines
Signed-off-by Robert Richter <[email protected]>--- drivers/cxl/acpi.c | 1 + drivers/cxl/mem.c | 1 + 2 files changed, 2 insertions(+)drivers/cxl/acpi.c +0
-0
drivers/cxl/acpi.c module_exit(cxl_host_exit); · line 837
Quoted 4 lines
drivers/cxl/acpi.c +1
-0@@ -834,3 +834,4 @@ module_exit(cxl_host_exit);MODULE_LICENSE ("GPL v2" );MODULE_IMPORT_NS (CXL );MODULE_IMPORT_NS (ACPI ); +MODULE_SOFTDEP ("pre: cxl_port" );
The only reason cxl_acpi would need to preload cxl_port is if it wanted to do something like:
port = devm_cxl_add_port(...);
if (port->dev.driver)
/* do something with an enabled port */ else /* do something else if the port failed to enable */
drivers/cxl/mem.c MODULE_ALIAS_CXL(CXL_DEVICE_MEMORY_EXPANDER); · line 131
Quoted 9 lines
drivers/cxl/mem.c +1
-0@@ -128,3 +128,4 @@ MODULE_ALIAS_CXL(CXL_DEVICE_MEMORY_EXPANDER);* endpoint registration. */ MODULE_SOFTDEP ("pre: cxl_port" ); +MODULE_SOFTDEP ("pre: cxl_acpi" );
There is no strict requirement that CXL topologies be limited to ACPI platforms. Per above, the cxl_mem driver will attach when the CXL root device finally appears, and async out-of-order arrival is ok.
Quoted 28 lines · On Wed, 31 Aug 2022 10:15:48 +0200 Robert Richter <[email protected]> wrote:
In Restricted CXL Device (RCD) mode (formerly referred to as CXL 1.1) the PCIe enumeration hierarchy is different from CXL VH Enumeration (formerly referred to as 2.0, for both modes see CXL spec 3.0: 9.11 and 9.12, [1]). This series adds support for RCD mode. It implements the detection of Restricted CXL Hosts (RCHs) and its corresponding Restricted CXL Devices (RCDs). It does the necessary enumeration of ports and connects the endpoints. With all the plumbing an RCH/RCD pair is registered at the Linux CXL bus and becomes visible in sysfs in the same way as CXL VH hosts and devices do already. RCDs are brought up as CXL endpoints and bound to subsequent drivers such as
cxl_mem.For CXL VH the host driver (
cxl_acpi) starts host bridge discovery once the ACPI0017 CXL root device is detected and then searches for ACPI0016 host bridges to enable CXL. In RCD mode an ACPI0017 device might not necessarily exist and the host bridge can have a standard PCIe host bridge PNP0A08 ID, there aren't any CXL port or switches in the PCIe hierarchy visible. As such the RCD mode enumeration and host discovery is very different from CXL VH. See patch #5 for implementation details.This implementation expects the host's downstream and upstream port RCRBs base address being reported by firmware using the optional CEDT CHBS entry of the host bridge (see CXL spec 3.0, 9.17.1.2).
RCD mode does not support hot-plug, so host discovery is at boot time only.
Quoted 7 lines
Patches #1 to #4 are prerequisites of the series with fixes needed and a rework of debug messages for port enumeration. Those are general patches and could be applied earlier and independently from the rest assuming there are no objections with them. Patches #5 to #15 contain the actual implementation of RCD mode support.
Hi Robert,
I'm curious on the aims of this work. Given expectation for RCDs is often that the host firmware has set them up before the OS loads, what functionality do you want to gain by mapping these into the CXL 2.0+ focused infrastructure?
When I did some analysis a while back on CXL 1.1 I was pretty much assuming that there was no real reason to let the OS know about it because it couldn't do much of any use with the information. There are some corners like RAS where it might be useful or perhaps to enable some of the CXL 3.0 features that are allowed to be EP only and so could be relevant for an older host (e.g. CPMUs).
With my QEMU hat on I wasn't planning to bother with anything pre 2.0 but it might be worth considering to let us exercise this code...
Jonathan
Quoted 30 lines
Robert Richter (15):
cxl/core: Remove duplicate declaration ofdevm_cxl_iomap_block()cxl/core: Check physical address before mapping it in
devm_cxl_iomap_block()
cxl: Unify debug messages when callingdevm_cxl_add_port()
cxl: Unify debug messages when callingdevm_cxl_add_dport()cxl/acpi: Add probe function to detect restricted CXL hosts in RCD
mode
PCI/ACPI: Link host bridge to its ACPI fw node
cxl/acpi: Check RCH's PCIe Host Bridge ACPI ID
cxl/acpi: Check RCH's CXL DVSEC capabilities
cxl/acpi: Determine PCI host bridge's ACPI UID
cxl/acpi: Extract the RCH's RCRB base address from CEDT cxl/acpi: Extract the host's component register base address from RCRB cxl/acpi: Skipdevm_cxl_port_enumerate_dports()when in RCD mode cxl/acpi: Reworkdevm_cxl_enumerate_ports()to support RCD mode cxl/acpi: Enumerate ports in RCD mode to enable RCHs and RCDs cxl/acpi: Specify module load order dependency for thecxl_acpimoduledrivers/acpi/pci_root.c | 1 + drivers/cxl/acpi.c | 311 ++++++++++++++++++++++++++++++++++- drivers/cxl/core/pci.c | 22 ++- drivers/cxl/core/port.c | 103 ++++++++---- drivers/cxl/core/regs.c | 3 + drivers/cxl/cxl.h | 2 - drivers/cxl/mem.c | 1 + tools/testing/cxl/test/cxl.c | 8 +- 8 files changed, 400 insertions(+), 51 deletions(-)
Jonathan,
Quoted 45 lines · Jonathan Cameron
Quoted 28 lines · On Wed, 31 Aug 2022 10:15:48 +0200 Robert Richter <[email protected]> wrote:
In Restricted CXL Device (RCD) mode (formerly referred to as CXL 1.1) the PCIe enumeration hierarchy is different from CXL VH Enumeration (formerly referred to as 2.0, for both modes see CXL spec 3.0: 9.11 and 9.12, [1]). This series adds support for RCD mode. It implements the detection of Restricted CXL Hosts (RCHs) and its corresponding Restricted CXL Devices (RCDs). It does the necessary enumeration of ports and connects the endpoints. With all the plumbing an RCH/RCD pair is registered at the Linux CXL bus and becomes visible in sysfs in the same way as CXL VH hosts and devices do already. RCDs are brought up as CXL endpoints and bound to subsequent drivers such as
cxl_mem.For CXL VH the host driver (
cxl_acpi) starts host bridge discovery once the ACPI0017 CXL root device is detected and then searches for ACPI0016 host bridges to enable CXL. In RCD mode an ACPI0017 device might not necessarily exist and the host bridge can have a standard PCIe host bridge PNP0A08 ID, there aren't any CXL port or switches in the PCIe hierarchy visible. As such the RCD mode enumeration and host discovery is very different from CXL VH. See patch #5 for implementation details.This implementation expects the host's downstream and upstream port RCRBs base address being reported by firmware using the optional CEDT CHBS entry of the host bridge (see CXL spec 3.0, 9.17.1.2).
RCD mode does not support hot-plug, so host discovery is at boot time only.
Quoted 7 lines
Patches #1 to #4 are prerequisites of the series with fixes needed and a rework of debug messages for port enumeration. Those are general patches and could be applied earlier and independently from the rest assuming there are no objections with them. Patches #5 to #15 contain the actual implementation of RCD mode support.
Hi Robert,
I'm curious on the aims of this work. Given expectation for RCDs is often that the host firmware has set them up before the OS loads, what functionality do you want to gain by mapping these into the CXL 2.0+ focused infrastructure?
Quoted 6 lines
When I did some analysis a while back on CXL 1.1 I was pretty much assuming that there was no real reason to let the OS know about it because it couldn't do much of any use with the information. There are some corners like RAS where it might be useful or perhaps to enable some of the CXL 3.0 features that are allowed to be EP only and so could be relevant for an older host (e.g. CPMUs).
though CXL RCD works with a legacy kernel or without any CXL functionality added, a CXL aware kernel can be useful also for RCD mode. RAS is a topic here but also gathering device information such as status or topology. Everything where access to the component register block or mailbox interface is required.
Another plus, the CXL hierarchy becomes visible for RCD mode in sysfs and the device hierarchy.
Reusing the existing infrastructure for this makes sense. Many features overlap in both modes (e.g. RAS, mailbox again, or topology information).
Thanks again for you review.
-Robert
Quoted 5 lines
With my QEMU hat on I wasn't planning to bother with anything pre 2.0 but it might be worth considering to let us exercise this code...
Jonathan
Quoted 55 lines · Robert Richter
Jonathan,
Quoted 45 lines · Jonathan Cameron
Quoted 28 lines · On Wed, 31 Aug 2022 10:15:48 +0200 Robert Richter <[email protected]> wrote:
In Restricted CXL Device (RCD) mode (formerly referred to as CXL 1.1) the PCIe enumeration hierarchy is different from CXL VH Enumeration (formerly referred to as 2.0, for both modes see CXL spec 3.0: 9.11 and 9.12, [1]). This series adds support for RCD mode. It implements the detection of Restricted CXL Hosts (RCHs) and its corresponding Restricted CXL Devices (RCDs). It does the necessary enumeration of ports and connects the endpoints. With all the plumbing an RCH/RCD pair is registered at the Linux CXL bus and becomes visible in sysfs in the same way as CXL VH hosts and devices do already. RCDs are brought up as CXL endpoints and bound to subsequent drivers such as
cxl_mem.For CXL VH the host driver (
cxl_acpi) starts host bridge discovery once the ACPI0017 CXL root device is detected and then searches for ACPI0016 host bridges to enable CXL. In RCD mode an ACPI0017 device might not necessarily exist and the host bridge can have a standard PCIe host bridge PNP0A08 ID, there aren't any CXL port or switches in the PCIe hierarchy visible. As such the RCD mode enumeration and host discovery is very different from CXL VH. See patch #5 for implementation details.This implementation expects the host's downstream and upstream port RCRBs base address being reported by firmware using the optional CEDT CHBS entry of the host bridge (see CXL spec 3.0, 9.17.1.2).
RCD mode does not support hot-plug, so host discovery is at boot time only.
Quoted 7 lines
Patches #1 to #4 are prerequisites of the series with fixes needed and a rework of debug messages for port enumeration. Those are general patches and could be applied earlier and independently from the rest assuming there are no objections with them. Patches #5 to #15 contain the actual implementation of RCD mode support.
Hi Robert,
I'm curious on the aims of this work. Given expectation for RCDs is often that the host firmware has set them up before the OS loads, what functionality do you want to gain by mapping these into the CXL 2.0+ focused infrastructure?
Quoted 6 lines
When I did some analysis a while back on CXL 1.1 I was pretty much assuming that there was no real reason to let the OS know about it because it couldn't do much of any use with the information. There are some corners like RAS where it might be useful or perhaps to enable some of the CXL 3.0 features that are allowed to be EP only and so could be relevant for an older host (e.g. CPMUs).
Quoted 5 lines
though CXL RCD works with a legacy kernel or without any CXL functionality added, a CXL aware kernel can be useful also for RCD mode. RAS is a topic here but also gathering device information such as status or topology. Everything where access to the component register block or mailbox interface is required.
Unless the BIOS is going actively enable the standard CXL topology with ACPI0017 then I think it should be hands off for the OS. The maintenance burden of some of the hack to work around missing BIOS descriptions is non-trivial, and it is still early days to encourage BIOS vendors to enable what is needed and set end user expectations that these pre-requisites exist.
As far as I can see this enabling adds an additional CXL "root" device and I do not think userspace should need to care if a CXL 2.0 device is attached to an RCH or not.
Quoted 6 lines
Another plus, the CXL hierarchy becomes visible for RCD mode in sysfs and the device hierarchy.
Reusing the existing infrastructure for this makes sense. Many features overlap in both modes (e.g. RAS, mailbox again, or topology information).
RAS only if OS first is supported by the BIOS. Mailbox support happens with or without a CXL root device. The topology information is certainly important in OS first error handling, but if its firmware first its going to have its own FRU id scheme. Much of the common case topology information for the RCH case (like which RCIEP is hosting which CXL address range) is covered by this pending lspci update:
https://github.com/pciutils/pciutils/pull/59:
...although that needs some help to get over the goal line.
Otherwise the topology information is mostly for describing all the degrees of freedom of a full blown CXL 2.0 topoloy with host bridge and switch interleaving.
Apologies for the delay in getting to this I had hoped to be able to finish up some other DAX work to focus on this, but time is getting short so I will need to do both in parallel.
Quoted 12 lines · Robert Richter
In Restricted CXL Device (RCD) mode (formerly referred to as CXL 1.1) the PCIe enumeration hierarchy is different from CXL VH Enumeration (formerly referred to as 2.0, for both modes see CXL spec 3.0: 9.11 and 9.12, [1]). This series adds support for RCD mode. It implements the detection of Restricted CXL Hosts (RCHs) and its corresponding Restricted CXL Devices (RCDs). It does the necessary enumeration of ports and connects the endpoints. With all the plumbing an RCH/RCD pair is registered at the Linux CXL bus and becomes visible in sysfs in the same way as CXL VH hosts and devices do already. RCDs are brought up as CXL endpoints and bound to subsequent drivers such as
cxl_mem.
Quoted 4 lines
For CXL VH the host driver (
cxl_acpi) starts host bridge discovery once the ACPI0017 CXL root device is detected and then searches for ACPI0016 host bridges to enable CXL. In RCD mode an ACPI0017 device might not necessarily exist
That's a broken BIOS as far as I can see. No ACPI0017 == no OS CXL services and the CXL aspects of the device need to be 100% managed by the BIOS. You can still run the cxl_pci driver in that case for mailbox operation, but error handling must be firmware-first without ACPI0017.
Quoted 52 lines
PCIe host bridge PNP0A08 ID, there aren't any CXL port or switches in the PCIe hierarchy visible. As such the RCD mode enumeration and host discovery is very different from CXL VH. See patch #5 for implementation details.
This implementation expects the host's downstream and upstream port RCRBs base address being reported by firmware using the optional CEDT CHBS entry of the host bridge (see CXL spec 3.0, 9.17.1.2).
RCD mode does not support hot-plug, so host discovery is at boot time only.
Patches #1 to #4 are prerequisites of the series with fixes needed and a rework of debug messages for port enumeration. Those are general patches and could be applied earlier and independently from the rest assuming there are no objections with them. Patches #5 to #15 contain the actual implementation of RCD mode support.
[1] https://www.computeexpresslink.org/spec-landing
Robert Richter (15):
cxl/core: Remove duplicate declaration ofdevm_cxl_iomap_block()cxl/core: Check physical address before mapping it in
devm_cxl_iomap_block()
cxl: Unify debug messages when callingdevm_cxl_add_port()
cxl: Unify debug messages when callingdevm_cxl_add_dport()cxl/acpi: Add probe function to detect restricted CXL hosts in RCD
mode
PCI/ACPI: Link host bridge to its ACPI fw node
cxl/acpi: Check RCH's PCIe Host Bridge ACPI ID
cxl/acpi: Check RCH's CXL DVSEC capabilities
cxl/acpi: Determine PCI host bridge's ACPI UID
cxl/acpi: Extract the RCH's RCRB base address from CEDT cxl/acpi: Extract the host's component register base address from RCRB cxl/acpi: Skipdevm_cxl_port_enumerate_dports()when in RCD mode cxl/acpi: Reworkdevm_cxl_enumerate_ports()to support RCD mode cxl/acpi: Enumerate ports in RCD mode to enable RCHs and RCDs cxl/acpi: Specify module load order dependency for thecxl_acpimoduledrivers/acpi/pci_root.c | 1 + drivers/cxl/acpi.c | 311 ++++++++++++++++++++++++++++++++++- drivers/cxl/core/pci.c | 22 ++- drivers/cxl/core/port.c | 103 ++++++++---- drivers/cxl/core/regs.c | 3 + drivers/cxl/cxl.h | 2 - drivers/cxl/mem.c | 1 + tools/testing/cxl/test/cxl.c | 8 +- 8 files changed, 400 insertions(+), 51 deletions(-)Signature · 1 line
2.30.2
Quoted 26 lines · Dan Williams
Apologies for the delay in getting to this I had hoped to be able to finish up some other DAX work to focus on this, but time is getting short so I will need to do both in parallel.
Quoted 12 lines · Robert Richter
In Restricted CXL Device (RCD) mode (formerly referred to as CXL 1.1) the PCIe enumeration hierarchy is different from CXL VH Enumeration (formerly referred to as 2.0, for both modes see CXL spec 3.0: 9.11 and 9.12, [1]). This series adds support for RCD mode. It implements the detection of Restricted CXL Hosts (RCHs) and its corresponding Restricted CXL Devices (RCDs). It does the necessary enumeration of ports and connects the endpoints. With all the plumbing an RCH/RCD pair is registered at the Linux CXL bus and becomes visible in sysfs in the same way as CXL VH hosts and devices do already. RCDs are brought up as CXL endpoints and bound to subsequent drivers such as
cxl_mem.Quoted 4 lines
For CXL VH the host driver (
cxl_acpi) starts host bridge discovery once the ACPI0017 CXL root device is detected and then searches for ACPI0016 host bridges to enable CXL. In RCD mode an ACPI0017 device might not necessarily exist
Quoted 4 lines
That's a broken BIOS as far as I can see. No ACPI0017 == no OS CXL services and the CXL aspects of the device need to be 100% managed by the BIOS. You can still run the
cxl_pcidriver in that case for mailbox operation, but error handling must be firmware-first without ACPI0017.
Firmware-first or OS-first applies to CXL protocol error handling. For CXL memory error handling, the device generates a DRAM error record, the OS parses such record and act accordingly. According to CXL spec (section 8.2.9.2.1.2 DRAM Event Record), DPA but not HPA is in such record. The OS needs to translate such DPA into HPA to act on. I am taking this as an example to show that OS CXL services is needed.
Instead of using ACPI0016 to tell whether the system is under RCH mode, I suppose one way is to check “CXL version” field of CHBS structure in CEDT?
Quoted 56 lines
Quoted 53 lines
PCIe host bridge PNP0A08 ID, there aren't any CXL port or switches in the PCIe hierarchy visible. As such the RCD mode enumeration and host discovery is very different from CXL VH. See patch #5 for implementation details.
This implementation expects the host's downstream and upstream port RCRBs base address being reported by firmware using the optional CEDT CHBS entry of the host bridge (see CXL spec 3.0, 9.17.1.2).
RCD mode does not support hot-plug, so host discovery is at boot time only.
Patches #1 to #4 are prerequisites of the series with fixes needed and a rework of debug messages for port enumeration. Those are general patches and could be applied earlier and independently from the rest assuming there are no objections with them. Patches #5 to #15 contain the actual implementation of RCD mode support.
[1] https://www.computeexpresslink.org/spec-landing
Robert Richter (15):
cxl/core: Remove duplicate declaration ofdevm_cxl_iomap_block()cxl/core: Check physical address before mapping it in
devm_cxl_iomap_block()
cxl: Unify debug messages when callingdevm_cxl_add_port()
cxl: Unify debug messages when callingdevm_cxl_add_dport()cxl/acpi: Add probe function to detect restricted CXL hosts in RCD
mode
PCI/ACPI: Link host bridge to its ACPI fw node
cxl/acpi: Check RCH's PCIe Host Bridge ACPI ID
cxl/acpi: Check RCH's CXL DVSEC capabilities
cxl/acpi: Determine PCI host bridge's ACPI UID
cxl/acpi: Extract the RCH's RCRB base address from CEDT cxl/acpi: Extract the host's component register base address from RCRB cxl/acpi: Skipdevm_cxl_port_enumerate_dports()when in RCD mode cxl/acpi: Reworkdevm_cxl_enumerate_ports()to support RCD mode cxl/acpi: Enumerate ports in RCD mode to enable RCHs and RCDs cxl/acpi: Specify module load order dependency for thecxl_acpimoduledrivers/acpi/pci_root.c | 1 + drivers/cxl/acpi.c | 311 ++++++++++++++++++++++++++++++++++- drivers/cxl/core/pci.c | 22 ++- drivers/cxl/core/port.c | 103 ++++++++---- drivers/cxl/core/regs.c | 3 + drivers/cxl/cxl.h | 2 - drivers/cxl/mem.c | 1 + tools/testing/cxl/test/cxl.c | 8 +- 8 files changed, 400 insertions(+), 51 deletions(-)Signature · 1 line
2.30.2
Quoted 30 lines · Jonathan Zhang (Infra)
Quoted 26 lines · Dan Williams
Apologies for the delay in getting to this I had hoped to be able to finish up some other DAX work to focus on this, but time is getting short so I will need to do both in parallel.
Quoted 12 lines · Robert Richter
In Restricted CXL Device (RCD) mode (formerly referred to as CXL 1.1) the PCIe enumeration hierarchy is different from CXL VH Enumeration (formerly referred to as 2.0, for both modes see CXL spec 3.0: 9.11 and 9.12, [1]). This series adds support for RCD mode. It implements the detection of Restricted CXL Hosts (RCHs) and its corresponding Restricted CXL Devices (RCDs). It does the necessary enumeration of ports and connects the endpoints. With all the plumbing an RCH/RCD pair is registered at the Linux CXL bus and becomes visible in sysfs in the same way as CXL VH hosts and devices do already. RCDs are brought up as CXL endpoints and bound to subsequent drivers such as
cxl_mem.Quoted 4 lines
For CXL VH the host driver (
cxl_acpi) starts host bridge discovery once the ACPI0017 CXL root device is detected and then searches for ACPI0016 host bridges to enable CXL. In RCD mode an ACPI0017 device might not necessarily existQuoted 4 lines
That's a broken BIOS as far as I can see. No ACPI0017 == no OS CXL services and the CXL aspects of the device need to be 100% managed by the BIOS. You can still run the
cxl_pcidriver in that case for mailbox operation, but error handling must be firmware-first without ACPI0017.
Quoted 8 lines
Firmware-first or OS-first applies to CXL protocol error handling. For CXL memory error handling, the device generates a DRAM error record, the OS parses such record and act accordingly. According to CXL spec (section 8.2.9.2.1.2 DRAM Event Record), DPA but not HPA is in such record. The OS needs to translate such DPA into HPA to act on. I am taking this as an example to show that OS CXL services is needed.
Instead of using ACPI0016 to tell whether the system is under RCH mode, I suppose one way is to check “CXL version” field of CHBS structure in CEDT?
Unless the OS has negotiated CXL _OSC the BIOS owns the event retrieval and translating it from DPA to HPA. I do want to add OS CXL services to Linux, but only in the case when the BIOS is actively enabling OS native address translation which includes populating ACPI0017, CFMWS, and devices with the HDM decoder capability registers instead of DVSEC range registers. Everything else is early-gen CXL that is 100% BIOS supported, similar to DDR where a driver is not expected.
Quoted 49 lines · Dan Williams
!-------------------------------------------------------------------|
This Message Is From an External Sender|-------------------------------------------------------------------!
Quoted 30 lines · Jonathan Zhang (Infra)
Quoted 26 lines · Dan Williams
Apologies for the delay in getting to this I had hoped to be able to finish up some other DAX work to focus on this, but time is getting short so I will need to do both in parallel.
Quoted 12 lines · Robert Richter
In Restricted CXL Device (RCD) mode (formerly referred to as CXL 1.1) the PCIe enumeration hierarchy is different from CXL VH Enumeration (formerly referred to as 2.0, for both modes see CXL spec 3.0: 9.11 and 9.12, [1]). This series adds support for RCD mode. It implements the detection of Restricted CXL Hosts (RCHs) and its corresponding Restricted CXL Devices (RCDs). It does the necessary enumeration of ports and connects the endpoints. With all the plumbing an RCH/RCD pair is registered at the Linux CXL bus and becomes visible in sysfs in the same way as CXL VH hosts and devices do already. RCDs are brought up as CXL endpoints and bound to subsequent drivers such as
cxl_mem.Quoted 4 lines
For CXL VH the host driver (
cxl_acpi) starts host bridge discovery once the ACPI0017 CXL root device is detected and then searches for ACPI0016 host bridges to enable CXL. In RCD mode an ACPI0017 device might not necessarily existQuoted 4 lines
That's a broken BIOS as far as I can see. No ACPI0017 == no OS CXL services and the CXL aspects of the device need to be 100% managed by the BIOS. You can still run the
cxl_pcidriver in that case for mailbox operation, but error handling must be firmware-first without ACPI0017.Quoted 8 lines
Firmware-first or OS-first applies to CXL protocol error handling. For CXL memory error handling, the device generates a DRAM error record, the OS parses such record and act accordingly. According to CXL spec (section 8.2.9.2.1.2 DRAM Event Record), DPA but not HPA is in such record. The OS needs to translate such DPA into HPA to act on. I am taking this as an example to show that OS CXL services is needed.
Instead of using ACPI0016 to tell whether the system is under RCH mode, I suppose one way is to check “CXL version” field of CHBS structure in CEDT?
Quoted 7 lines
Unless the OS has negotiated CXL
_OSCthe BIOS owns the event retrieval and translating it from DPA to HPA. I do want to add OS CXL services to Linux, but only in the case when the BIOS is actively enabling OS native address translation which includes populating ACPI0017, CFMWS, and devices with the HDM decoder capability registers instead of DVSEC range registers. Everything else is early-gen CXL that is 100% BIOS supported, similar to DDR where a driver is not expected.
It makes sense that the BIOS and OS need to negotiate CXL _OSC so that OS would take care of address translation. That being said, only DVSEC range register (but not HDM decoder capability register) is available when the device is in RCRB mode (section 9.11.8 figure 9-7) attached to a RCH. This type of configuration needs to be supported with OS CXL service.
Quoted 58 lines · Jonathan Zhang (Infra)
Quoted 49 lines · Dan Williams
!-------------------------------------------------------------------|
This Message Is From an External Sender|-------------------------------------------------------------------!
Quoted 30 lines · Jonathan Zhang (Infra)
Quoted 26 lines · Dan Williams
Apologies for the delay in getting to this I had hoped to be able to finish up some other DAX work to focus on this, but time is getting short so I will need to do both in parallel.
Quoted 12 lines · Robert Richter
In Restricted CXL Device (RCD) mode (formerly referred to as CXL 1.1) the PCIe enumeration hierarchy is different from CXL VH Enumeration (formerly referred to as 2.0, for both modes see CXL spec 3.0: 9.11 and 9.12, [1]). This series adds support for RCD mode. It implements the detection of Restricted CXL Hosts (RCHs) and its corresponding Restricted CXL Devices (RCDs). It does the necessary enumeration of ports and connects the endpoints. With all the plumbing an RCH/RCD pair is registered at the Linux CXL bus and becomes visible in sysfs in the same way as CXL VH hosts and devices do already. RCDs are brought up as CXL endpoints and bound to subsequent drivers such as
cxl_mem.Quoted 4 lines
For CXL VH the host driver (
cxl_acpi) starts host bridge discovery once the ACPI0017 CXL root device is detected and then searches for ACPI0016 host bridges to enable CXL. In RCD mode an ACPI0017 device might not necessarily existQuoted 4 lines
That's a broken BIOS as far as I can see. No ACPI0017 == no OS CXL services and the CXL aspects of the device need to be 100% managed by the BIOS. You can still run the
cxl_pcidriver in that case for mailbox operation, but error handling must be firmware-first without ACPI0017.Quoted 8 lines
Firmware-first or OS-first applies to CXL protocol error handling. For CXL memory error handling, the device generates a DRAM error record, the OS parses such record and act accordingly. According to CXL spec (section 8.2.9.2.1.2 DRAM Event Record), DPA but not HPA is in such record. The OS needs to translate such DPA into HPA to act on. I am taking this as an example to show that OS CXL services is needed.
Instead of using ACPI0016 to tell whether the system is under RCH mode, I suppose one way is to check “CXL version” field of CHBS structure in CEDT?Quoted 7 lines
Unless the OS has negotiated CXL
_OSCthe BIOS owns the event retrieval and translating it from DPA to HPA. I do want to add OS CXL services to Linux, but only in the case when the BIOS is actively enabling OS native address translation which includes populating ACPI0017, CFMWS, and devices with the HDM decoder capability registers instead of DVSEC range registers. Everything else is early-gen CXL that is 100% BIOS supported, similar to DDR where a driver is not expected.
Quoted 6 lines
It makes sense that the BIOS and OS need to negotiate CXL
_OSCso that OS would take care of address translation. That being said, only DVSEC range register (but not HDM decoder capability register) is available when the device is in RCRB mode (section 9.11.8 figure 9-7) attached to a RCH. This type of configuration needs to be supported with OS CXL service.
So that figure does have the HDM capabilty pictured in the RCD upstream port. However, Table 8-22 does seem to incidate that Type 3 D1 devices are not permitted to have an HDM Decoder Capabilitiy Structure.
However that then leave me confused about figure 9-8 as that shows an HDM decoder capability in the BAR and not the RCRB. Is that picture wrong with respect what Table 8-22 indicates?
Quoted 25 lines · Robert Richter
In Restricted CXL Device (RCD) mode (formerly referred to as CXL 1.1) the PCIe enumeration hierarchy is different from CXL VH Enumeration (formerly referred to as 2.0, for both modes see CXL spec 3.0: 9.11 and 9.12, [1]). This series adds support for RCD mode. It implements the detection of Restricted CXL Hosts (RCHs) and its corresponding Restricted CXL Devices (RCDs). It does the necessary enumeration of ports and connects the endpoints. With all the plumbing an RCH/RCD pair is registered at the Linux CXL bus and becomes visible in sysfs in the same way as CXL VH hosts and devices do already. RCDs are brought up as CXL endpoints and bound to subsequent drivers such as
cxl_mem.For CXL VH the host driver (
cxl_acpi) starts host bridge discovery once the ACPI0017 CXL root device is detected and then searches for ACPI0016 host bridges to enable CXL. In RCD mode an ACPI0017 device might not necessarily exist and the host bridge can have a standard PCIe host bridge PNP0A08 ID, there aren't any CXL port or switches in the PCIe hierarchy visible. As such the RCD mode enumeration and host discovery is very different from CXL VH. See patch #5 for implementation details.This implementation expects the host's downstream and upstream port RCRBs base address being reported by firmware using the optional CEDT CHBS entry of the host bridge (see CXL spec 3.0, 9.17.1.2).
Quoted 8 lines
RCD mode does not support hot-plug, so host discovery is at boot time only.
Patches #1 to #4 are prerequisites of the series with fixes needed and a rework of debug messages for port enumeration. Those are general patches and could be applied earlier and independently from the rest assuming there are no objections with them. Patches #5 to #15 contain the actual implementation of RCD mode support.
Hi Robert,
I did not see a response to some of my feedback but wanted to summarize where I think the next version of this set needs to go:
1/ ACPI0017 is mandatory. If a BIOS does not provide ACPI0017 it is explicitly opting the OS out of managing anything other than the CXL.io side of memory expanders.
2/ Per table 8-22 in CXL 3.0 RCDs are not permitted to have HDM decoders so that assumption in the driver needs to be reworked.
3/ It's not even clear that the Register Locator DVSEC has any role to play in an RCD as every register the driver needs should be relative to the RCRB. So the assumptions in the driver need to consider RCRB located registers as a first class citizen.