* Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
@ 2024-11-18 8:50 François Legal
2024-11-18 9:01 ` Jan Kiszka
0 siblings, 1 reply; 23+ messages in thread
From: François Legal @ 2024-11-18 8:50 UTC (permalink / raw)
To: xenomai
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
Hello,
running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
Attached is my config.
Thanks
François
[-- Attachment #2: config --]
[-- Type: application/octet-stream, Size: 88420 bytes --]
#
# Automatically generated file; DO NOT EDIT.
# Linux/arm 5.15.170 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="arm-oe-linux-gnueabi-gcc (GCC) 11.4.0"
CONFIG_CC_IS_GCC=y
CONFIG_GCC_VERSION=110400
CONFIG_CLANG_VERSION=0
CONFIG_AS_IS_GNU=y
CONFIG_AS_VERSION=20244508
CONFIG_LD_IS_BFD=y
CONFIG_LD_VERSION=20244508
CONFIG_LLD_VERSION=0
CONFIG_CC_HAS_ASM_GOTO=y
CONFIG_CC_HAS_ASM_GOTO_OUTPUT=y
CONFIG_CC_HAS_ASM_GOTO_TIED_OUTPUT=y
CONFIG_CC_HAS_ASM_INLINE=y
CONFIG_CC_HAS_NO_PROFILE_FN_ATTR=y
CONFIG_PAHOLE_VERSION=0
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_TABLE_SORT=y
#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
# CONFIG_COMPILE_TEST is not set
# CONFIG_WERROR is not set
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_BUILD_SALT=""
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
# CONFIG_KERNEL_GZIP is not set
# CONFIG_KERNEL_LZMA is not set
CONFIG_KERNEL_XZ=y
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_INIT=""
CONFIG_DEFAULT_HOSTNAME="(none)"
# CONFIG_SWAP is not set
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_WATCH_QUEUE is not set
# CONFIG_CROSS_MEMORY_ATTACH is not set
# CONFIG_USELIB is not set
# CONFIG_AUDIT is not set
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_SHOW_LEVEL=y
CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK=y
CONFIG_HARDIRQS_SW_RESEND=y
CONFIG_IRQ_DOMAIN=y
CONFIG_IRQ_DOMAIN_HIERARCHY=y
CONFIG_IRQ_DOMAIN_NOMAP=y
CONFIG_GENERIC_IRQ_IPI=y
CONFIG_HANDLE_DOMAIN_IRQ=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
# CONFIG_GENERIC_IRQ_DEBUGFS is not set
CONFIG_HAVE_IRQ_PIPELINE=y
CONFIG_IRQ_PIPELINE=y
# end of IRQ subsystem
CONFIG_GENERIC_IRQ_MULTI_HANDLER=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_ARCH_HAS_TICK_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_HZ_PERIODIC=y
# CONFIG_NO_HZ_IDLE is not set
# CONFIG_NO_HZ_FULL is not set
# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y
# end of Timers subsystem
CONFIG_BPF=y
CONFIG_HAVE_EBPF_JIT=y
#
# BPF subsystem
#
# CONFIG_BPF_SYSCALL is not set
# end of BPF subsystem
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
# CONFIG_IRQ_TIME_ACCOUNTING is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_PSI is not set
# end of CPU/Task time and stats accounting
CONFIG_CPU_ISOLATION=y
#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_RCU_EXPERT is not set
CONFIG_SRCU=y
CONFIG_TREE_SRCU=y
CONFIG_RCU_STALL_COMMON=y
CONFIG_RCU_NEED_SEGCBLIST=y
# end of RCU Subsystem
# CONFIG_IKCONFIG is not set
# CONFIG_IKHEADERS is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_LOG_CPU_MAX_BUF_SHIFT=12
CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
# CONFIG_PRINTK_INDEX is not set
CONFIG_GENERIC_SCHED_CLOCK=y
#
# Scheduler features
#
# end of Scheduler features
# CONFIG_CGROUPS is not set
# CONFIG_NAMESPACES is not set
# CONFIG_CHECKPOINT_RESTORE is not set
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_SYSFS_DEPRECATED is not set
# CONFIG_RELAY is not set
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_BOOT_CONFIG is not set
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_LD_ORPHAN_WARN=y
CONFIG_SYSCTL=y
CONFIG_HAVE_UID16=y
CONFIG_EXPERT=y
CONFIG_UID16=y
CONFIG_MULTIUSER=y
# CONFIG_SGETMASK_SYSCALL is not set
CONFIG_SYSFS_SYSCALL=y
CONFIG_FHANDLE=y
CONFIG_POSIX_TIMERS=y
CONFIG_PRINTK=y
# CONFIG_RAW_PRINTK is not set
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_FUTEX_PI=y
CONFIG_HAVE_FUTEX_CMPXCHG=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
# CONFIG_AIO is not set
# CONFIG_IO_URING is not set
# CONFIG_ADVISE_SYSCALLS is not set
CONFIG_MEMBARRIER=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_KALLSYMS_BASE_RELATIVE=y
# CONFIG_USERFAULTFD is not set
CONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=y
CONFIG_KCMP=y
CONFIG_RSEQ=y
# CONFIG_DEBUG_RSEQ is not set
CONFIG_EMBEDDED=y
CONFIG_HAVE_PERF_EVENTS=y
CONFIG_PERF_USE_VMALLOC=y
# CONFIG_PC104 is not set
#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
# end of Kernel Performance Events And Counters
CONFIG_VM_EVENT_COUNTERS=y
# CONFIG_SLUB_DEBUG is not set
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_SLAB_MERGE_DEFAULT=y
# CONFIG_SLAB_FREELIST_RANDOM is not set
# CONFIG_SLAB_FREELIST_HARDENED is not set
# CONFIG_SHUFFLE_PAGE_ALLOCATOR is not set
CONFIG_SLUB_CPU_PARTIAL=y
# CONFIG_PROFILING is not set
# end of General setup
CONFIG_ARM=y
CONFIG_ARM_HAS_SG_CHAIN=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_HAVE_PROC_CPU=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_IPIPE_COMPAT=y
CONFIG_ARM_PATCH_PHYS_VIRT=y
CONFIG_GENERIC_BUG=y
CONFIG_PGTABLE_LEVELS=2
#
# System Type
#
CONFIG_MMU=y
CONFIG_ARCH_MMAP_RND_BITS_MIN=8
CONFIG_ARCH_MMAP_RND_BITS_MAX=16
CONFIG_ARCH_MULTIPLATFORM=y
# CONFIG_ARCH_EP93XX is not set
# CONFIG_ARCH_FOOTBRIDGE is not set
# CONFIG_ARCH_IOP32X is not set
# CONFIG_ARCH_IXP4XX is not set
# CONFIG_ARCH_DOVE is not set
# CONFIG_ARCH_PXA is not set
# CONFIG_ARCH_RPC is not set
# CONFIG_ARCH_SA1100 is not set
# CONFIG_ARCH_S3C24XX is not set
# CONFIG_ARCH_OMAP1 is not set
#
# Multiple platform selection
#
#
# CPU Core family selection
#
# CONFIG_ARCH_MULTI_V6 is not set
CONFIG_ARCH_MULTI_V7=y
CONFIG_ARCH_MULTI_V6_V7=y
# end of Multiple platform selection
# CONFIG_ARCH_VIRT is not set
# CONFIG_ARCH_ACTIONS is not set
# CONFIG_ARCH_ALPINE is not set
# CONFIG_ARCH_ARTPEC is not set
# CONFIG_ARCH_ASPEED is not set
# CONFIG_ARCH_AT91 is not set
# CONFIG_ARCH_BCM is not set
# CONFIG_ARCH_BERLIN is not set
# CONFIG_ARCH_DIGICOLOR is not set
# CONFIG_ARCH_EXYNOS is not set
# CONFIG_ARCH_HIGHBANK is not set
# CONFIG_ARCH_HISI is not set
# CONFIG_ARCH_MXC is not set
# CONFIG_ARCH_KEYSTONE is not set
# CONFIG_ARCH_MEDIATEK is not set
# CONFIG_ARCH_MESON is not set
# CONFIG_ARCH_MILBEAUT is not set
# CONFIG_ARCH_MMP is not set
# CONFIG_ARCH_MSTARV7 is not set
# CONFIG_ARCH_MVEBU is not set
# CONFIG_ARCH_NPCM is not set
#
# TI OMAP/AM/DM/DRA Family
#
# CONFIG_ARCH_OMAP3 is not set
# CONFIG_ARCH_OMAP4 is not set
# CONFIG_SOC_OMAP5 is not set
# CONFIG_SOC_AM33XX is not set
# CONFIG_SOC_AM43XX is not set
# CONFIG_SOC_DRA7XX is not set
# end of TI OMAP/AM/DM/DRA Family
# CONFIG_ARCH_QCOM is not set
# CONFIG_ARCH_RDA is not set
# CONFIG_ARCH_REALTEK is not set
# CONFIG_ARCH_REALVIEW is not set
# CONFIG_ARCH_ROCKCHIP is not set
# CONFIG_ARCH_S5PV210 is not set
# CONFIG_ARCH_RENESAS is not set
# CONFIG_ARCH_INTEL_SOCFPGA is not set
# CONFIG_PLAT_SPEAR is not set
# CONFIG_ARCH_STI is not set
# CONFIG_ARCH_STM32 is not set
# CONFIG_ARCH_SUNXI is not set
# CONFIG_ARCH_TEGRA is not set
# CONFIG_ARCH_UNIPHIER is not set
# CONFIG_ARCH_U8500 is not set
# CONFIG_ARCH_VEXPRESS is not set
# CONFIG_ARCH_WM8850 is not set
CONFIG_ARCH_ZYNQ=y
#
# Processor Type
#
CONFIG_CPU_V7=y
CONFIG_CPU_THUMB_CAPABLE=y
CONFIG_CPU_32v6K=y
CONFIG_CPU_32v7=y
CONFIG_CPU_ABRT_EV7=y
CONFIG_CPU_PABRT_V7=y
CONFIG_CPU_CACHE_V7=y
CONFIG_CPU_CACHE_VIPT=y
CONFIG_CPU_COPY_V6=y
CONFIG_CPU_TLB_V7=y
CONFIG_CPU_HAS_ASID=y
CONFIG_CPU_CP15=y
CONFIG_CPU_CP15_MMU=y
#
# Processor Features
#
# CONFIG_ARM_LPAE is not set
CONFIG_ARM_THUMB=y
# CONFIG_ARM_THUMBEE is not set
CONFIG_ARM_VIRT_EXT=y
CONFIG_SWP_EMULATE=y
# CONFIG_CPU_BIG_ENDIAN is not set
# CONFIG_CPU_ICACHE_DISABLE is not set
# CONFIG_CPU_ICACHE_MISMATCH_WORKAROUND is not set
# CONFIG_CPU_BPREDICT_DISABLE is not set
CONFIG_CPU_SPECTRE=y
CONFIG_HARDEN_BRANCH_PREDICTOR=y
CONFIG_HARDEN_BRANCH_HISTORY=y
CONFIG_KUSER_HELPERS=y
CONFIG_VDSO=y
CONFIG_OUTER_CACHE=y
CONFIG_OUTER_CACHE_SYNC=y
CONFIG_MIGHT_HAVE_CACHE_L2X0=y
CONFIG_CACHE_L2X0=y
# CONFIG_CACHE_L2X0_PMU is not set
CONFIG_PL310_ERRATA_588369=y
CONFIG_PL310_ERRATA_727915=y
CONFIG_PL310_ERRATA_753970=y
CONFIG_PL310_ERRATA_769419=y
CONFIG_ARM_L1_CACHE_SHIFT_6=y
CONFIG_ARM_L1_CACHE_SHIFT=6
CONFIG_ARM_DMA_MEM_BUFFERABLE=y
CONFIG_ARM_HEAVY_MB=y
CONFIG_ARCH_SUPPORTS_BIG_ENDIAN=y
CONFIG_DEBUG_ALIGN_RODATA=y
# CONFIG_ARM_ERRATA_430973 is not set
# CONFIG_ARM_ERRATA_643719 is not set
# CONFIG_ARM_ERRATA_720789 is not set
CONFIG_ARM_ERRATA_754322=y
# CONFIG_ARM_ERRATA_754327 is not set
CONFIG_ARM_ERRATA_764369=y
CONFIG_ARM_ERRATA_775420=y
# CONFIG_ARM_ERRATA_798181 is not set
# CONFIG_ARM_ERRATA_773022 is not set
# CONFIG_ARM_ERRATA_818325_852422 is not set
# CONFIG_ARM_ERRATA_821420 is not set
# CONFIG_ARM_ERRATA_825619 is not set
# CONFIG_ARM_ERRATA_857271 is not set
# CONFIG_ARM_ERRATA_852421 is not set
# CONFIG_ARM_ERRATA_852423 is not set
# CONFIG_ARM_ERRATA_857272 is not set
# end of System Type
#
# Bus support
#
# CONFIG_ARM_ERRATA_814220 is not set
# end of Bus support
#
# Kernel Features
#
CONFIG_HAVE_SMP=y
CONFIG_SMP=y
# CONFIG_SMP_ON_UP is not set
CONFIG_ARM_CPU_TOPOLOGY=y
# CONFIG_SCHED_MC is not set
# CONFIG_SCHED_SMT is not set
CONFIG_HAVE_DOVETAIL=y
CONFIG_DOVETAIL=y
CONFIG_DOVETAIL_LEGACY_SYSCALL_RANGE=y
CONFIG_HAVE_ARM_SCU=y
CONFIG_HAVE_ARM_ARCH_TIMER=y
CONFIG_HAVE_ARM_TWD=y
# CONFIG_MCPM is not set
# CONFIG_BIG_LITTLE is not set
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_3G_OPT is not set
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_NR_CPUS=2
# CONFIG_HOTPLUG_CPU is not set
# CONFIG_ARM_PSCI is not set
CONFIG_ARCH_NR_GPIO=1024
CONFIG_HZ_FIXED=0
CONFIG_HZ_100=y
# CONFIG_HZ_200 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_500 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100
CONFIG_SCHED_HRTICK=y
# CONFIG_THUMB2_KERNEL is not set
CONFIG_ARM_PATCH_IDIV=y
CONFIG_AEABI=y
# CONFIG_OABI_COMPAT is not set
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_HIGHMEM=y
CONFIG_HIGHPTE=y
CONFIG_CPU_SW_DOMAIN_PAN=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_FORCE_MAX_ZONEORDER=12
CONFIG_ALIGNMENT_TRAP=y
# CONFIG_UACCESS_WITH_MEMCPY is not set
# CONFIG_PARAVIRT is not set
# CONFIG_PARAVIRT_TIME_ACCOUNTING is not set
# CONFIG_XEN is not set
# end of Kernel Features
#
# Boot options
#
CONFIG_USE_OF=y
CONFIG_ATAGS=y
# CONFIG_DEPRECATED_PARAM_STRUCT is not set
CONFIG_ZBOOT_ROM_TEXT=0x0
CONFIG_ZBOOT_ROM_BSS=0x0
CONFIG_ARM_APPENDED_DTB=y
CONFIG_ARM_ATAG_DTB_COMPAT=y
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y
# CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND is not set
CONFIG_CMDLINE=""
# CONFIG_CRASH_DUMP is not set
CONFIG_AUTO_ZRELADDR=y
# CONFIG_EFI is not set
# end of Boot options
#
# CPU Power Management
#
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
# end of CPU Frequency scaling
#
# CPU Idle
#
# CONFIG_CPU_IDLE is not set
# end of CPU Idle
# end of CPU Power Management
#
# Floating point emulation
#
#
# At least one emulation must be selected
#
CONFIG_VFP=y
CONFIG_VFPv3=y
CONFIG_NEON=y
CONFIG_KERNEL_MODE_NEON=y
# end of Floating point emulation
#
# Power management options
#
# CONFIG_SUSPEND is not set
# CONFIG_PM is not set
# CONFIG_APM_EMULATION is not set
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
# end of Power management options
# CONFIG_ARM_CRYPTO is not set
CONFIG_AS_VFP_VMRS_FPINST=y
CONFIG_CPU_MITIGATIONS=y
#
# General architecture-dependent options
#
# CONFIG_JUMP_LABEL is not set
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_ARCH_USE_BUILTIN_BSWAP=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_NMI=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_CONTIGUOUS=y
CONFIG_GENERIC_SMP_IDLE_THREAD=y
CONFIG_GENERIC_IDLE_POLL_SETUP=y
CONFIG_ARCH_HAS_FORTIFY_SOURCE=y
CONFIG_ARCH_HAS_KEEPINITRD=y
CONFIG_ARCH_HAS_SET_MEMORY=y
CONFIG_ARCH_HAS_CPU_FINALIZE_INIT=y
CONFIG_HAVE_ARCH_THREAD_STRUCT_WHITELIST=y
CONFIG_ARCH_32BIT_OFF_T=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_RSEQ=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_PERF_REGS=y
CONFIG_HAVE_PERF_USER_STACK_DUMP=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y
CONFIG_ARCH_WANT_IRQS_OFF_ACTIVATE_MM=y
CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y
CONFIG_ARCH_WANT_IPC_PARSE_VERSION=y
CONFIG_HAVE_ARCH_SECCOMP=y
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP=y
CONFIG_SECCOMP_FILTER=y
# CONFIG_SECCOMP_CACHE_DEBUG is not set
CONFIG_HAVE_STACKPROTECTOR=y
CONFIG_STACKPROTECTOR=y
CONFIG_STACKPROTECTOR_STRONG=y
CONFIG_LTO_NONE=y
CONFIG_HAVE_CONTEXT_TRACKING=y
CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y
CONFIG_HAVE_MOD_ARCH_SPECIFIC=y
CONFIG_MODULES_USE_ELF_REL=y
CONFIG_ARCH_HAS_ELF_RANDOMIZE=y
CONFIG_HAVE_ARCH_MMAP_RND_BITS=y
CONFIG_HAVE_EXIT_THREAD=y
CONFIG_ARCH_MMAP_RND_BITS=8
CONFIG_ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT=y
CONFIG_CLONE_BACKWARDS=y
CONFIG_OLD_SIGSUSPEND3=y
CONFIG_OLD_SIGACTION=y
CONFIG_COMPAT_32BIT_TIME=y
CONFIG_ARCH_OPTIONAL_KERNEL_RWX=y
CONFIG_ARCH_OPTIONAL_KERNEL_RWX_DEFAULT=y
CONFIG_ARCH_HAS_STRICT_KERNEL_RWX=y
CONFIG_STRICT_KERNEL_RWX=y
CONFIG_ARCH_HAS_STRICT_MODULE_RWX=y
CONFIG_ARCH_HAS_PHYS_TO_DMA=y
# CONFIG_LOCK_EVENT_COUNTS is not set
CONFIG_ARCH_WANT_LD_ORPHAN_WARN=y
CONFIG_HAVE_ARCH_PFN_VALID=y
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
# end of GCOV-based kernel profiling
CONFIG_HAVE_GCC_PLUGINS=y
# CONFIG_GCC_PLUGINS is not set
CONFIG_FUNCTION_ALIGNMENT=0
# end of General architecture-dependent options
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
# CONFIG_MODULES is not set
CONFIG_MODULES_TREE_LOOKUP=y
CONFIG_BLOCK=y
# CONFIG_BLK_DEV_BSGLIB is not set
# CONFIG_BLK_DEV_INTEGRITY is not set
# CONFIG_BLK_DEV_ZONED is not set
# CONFIG_BLK_WBT is not set
# CONFIG_BLK_DEBUG_FS is not set
# CONFIG_BLK_SED_OPAL is not set
# CONFIG_BLK_INLINE_ENCRYPTION is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_EFI_PARTITION=y
# end of Partition Types
#
# IO Schedulers
#
CONFIG_MQ_IOSCHED_DEADLINE=y
# CONFIG_MQ_IOSCHED_KYBER is not set
# CONFIG_IOSCHED_BFQ is not set
# end of IO Schedulers
CONFIG_ASN1=y
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
CONFIG_INLINE_READ_UNLOCK=y
CONFIG_INLINE_READ_UNLOCK_IRQ=y
CONFIG_INLINE_WRITE_UNLOCK=y
CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_RWSEM_SPIN_ON_OWNER=y
CONFIG_LOCK_SPIN_ON_OWNER=y
CONFIG_ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE=y
CONFIG_XENOMAI=y
#
# Core features
#
# CONFIG_XENO_OPT_SCHED_CLASSES is not set
CONFIG_XENO_OPT_STATS=y
# CONFIG_XENO_OPT_SHIRQ is not set
CONFIG_XENO_OPT_RR_QUANTUM=1000
CONFIG_XENO_OPT_AUTOTUNE=y
# CONFIG_XENO_OPT_SCALABLE_SCHED is not set
CONFIG_XENO_OPT_TIMER_LIST=y
# CONFIG_XENO_OPT_TIMER_RBTREE is not set
CONFIG_XENO_OPT_VFILE=y
# end of Core features
#
# Sizes and static limits
#
CONFIG_XENO_OPT_REGISTRY_NRSLOTS=512
CONFIG_XENO_OPT_SYS_HEAPSZ=4096
CONFIG_XENO_OPT_PRIVATE_HEAPSZ=256
CONFIG_XENO_OPT_SHARED_HEAPSZ=256
CONFIG_XENO_OPT_NRTIMERS=256
# end of Sizes and static limits
#
# Latency settings
#
CONFIG_XENO_OPT_TIMING_SCHEDLAT=0
CONFIG_XENO_OPT_TIMING_KSCHEDLAT=0
CONFIG_XENO_OPT_TIMING_IRQLAT=0
# end of Latency settings
# CONFIG_XENO_OPT_DEBUG is not set
#
# Drivers
#
# CONFIG_XENO_OPT_RTDM_COMPAT_DEVNODE is not set
CONFIG_XENO_DRIVERS_AUTOTUNE=y
#
# Serial drivers
#
# CONFIG_XENO_DRIVERS_16550A is not set
# end of Serial drivers
#
# Testing drivers
#
CONFIG_XENO_DRIVERS_TIMERBENCH=y
CONFIG_XENO_DRIVERS_SWITCHTEST=y
CONFIG_XENO_DRIVERS_HEAPCHECK=y
# end of Testing drivers
#
# CAN drivers
#
# CONFIG_XENO_DRIVERS_CAN is not set
# end of CAN drivers
#
# RTnet
#
# CONFIG_XENO_DRIVERS_NET is not set
# end of RTnet
#
# ANALOGY drivers
#
# CONFIG_XENO_DRIVERS_ANALOGY is not set
# end of ANALOGY drivers
#
# Real-time IPC drivers
#
# CONFIG_XENO_DRIVERS_RTIPC is not set
# end of Real-time IPC drivers
#
# UDD support
#
# CONFIG_XENO_DRIVERS_UDD is not set
# end of UDD support
#
# Real-time GPIO drivers
#
# CONFIG_XENO_DRIVERS_GPIO is not set
# end of Real-time GPIO drivers
#
# GPIOPWM support
#
# CONFIG_XENO_DRIVERS_GPIOPWM is not set
# end of GPIOPWM support
#
# Real-time SPI master drivers
#
# end of Real-time SPI master drivers
# end of Drivers
CONFIG_XENO_ARCH_FPU=y
CONFIG_XENO_ARCH_OUTOFLINE_XNLOCK=y
CONFIG_XENO_ARCH_IPIPE_COMPAT=y
#
# WARNING! Page migration (CONFIG_MIGRATION) may increase
#
#
# latency.
#
CONFIG_XENO_VERSION_MAJOR=3
CONFIG_XENO_VERSION_MINOR=3
CONFIG_XENO_REVISION_LEVEL=0
CONFIG_XENO_VERSION_STRING="3.3"
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_ELF_FDPIC is not set
CONFIG_ELFCORE=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
CONFIG_BINFMT_SCRIPT=y
CONFIG_ARCH_HAS_BINFMT_FLAT=y
# CONFIG_BINFMT_FLAT is not set
CONFIG_BINFMT_FLAT_ARGVP_ENVP_ON_STACK=y
# CONFIG_BINFMT_MISC is not set
CONFIG_COREDUMP=y
# end of Executable file formats
#
# Memory Management options
#
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_ARCH_KEEP_MEMBLOCK=y
CONFIG_MEMORY_ISOLATION=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_COMPACTION=y
# CONFIG_PAGE_REPORTING is not set
CONFIG_MIGRATION=y
CONFIG_CONTIG_ALLOC=y
CONFIG_BOUNCE=y
# CONFIG_KSM is not set
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
# CONFIG_CLEANCACHE is not set
CONFIG_CMA=y
# CONFIG_CMA_DEBUG is not set
# CONFIG_CMA_DEBUGFS is not set
# CONFIG_CMA_SYSFS is not set
CONFIG_CMA_AREAS=7
# CONFIG_ZPOOL is not set
# CONFIG_ZSMALLOC is not set
CONFIG_GENERIC_EARLY_IOREMAP=y
# CONFIG_IDLE_PAGE_TRACKING is not set
# CONFIG_PERCPU_STATS is not set
# CONFIG_GUP_TEST is not set
CONFIG_KMAP_LOCAL=y
CONFIG_KMAP_LOCAL_NON_LINEAR_PTE_ARRAY=y
#
# Data Access Monitoring
#
# CONFIG_DAMON is not set
# end of Data Access Monitoring
# end of Memory Management options
CONFIG_NET=y
CONFIG_NET_INGRESS=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_DIAG is not set
CONFIG_UNIX=y
CONFIG_UNIX_SCM=y
CONFIG_AF_UNIX_OOB=y
# CONFIG_UNIX_DIAG is not set
# CONFIG_TLS is not set
# CONFIG_XFRM_USER is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_PNP=y
# CONFIG_IP_PNP_DHCP is not set
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE_DEMUX is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_NET_IPVTI is not set
# CONFIG_NET_FOU is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
CONFIG_INET_TABLE_PERTURB_ORDER=16
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_INET_UDP_DIAG is not set
# CONFIG_INET_RAW_DIAG is not set
# CONFIG_INET_DIAG_DESTROY is not set
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_MPTCP is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
CONFIG_NETFILTER=y
CONFIG_NETFILTER_ADVANCED=y
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_INGRESS=y
CONFIG_NETFILTER_NETLINK=y
# CONFIG_NETFILTER_NETLINK_HOOK is not set
# CONFIG_NETFILTER_NETLINK_ACCT is not set
# CONFIG_NETFILTER_NETLINK_QUEUE is not set
# CONFIG_NETFILTER_NETLINK_LOG is not set
# CONFIG_NETFILTER_NETLINK_OSF is not set
# CONFIG_NF_CONNTRACK is not set
# CONFIG_NF_LOG_SYSLOG is not set
CONFIG_NF_TABLES=y
# CONFIG_NF_TABLES_NETDEV is not set
# CONFIG_NFT_NUMGEN is not set
# CONFIG_NFT_COUNTER is not set
CONFIG_NFT_LOG=y
CONFIG_NFT_LIMIT=y
# CONFIG_NFT_TUNNEL is not set
# CONFIG_NFT_OBJREF is not set
# CONFIG_NFT_QUOTA is not set
CONFIG_NFT_REJECT=y
# CONFIG_NFT_HASH is not set
# CONFIG_NFT_SOCKET is not set
# CONFIG_NFT_OSF is not set
# CONFIG_NFT_TPROXY is not set
# CONFIG_NF_FLOW_TABLE_PROCFS is not set
# CONFIG_NETFILTER_XTABLES is not set
# end of Core Netfilter Configuration
# CONFIG_IP_SET is not set
# CONFIG_IP_VS is not set
#
# IP: Netfilter Configuration
#
# CONFIG_NF_SOCKET_IPV4 is not set
# CONFIG_NF_TPROXY_IPV4 is not set
CONFIG_NF_TABLES_IPV4=y
CONFIG_NFT_REJECT_IPV4=y
# CONFIG_NFT_DUP_IPV4 is not set
# CONFIG_NFT_FIB_IPV4 is not set
# CONFIG_NF_TABLES_ARP is not set
# CONFIG_NF_DUP_IPV4 is not set
# CONFIG_NF_LOG_ARP is not set
# CONFIG_NF_LOG_IPV4 is not set
CONFIG_NF_REJECT_IPV4=y
# CONFIG_IP_NF_IPTABLES is not set
# CONFIG_IP_NF_ARPTABLES is not set
# end of IP: Netfilter Configuration
# CONFIG_BPFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_L2TP is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DSA is not set
CONFIG_VLAN_8021Q=y
# CONFIG_VLAN_8021Q_GVRP is not set
# CONFIG_VLAN_8021Q_MVRP is not set
# CONFIG_LLC2 is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_PHONET is not set
# CONFIG_IEEE802154 is not set
# CONFIG_NET_SCHED is not set
# CONFIG_DCB is not set
# CONFIG_BATMAN_ADV is not set
# CONFIG_OPENVSWITCH is not set
# CONFIG_VSOCKETS is not set
# CONFIG_NETLINK_DIAG is not set
# CONFIG_MPLS is not set
# CONFIG_NET_NSH is not set
# CONFIG_HSR is not set
# CONFIG_NET_SWITCHDEV is not set
# CONFIG_NET_L3_MASTER_DEV is not set
# CONFIG_QRTR is not set
# CONFIG_NET_NCSI is not set
# CONFIG_PCPU_DEV_REFCNT is not set
CONFIG_RPS=y
CONFIG_RFS_ACCEL=y
CONFIG_SOCK_RX_QUEUE_MAPPING=y
CONFIG_XPS=y
CONFIG_NET_RX_BUSY_POLL=y
CONFIG_BQL=y
CONFIG_NET_FLOW_LIMIT=y
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# end of Network testing
# end of Networking options
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
# CONFIG_AF_KCM is not set
# CONFIG_MCTP is not set
# CONFIG_WIRELESS is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set
# CONFIG_CEPH_LIB is not set
# CONFIG_NFC is not set
# CONFIG_PSAMPLE is not set
# CONFIG_NET_IFE is not set
# CONFIG_LWTUNNEL is not set
CONFIG_NET_SELFTESTS=y
# CONFIG_FAILOVER is not set
# CONFIG_ETHTOOL_NETLINK is not set
#
# Device Drivers
#
CONFIG_ARM_AMBA=y
CONFIG_HAVE_PCI=y
# CONFIG_PCI is not set
# CONFIG_PCCARD is not set
#
# Generic Driver Options
#
# CONFIG_UEVENT_HELPER is not set
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
#
# Firmware loader
#
CONFIG_FW_LOADER=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_FW_LOADER_USER_HELPER is not set
# CONFIG_FW_LOADER_COMPRESS is not set
# end of Firmware loader
# CONFIG_ALLOW_DEV_COREDUMP is not set
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_DEBUG_TEST_DRIVER_REMOVE is not set
CONFIG_GENERIC_CPU_AUTOPROBE=y
CONFIG_GENERIC_CPU_VULNERABILITIES=y
CONFIG_SOC_BUS=y
CONFIG_REGMAP=y
CONFIG_REGMAP_I2C=y
CONFIG_REGMAP_MMIO=y
CONFIG_GENERIC_ARCH_TOPOLOGY=y
# end of Generic Driver Options
#
# Bus devices
#
# CONFIG_BRCMSTB_GISB_ARB is not set
# CONFIG_MOXTET is not set
# CONFIG_VEXPRESS_CONFIG is not set
# CONFIG_MHI_BUS is not set
# end of Bus devices
# CONFIG_CONNECTOR is not set
#
# Firmware Drivers
#
#
# ARM System Control and Management Interface Protocol
#
# CONFIG_ARM_SCMI_PROTOCOL is not set
# end of ARM System Control and Management Interface Protocol
# CONFIG_FIRMWARE_MEMMAP is not set
# CONFIG_FW_CFG_SYSFS is not set
# CONFIG_TRUSTED_FOUNDATIONS is not set
# CONFIG_GOOGLE_FIRMWARE is not set
CONFIG_HAVE_ARM_SMCCC=y
#
# Tegra firmware driver
#
# end of Tegra firmware driver
# end of Firmware Drivers
# CONFIG_GNSS is not set
CONFIG_MTD=y
#
# Partition parsers
#
# CONFIG_MTD_AR7_PARTS is not set
CONFIG_MTD_CMDLINE_PARTS=y
CONFIG_MTD_OF_PARTS=y
# CONFIG_MTD_AFS_PARTS is not set
# CONFIG_MTD_REDBOOT_PARTS is not set
# end of Partition parsers
#
# User Modules And Translation Layers
#
# CONFIG_MTD_BLOCK is not set
# CONFIG_MTD_BLOCK_RO is not set
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_RFD_FTL is not set
# CONFIG_SSFDC is not set
# CONFIG_SM_FTL is not set
# CONFIG_MTD_OOPS is not set
# CONFIG_MTD_PARTITIONED_MASTER is not set
#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=y
CONFIG_MTD_JEDECPROBE=y
CONFIG_MTD_GEN_PROBE=y
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_INTELEXT is not set
# CONFIG_MTD_CFI_AMDSTD is not set
# CONFIG_MTD_CFI_STAA is not set
CONFIG_MTD_CFI_UTIL=y
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# end of RAM/ROM/Flash chip drivers
#
# Mapping drivers for chip access
#
CONFIG_MTD_COMPLEX_MAPPINGS=y
CONFIG_MTD_PHYSMAP=y
# CONFIG_MTD_PHYSMAP_COMPAT is not set
# CONFIG_MTD_PHYSMAP_OF is not set
# CONFIG_MTD_PHYSMAP_GPIO_ADDR is not set
# CONFIG_MTD_IMPA7 is not set
# CONFIG_MTD_PLATRAM is not set
# end of Mapping drivers for chip access
#
# Self-contained MTD device drivers
#
# CONFIG_MTD_DATAFLASH is not set
# CONFIG_MTD_MCHP23K256 is not set
# CONFIG_MTD_MCHP48L640 is not set
# CONFIG_MTD_SST25L is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLOCK2MTD is not set
#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOCG3 is not set
# end of Self-contained MTD device drivers
#
# NAND
#
# CONFIG_MTD_ONENAND is not set
# CONFIG_MTD_RAW_NAND is not set
# CONFIG_MTD_SPI_NAND is not set
#
# ECC engine support
#
# CONFIG_MTD_NAND_ECC_SW_HAMMING is not set
# CONFIG_MTD_NAND_ECC_SW_BCH is not set
# end of ECC engine support
# end of NAND
#
# LPDDR & LPDDR2 PCM memory drivers
#
# CONFIG_MTD_LPDDR is not set
# CONFIG_MTD_LPDDR2_NVM is not set
# end of LPDDR & LPDDR2 PCM memory drivers
CONFIG_MTD_SPI_NOR=y
CONFIG_MTD_SPI_NOR_USE_4K_SECTORS=y
# CONFIG_MTD_SPI_NOR_SWP_DISABLE is not set
CONFIG_MTD_SPI_NOR_SWP_DISABLE_ON_VOLATILE=y
# CONFIG_MTD_SPI_NOR_SWP_KEEP is not set
# CONFIG_MTD_UBI is not set
# CONFIG_MTD_HYPERBUS is not set
CONFIG_DTC=y
CONFIG_OF=y
# CONFIG_OF_UNITTEST is not set
CONFIG_OF_FLATTREE=y
CONFIG_OF_EARLY_FLATTREE=y
CONFIG_OF_KOBJ=y
CONFIG_OF_DYNAMIC=y
CONFIG_OF_ADDRESS=y
CONFIG_OF_IRQ=y
CONFIG_OF_RESERVED_MEM=y
CONFIG_OF_RESOLVE=y
CONFIG_OF_OVERLAY=y
CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_NULL_BLK is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=65536
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_BLK_DEV_RBD is not set
#
# NVME Support
#
# CONFIG_NVME_FC is not set
# CONFIG_NVME_TCP is not set
# CONFIG_NVME_TARGET is not set
# end of NVME Support
#
# Misc devices
#
# CONFIG_AD525X_DPOT is not set
# CONFIG_DUMMY_IRQ is not set
# CONFIG_ICS932S401 is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_APDS9802ALS is not set
# CONFIG_ISL29003 is not set
# CONFIG_ISL29020 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_SENSORS_BH1770 is not set
# CONFIG_SENSORS_APDS990X is not set
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not set
# CONFIG_LATTICE_ECP3_CONFIG is not set
CONFIG_SRAM=y
CONFIG_SRAM_EXEC=y
# CONFIG_XILINX_SDFEC is not set
# CONFIG_C2PORT is not set
#
# EEPROM support
#
CONFIG_EEPROM_AT24=y
# CONFIG_EEPROM_AT25 is not set
# CONFIG_EEPROM_LEGACY is not set
# CONFIG_EEPROM_MAX6875 is not set
CONFIG_EEPROM_93CX6=y
# CONFIG_EEPROM_93XX46 is not set
# CONFIG_EEPROM_IDT_89HPESX is not set
# CONFIG_EEPROM_EE1004 is not set
# end of EEPROM support
#
# Texas Instruments shared transport line discipline
#
# CONFIG_TI_ST is not set
# end of Texas Instruments shared transport line discipline
# CONFIG_SENSORS_LIS3_SPI is not set
# CONFIG_SENSORS_LIS3_I2C is not set
# CONFIG_ALTERA_STAPL is not set
# CONFIG_ECHO is not set
# CONFIG_PVPANIC is not set
# end of Misc devices
#
# SCSI device support
#
CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI_COMMON=y
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_PROC_FS is not set
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_CHR_DEV_SCH is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
# end of SCSI Transports
# CONFIG_SCSI_LOWLEVEL is not set
# CONFIG_SCSI_DH is not set
# end of SCSI device support
# CONFIG_ATA is not set
# CONFIG_MD is not set
# CONFIG_TARGET_CORE is not set
CONFIG_NETDEVICES=y
CONFIG_NET_CORE=y
# CONFIG_BONDING is not set
# CONFIG_DUMMY is not set
# CONFIG_WIREGUARD is not set
# CONFIG_EQUALIZER is not set
# CONFIG_NET_TEAM is not set
# CONFIG_MACVLAN is not set
# CONFIG_IPVLAN is not set
# CONFIG_VXLAN is not set
# CONFIG_GENEVE is not set
# CONFIG_BAREUDP is not set
# CONFIG_GTP is not set
# CONFIG_MACSEC is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_TUN is not set
# CONFIG_TUN_VNET_CROSS_LE is not set
# CONFIG_VETH is not set
# CONFIG_NLMON is not set
CONFIG_ETHERNET=y
# CONFIG_NET_VENDOR_ALACRITECH is not set
# CONFIG_ALTERA_TSE is not set
# CONFIG_NET_VENDOR_AMAZON is not set
# CONFIG_NET_VENDOR_AQUANTIA is not set
# CONFIG_NET_VENDOR_ARC is not set
# CONFIG_NET_VENDOR_BROADCOM is not set
CONFIG_NET_VENDOR_CADENCE=y
CONFIG_MACB=y
# CONFIG_NET_VENDOR_CAVIUM is not set
# CONFIG_NET_VENDOR_CIRRUS is not set
# CONFIG_NET_VENDOR_CORTINA is not set
# CONFIG_DM9000 is not set
# CONFIG_DNET is not set
# CONFIG_NET_VENDOR_EZCHIP is not set
# CONFIG_NET_VENDOR_FARADAY is not set
CONFIG_NET_VENDOR_FLEXIBILIS=y
CONFIG_NET_FLX_FRS=y
CONFIG_NET_FLX_FRTC=y
# CONFIG_NET_FLX_MDIO_ITF is not set
# CONFIG_NET_VENDOR_GOOGLE is not set
# CONFIG_NET_VENDOR_HISILICON is not set
# CONFIG_NET_VENDOR_HUAWEI is not set
# CONFIG_NET_VENDOR_INTEL is not set
# CONFIG_NET_VENDOR_LITEX is not set
# CONFIG_NET_VENDOR_MARVELL is not set
# CONFIG_NET_VENDOR_MELLANOX is not set
# CONFIG_NET_VENDOR_MICREL is not set
# CONFIG_NET_VENDOR_MICROCHIP is not set
# CONFIG_NET_VENDOR_MICROSEMI is not set
# CONFIG_NET_VENDOR_MICROSOFT is not set
# CONFIG_NET_VENDOR_NI is not set
# CONFIG_NET_VENDOR_NATSEMI is not set
# CONFIG_NET_VENDOR_NETRONOME is not set
# CONFIG_ETHOC is not set
# CONFIG_NET_VENDOR_PENSANDO is not set
# CONFIG_NET_VENDOR_QUALCOMM is not set
# CONFIG_NET_VENDOR_RENESAS is not set
# CONFIG_NET_VENDOR_ROCKER is not set
# CONFIG_NET_VENDOR_SAMSUNG is not set
CONFIG_NET_VENDOR_SCLE=y
CONFIG_MACIP_ANY=y
CONFIG_MACIP=y
# CONFIG_MACIP_NEW is not set
# CONFIG_NET_VENDOR_SEEQ is not set
# CONFIG_NET_VENDOR_SOLARFLARE is not set
# CONFIG_NET_VENDOR_SMSC is not set
# CONFIG_NET_VENDOR_SOCIONEXT is not set
# CONFIG_NET_VENDOR_STMICRO is not set
# CONFIG_NET_VENDOR_SYNOPSYS is not set
# CONFIG_NET_VENDOR_VIA is not set
# CONFIG_NET_VENDOR_WIZNET is not set
# CONFIG_NET_VENDOR_XILINX is not set
CONFIG_PHYLINK=y
CONFIG_PHYLIB=y
CONFIG_SWPHY=y
CONFIG_FIXED_PHY=y
CONFIG_SFP=y
#
# MII PHY device drivers
#
# CONFIG_AMD_PHY is not set
# CONFIG_ADIN_PHY is not set
# CONFIG_AQUANTIA_PHY is not set
# CONFIG_AX88796B_PHY is not set
# CONFIG_BROADCOM_PHY is not set
# CONFIG_BCM54140_PHY is not set
# CONFIG_BCM7XXX_PHY is not set
# CONFIG_BCM84881_PHY is not set
# CONFIG_BCM87XX_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_CORTINA_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_ICPLUS_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_INTEL_XWAY_PHY is not set
# CONFIG_LSI_ET1011C_PHY is not set
CONFIG_MARVELL_PHY=y
# CONFIG_MARVELL_10G_PHY is not set
# CONFIG_MARVELL_88X2222_PHY is not set
# CONFIG_MAXLINEAR_GPHY is not set
# CONFIG_MEDIATEK_GE_PHY is not set
# CONFIG_MICREL_PHY is not set
# CONFIG_MICROCHIP_PHY is not set
# CONFIG_MICROCHIP_T1_PHY is not set
# CONFIG_MICROSEMI_PHY is not set
# CONFIG_MOTORCOMM_PHY is not set
# CONFIG_NATIONAL_PHY is not set
# CONFIG_NXP_C45_TJA11XX_PHY is not set
# CONFIG_QSEMI_PHY is not set
# CONFIG_REALTEK_PHY is not set
# CONFIG_RENESAS_PHY is not set
# CONFIG_ROCKCHIP_PHY is not set
# CONFIG_SMSC_PHY is not set
# CONFIG_STE10XP is not set
# CONFIG_TERANETICS_PHY is not set
# CONFIG_DP83822_PHY is not set
# CONFIG_DP83TC811_PHY is not set
# CONFIG_DP83848_PHY is not set
# CONFIG_DP83867_PHY is not set
# CONFIG_DP83869_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_XILINX_GMII2RGMII is not set
# CONFIG_MICREL_KS8995MA is not set
CONFIG_MDIO_DEVICE=y
CONFIG_MDIO_BUS=y
CONFIG_FWNODE_MDIO=y
CONFIG_OF_MDIO=y
CONFIG_MDIO_DEVRES=y
# CONFIG_MDIO_BITBANG is not set
# CONFIG_MDIO_BCM_UNIMAC is not set
# CONFIG_MDIO_HISI_FEMAC is not set
CONFIG_MDIO_I2C=y
# CONFIG_MDIO_MSCC_MIIM is not set
# CONFIG_MDIO_IPQ4019 is not set
# CONFIG_MDIO_IPQ8064 is not set
#
# MDIO Multiplexers
#
# CONFIG_MDIO_BUS_MUX_GPIO is not set
# CONFIG_MDIO_BUS_MUX_MULTIPLEXER is not set
# CONFIG_MDIO_BUS_MUX_MMIOREG is not set
#
# PCS device drivers
#
# CONFIG_PCS_XPCS is not set
# end of PCS device drivers
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
#
# Host-side USB support is needed for USB Network Adapter support
#
# CONFIG_WLAN is not set
# CONFIG_WAN is not set
#
# Wireless WAN
#
# CONFIG_WWAN is not set
# end of Wireless WAN
# CONFIG_NETDEVSIM is not set
# CONFIG_NET_FAILOVER is not set
# CONFIG_ISDN is not set
#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=y
# CONFIG_INPUT_SPARSEKMAP is not set
# CONFIG_INPUT_MATRIXKMAP is not set
#
# Userland interfaces
#
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
# CONFIG_INPUT_KEYBOARD is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
# CONFIG_RMI4_CORE is not set
#
# Hardware I/O ports
#
# CONFIG_SERIO is not set
# CONFIG_GAMEPORT is not set
# end of Hardware I/O ports
# end of Input device support
#
# Character devices
#
CONFIG_TTY=y
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
# CONFIG_UNIX98_PTYS is not set
# CONFIG_LEGACY_PTYS is not set
# CONFIG_LDISC_AUTOLOAD is not set
#
# Serial drivers
#
CONFIG_SERIAL_EARLYCON=y
# CONFIG_SERIAL_8250 is not set
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_AMBA_PL010 is not set
# CONFIG_SERIAL_AMBA_PL011 is not set
# CONFIG_SERIAL_EARLYCON_ARM_SEMIHOST is not set
# CONFIG_SERIAL_MAX3100 is not set
# CONFIG_SERIAL_MAX310X is not set
# CONFIG_SERIAL_UARTLITE is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_SIFIVE is not set
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_SC16IS7XX is not set
# CONFIG_SERIAL_BCM63XX is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
CONFIG_SERIAL_XILINX_PS_UART=y
CONFIG_SERIAL_XILINX_PS_UART_CONSOLE=y
# CONFIG_SERIAL_ARC is not set
# CONFIG_SERIAL_FSL_LPUART is not set
# CONFIG_SERIAL_FSL_LINFLEXUART is not set
# CONFIG_SERIAL_CONEXANT_DIGICOLOR is not set
# CONFIG_SERIAL_ST_ASC is not set
# CONFIG_SERIAL_SPRD is not set
# end of Serial drivers
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_N_GSM is not set
# CONFIG_NULL_TTY is not set
# CONFIG_HVC_DCC is not set
# CONFIG_SERIAL_DEV_BUS is not set
# CONFIG_TTY_PRINTK is not set
# CONFIG_VIRTIO_CONSOLE is not set
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
# CONFIG_HW_RANDOM_BA431 is not set
# CONFIG_HW_RANDOM_CCTRNG is not set
# CONFIG_HW_RANDOM_XIPHERA is not set
CONFIG_DEVMEM=y
CONFIG_TCG_TPM=y
CONFIG_HW_RANDOM_TPM=y
CONFIG_TCG_TIS_CORE=y
# CONFIG_TCG_TIS is not set
CONFIG_TCG_TIS_SPI=y
# CONFIG_TCG_TIS_SPI_CR50 is not set
# CONFIG_TCG_TIS_I2C_CR50 is not set
# CONFIG_TCG_TIS_I2C_ATMEL is not set
# CONFIG_TCG_TIS_I2C_INFINEON is not set
# CONFIG_TCG_TIS_I2C_NUVOTON is not set
# CONFIG_TCG_ATMEL is not set
# CONFIG_TCG_VTPM_PROXY is not set
# CONFIG_TCG_TIS_ST33ZP24_I2C is not set
# CONFIG_TCG_TIS_ST33ZP24_SPI is not set
# CONFIG_XILLYBUS is not set
# CONFIG_RANDOM_TRUST_BOOTLOADER is not set
# end of Character devices
#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_MUX=y
#
# Multiplexer I2C Chip support
#
CONFIG_I2C_ARB_GPIO_CHALLENGE=y
# CONFIG_I2C_MUX_GPIO is not set
# CONFIG_I2C_MUX_GPMUX is not set
# CONFIG_I2C_MUX_LTC4306 is not set
# CONFIG_I2C_MUX_PCA9541 is not set
# CONFIG_I2C_MUX_PCA954x is not set
CONFIG_I2C_MUX_PINCTRL=y
CONFIG_I2C_MUX_REG=y
# CONFIG_I2C_DEMUX_PINCTRL is not set
# CONFIG_I2C_MUX_MLXCPLD is not set
# end of Multiplexer I2C Chip support
# CONFIG_I2C_HELPER_AUTO is not set
# CONFIG_I2C_SMBUS is not set
#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set
# end of I2C Algorithms
#
# I2C Hardware Bus support
#
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
CONFIG_I2C_CADENCE=y
# CONFIG_I2C_CBUS_GPIO is not set
# CONFIG_I2C_DESIGNWARE_PLATFORM is not set
# CONFIG_I2C_EMEV2 is not set
# CONFIG_I2C_GPIO is not set
# CONFIG_I2C_NOMADIK is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_RK3X is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_XILINX is not set
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_TAOS_EVM is not set
#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_VIRTIO is not set
# end of I2C Hardware Bus support
# CONFIG_I2C_SLAVE is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# end of I2C support
# CONFIG_I3C is not set
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y
CONFIG_SPI_MEM=y
#
# SPI Master Controller Drivers
#
# CONFIG_SPI_ALTERA is not set
# CONFIG_SPI_AXI_SPI_ENGINE is not set
# CONFIG_SPI_BITBANG is not set
# CONFIG_SPI_CADENCE is not set
# CONFIG_SPI_CADENCE_QUADSPI is not set
# CONFIG_SPI_DESIGNWARE is not set
# CONFIG_SPI_NXP_FLEXSPI is not set
# CONFIG_SPI_GPIO is not set
# CONFIG_SPI_FSL_SPI is not set
# CONFIG_SPI_OC_TINY is not set
# CONFIG_SPI_PL022 is not set
# CONFIG_SPI_ROCKCHIP is not set
# CONFIG_SPI_SC18IS602 is not set
# CONFIG_SPI_SIFIVE is not set
# CONFIG_SPI_MXIC is not set
# CONFIG_SPI_XCOMM is not set
# CONFIG_SPI_XILINX is not set
# CONFIG_SPI_ZYNQ_QSPI is not set
# CONFIG_SPI_ZYNQMP_GQSPI is not set
# CONFIG_SPI_AMD is not set
#
# SPI Multiplexer support
#
# CONFIG_SPI_MUX is not set
#
# SPI Protocol Masters
#
CONFIG_SPI_SPIDEV=y
# CONFIG_SPI_TLE62X0 is not set
# CONFIG_SPI_SLAVE is not set
CONFIG_SPI_DYNAMIC=y
# CONFIG_SPMI is not set
# CONFIG_HSI is not set
# CONFIG_PPS is not set
#
# PTP clock support
#
# CONFIG_PTP_1588_CLOCK is not set
CONFIG_PTP_1588_CLOCK_OPTIONAL=y
#
# Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks.
#
# end of PTP clock support
CONFIG_PINCTRL=y
CONFIG_PINMUX=y
CONFIG_PINCONF=y
CONFIG_GENERIC_PINCONF=y
# CONFIG_DEBUG_PINCTRL is not set
# CONFIG_PINCTRL_MCP23S08 is not set
# CONFIG_PINCTRL_SINGLE is not set
# CONFIG_PINCTRL_SX150X is not set
# CONFIG_PINCTRL_STMFX is not set
CONFIG_PINCTRL_ZYNQ=y
# CONFIG_PINCTRL_OCELOT is not set
# CONFIG_PINCTRL_MICROCHIP_SGPIO is not set
#
# Renesas pinctrl drivers
#
# end of Renesas pinctrl drivers
CONFIG_ARCH_HAVE_CUSTOM_GPIO_H=y
CONFIG_GPIOLIB=y
CONFIG_GPIOLIB_FASTPATH_LIMIT=512
CONFIG_OF_GPIO=y
CONFIG_GPIOLIB_IRQCHIP=y
# CONFIG_DEBUG_GPIO is not set
# CONFIG_GPIO_SYSFS is not set
# CONFIG_GPIO_CDEV is not set
#
# Memory mapped GPIO drivers
#
# CONFIG_GPIO_74XX_MMIO is not set
# CONFIG_GPIO_ALTERA is not set
# CONFIG_GPIO_CADENCE is not set
# CONFIG_GPIO_DWAPB is not set
# CONFIG_GPIO_FTGPIO010 is not set
# CONFIG_GPIO_GENERIC_PLATFORM is not set
# CONFIG_GPIO_GRGPIO is not set
# CONFIG_GPIO_HLWD is not set
# CONFIG_GPIO_LOGICVC is not set
# CONFIG_GPIO_MB86S7X is not set
# CONFIG_GPIO_MPC8XXX is not set
# CONFIG_GPIO_PL061 is not set
# CONFIG_GPIO_SAMA5D2_PIOBU is not set
# CONFIG_GPIO_SIFIVE is not set
# CONFIG_GPIO_SYSCON is not set
# CONFIG_GPIO_XILINX is not set
# CONFIG_GPIO_ZEVIO is not set
CONFIG_GPIO_ZYNQ=y
# CONFIG_GPIO_AMD_FCH is not set
# end of Memory mapped GPIO drivers
#
# I2C GPIO expanders
#
# CONFIG_GPIO_ADP5588 is not set
# CONFIG_GPIO_ADNP is not set
# CONFIG_GPIO_GW_PLD is not set
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCA9570 is not set
# CONFIG_GPIO_PCF857X is not set
# CONFIG_GPIO_TPIC2810 is not set
# end of I2C GPIO expanders
#
# MFD GPIO expanders
#
# CONFIG_HTC_EGPIO is not set
# end of MFD GPIO expanders
#
# SPI GPIO expanders
#
# CONFIG_GPIO_74X164 is not set
# CONFIG_GPIO_MAX3191X is not set
# CONFIG_GPIO_MAX7301 is not set
# CONFIG_GPIO_MC33880 is not set
# CONFIG_GPIO_PISOSR is not set
# CONFIG_GPIO_XRA1403 is not set
# end of SPI GPIO expanders
#
# Virtual GPIO drivers
#
# CONFIG_GPIO_AGGREGATOR is not set
# CONFIG_GPIO_MOCKUP is not set
# end of Virtual GPIO drivers
# CONFIG_W1 is not set
CONFIG_POWER_RESET=y
# CONFIG_POWER_RESET_BRCMKONA is not set
# CONFIG_POWER_RESET_BRCMSTB is not set
# CONFIG_POWER_RESET_GPIO is not set
# CONFIG_POWER_RESET_GPIO_RESTART is not set
# CONFIG_POWER_RESET_LTC2952 is not set
# CONFIG_POWER_RESET_RESTART is not set
# CONFIG_POWER_RESET_VERSATILE is not set
CONFIG_POWER_RESET_SYSCON=y
# CONFIG_POWER_RESET_SYSCON_POWEROFF is not set
# CONFIG_SYSCON_REBOOT_MODE is not set
# CONFIG_NVMEM_REBOOT_MODE is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_GENERIC_ADC_BATTERY is not set
# CONFIG_TEST_POWER is not set
# CONFIG_CHARGER_ADP5061 is not set
# CONFIG_BATTERY_CW2015 is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2781 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_SBS is not set
# CONFIG_CHARGER_SBS is not set
# CONFIG_MANAGER_SBS is not set
# CONFIG_BATTERY_BQ27XXX is not set
# CONFIG_BATTERY_MAX17040 is not set
# CONFIG_BATTERY_MAX17042 is not set
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_LP8727 is not set
# CONFIG_CHARGER_GPIO is not set
# CONFIG_CHARGER_LT3651 is not set
# CONFIG_CHARGER_LTC4162L is not set
# CONFIG_CHARGER_DETECTOR_MAX14656 is not set
# CONFIG_CHARGER_BQ2415X is not set
# CONFIG_CHARGER_BQ24257 is not set
# CONFIG_CHARGER_BQ24735 is not set
# CONFIG_CHARGER_BQ2515X is not set
# CONFIG_CHARGER_BQ25890 is not set
# CONFIG_CHARGER_BQ25980 is not set
# CONFIG_CHARGER_BQ256XX is not set
# CONFIG_BATTERY_GAUGE_LTC2941 is not set
# CONFIG_BATTERY_GOLDFISH is not set
# CONFIG_BATTERY_RT5033 is not set
# CONFIG_CHARGER_RT9455 is not set
# CONFIG_CHARGER_BD99954 is not set
# CONFIG_HWMON is not set
CONFIG_THERMAL=y
# CONFIG_THERMAL_NETLINK is not set
# CONFIG_THERMAL_STATISTICS is not set
CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS=0
# CONFIG_THERMAL_OF is not set
# CONFIG_THERMAL_WRITABLE_TRIPS is not set
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 is not set
CONFIG_THERMAL_GOV_STEP_WISE=y
# CONFIG_THERMAL_GOV_BANG_BANG is not set
# CONFIG_THERMAL_GOV_USER_SPACE is not set
# CONFIG_THERMAL_EMULATION is not set
# CONFIG_THERMAL_MMIO is not set
# CONFIG_GENERIC_ADC_THERMAL is not set
CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_CORE=y
CONFIG_WATCHDOG_NOWAYOUT=y
# CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED is not set
CONFIG_WATCHDOG_OPEN_TIMEOUT=0
# CONFIG_WATCHDOG_SYSFS is not set
# CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT is not set
#
# Watchdog Pretimeout Governors
#
# CONFIG_WATCHDOG_PRETIMEOUT_GOV is not set
#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_GPIO_WATCHDOG is not set
# CONFIG_XILINX_WATCHDOG is not set
# CONFIG_ZIIRAVE_WATCHDOG is not set
CONFIG_ARM_SP805_WATCHDOG=y
CONFIG_CADENCE_WATCHDOG=y
# CONFIG_FTWDT010_WATCHDOG is not set
# CONFIG_DW_WATCHDOG is not set
# CONFIG_MAX63XX_WATCHDOG is not set
# CONFIG_ARM_SMC_WATCHDOG is not set
# CONFIG_MEN_A21_WDT is not set
CONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not set
CONFIG_BCMA_POSSIBLE=y
# CONFIG_BCMA is not set
#
# Multifunction device drivers
#
# CONFIG_MFD_ACT8945A is not set
# CONFIG_MFD_AS3711 is not set
# CONFIG_MFD_AS3722 is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_AAT2870_CORE is not set
# CONFIG_MFD_ATMEL_FLEXCOM is not set
# CONFIG_MFD_ATMEL_HLCDC is not set
# CONFIG_MFD_BCM590XX is not set
# CONFIG_MFD_BD9571MWV is not set
# CONFIG_MFD_AXP20X_I2C is not set
# CONFIG_MFD_MADERA is not set
# CONFIG_MFD_ASIC3 is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_MFD_DA9052_SPI is not set
# CONFIG_MFD_DA9052_I2C is not set
# CONFIG_MFD_DA9055 is not set
# CONFIG_MFD_DA9062 is not set
# CONFIG_MFD_DA9063 is not set
# CONFIG_MFD_DA9150 is not set
# CONFIG_MFD_GATEWORKS_GSC is not set
# CONFIG_MFD_MC13XXX_SPI is not set
# CONFIG_MFD_MC13XXX_I2C is not set
# CONFIG_MFD_MP2629 is not set
# CONFIG_MFD_HI6421_PMIC is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_HTC_I2CPLD is not set
# CONFIG_MFD_IQS62X is not set
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not set
# CONFIG_MFD_88PM805 is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_MAX14577 is not set
# CONFIG_MFD_MAX77620 is not set
# CONFIG_MFD_MAX77650 is not set
# CONFIG_MFD_MAX77686 is not set
# CONFIG_MFD_MAX77693 is not set
# CONFIG_MFD_MAX77843 is not set
# CONFIG_MFD_MAX8907 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8997 is not set
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_MT6360 is not set
# CONFIG_MFD_MT6397 is not set
# CONFIG_MFD_MENF21BMC is not set
# CONFIG_EZX_PCAP is not set
# CONFIG_MFD_CPCAP is not set
# CONFIG_MFD_NTXEC is not set
# CONFIG_MFD_RETU is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_MFD_PM8XXX is not set
# CONFIG_MFD_RT4831 is not set
# CONFIG_MFD_RT5033 is not set
# CONFIG_MFD_RC5T583 is not set
# CONFIG_MFD_RK808 is not set
# CONFIG_MFD_RN5T618 is not set
# CONFIG_MFD_SEC_CORE is not set
# CONFIG_MFD_SI476X_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_MFD_SKY81452 is not set
# CONFIG_MFD_STMPE is not set
CONFIG_MFD_SYSCON=y
# CONFIG_MFD_LP3943 is not set
# CONFIG_MFD_LP8788 is not set
# CONFIG_MFD_TI_LMU is not set
# CONFIG_MFD_PALMAS is not set
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
# CONFIG_MFD_TPS65086 is not set
# CONFIG_MFD_TPS65090 is not set
# CONFIG_MFD_TPS65217 is not set
# CONFIG_MFD_TI_LP873X is not set
# CONFIG_MFD_TI_LP87565 is not set
# CONFIG_MFD_TPS65218 is not set
# CONFIG_MFD_TPS6586X is not set
# CONFIG_MFD_TPS65910 is not set
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_MFD_TPS65912_SPI is not set
# CONFIG_MFD_TPS80031 is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_TWL6040_CORE is not set
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_MFD_LM3533 is not set
# CONFIG_MFD_TC3589X is not set
# CONFIG_MFD_T7L66XB is not set
# CONFIG_MFD_TC6387XB is not set
# CONFIG_MFD_TC6393XB is not set
# CONFIG_MFD_TQMX86 is not set
# CONFIG_MFD_LOCHNAGAR is not set
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_ARIZONA_SPI is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM831X_SPI is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
# CONFIG_MFD_ROHM_BD718XX is not set
# CONFIG_MFD_ROHM_BD70528 is not set
# CONFIG_MFD_ROHM_BD71828 is not set
# CONFIG_MFD_ROHM_BD957XMUF is not set
# CONFIG_MFD_STPMIC1 is not set
# CONFIG_MFD_STMFX is not set
# CONFIG_MFD_ATC260X_I2C is not set
# CONFIG_MFD_QCOM_PM8008 is not set
# CONFIG_MFD_INTEL_M10_BMC is not set
# CONFIG_MFD_RSMU_I2C is not set
# CONFIG_MFD_RSMU_SPI is not set
# end of Multifunction device drivers
# CONFIG_REGULATOR is not set
# CONFIG_RC_CORE is not set
# CONFIG_MEDIA_CEC_SUPPORT is not set
# CONFIG_MEDIA_SUPPORT is not set
#
# Graphics support
#
# CONFIG_IMX_IPUV3_CORE is not set
# CONFIG_DRM is not set
#
# ARM devices
#
# end of ARM devices
#
# Frame buffer Devices
#
# CONFIG_FB is not set
# end of Frame buffer Devices
#
# Backlight & LCD device support
#
# CONFIG_LCD_CLASS_DEVICE is not set
# CONFIG_BACKLIGHT_CLASS_DEVICE is not set
# end of Backlight & LCD device support
#
# Console display driver support
#
CONFIG_DUMMY_CONSOLE=y
# end of Console display driver support
# end of Graphics support
# CONFIG_SOUND is not set
#
# HID support
#
CONFIG_HID=y
# CONFIG_HID_BATTERY_STRENGTH is not set
# CONFIG_HIDRAW is not set
# CONFIG_UHID is not set
# CONFIG_HID_GENERIC is not set
#
# Special HID drivers
#
# CONFIG_HID_A4TECH is not set
# CONFIG_HID_ACRUX is not set
# CONFIG_HID_APPLE is not set
# CONFIG_HID_AUREAL is not set
# CONFIG_HID_BELKIN is not set
# CONFIG_HID_CHERRY is not set
# CONFIG_HID_COUGAR is not set
# CONFIG_HID_MACALLY is not set
# CONFIG_HID_CMEDIA is not set
# CONFIG_HID_CYPRESS is not set
# CONFIG_HID_DRAGONRISE is not set
# CONFIG_HID_EMS_FF is not set
# CONFIG_HID_ELECOM is not set
# CONFIG_HID_EZKEY is not set
# CONFIG_HID_GEMBIRD is not set
# CONFIG_HID_GFRM is not set
# CONFIG_HID_GLORIOUS is not set
# CONFIG_HID_VIVALDI is not set
# CONFIG_HID_KEYTOUCH is not set
# CONFIG_HID_KYE is not set
# CONFIG_HID_WALTOP is not set
# CONFIG_HID_VIEWSONIC is not set
# CONFIG_HID_GYRATION is not set
# CONFIG_HID_ICADE is not set
# CONFIG_HID_ITE is not set
# CONFIG_HID_JABRA is not set
# CONFIG_HID_TWINHAN is not set
# CONFIG_HID_KENSINGTON is not set
# CONFIG_HID_LCPOWER is not set
# CONFIG_HID_LENOVO is not set
# CONFIG_HID_MAGICMOUSE is not set
# CONFIG_HID_MALTRON is not set
# CONFIG_HID_MAYFLASH is not set
# CONFIG_HID_REDRAGON is not set
# CONFIG_HID_MICROSOFT is not set
# CONFIG_HID_MONTEREY is not set
# CONFIG_HID_MULTITOUCH is not set
# CONFIG_HID_NTI is not set
# CONFIG_HID_ORTEK is not set
# CONFIG_HID_PANTHERLORD is not set
# CONFIG_HID_PETALYNX is not set
# CONFIG_HID_PICOLCD is not set
# CONFIG_HID_PLANTRONICS is not set
# CONFIG_HID_PLAYSTATION is not set
# CONFIG_HID_PRIMAX is not set
# CONFIG_HID_SAITEK is not set
# CONFIG_HID_SEMITEK is not set
# CONFIG_HID_SPEEDLINK is not set
# CONFIG_HID_STEAM is not set
# CONFIG_HID_STEELSERIES is not set
# CONFIG_HID_SUNPLUS is not set
# CONFIG_HID_RMI is not set
# CONFIG_HID_GREENASIA is not set
# CONFIG_HID_SMARTJOYPLUS is not set
# CONFIG_HID_TIVO is not set
# CONFIG_HID_TOPSEED is not set
# CONFIG_HID_UDRAW_PS3 is not set
# CONFIG_HID_XINMO is not set
# CONFIG_HID_ZEROPLUS is not set
# CONFIG_HID_ZYDACRON is not set
# CONFIG_HID_SENSOR_HUB is not set
# CONFIG_HID_ALPS is not set
# end of Special HID drivers
#
# I2C HID support
#
# CONFIG_I2C_HID_OF is not set
# CONFIG_I2C_HID_OF_GOODIX is not set
# end of I2C HID support
# end of HID support
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
# CONFIG_USB_SUPPORT is not set
CONFIG_MMC=y
# CONFIG_PWRSEQ_EMMC is not set
# CONFIG_PWRSEQ_SIMPLE is not set
CONFIG_MMC_BLOCK=y
CONFIG_MMC_BLOCK_MINORS=16
# CONFIG_SDIO_UART is not set
# CONFIG_MMC_TEST is not set
#
# MMC/SD/SDIO Host Controller Drivers
#
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_ARMMMCI is not set
CONFIG_MMC_SDHCI=y
CONFIG_MMC_SDHCI_PLTFM=y
CONFIG_MMC_SDHCI_OF_ARASAN=y
# CONFIG_MMC_SDHCI_OF_ASPEED is not set
# CONFIG_MMC_SDHCI_OF_AT91 is not set
# CONFIG_MMC_SDHCI_OF_DWCMSHC is not set
# CONFIG_MMC_SDHCI_CADENCE is not set
# CONFIG_MMC_SDHCI_F_SDH30 is not set
# CONFIG_MMC_SDHCI_MILBEAUT is not set
# CONFIG_MMC_SPI is not set
# CONFIG_MMC_DW is not set
# CONFIG_MMC_USDHI6ROL0 is not set
CONFIG_MMC_CQHCI=y
# CONFIG_MMC_HSQ is not set
# CONFIG_MMC_MTK is not set
# CONFIG_MMC_SDHCI_XENON is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC_ATOMIC_SCRUB=y
CONFIG_EDAC_SUPPORT=y
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
CONFIG_RTC_SYSTOHC=y
CONFIG_RTC_SYSTOHC_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
# CONFIG_RTC_NVMEM is not set
#
# RTC interfaces
#
# CONFIG_RTC_INTF_SYSFS is not set
# CONFIG_RTC_INTF_PROC is not set
# CONFIG_RTC_INTF_DEV is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_ABB5ZES3 is not set
# CONFIG_RTC_DRV_ABEOZ9 is not set
# CONFIG_RTC_DRV_ABX80X is not set
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_HYM8563 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_ISL12022 is not set
# CONFIG_RTC_DRV_ISL12026 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8523 is not set
# CONFIG_RTC_DRV_PCF85063 is not set
CONFIG_RTC_DRV_PCF85363=y
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_BQ32K is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8010 is not set
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set
# CONFIG_RTC_DRV_EM3027 is not set
# CONFIG_RTC_DRV_RV3028 is not set
# CONFIG_RTC_DRV_RV3032 is not set
# CONFIG_RTC_DRV_RV8803 is not set
# CONFIG_RTC_DRV_SD3078 is not set
#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T93 is not set
# CONFIG_RTC_DRV_M41T94 is not set
# CONFIG_RTC_DRV_DS1302 is not set
# CONFIG_RTC_DRV_DS1305 is not set
# CONFIG_RTC_DRV_DS1343 is not set
# CONFIG_RTC_DRV_DS1347 is not set
# CONFIG_RTC_DRV_DS1390 is not set
# CONFIG_RTC_DRV_MAX6916 is not set
# CONFIG_RTC_DRV_R9701 is not set
# CONFIG_RTC_DRV_RX4581 is not set
# CONFIG_RTC_DRV_RS5C348 is not set
# CONFIG_RTC_DRV_MAX6902 is not set
# CONFIG_RTC_DRV_PCF2123 is not set
# CONFIG_RTC_DRV_MCP795 is not set
CONFIG_RTC_I2C_AND_SPI=y
#
# SPI and I2C RTC drivers
#
# CONFIG_RTC_DRV_DS3232 is not set
# CONFIG_RTC_DRV_PCF2127 is not set
# CONFIG_RTC_DRV_RV3029C2 is not set
# CONFIG_RTC_DRV_RX6110 is not set
#
# Platform RTC drivers
#
# CONFIG_RTC_DRV_CMOS is not set
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1685_FAMILY is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_DS2404 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_V3020 is not set
# CONFIG_RTC_DRV_ZYNQMP is not set
#
# on-CPU RTC drivers
#
# CONFIG_RTC_DRV_PL030 is not set
# CONFIG_RTC_DRV_PL031 is not set
# CONFIG_RTC_DRV_CADENCE is not set
# CONFIG_RTC_DRV_FTRTC010 is not set
# CONFIG_RTC_DRV_R7301 is not set
#
# HID Sensor RTC drivers
#
# CONFIG_RTC_DRV_GOLDFISH is not set
CONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set
#
# DMA Devices
#
CONFIG_DMA_ENGINE=y
CONFIG_DMA_OF=y
# CONFIG_ALTERA_MSGDMA is not set
# CONFIG_AMBA_PL08X is not set
# CONFIG_AXI_DMAC is not set
# CONFIG_DW_AXI_DMAC is not set
# CONFIG_FSL_EDMA is not set
# CONFIG_FSL_QDMA is not set
# CONFIG_INTEL_IDMA64 is not set
# CONFIG_NBPFAXI_DMA is not set
CONFIG_PL330_DMA=y
# CONFIG_XILINX_DMA is not set
# CONFIG_XILINX_ZYNQMP_DMA is not set
# CONFIG_XILINX_ZYNQMP_DPDMA is not set
# CONFIG_QCOM_HIDMA_MGMT is not set
# CONFIG_QCOM_HIDMA is not set
# CONFIG_DW_DMAC is not set
# CONFIG_SF_PDMA is not set
#
# DMA Clients
#
# CONFIG_ASYNC_TX_DMA is not set
# CONFIG_DMATEST is not set
#
# DMABUF options
#
# CONFIG_SYNC_FILE is not set
# CONFIG_DMABUF_HEAPS is not set
# end of DMABUF options
# CONFIG_AUXDISPLAY is not set
# CONFIG_UIO is not set
# CONFIG_VFIO is not set
# CONFIG_VIRT_DRIVERS is not set
# CONFIG_VIRTIO_MENU is not set
# CONFIG_VDPA is not set
# CONFIG_VHOST_MENU is not set
#
# Microsoft Hyper-V guest support
#
# end of Microsoft Hyper-V guest support
# CONFIG_GREYBUS is not set
# CONFIG_COMEDI is not set
# CONFIG_STAGING is not set
# CONFIG_GOLDFISH is not set
# CONFIG_CHROME_PLATFORMS is not set
# CONFIG_MELLANOX_PLATFORM is not set
CONFIG_HAVE_CLK=y
CONFIG_HAVE_CLK_PREPARE=y
CONFIG_COMMON_CLK=y
#
# Clock driver for ARM Reference designs
#
CONFIG_ICST=y
CONFIG_CLK_SP810=y
# end of Clock driver for ARM Reference designs
# CONFIG_LMK04832 is not set
# CONFIG_COMMON_CLK_MAX9485 is not set
# CONFIG_COMMON_CLK_SI5341 is not set
# CONFIG_COMMON_CLK_SI5351 is not set
# CONFIG_COMMON_CLK_SI514 is not set
# CONFIG_COMMON_CLK_SI544 is not set
# CONFIG_COMMON_CLK_SI570 is not set
# CONFIG_COMMON_CLK_CDCE706 is not set
# CONFIG_COMMON_CLK_CDCE925 is not set
# CONFIG_COMMON_CLK_CS2000_CP is not set
# CONFIG_COMMON_CLK_AXI_CLKGEN is not set
# CONFIG_COMMON_CLK_VC5 is not set
# CONFIG_COMMON_CLK_FIXED_MMIO is not set
# CONFIG_XILINX_VCU is not set
# CONFIG_HWSPINLOCK is not set
#
# Clock Source drivers
#
CONFIG_TIMER_OF=y
CONFIG_TIMER_PROBE=y
CONFIG_CLKSRC_MMIO=y
CONFIG_CADENCE_TTC_TIMER=y
CONFIG_ARM_ARCH_TIMER=y
CONFIG_ARM_ARCH_TIMER_EVTSTREAM=y
CONFIG_ARM_GLOBAL_TIMER=y
CONFIG_ARM_GT_INITIAL_PRESCALER_VAL=2
CONFIG_CLKSRC_ARM_GLOBAL_TIMER_SCHED_CLOCK=y
CONFIG_MICROCHIP_PIT64B=y
# end of Clock Source drivers
# CONFIG_MAILBOX is not set
# CONFIG_IOMMU_SUPPORT is not set
#
# Remoteproc drivers
#
# CONFIG_REMOTEPROC is not set
# end of Remoteproc drivers
#
# Rpmsg drivers
#
# CONFIG_RPMSG_VIRTIO is not set
# end of Rpmsg drivers
# CONFIG_SOUNDWIRE is not set
#
# SOC (System On Chip) specific Drivers
#
#
# Amlogic SoC drivers
#
# end of Amlogic SoC drivers
#
# Broadcom SoC drivers
#
# CONFIG_SOC_BRCMSTB is not set
# end of Broadcom SoC drivers
#
# NXP/Freescale QorIQ SoC drivers
#
# CONFIG_QUICC_ENGINE is not set
# end of NXP/Freescale QorIQ SoC drivers
#
# i.MX SoC drivers
#
# end of i.MX SoC drivers
#
# Enable LiteX SoC Builder specific drivers
#
# CONFIG_LITEX_SOC_CONTROLLER is not set
# end of Enable LiteX SoC Builder specific drivers
#
# Qualcomm SoC drivers
#
# end of Qualcomm SoC drivers
# CONFIG_SOC_TI is not set
#
# Xilinx SoC drivers
#
# end of Xilinx SoC drivers
# end of SOC (System On Chip) specific Drivers
# CONFIG_PM_DEVFREQ is not set
# CONFIG_EXTCON is not set
# CONFIG_MEMORY is not set
CONFIG_IIO=y
CONFIG_IIO_BUFFER=y
# CONFIG_IIO_BUFFER_CB is not set
# CONFIG_IIO_BUFFER_DMA is not set
# CONFIG_IIO_BUFFER_DMAENGINE is not set
# CONFIG_IIO_BUFFER_HW_CONSUMER is not set
CONFIG_IIO_KFIFO_BUF=y
CONFIG_IIO_TRIGGERED_BUFFER=y
# CONFIG_IIO_CONFIGFS is not set
CONFIG_IIO_TRIGGER=y
CONFIG_IIO_CONSUMERS_PER_TRIGGER=2
# CONFIG_IIO_SW_DEVICE is not set
# CONFIG_IIO_SW_TRIGGER is not set
# CONFIG_IIO_TRIGGERED_EVENT is not set
#
# Accelerometers
#
# CONFIG_ADIS16201 is not set
# CONFIG_ADIS16209 is not set
# CONFIG_ADXL345_I2C is not set
# CONFIG_ADXL345_SPI is not set
# CONFIG_ADXL372_SPI is not set
# CONFIG_ADXL372_I2C is not set
# CONFIG_BMA180 is not set
# CONFIG_BMA220 is not set
# CONFIG_BMA400 is not set
# CONFIG_BMC150_ACCEL is not set
# CONFIG_BMI088_ACCEL is not set
# CONFIG_DA280 is not set
# CONFIG_DA311 is not set
# CONFIG_DMARD06 is not set
# CONFIG_DMARD09 is not set
# CONFIG_DMARD10 is not set
# CONFIG_FXLS8962AF_I2C is not set
# CONFIG_FXLS8962AF_SPI is not set
# CONFIG_IIO_ST_ACCEL_3AXIS is not set
# CONFIG_KXSD9 is not set
# CONFIG_KXCJK1013 is not set
# CONFIG_MC3230 is not set
# CONFIG_MMA7455_I2C is not set
# CONFIG_MMA7455_SPI is not set
# CONFIG_MMA7660 is not set
# CONFIG_MMA8452 is not set
# CONFIG_MMA9551 is not set
# CONFIG_MMA9553 is not set
# CONFIG_MXC4005 is not set
# CONFIG_MXC6255 is not set
# CONFIG_SCA3000 is not set
# CONFIG_SCA3300 is not set
# CONFIG_STK8312 is not set
# CONFIG_STK8BA50 is not set
# end of Accelerometers
#
# Analog to digital converters
#
# CONFIG_AD7091R5 is not set
# CONFIG_AD7124 is not set
# CONFIG_AD7192 is not set
# CONFIG_AD7266 is not set
# CONFIG_AD7291 is not set
# CONFIG_AD7292 is not set
# CONFIG_AD7298 is not set
# CONFIG_AD7476 is not set
# CONFIG_AD7606_IFACE_PARALLEL is not set
# CONFIG_AD7606_IFACE_SPI is not set
# CONFIG_AD7766 is not set
# CONFIG_AD7768_1 is not set
# CONFIG_AD7780 is not set
# CONFIG_AD7791 is not set
# CONFIG_AD7793 is not set
# CONFIG_AD7887 is not set
# CONFIG_AD7923 is not set
# CONFIG_AD7949 is not set
# CONFIG_AD799X is not set
# CONFIG_ADI_AXI_ADC is not set
# CONFIG_ENVELOPE_DETECTOR is not set
# CONFIG_HI8435 is not set
# CONFIG_HX711 is not set
# CONFIG_INA2XX_ADC is not set
# CONFIG_LTC2471 is not set
# CONFIG_LTC2485 is not set
# CONFIG_LTC2496 is not set
# CONFIG_LTC2497 is not set
# CONFIG_MAX1027 is not set
# CONFIG_MAX11100 is not set
# CONFIG_MAX1118 is not set
# CONFIG_MAX1241 is not set
# CONFIG_MAX1363 is not set
# CONFIG_MAX9611 is not set
# CONFIG_MCP320X is not set
# CONFIG_MCP3422 is not set
# CONFIG_MCP3911 is not set
# CONFIG_NAU7802 is not set
# CONFIG_SD_ADC_MODULATOR is not set
# CONFIG_TI_ADC081C is not set
# CONFIG_TI_ADC0832 is not set
# CONFIG_TI_ADC084S021 is not set
# CONFIG_TI_ADC12138 is not set
# CONFIG_TI_ADC108S102 is not set
# CONFIG_TI_ADC128S052 is not set
# CONFIG_TI_ADC161S626 is not set
# CONFIG_TI_ADS1015 is not set
# CONFIG_TI_ADS7950 is not set
# CONFIG_TI_ADS8344 is not set
# CONFIG_TI_ADS8688 is not set
# CONFIG_TI_ADS124S08 is not set
# CONFIG_TI_ADS131E08 is not set
# CONFIG_TI_TLC4541 is not set
# CONFIG_TI_TSC2046 is not set
# CONFIG_VF610_ADC is not set
CONFIG_XILINX_XADC=y
# end of Analog to digital converters
#
# Analog to digital and digital to analog converters
#
# end of Analog to digital and digital to analog converters
#
# Analog Front Ends
#
# CONFIG_IIO_RESCALE is not set
# end of Analog Front Ends
#
# Amplifiers
#
# CONFIG_AD8366 is not set
# CONFIG_HMC425 is not set
# end of Amplifiers
#
# Capacitance to digital converters
#
# CONFIG_AD7150 is not set
# end of Capacitance to digital converters
#
# Chemical Sensors
#
# CONFIG_ATLAS_PH_SENSOR is not set
# CONFIG_ATLAS_EZO_SENSOR is not set
# CONFIG_BME680 is not set
# CONFIG_CCS811 is not set
# CONFIG_IAQCORE is not set
# CONFIG_SCD30_CORE is not set
# CONFIG_SENSIRION_SGP30 is not set
# CONFIG_SENSIRION_SGP40 is not set
# CONFIG_SPS30_I2C is not set
# CONFIG_VZ89X is not set
# end of Chemical Sensors
#
# Hid Sensor IIO Common
#
# end of Hid Sensor IIO Common
#
# IIO SCMI Sensors
#
# end of IIO SCMI Sensors
#
# SSP Sensor Common
#
# CONFIG_IIO_SSP_SENSORHUB is not set
# end of SSP Sensor Common
#
# Digital to analog converters
#
# CONFIG_AD5064 is not set
# CONFIG_AD5360 is not set
# CONFIG_AD5380 is not set
# CONFIG_AD5421 is not set
# CONFIG_AD5446 is not set
# CONFIG_AD5449 is not set
# CONFIG_AD5592R is not set
# CONFIG_AD5593R is not set
# CONFIG_AD5504 is not set
# CONFIG_AD5624R_SPI is not set
# CONFIG_AD5686_SPI is not set
# CONFIG_AD5696_I2C is not set
# CONFIG_AD5755 is not set
# CONFIG_AD5758 is not set
# CONFIG_AD5761 is not set
# CONFIG_AD5764 is not set
# CONFIG_AD5766 is not set
# CONFIG_AD5770R is not set
# CONFIG_AD5791 is not set
# CONFIG_AD7303 is not set
# CONFIG_AD8801 is not set
# CONFIG_DPOT_DAC is not set
# CONFIG_DS4424 is not set
# CONFIG_LTC1660 is not set
# CONFIG_LTC2632 is not set
# CONFIG_M62332 is not set
# CONFIG_MAX517 is not set
# CONFIG_MAX5821 is not set
# CONFIG_MCP4725 is not set
# CONFIG_MCP4922 is not set
# CONFIG_TI_DAC082S085 is not set
# CONFIG_TI_DAC5571 is not set
# CONFIG_TI_DAC7311 is not set
# CONFIG_TI_DAC7612 is not set
# CONFIG_VF610_DAC is not set
# end of Digital to analog converters
#
# IIO dummy driver
#
# end of IIO dummy driver
#
# Frequency Synthesizers DDS/PLL
#
#
# Clock Generator/Distribution
#
# CONFIG_AD9523 is not set
# end of Clock Generator/Distribution
#
# Phase-Locked Loop (PLL) frequency synthesizers
#
# CONFIG_ADF4350 is not set
# CONFIG_ADF4371 is not set
# end of Phase-Locked Loop (PLL) frequency synthesizers
# end of Frequency Synthesizers DDS/PLL
#
# Digital gyroscope sensors
#
# CONFIG_ADIS16080 is not set
# CONFIG_ADIS16130 is not set
# CONFIG_ADIS16136 is not set
# CONFIG_ADIS16260 is not set
# CONFIG_ADXRS290 is not set
# CONFIG_ADXRS450 is not set
# CONFIG_BMG160 is not set
# CONFIG_FXAS21002C is not set
# CONFIG_MPU3050_I2C is not set
# CONFIG_IIO_ST_GYRO_3AXIS is not set
# CONFIG_ITG3200 is not set
# end of Digital gyroscope sensors
#
# Health Sensors
#
#
# Heart Rate Monitors
#
# CONFIG_AFE4403 is not set
# CONFIG_AFE4404 is not set
# CONFIG_MAX30100 is not set
# CONFIG_MAX30102 is not set
# end of Heart Rate Monitors
# end of Health Sensors
#
# Humidity sensors
#
# CONFIG_AM2315 is not set
# CONFIG_DHT11 is not set
# CONFIG_HDC100X is not set
# CONFIG_HDC2010 is not set
# CONFIG_HTS221 is not set
# CONFIG_HTU21 is not set
# CONFIG_SI7005 is not set
# CONFIG_SI7020 is not set
# end of Humidity sensors
#
# Inertial measurement units
#
# CONFIG_ADIS16400 is not set
# CONFIG_ADIS16460 is not set
# CONFIG_ADIS16475 is not set
# CONFIG_ADIS16480 is not set
# CONFIG_BMI160_I2C is not set
# CONFIG_BMI160_SPI is not set
# CONFIG_FXOS8700_I2C is not set
# CONFIG_FXOS8700_SPI is not set
# CONFIG_KMX61 is not set
# CONFIG_INV_ICM42600_I2C is not set
# CONFIG_INV_ICM42600_SPI is not set
# CONFIG_INV_MPU6050_I2C is not set
# CONFIG_INV_MPU6050_SPI is not set
# CONFIG_IIO_ST_LSM6DSX is not set
# CONFIG_IIO_ST_LSM9DS0 is not set
# end of Inertial measurement units
#
# Light sensors
#
# CONFIG_ADJD_S311 is not set
# CONFIG_ADUX1020 is not set
# CONFIG_AL3010 is not set
# CONFIG_AL3320A is not set
# CONFIG_APDS9300 is not set
# CONFIG_APDS9960 is not set
# CONFIG_AS73211 is not set
# CONFIG_BH1750 is not set
# CONFIG_BH1780 is not set
# CONFIG_CM32181 is not set
# CONFIG_CM3232 is not set
# CONFIG_CM3323 is not set
# CONFIG_CM3605 is not set
# CONFIG_CM36651 is not set
# CONFIG_GP2AP002 is not set
# CONFIG_GP2AP020A00F is not set
# CONFIG_SENSORS_ISL29018 is not set
# CONFIG_SENSORS_ISL29028 is not set
# CONFIG_ISL29125 is not set
# CONFIG_JSA1212 is not set
# CONFIG_RPR0521 is not set
# CONFIG_LTR501 is not set
# CONFIG_LV0104CS is not set
# CONFIG_MAX44000 is not set
# CONFIG_MAX44009 is not set
# CONFIG_NOA1305 is not set
# CONFIG_OPT3001 is not set
# CONFIG_PA12203001 is not set
# CONFIG_SI1133 is not set
# CONFIG_SI1145 is not set
# CONFIG_STK3310 is not set
# CONFIG_ST_UVIS25 is not set
# CONFIG_TCS3414 is not set
# CONFIG_TCS3472 is not set
# CONFIG_SENSORS_TSL2563 is not set
# CONFIG_TSL2583 is not set
# CONFIG_TSL2591 is not set
# CONFIG_TSL2772 is not set
# CONFIG_TSL4531 is not set
# CONFIG_US5182D is not set
# CONFIG_VCNL4000 is not set
# CONFIG_VCNL4035 is not set
# CONFIG_VEML6030 is not set
# CONFIG_VEML6070 is not set
# CONFIG_VL6180 is not set
# CONFIG_ZOPT2201 is not set
# end of Light sensors
#
# Magnetometer sensors
#
# CONFIG_AK8974 is not set
# CONFIG_AK8975 is not set
# CONFIG_AK09911 is not set
# CONFIG_BMC150_MAGN_I2C is not set
# CONFIG_BMC150_MAGN_SPI is not set
# CONFIG_MAG3110 is not set
# CONFIG_MMC35240 is not set
# CONFIG_IIO_ST_MAGN_3AXIS is not set
# CONFIG_SENSORS_HMC5843_I2C is not set
# CONFIG_SENSORS_HMC5843_SPI is not set
# CONFIG_SENSORS_RM3100_I2C is not set
# CONFIG_SENSORS_RM3100_SPI is not set
# CONFIG_YAMAHA_YAS530 is not set
# end of Magnetometer sensors
#
# Multiplexers
#
# CONFIG_IIO_MUX is not set
# end of Multiplexers
#
# Inclinometer sensors
#
# end of Inclinometer sensors
#
# Triggers - standalone
#
# CONFIG_IIO_INTERRUPT_TRIGGER is not set
# CONFIG_IIO_SYSFS_TRIGGER is not set
# end of Triggers - standalone
#
# Linear and angular position sensors
#
# end of Linear and angular position sensors
#
# Digital potentiometers
#
# CONFIG_AD5110 is not set
# CONFIG_AD5272 is not set
# CONFIG_DS1803 is not set
# CONFIG_MAX5432 is not set
# CONFIG_MAX5481 is not set
# CONFIG_MAX5487 is not set
# CONFIG_MCP4018 is not set
# CONFIG_MCP4131 is not set
# CONFIG_MCP4531 is not set
# CONFIG_MCP41010 is not set
# CONFIG_TPL0102 is not set
# end of Digital potentiometers
#
# Digital potentiostats
#
# CONFIG_LMP91000 is not set
# end of Digital potentiostats
#
# Pressure sensors
#
# CONFIG_ABP060MG is not set
# CONFIG_BMP280 is not set
# CONFIG_DLHL60D is not set
# CONFIG_DPS310 is not set
# CONFIG_HP03 is not set
# CONFIG_ICP10100 is not set
# CONFIG_MPL115_I2C is not set
# CONFIG_MPL115_SPI is not set
# CONFIG_MPL3115 is not set
# CONFIG_MS5611 is not set
# CONFIG_MS5637 is not set
# CONFIG_IIO_ST_PRESS is not set
# CONFIG_T5403 is not set
# CONFIG_HP206C is not set
# CONFIG_ZPA2326 is not set
# end of Pressure sensors
#
# Lightning sensors
#
# CONFIG_AS3935 is not set
# end of Lightning sensors
#
# Proximity and distance sensors
#
# CONFIG_ISL29501 is not set
# CONFIG_LIDAR_LITE_V2 is not set
# CONFIG_MB1232 is not set
# CONFIG_PING is not set
# CONFIG_RFD77402 is not set
# CONFIG_SRF04 is not set
# CONFIG_SX9310 is not set
# CONFIG_SX9500 is not set
# CONFIG_SRF08 is not set
# CONFIG_VCNL3020 is not set
# CONFIG_VL53L0X_I2C is not set
# end of Proximity and distance sensors
#
# Resolver to digital converters
#
# CONFIG_AD2S90 is not set
# CONFIG_AD2S1200 is not set
# end of Resolver to digital converters
#
# Temperature sensors
#
# CONFIG_LTC2983 is not set
# CONFIG_MAXIM_THERMOCOUPLE is not set
# CONFIG_MLX90614 is not set
# CONFIG_MLX90632 is not set
# CONFIG_TMP006 is not set
# CONFIG_TMP007 is not set
# CONFIG_TMP117 is not set
# CONFIG_TSYS01 is not set
# CONFIG_TSYS02D is not set
# CONFIG_MAX31856 is not set
# end of Temperature sensors
# CONFIG_PWM is not set
#
# IRQ chip support
#
CONFIG_IRQCHIP=y
CONFIG_ARM_GIC=y
CONFIG_ARM_GIC_MAX_NR=1
# CONFIG_AL_FIC is not set
# CONFIG_XILINX_INTC is not set
# end of IRQ chip support
# CONFIG_IPACK_BUS is not set
CONFIG_ARCH_HAS_RESET_CONTROLLER=y
CONFIG_RESET_CONTROLLER=y
# CONFIG_RESET_TI_SYSCON is not set
CONFIG_RESET_ZYNQ=y
#
# PHY Subsystem
#
CONFIG_GENERIC_PHY=y
# CONFIG_PHY_CAN_TRANSCEIVER is not set
# CONFIG_BCM_KONA_USB2_PHY is not set
# CONFIG_PHY_CADENCE_TORRENT is not set
# CONFIG_PHY_CADENCE_DPHY is not set
# CONFIG_PHY_CADENCE_SIERRA is not set
# CONFIG_PHY_CADENCE_SALVO is not set
# CONFIG_PHY_FSL_IMX8MQ_USB is not set
# CONFIG_PHY_MIXEL_MIPI_DPHY is not set
# CONFIG_PHY_PXA_28NM_HSIC is not set
# CONFIG_PHY_PXA_28NM_USB2 is not set
# CONFIG_PHY_OCELOT_SERDES is not set
# end of PHY Subsystem
# CONFIG_POWERCAP is not set
# CONFIG_MCB is not set
#
# Performance monitor support
#
# CONFIG_ARM_CCI_PMU is not set
# CONFIG_ARM_CCN is not set
# CONFIG_ARM_PMU is not set
# end of Performance monitor support
# CONFIG_RAS is not set
#
# Android
#
# CONFIG_ANDROID is not set
# end of Android
# CONFIG_DAX is not set
CONFIG_NVMEM=y
CONFIG_NVMEM_SYSFS=y
CONFIG_NVMEM_RMEM=y
#
# HW tracing support
#
# CONFIG_STM is not set
# CONFIG_INTEL_TH is not set
# end of HW tracing support
# CONFIG_FPGA is not set
# CONFIG_FSI is not set
# CONFIG_TEE is not set
# CONFIG_SIOX is not set
# CONFIG_SLIMBUS is not set
# CONFIG_INTERCONNECT is not set
# CONFIG_COUNTER is not set
# CONFIG_MOST is not set
# end of Device Drivers
#
# File systems
#
CONFIG_DCACHE_WORD_ACCESS=y
# CONFIG_VALIDATE_FS_PARSER is not set
CONFIG_FS_IOMAP=y
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not set
CONFIG_EXT4_FS=y
CONFIG_EXT4_USE_FOR_EXT2=y
# CONFIG_EXT4_FS_POSIX_ACL is not set
# CONFIG_EXT4_FS_SECURITY is not set
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
# CONFIG_F2FS_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_EXPORTFS=y
# CONFIG_EXPORTFS_BLOCK_OPS is not set
CONFIG_FILE_LOCKING=y
# CONFIG_FS_ENCRYPTION is not set
# CONFIG_FS_VERITY is not set
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_FANOTIFY is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_FUSE_FS is not set
# CONFIG_OVERLAY_FS is not set
#
# Caches
#
# CONFIG_FSCACHE is not set
# end of Caches
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set
# end of CD-ROM/DVD Filesystems
#
# DOS/FAT/EXFAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_EXFAT_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS3_FS is not set
# end of DOS/FAT/EXFAT/NT Filesystems
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
# CONFIG_PROC_CHILDREN is not set
CONFIG_KERNFS=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
CONFIG_MEMFD_CREATE=y
CONFIG_CONFIGFS_FS=y
# end of Pseudo filesystems
# CONFIG_MISC_FILESYSTEMS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
# CONFIG_NFS_V2 is not set
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
CONFIG_ROOT_NFS=y
# CONFIG_NFS_DISABLE_UDP_SUPPORT is not set
# CONFIG_NFSD is not set
CONFIG_GRACE_PERIOD=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_DEBUG is not set
# CONFIG_CEPH_FS is not set
# CONFIG_CIFS is not set
# CONFIG_SMB_SERVER is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf-8"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_MAC_ROMAN is not set
# CONFIG_NLS_MAC_CELTIC is not set
# CONFIG_NLS_MAC_CENTEURO is not set
# CONFIG_NLS_MAC_CROATIAN is not set
# CONFIG_NLS_MAC_CYRILLIC is not set
# CONFIG_NLS_MAC_GAELIC is not set
# CONFIG_NLS_MAC_GREEK is not set
# CONFIG_NLS_MAC_ICELAND is not set
# CONFIG_NLS_MAC_INUIT is not set
# CONFIG_NLS_MAC_ROMANIAN is not set
# CONFIG_NLS_MAC_TURKISH is not set
CONFIG_NLS_UTF8=y
# CONFIG_DLM is not set
# CONFIG_UNICODE is not set
# end of File systems
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY_DMESG_RESTRICT is not set
CONFIG_PROC_MEM_ALWAYS_FORCE=y
# CONFIG_PROC_MEM_FORCE_PTRACE is not set
# CONFIG_PROC_MEM_NO_FORCE is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
CONFIG_HAVE_HARDENED_USERCOPY_ALLOCATOR=y
# CONFIG_HARDENED_USERCOPY is not set
# CONFIG_FORTIFY_SOURCE is not set
# CONFIG_STATIC_USERMODEHELPER is not set
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_LSM="landlock,lockdown,yama,loadpin,safesetid,integrity,bpf"
#
# Kernel hardening options
#
#
# Memory initialization
#
CONFIG_INIT_STACK_NONE=y
# CONFIG_INIT_ON_ALLOC_DEFAULT_ON is not set
# CONFIG_INIT_ON_FREE_DEFAULT_ON is not set
CONFIG_CC_HAS_ZERO_CALL_USED_REGS=y
# CONFIG_ZERO_CALL_USED_REGS is not set
# end of Memory initialization
# end of Kernel hardening options
# end of Security options
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_SKCIPHER=y
CONFIG_CRYPTO_SKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_RNG_DEFAULT=y
CONFIG_CRYPTO_AKCIPHER2=y
CONFIG_CRYPTO_AKCIPHER=y
CONFIG_CRYPTO_KPP2=y
CONFIG_CRYPTO_KPP=y
CONFIG_CRYPTO_ACOMP2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
CONFIG_CRYPTO_USER=y
CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
CONFIG_CRYPTO_GF128MUL=y
CONFIG_CRYPTO_NULL=y
CONFIG_CRYPTO_NULL2=y
# CONFIG_CRYPTO_PCRYPT is not set
CONFIG_CRYPTO_CRYPTD=y
CONFIG_CRYPTO_AUTHENC=y
# CONFIG_CRYPTO_TEST is not set
CONFIG_CRYPTO_ENGINE=y
#
# Public-key cryptography
#
CONFIG_CRYPTO_RSA=y
# CONFIG_CRYPTO_DH is not set
CONFIG_CRYPTO_ECC=y
CONFIG_CRYPTO_ECDH=y
# CONFIG_CRYPTO_ECDSA is not set
# CONFIG_CRYPTO_ECRDSA is not set
# CONFIG_CRYPTO_SM2 is not set
# CONFIG_CRYPTO_CURVE25519 is not set
#
# Authenticated Encryption with Associated Data
#
CONFIG_CRYPTO_CCM=y
CONFIG_CRYPTO_GCM=y
# CONFIG_CRYPTO_CHACHA20POLY1305 is not set
# CONFIG_CRYPTO_AEGIS128 is not set
CONFIG_CRYPTO_SEQIV=y
CONFIG_CRYPTO_ECHAINIV=y
#
# Block modes
#
CONFIG_CRYPTO_CBC=y
# CONFIG_CRYPTO_CFB is not set
CONFIG_CRYPTO_CTR=y
# CONFIG_CRYPTO_CTS is not set
CONFIG_CRYPTO_ECB=y
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_OFB is not set
# CONFIG_CRYPTO_PCBC is not set
CONFIG_CRYPTO_XTS=y
# CONFIG_CRYPTO_KEYWRAP is not set
# CONFIG_CRYPTO_ADIANTUM is not set
# CONFIG_CRYPTO_ESSIV is not set
#
# Hash modes
#
CONFIG_CRYPTO_CMAC=y
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_VMAC is not set
#
# Digest
#
CONFIG_CRYPTO_CRC32C=y
# CONFIG_CRYPTO_CRC32 is not set
# CONFIG_CRYPTO_XXHASH is not set
# CONFIG_CRYPTO_BLAKE2B is not set
# CONFIG_CRYPTO_CRCT10DIF is not set
CONFIG_CRYPTO_GHASH=y
# CONFIG_CRYPTO_POLY1305 is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD160 is not set
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=y
# CONFIG_CRYPTO_SHA3 is not set
# CONFIG_CRYPTO_SM3 is not set
# CONFIG_CRYPTO_STREEBOG is not set
# CONFIG_CRYPTO_WP512 is not set
#
# Ciphers
#
CONFIG_CRYPTO_AES=y
# CONFIG_CRYPTO_AES_TI is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_CHACHA20 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_SM4 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
#
# Compression
#
CONFIG_CRYPTO_DEFLATE=y
CONFIG_CRYPTO_LZO=y
# CONFIG_CRYPTO_842 is not set
# CONFIG_CRYPTO_LZ4 is not set
# CONFIG_CRYPTO_LZ4HC is not set
CONFIG_CRYPTO_ZSTD=y
#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
CONFIG_CRYPTO_DRBG_MENU=y
CONFIG_CRYPTO_DRBG_HMAC=y
# CONFIG_CRYPTO_DRBG_HASH is not set
# CONFIG_CRYPTO_DRBG_CTR is not set
CONFIG_CRYPTO_DRBG=y
CONFIG_CRYPTO_JITTERENTROPY=y
CONFIG_CRYPTO_USER_API=y
CONFIG_CRYPTO_USER_API_HASH=y
CONFIG_CRYPTO_USER_API_SKCIPHER=y
CONFIG_CRYPTO_USER_API_RNG=y
# CONFIG_CRYPTO_USER_API_RNG_CAVP is not set
CONFIG_CRYPTO_USER_API_AEAD=y
CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE=y
# CONFIG_CRYPTO_STATS is not set
CONFIG_CRYPTO_HASH_INFO=y
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_ATMEL_ECC is not set
# CONFIG_CRYPTO_DEV_ATMEL_SHA204A is not set
# CONFIG_CRYPTO_DEV_SAFEXCEL is not set
# CONFIG_CRYPTO_DEV_CCREE is not set
CONFIG_CRYPTO_DEV_AMLOGIC_GXL=y
# CONFIG_CRYPTO_DEV_AMLOGIC_GXL_DEBUG is not set
#
# Certificates for signature checking
#
# end of Certificates for signature checking
#
# Library routines
#
# CONFIG_PACKING is not set
CONFIG_BITREVERSE=y
CONFIG_HAVE_ARCH_BITREVERSE=y
CONFIG_GENERIC_STRNCPY_FROM_USER=y
CONFIG_GENERIC_STRNLEN_USER=y
CONFIG_GENERIC_NET_UTILS=y
# CONFIG_CORDIC is not set
# CONFIG_PRIME_NUMBERS is not set
CONFIG_RATIONAL=y
CONFIG_GENERIC_PCI_IOMAP=y
CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y
#
# Crypto library routines
#
CONFIG_CRYPTO_LIB_AES=y
CONFIG_CRYPTO_LIB_BLAKE2S_GENERIC=y
# CONFIG_CRYPTO_LIB_CHACHA is not set
# CONFIG_CRYPTO_LIB_CURVE25519 is not set
CONFIG_CRYPTO_LIB_DES=y
CONFIG_CRYPTO_LIB_POLY1305_RSIZE=9
# CONFIG_CRYPTO_LIB_POLY1305 is not set
# CONFIG_CRYPTO_LIB_CHACHA20POLY1305 is not set
CONFIG_CRYPTO_LIB_SHA256=y
# end of Crypto library routines
CONFIG_LIB_MEMNEQ=y
CONFIG_CRC_CCITT=y
CONFIG_CRC16=y
# CONFIG_CRC_T10DIF is not set
CONFIG_CRC_ITU_T=y
CONFIG_CRC32=y
# CONFIG_CRC32_SELFTEST is not set
CONFIG_CRC32_SLICEBY8=y
# CONFIG_CRC32_SLICEBY4 is not set
# CONFIG_CRC32_SARWATE is not set
# CONFIG_CRC32_BIT is not set
# CONFIG_CRC64 is not set
CONFIG_CRC4=y
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=y
# CONFIG_CRC8 is not set
CONFIG_XXHASH=y
# CONFIG_RANDOM32_SELFTEST is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_LZO_COMPRESS=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_ZSTD_COMPRESS=y
CONFIG_ZSTD_DECOMPRESS=y
CONFIG_XZ_DEC=y
CONFIG_XZ_DEC_X86=y
CONFIG_XZ_DEC_POWERPC=y
CONFIG_XZ_DEC_IA64=y
CONFIG_XZ_DEC_ARM=y
CONFIG_XZ_DEC_ARMTHUMB=y
CONFIG_XZ_DEC_SPARC=y
CONFIG_XZ_DEC_BCJ=y
# CONFIG_XZ_DEC_TEST is not set
CONFIG_GENERIC_ALLOCATOR=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT_MAP=y
CONFIG_HAS_DMA=y
CONFIG_DMA_OPS=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_DMA_DECLARE_COHERENT=y
CONFIG_ARCH_HAS_SETUP_DMA_OPS=y
CONFIG_ARCH_HAS_TEARDOWN_DMA_OPS=y
CONFIG_DMA_NONCOHERENT_MMAP=y
CONFIG_DMA_REMAP=y
CONFIG_DMA_CMA=y
# CONFIG_DMA_PERNUMA_CMA is not set
#
# Default contiguous memory area size:
#
CONFIG_CMA_SIZE_MBYTES=64
CONFIG_CMA_SIZE_SEL_MBYTES=y
# CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set
# CONFIG_CMA_SIZE_SEL_MIN is not set
# CONFIG_CMA_SIZE_SEL_MAX is not set
CONFIG_CMA_ALIGNMENT=8
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_DMA_MAP_BENCHMARK is not set
CONFIG_SGL_ALLOC=y
CONFIG_CPU_RMAP=y
CONFIG_DQL=y
CONFIG_GLOB=y
# CONFIG_GLOB_SELFTEST is not set
CONFIG_NLATTR=y
CONFIG_CLZ_TAB=y
# CONFIG_IRQ_POLL is not set
CONFIG_MPILIB=y
CONFIG_LIBFDT=y
CONFIG_HAVE_GENERIC_VDSO=y
CONFIG_GENERIC_GETTIMEOFDAY=y
CONFIG_GENERIC_VDSO_32=y
CONFIG_GENERIC_CLOCKSOURCE_VDSO=y
CONFIG_SG_POOL=y
CONFIG_SBITMAP=y
# end of Library routines
CONFIG_GENERIC_LIB_DEVMEM_IS_ALLOWED=y
#
# Kernel hacking
#
#
# printk and dmesg options
#
CONFIG_PRINTK_TIME=y
# CONFIG_PRINTK_CALLER is not set
# CONFIG_STACKTRACE_BUILD_ID is not set
CONFIG_CONSOLE_LOGLEVEL_DEFAULT=7
CONFIG_CONSOLE_LOGLEVEL_QUIET=4
CONFIG_MESSAGE_LOGLEVEL_DEFAULT=4
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_DYNAMIC_DEBUG is not set
# CONFIG_DYNAMIC_DEBUG_CORE is not set
CONFIG_SYMBOLIC_ERRNAME=y
CONFIG_DEBUG_BUGVERBOSE=y
# end of printk and dmesg options
CONFIG_AS_HAS_NON_CONST_LEB128=y
#
# Compile-time checks and compiler options
#
# CONFIG_DEBUG_INFO is not set
CONFIG_FRAME_WARN=1024
# CONFIG_STRIP_ASM_SYMS is not set
# CONFIG_READABLE_ASM is not set
# CONFIG_HEADERS_INSTALL is not set
# CONFIG_DEBUG_SECTION_MISMATCH is not set
CONFIG_SECTION_MISMATCH_WARN_ONLY=y
# CONFIG_VMLINUX_MAP is not set
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# end of Compile-time checks and compiler options
#
# Generic Kernel Debugging Instruments
#
CONFIG_MAGIC_SYSRQ=y
CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x1
CONFIG_MAGIC_SYSRQ_SERIAL=y
CONFIG_MAGIC_SYSRQ_SERIAL_SEQUENCE=""
CONFIG_DEBUG_FS=y
CONFIG_DEBUG_FS_ALLOW_ALL=y
# CONFIG_DEBUG_FS_DISALLOW_MOUNT is not set
# CONFIG_DEBUG_FS_ALLOW_NONE is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
# CONFIG_UBSAN is not set
CONFIG_HAVE_KCSAN_COMPILER=y
# end of Generic Kernel Debugging Instruments
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_MISC=y
#
# Memory Debugging
#
# CONFIG_PAGE_EXTENSION is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_PAGE_OWNER is not set
# CONFIG_PAGE_POISONING is not set
# CONFIG_DEBUG_RODATA_TEST is not set
# CONFIG_DEBUG_WX is not set
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_SLUB_STATS is not set
CONFIG_HAVE_DEBUG_KMEMLEAK=y
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_SCHED_STACK_END_CHECK is not set
# CONFIG_DEBUG_VM is not set
CONFIG_ARCH_HAS_DEBUG_VIRTUAL=y
# CONFIG_DEBUG_VIRTUAL is not set
# CONFIG_DEBUG_MEMORY_INIT is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_DEBUG_KMAP_LOCAL is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_HAVE_ARCH_KASAN=y
CONFIG_CC_HAS_KASAN_GENERIC=y
CONFIG_CC_HAS_WORKING_NOSANITIZE_ADDRESS=y
# CONFIG_KASAN is not set
# end of Memory Debugging
# CONFIG_DEBUG_SHIRQ is not set
# CONFIG_DEBUG_IRQ_PIPELINE is not set
# CONFIG_DEBUG_DOVETAIL is not set
#
# Debug Oops, Lockups and Hangs
#
# CONFIG_PANIC_ON_OOPS is not set
CONFIG_PANIC_ON_OOPS_VALUE=0
CONFIG_PANIC_TIMEOUT=0
# CONFIG_SOFTLOCKUP_DETECTOR is not set
# CONFIG_DETECT_HUNG_TASK is not set
# CONFIG_WQ_WATCHDOG is not set
# end of Debug Oops, Lockups and Hangs
#
# Scheduler Debugging
#
# CONFIG_SCHED_DEBUG is not set
# CONFIG_SCHEDSTATS is not set
# end of Scheduler Debugging
# CONFIG_DEBUG_TIMEKEEPING is not set
#
# Lock Debugging (spinlocks, mutexes, etc...)
#
CONFIG_LOCK_DEBUGGING_SUPPORT=y
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_WW_MUTEX_SLOWPATH is not set
# CONFIG_DEBUG_RWSEMS is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_DEBUG_ATOMIC_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_LOCK_TORTURE_TEST is not set
# CONFIG_WW_MUTEX_SELFTEST is not set
# CONFIG_SCF_TORTURE_TEST is not set
# end of Lock Debugging (spinlocks, mutexes, etc...)
# CONFIG_DEBUG_IRQFLAGS is not set
CONFIG_STACKTRACE=y
# CONFIG_WARN_ALL_UNSEEDED_RANDOM is not set
# CONFIG_DEBUG_KOBJECT is not set
#
# Debug kernel data structures
#
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_PLIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_BUG_ON_DATA_CORRUPTION is not set
# end of Debug kernel data structures
# CONFIG_DEBUG_CREDENTIALS is not set
#
# RCU Debugging
#
# CONFIG_RCU_SCALE_TEST is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_REF_SCALE_TEST is not set
CONFIG_RCU_CPU_STALL_TIMEOUT=21
# CONFIG_RCU_TRACE is not set
# CONFIG_RCU_EQS_DEBUG is not set
# end of RCU Debugging
# CONFIG_DEBUG_WQ_FORCE_RR_CPU is not set
# CONFIG_LATENCYTOP is not set
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_DYNAMIC_FTRACE_WITH_REGS=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_HAVE_C_RECORDMCOUNT=y
CONFIG_TRACING_SUPPORT=y
# CONFIG_FTRACE is not set
# CONFIG_SAMPLES is not set
# CONFIG_STRICT_DEVMEM is not set
#
# arm Debugging
#
# CONFIG_ARM_PTDUMP_DEBUGFS is not set
# CONFIG_UNWINDER_FRAME_POINTER is not set
CONFIG_UNWINDER_ARM=y
CONFIG_ARM_UNWIND=y
# CONFIG_DEBUG_USER is not set
CONFIG_DEBUG_LL=y
CONFIG_DEBUG_ZYNQ_UART0=y
# CONFIG_DEBUG_ZYNQ_UART1 is not set
# CONFIG_DEBUG_ICEDCC is not set
# CONFIG_DEBUG_SEMIHOSTING is not set
# CONFIG_DEBUG_LL_UART_8250 is not set
# CONFIG_DEBUG_LL_UART_PL01X is not set
# CONFIG_DEBUG_UART_FLOW_CONTROL is not set
CONFIG_DEBUG_LL_INCLUDE="debug/zynq.S"
# CONFIG_DEBUG_UNCOMPRESS is not set
CONFIG_UNCOMPRESS_INCLUDE="debug/uncompress.h"
# CONFIG_EARLY_PRINTK is not set
# CONFIG_PID_IN_CONTEXTIDR is not set
# CONFIG_CORESIGHT is not set
# end of arm Debugging
#
# Kernel Testing and Coverage
#
# CONFIG_KUNIT is not set
# CONFIG_NOTIFIER_ERROR_INJECTION is not set
# CONFIG_FAULT_INJECTION is not set
CONFIG_ARCH_HAS_KCOV=y
CONFIG_CC_HAS_SANCOV_TRACE_PC=y
# CONFIG_KCOV is not set
# CONFIG_RUNTIME_TESTING_MENU is not set
CONFIG_ARCH_USE_MEMTEST=y
# CONFIG_MEMTEST is not set
# end of Kernel Testing and Coverage
# end of Kernel hacking
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-18 8:50 Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail François Legal
@ 2024-11-18 9:01 ` Jan Kiszka
2024-11-18 10:21 ` François Legal
0 siblings, 1 reply; 23+ messages in thread
From: Jan Kiszka @ 2024-11-18 9:01 UTC (permalink / raw)
To: François Legal, xenomai
On 18.11.24 09:50, François Legal wrote:
> Hello,
>
> running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
>
> I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
>
> Attached is my config.
Can you factor out from it what the SoC is, if you patched the kernel
for it (in the past and now), if you had to adopt Dovetail etc.?
Jan
--
Siemens AG, Technology
Linux Expert Center
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-18 9:01 ` Jan Kiszka
@ 2024-11-18 10:21 ` François Legal
2024-11-18 10:32 ` Florian Bezdeka
0 siblings, 1 reply; 23+ messages in thread
From: François Legal @ 2024-11-18 10:21 UTC (permalink / raw)
To: Jan Kiszka; +Cc: xenomai
Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit:
> On 18.11.24 09:50, François Legal wrote:
> > Hello,
> >
> > running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
> >
> > I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
> >
> > Attached is my config.
>
> Can you factor out from it what the SoC is, if you patched the kernel
> for it (in the past and now), if you had to adopt Dovetail etc.?
>
> Jan
The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
>
> --
> Siemens AG, Technology
> Linux Expert Center
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-18 10:21 ` François Legal
@ 2024-11-18 10:32 ` Florian Bezdeka
2024-11-18 11:18 ` François Legal
0 siblings, 1 reply; 23+ messages in thread
From: Florian Bezdeka @ 2024-11-18 10:32 UTC (permalink / raw)
To: François Legal, Jan Kiszka; +Cc: xenomai
On Mon, 2024-11-18 at 11:21 +0100, François Legal wrote:
> Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit:
>
> > On 18.11.24 09:50, François Legal wrote:
> > > Hello,
> > >
> > > running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
> > >
> > > I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
> > >
> > > Attached is my config.
> >
> > Can you factor out from it what the SoC is, if you patched the kernel
> > for it (in the past and now), if you had to adopt Dovetail etc.?
> >
> > Jan
>
> The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
We had a similar report for the zynq 7020 a couple of days ago.
See [1].
What happens if you disable CONFIG_SMP? (Not that this should be the
final solution, but it might help to track the issue down...)
Florian
[1]
https://lore.kernel.org/xenomai/71139a9c193d776b890f11ebb01ae7a3e9dbd7bb.camel@siemens.com/T/#t
>
> >
> > --
> > Siemens AG, Technology
> > Linux Expert Center
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-18 10:32 ` Florian Bezdeka
@ 2024-11-18 11:18 ` François Legal
2024-11-18 11:37 ` Philippe Gerum
0 siblings, 1 reply; 23+ messages in thread
From: François Legal @ 2024-11-18 11:18 UTC (permalink / raw)
To: Florian Bezdeka; +Cc: Jan Kiszka, xenomai
Le Lundi, Novembre 18, 2024 11:32 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
> On Mon, 2024-11-18 at 11:21 +0100, François Legal wrote:
> > Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit:
> >
> > > On 18.11.24 09:50, François Legal wrote:
> > > > Hello,
> > > >
> > > > running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
> > > >
> > > > I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
> > > >
> > > > Attached is my config.
> > >
> > > Can you factor out from it what the SoC is, if you patched the kernel
> > > for it (in the past and now), if you had to adopt Dovetail etc.?
> > >
> > > Jan
> >
> > The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
>
> We had a similar report for the zynq 7020 a couple of days ago.
> See [1].
>
> What happens if you disable CONFIG_SMP? (Not that this should be the
> final solution, but it might help to track the issue down...)
>
> Florian
>
Disabling config SMP makes my system boot again.
How can I help working this out ?
François
> [1]
> https://lore.kernel.org/xenomai/71139a9c193d776b890f11ebb01ae7a3e9dbd7bb.camel@siemens.com/T/#t
> >
> > >
> > > --
> > > Siemens AG, Technology
> > > Linux Expert Center
>
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-18 11:18 ` François Legal
@ 2024-11-18 11:37 ` Philippe Gerum
2024-11-18 12:06 ` Florian Bezdeka
0 siblings, 1 reply; 23+ messages in thread
From: Philippe Gerum @ 2024-11-18 11:37 UTC (permalink / raw)
To: François Legal; +Cc: Florian Bezdeka, Jan Kiszka, xenomai
François Legal <devel@thom.fr.eu.org> writes:
> Le Lundi, Novembre 18, 2024 11:32 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
>
>> On Mon, 2024-11-18 at 11:21 +0100, François Legal wrote:
>> > Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit:
>> >
>> > > On 18.11.24 09:50, François Legal wrote:
>> > > > Hello,
>> > > >
>> > > > running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
>> > > >
>> > > > I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
>> > > >
>> > > > Attached is my config.
>> > >
>> > > Can you factor out from it what the SoC is, if you patched the kernel
>> > > for it (in the past and now), if you had to adopt Dovetail etc.?
>> > >
>> > > Jan
>> >
>> > The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
>>
>> We had a similar report for the zynq 7020 a couple of days ago.
>> See [1].
>>
>> What happens if you disable CONFIG_SMP? (Not that this should be the
>> final solution, but it might help to track the issue down...)
>>
>> Florian
>>
>
> Disabling config SMP makes my system boot again.
> How can I help working this out ?
>
> François
>
This looks like an issue with the proxy tick device. First thing is to
disable CONFIG_XENOMAI, enabling CONFIG_IRQ_PIPELINE_TORTURE_TEST. If
the kernel still hangs, we may have a hint about the reason
why. Alternatively, you could keep CONFIG_XENOMAI in, booting the kernel
with "xenomai.state=stopped". If no hang occurs at boot anymore, there
may be an issue with proxying the timer device on this SoC.
[1] https://v4.xenomai.org/dovetail/porting/timer/
[2] https://v4.xenomai.org/dovetail/porting/devnotes/#check-that-the-pipeline-torture-tests-pass
--
Philippe.
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-18 11:37 ` Philippe Gerum
@ 2024-11-18 12:06 ` Florian Bezdeka
2024-11-18 13:21 ` François Legal
2024-11-18 13:38 ` François Legal
0 siblings, 2 replies; 23+ messages in thread
From: Florian Bezdeka @ 2024-11-18 12:06 UTC (permalink / raw)
To: Philippe Gerum, François Legal; +Cc: Jan Kiszka, xenomai, 孙涛
[ Updated CC list to merge both mail threads ]
On Mon, 2024-11-18 at 12:37 +0100, Philippe Gerum wrote:
> François Legal <devel@thom.fr.eu.org> writes:
>
> > Le Lundi, Novembre 18, 2024 11:32 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
> >
> > > On Mon, 2024-11-18 at 11:21 +0100, François Legal wrote:
> > > > Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit:
> > > >
> > > > > On 18.11.24 09:50, François Legal wrote:
> > > > > > Hello,
> > > > > >
> > > > > > running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
> > > > > >
> > > > > > I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
> > > > > >
> > > > > > Attached is my config.
> > > > >
> > > > > Can you factor out from it what the SoC is, if you patched the kernel
> > > > > for it (in the past and now), if you had to adopt Dovetail etc.?
> > > > >
> > > > > Jan
> > > >
> > > > The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
> > >
> > > We had a similar report for the zynq 7020 a couple of days ago.
> > > See [1].
> > >
> > > What happens if you disable CONFIG_SMP? (Not that this should be the
> > > final solution, but it might help to track the issue down...)
> > >
> > > Florian
> > >
> >
> > Disabling config SMP makes my system boot again.
> > How can I help working this out ?
> >
> > François
> >
>
> This looks like an issue with the proxy tick device. First thing is to
> disable CONFIG_XENOMAI, enabling CONFIG_IRQ_PIPELINE_TORTURE_TEST. If
> the kernel still hangs, we may have a hint about the reason
> why. Alternatively, you could keep CONFIG_XENOMAI in, booting the kernel
> with "xenomai.state=stopped". If no hang occurs at boot anymore, there
> may be an issue with proxying the timer device on this SoC.
>
> [1] https://v4.xenomai.org/dovetail/porting/timer/
> [2] https://v4.xenomai.org/dovetail/porting/devnotes/#check-that-the-pipeline-torture-tests-pass
>
> --
> Philippe.
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-18 12:06 ` Florian Bezdeka
@ 2024-11-18 13:21 ` François Legal
2024-11-18 13:37 ` Philippe Gerum
2024-11-18 13:38 ` François Legal
1 sibling, 1 reply; 23+ messages in thread
From: François Legal @ 2024-11-18 13:21 UTC (permalink / raw)
To: Florian Bezdeka; +Cc: Philippe Gerum, Jan Kiszka, xenomai, 孙涛
[-- Attachment #1: Type: text/plain, Size: 3000 bytes --]
Le Lundi, Novembre 18, 2024 13:06 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
>
> [ Updated CC list to merge both mail threads ]
>
> On Mon, 2024-11-18 at 12:37 +0100, Philippe Gerum wrote:
> > François Legal <devel@thom.fr.eu.org> writes:
> >
> > > Le Lundi, Novembre 18, 2024 11:32 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
> > >
> > > > On Mon, 2024-11-18 at 11:21 +0100, François Legal wrote:
> > > > > Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit:
> > > > >
> > > > > > On 18.11.24 09:50, François Legal wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > > > running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
> > > > > > >
> > > > > > > I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
> > > > > > >
> > > > > > > Attached is my config.
> > > > > >
> > > > > > Can you factor out from it what the SoC is, if you patched the kernel
> > > > > > for it (in the past and now), if you had to adopt Dovetail etc.?
> > > > > >
> > > > > > Jan
> > > > >
> > > > > The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
> > > >
> > > > We had a similar report for the zynq 7020 a couple of days ago.
> > > > See [1].
> > > >
> > > > What happens if you disable CONFIG_SMP? (Not that this should be the
> > > > final solution, but it might help to track the issue down...)
> > > >
> > > > Florian
> > > >
> > >
> > > Disabling config SMP makes my system boot again.
> > > How can I help working this out ?
> > >
> > > François
> > >
> >
> > This looks like an issue with the proxy tick device. First thing is to
> > disable CONFIG_XENOMAI, enabling CONFIG_IRQ_PIPELINE_TORTURE_TEST. If
> > the kernel still hangs, we may have a hint about the reason
> > why. Alternatively, you could keep CONFIG_XENOMAI in, booting the kernel
> > with "xenomai.state=stopped". If no hang occurs at boot anymore, there
> > may be an issue with proxying the timer device on this SoC.
> >
CONFIG_IRQ_PIPELINE_TORTURE_TEST seems to report OK (attached bootlog CONFIG_IRQ_PIPELINE_TORTURE_TEST.boot
Starting with "xenomai.state=stopped" works (attached boolog xenomai.state-stopped.boot)
Starting up xenomai with coreclk afterwards seem to work and not hang system :
root@Arkens_SV:~# /usr/xenomai/sbin/corectl -start
[ 117.328878] CPU1: proxy tick device registered (333.33MHz)
[ 117.328883] CPU0: proxy tick device registered (333.33MHz)
[ 117.339995] [Xenomai] services started
> > [1] https://v4.xenomai.org/dovetail/porting/timer/
> > [2] https://v4.xenomai.org/dovetail/porting/devnotes/#check-that-the-pipeline-torture-tests-pass
> >
> > --
> > Philippe.
>
[-- Attachment #2: CONFIG_IRQ_PIPELINE_TORTURE_TEST.boot --]
[-- Type: application/octet-stream, Size: 11071 bytes --]
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 5.15.170-01498-g889fd6cd2ca7-dirty (francois@Dev-RSpace) (arm-oe-linux-gnueabi-gcc (GCC) 11.4.0, GNU ld (GNU Binutils) 2.38.20220708) #16 SMP IRQPIPE Mon Nov 18 13:51:27 CET 2024
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt: Machine model: SCLE UCC+T07 CPU Board
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] cma: Reserved 64 MiB at 0x3c000000
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x0000000000000000-0x000000002fffffff]
[ 0.000000] HighMem [mem 0x0000000030000000-0x000000003fffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x000000003fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000003fffffff]
[ 0.000000] percpu: Embedded 9 pages/cpu s14476 r0 d22388 u36864
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 260608
[ 0.000000] Kernel command line: earlyprintk console=ttyPS0,115200n8 root=/dev/nfs
[ 0.000000] Unknown kernel command line parameters "earlyprintk", will be passed to user space.
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 963300K/1048576K available (6144K kernel code, 581K rwdata, 996K rodata, 1024K init, 228K bss, 19740K reserved, 65536K cma-reserved, 196608K highmem)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] slcr mapped to (ptrval)
[ 0.000000] L2C: platform modifies aux control register: 0x02060000 -> 0x02460000
[ 0.000000] L2C: DT/platform modifies aux control register: 0x02060000 -> 0x02460000
[ 0.000000] L2C-310 erratum 769419 enabled
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x46460001
[ 0.000000] IRQ pipeline enabled
[ 0.000000] zynq_clock_init: clkc starts at (ptrval)
[ 0.000000] Zynq clock init
[ 0.000001] sched_clock: 64 bits at 166MHz, resolution 6ns, wraps every 4398046511103ns
[ 0.000024] clocksource: arm_global_timer: freq: 166666665 Hz, mask: 0xffffffffffffffff max_cycles: 0x26703d7dd8, max_idle_ns: 440795208065 ns
[ 0.000059] Switching to timer-based delay loop, resolution 6ns
[ 0.000710] Console: colour dummy device 80x30
[ 0.000784] Calibrating delay loop (skipped), value calculated using timer frequency.. 333.33 BogoMIPS (lpj=1666666)
[ 0.000808] CPU: Testing write buffer coherency: ok
[ 0.000862] CPU0: Spectre v2: using BPIALL workaround
[ 0.000876] pid_max: default: 32768 minimum: 301
[ 0.001032] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.001056] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.001915] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.002701] Setting up static identity map for 0x100000 - 0x10003c
[ 0.002886] rcu: Hierarchical SRCU implementation.
[ 0.003301] smp: Bringing up secondary CPUs ...
[ 0.004082] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.004100] CPU1: Spectre v2: using BPIALL workaround
[ 0.004240] smp: Brought up 1 node, 2 CPUs
[ 0.004268] SMP: Total of 2 processors activated (666.66 BogoMIPS).
[ 0.004283] CPU: All CPU(s) started in SVC mode.
[ 0.004844] devtmpfs: initialized
[ 0.012671] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.012818] clocksource: jiffies: freq: 0 Hz, mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.012850] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[ 0.016642] pinctrl core: initialized pinctrl subsystem
[ 0.017547] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.021004] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.022010] thermal_sys: Registered thermal governor 'step_wise'
[ 0.032977] amba f8801000.etb: Fixing up cyclic dependency with replicator
[ 0.033338] amba f8803000.tpiu: Fixing up cyclic dependency with replicator
[ 0.033751] amba f8804000.funnel: Fixing up cyclic dependency with replicator
[ 0.034107] amba f889c000.ptm: Fixing up cyclic dependency with f8804000.funnel
[ 0.034459] amba f889d000.ptm: Fixing up cyclic dependency with f8804000.funnel
[ 0.047402] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.047427] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.048022] zynq-pinctrl 700.pinctrl: zynq pinctrl initialized
[ 0.048901] e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 35, base_baud = 6249999) is a xuartps
[ 0.544779] printk: console [ttyPS0] enabled
[ 0.549646] xuartps e0001000.serial: uart_add_one_port() failed; err=-22
[ 0.556447] xuartps: probe of e0001000.serial failed with error -22
[ 0.570632] cryptd: max_cpu_qlen set to 1000
[ 0.579163] SCSI subsystem initialized
[ 0.584089] clocksource: Switched to clocksource arm_global_timer
[ 0.597937] NET: Registered PF_INET protocol family
[ 0.603103] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[ 0.611588] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[ 0.619976] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.627758] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[ 0.635599] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.642966] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.649408] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.656090] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.663364] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.669756] RPC: Registered named UNIX socket transport module.
[ 0.675714] RPC: Registered udp transport module.
[ 0.680426] RPC: Registered tcp transport module.
[ 0.685127] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.692555] workingset: timestamp_bits=30 max_order=18 bucket_order=0
[ 0.815445] NET: Registered PF_ALG protocol family
[ 0.820400] bounce: pool size: 64 pages
[ 0.824256] io scheduler mq-deadline registered
[ 0.832521] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.839225] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.856744] brd: module loaded
[ 0.880709] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 38 (80:1f:12:f8:48:87)
[ 0.892573] flx_frtc 41040000.frtc: Component Local NCO IO remapped to: (ptrval)
[ 0.901417] macip_mdio 4000514c.mdio: Successfully probed SCLE MACIP MDIO bus !
[ 0.909127] macip 40004000.macip: SCLE MACIP using OCM memory for BDs
[ 0.916055] [macip_set_features:1698] TODO
[ 0.920568] macip 40004000.macip eth1: Scle MAC rev 0x00000002 at 0x40004000 irq 62-63L (80:1f:12:f8:22:88). Ring length : 128/128
[ 0.932337] macip 40004000.macip eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=fixed-0:00, irq=-1)
[ 0.942631] i2c_dev: i2c /dev entries driver
[ 0.947392] cdns-i2c e0004000.i2c: 100 kHz mmio e0004000 irq 32
[ 0.954799] at24 1-0052: 256 byte 24c02 EEPROM, writable, 16 bytes/write
[ 0.962268] at24 1-0053: 256 byte 24c02 EEPROM, writable, 16 bytes/write
[ 0.969728] at24 1-0054: 256 byte 24c02 EEPROM, writable, 16 bytes/write
[ 0.976504] cdns-i2c e0005000.i2c: 100 kHz mmio e0005000 irq 33
[ 0.983237] zynq-pinctrl 700.pinctrl: invalid function i2c0_emio in map table
[ 0.990572] zynq-pinctrl 700.pinctrl: invalid function i2c0_emio in map table
[ 0.997955] i2c i2c-0: Added multiplexed i2c bus 2
[ 1.003018] i2c i2c-0: Added multiplexed i2c bus 3
[ 1.008395] i2c i2c-3: Added multiplexed i2c bus 4
[ 1.013454] i2c i2c-3: Added multiplexed i2c bus 5
[ 1.019086] cdns-wdt f8005000.watchdog: Xilinx Watchdog Timer with timeout 10s, nowayout
[ 1.027484] sdhci: Secure Digital Host Controller Interface driver
[ 1.033667] sdhci: Copyright(c) Pierre Ossman
[ 1.038013] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.044979] clocksource: ttc_clocksource: freq: 54253 Hz, mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
[ 1.055613] timer #0 at (ptrval), irq=52
[ 1.062115] NET: Registered PF_PACKET protocol family
[ 1.067216] 8021q: 802.1Q VLAN Support v1.8
[ 1.071539] Registering SWP/SWPB emulation handler
[ 1.076420] Starting IRQ pipeline tests...
[ 1.076430] IRQ pipeline: high-priority torture stage added.
[ 1.084089] mmc0: SDHCI controller on e0100000.mmc [e0100000.mmc] using ADMA
[ 1.086184] irq_pipeline-torture: CPU0 initiates stop_machine()
[ 1.099159] irq_pipeline-torture: CPU1 responds to stop_machine()
[ 1.099238] irq_pipeline-torture: CPU0 calls function on remote(s)
[ 1.111522] irq_pipeline-torture: CPU1 handles remote function call
[ 1.111634] CPU0: proxy tick device registered (333.33MHz)
[ 1.111637] CPU1: proxy tick device registered (333.33MHz)
[ 1.128953] irq_pipeline-torture: CPU0: irq_work handled
[ 1.134292] irq_pipeline-torture: CPU0: in-band->in-band irq_work trigger works
[ 1.141610] irq_pipeline-torture: CPU0: stage escalation request works
[ 1.141619] irq_pipeline-torture: CPU0: irq_work handled
[ 1.153456] irq_pipeline-torture: CPU0: oob->in-band irq_work trigger works
[ 1.262818] mmc0: new high speed MMC card at address 0001
[ 1.268858] mmcblk0: mmc0:0001 008GB0 7.28 GiB
[ 1.284463] mmcblk0: p1 p2 p3 p4 p5
[ 1.289171] mmcblk0boot0: mmc0:0001 008GB0 4.00 MiB
[ 1.295276] mmcblk0boot1: mmc0:0001 008GB0 4.00 MiB
[ 1.301189] mmcblk0rpmb: mmc0:0001 008GB0 4.00 MiB, chardev (248:0)
[ 2.204154] CPU0: proxy tick device unregistered
[ 2.204158] CPU1: proxy tick device unregistered
[ 2.213448] IRQ pipeline: torture stage removed.
[ 2.218091] IRQ pipeline tests OK.
[ 2.227641] sfp sfp-lanM: Host maximum power 2.0W
[-- Attachment #3: xenomai.state-stopped.boot --]
[-- Type: application/octet-stream, Size: 10597 bytes --]
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 5.15.170-01498-g889fd6cd2ca7-dirty (francois@Dev-RSpace) (arm-oe-linux-gnueabi-gcc (GCC) 11.4.0, GNU ld (GNU Binutils) 2.38.20220708) #17 SMP IRQPIPE Mon Nov 18 14:11:28 CET 2024
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt: Machine model: SCLE UCC+T07 CPU Board
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] cma: Reserved 64 MiB at 0x3c000000
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x0000000000000000-0x000000002fffffff]
[ 0.000000] HighMem [mem 0x0000000030000000-0x000000003fffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x000000003fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000003fffffff]
[ 0.000000] percpu: Embedded 9 pages/cpu s15564 r0 d21300 u36864
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 260608
[ 0.000000] Kernel command line: earlyprintk console=ttyPS0,115200n8 root=/dev/nfs nfsroot=192.168.10.2:/home/rootfs/BCU,v3 ip=192.168.10.1:192.168.10.2:::Scle-UCC:eth0:off xenomai.state=stopped
[ 0.000000] Unknown kernel command line parameters "earlyprintk", will be passed to user space.
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 963268K/1048576K available (6144K kernel code, 600K rwdata, 1032K rodata, 1024K init, 239K bss, 19772K reserved, 65536K cma-reserved, 196608K highmem)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] slcr mapped to (ptrval)
[ 0.000000] L2C: platform modifies aux control register: 0x02060000 -> 0x02460000
[ 0.000000] L2C: DT/platform modifies aux control register: 0x02060000 -> 0x02460000
[ 0.000000] L2C-310 erratum 769419 enabled
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x46460001
[ 0.000000] IRQ pipeline enabled
[ 0.000000] zynq_clock_init: clkc starts at (ptrval)
[ 0.000000] Zynq clock init
[ 0.000001] sched_clock: 64 bits at 166MHz, resolution 6ns, wraps every 4398046511103ns
[ 0.000024] clocksource: arm_global_timer: freq: 166666665 Hz, mask: 0xffffffffffffffff max_cycles: 0x26703d7dd8, max_idle_ns: 440795208065 ns
[ 0.000059] Switching to timer-based delay loop, resolution 6ns
[ 0.000702] Console: colour dummy device 80x30
[ 0.000778] Calibrating delay loop (skipped), value calculated using timer frequency.. 333.33 BogoMIPS (lpj=1666666)
[ 0.000802] CPU: Testing write buffer coherency: ok
[ 0.000857] CPU0: Spectre v2: using BPIALL workaround
[ 0.000871] pid_max: default: 32768 minimum: 301
[ 0.001028] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.001053] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.001911] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.002711] Setting up static identity map for 0x100000 - 0x10003c
[ 0.002896] rcu: Hierarchical SRCU implementation.
[ 0.003316] smp: Bringing up secondary CPUs ...
[ 0.004100] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.004117] CPU1: Spectre v2: using BPIALL workaround
[ 0.004255] smp: Brought up 1 node, 2 CPUs
[ 0.004284] SMP: Total of 2 processors activated (666.66 BogoMIPS).
[ 0.004299] CPU: All CPU(s) started in SVC mode.
[ 0.004878] devtmpfs: initialized
[ 0.012809] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.012959] clocksource: jiffies: freq: 0 Hz, mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.012991] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[ 0.016807] pinctrl core: initialized pinctrl subsystem
[ 0.017716] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.021187] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.022222] thermal_sys: Registered thermal governor 'step_wise'
[ 0.033315] amba f8801000.etb: Fixing up cyclic dependency with replicator
[ 0.033676] amba f8803000.tpiu: Fixing up cyclic dependency with replicator
[ 0.034095] amba f8804000.funnel: Fixing up cyclic dependency with replicator
[ 0.034455] amba f889c000.ptm: Fixing up cyclic dependency with f8804000.funnel
[ 0.034806] amba f889d000.ptm: Fixing up cyclic dependency with f8804000.funnel
[ 0.047900] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.047927] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.048548] zynq-pinctrl 700.pinctrl: zynq pinctrl initialized
[ 0.049429] e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 35, base_baud = 6249999) is a xuartps
[ 0.547318] printk: console [ttyPS0] enabled
[ 0.552157] xuartps e0001000.serial: uart_add_one_port() failed; err=-22
[ 0.558931] xuartps: probe of e0001000.serial failed with error -22
[ 0.573623] cryptd: max_cpu_qlen set to 1000
[ 0.582362] SCSI subsystem initialized
[ 0.587268] clocksource: Switched to clocksource arm_global_timer
[ 0.601247] NET: Registered PF_INET protocol family
[ 0.606363] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[ 0.614850] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[ 0.623267] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.631033] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[ 0.638855] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.646222] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.652682] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.659346] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.666621] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.673107] RPC: Registered named UNIX socket transport module.
[ 0.679071] RPC: Registered udp transport module.
[ 0.683771] RPC: Registered tcp transport module.
[ 0.688486] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.695774] [Xenomai] scheduling class idle registered.
[ 0.701002] [Xenomai] scheduling class rt registered.
[ 0.706103] IRQ pipeline: high-priority Xenomai stage added.
[ 0.714399] [Xenomai] Cobalt v3.3 [STOPPED]
[ 0.718760] workingset: timestamp_bits=30 max_order=18 bucket_order=0
[ 0.835835] NET: Registered PF_ALG protocol family
[ 0.840775] bounce: pool size: 64 pages
[ 0.844659] io scheduler mq-deadline registered
[ 0.853009] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.859717] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.877268] brd: module loaded
[ 0.900728] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 38 (80:1f:12:f8:48:87)
[ 0.912585] flx_frtc 41040000.frtc: Component Local NCO IO remapped to: (ptrval)
[ 0.921461] macip_mdio 4000514c.mdio: Successfully probed SCLE MACIP MDIO bus !
[ 0.929194] macip 40004000.macip: SCLE MACIP using OCM memory for BDs
[ 0.936119] [macip_set_features:1698] TODO
[ 0.940658] macip 40004000.macip eth1: Scle MAC rev 0x00000002 at 0x40004000 irq 62-63L (80:1f:12:f8:22:88). Ring length : 128/128
[ 0.952431] macip 40004000.macip eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=fixed-0:00, irq=-1)
[ 0.962729] i2c_dev: i2c /dev entries driver
[ 0.967482] cdns-i2c e0004000.i2c: 100 kHz mmio e0004000 irq 32
[ 0.974920] at24 1-0052: 256 byte 24c02 EEPROM, writable, 16 bytes/write
[ 0.982401] at24 1-0053: 256 byte 24c02 EEPROM, writable, 16 bytes/write
[ 0.989835] at24 1-0054: 256 byte 24c02 EEPROM, writable, 16 bytes/write
[ 0.996612] cdns-i2c e0005000.i2c: 100 kHz mmio e0005000 irq 33
[ 1.003368] zynq-pinctrl 700.pinctrl: invalid function i2c0_emio in map table
[ 1.010717] zynq-pinctrl 700.pinctrl: invalid function i2c0_emio in map table
[ 1.018110] i2c i2c-0: Added multiplexed i2c bus 2
[ 1.023134] i2c i2c-0: Added multiplexed i2c bus 3
[ 1.028523] i2c i2c-3: Added multiplexed i2c bus 4
[ 1.033547] i2c i2c-3: Added multiplexed i2c bus 5
[ 1.039188] cdns-wdt f8005000.watchdog: Xilinx Watchdog Timer with timeout 10s, nowayout
[ 1.047574] sdhci: Secure Digital Host Controller Interface driver
[ 1.053765] sdhci: Copyright(c) Pierre Ossman
[ 1.058114] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.065121] clocksource: ttc_clocksource: freq: 54253 Hz, mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
[ 1.075746] timer #0 at (ptrval), irq=52
[ 1.082522] RTnet:
[ 1.082522] *** RTnet for Xenomai v3.3 ***
[ 1.082522]
[ 1.090214] RTnet: initialising real-time networking
[ 1.095956] rtmacb e000c000.ethernet: No pinctrl provided
[ 1.103127] RTnet: registered rteth0
[ 1.105974] mmc0: SDHCI controller on e0100000.mmc [e0100000.mmc] using ADMA
[ 1.107000] rt_macb: rteth0: Cadence GEM at 0xe000c000 irq 39 (00:00:00:00:00:00) - txdis/using BD in OCM
[ 1.123341] rt_macb: rteth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=fixed-0:01, irq=-1)
[ 1.133600] NET: Registered PF_PACKET protocol family
[ 1.138697] 8021q: 802.1Q VLAN Support v1.8
[ 1.143035] Registering SWP/SWPB emulation handler
[ 1.147922] Starting IRQ pipeline tests...
[ 1.147931] irq_pipeline-torture: won't run, oob stage 'Xenomai' is already installed
[ 1.161449] sfp sfp-lanM: Host maximum power 2.0W
[-- Attachment #4: normal-hang.boot --]
[-- Type: application/octet-stream, Size: 7899 bytes --]
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 5.15.170-01498-g889fd6cd2ca7-dirty (francois@Dev-RSpace) (arm-oe-linux-gnueabi-gcc (GCC) 11.4.0, GNU ld (GNU Binutils) 2.38.20220708) #17 SMP IRQPIPE Mon Nov 18 14:11:28 CET 2024
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt: Machine model: SCLE UCC+T07 CPU Board
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] cma: Reserved 64 MiB at 0x3c000000
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x0000000000000000-0x000000002fffffff]
[ 0.000000] HighMem [mem 0x0000000030000000-0x000000003fffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x000000003fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000003fffffff]
[ 0.000000] percpu: Embedded 9 pages/cpu s15564 r0 d21300 u36864
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 260608
[ 0.000000] Kernel command line: earlyprintk console=ttyPS0,115200n8 root=/dev/nfs nfsroot=192.168.10.2:/home/rootfs/BCU,v3 ip=192.168.10.1:192.168.10.2:::Scle-UCC:eth0:off
[ 0.000000] Unknown kernel command line parameters "earlyprintk", will be passed to user space.
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 963268K/1048576K available (6144K kernel code, 600K rwdata, 1032K rodata, 1024K init, 239K bss, 19772K reserved, 65536K cma-reserved, 196608K highmem)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] slcr mapped to (ptrval)
[ 0.000000] L2C: platform modifies aux control register: 0x02060000 -> 0x02460000
[ 0.000000] L2C: DT/platform modifies aux control register: 0x02060000 -> 0x02460000
[ 0.000000] L2C-310 erratum 769419 enabled
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x46460001
[ 0.000000] IRQ pipeline enabled
[ 0.000000] zynq_clock_init: clkc starts at (ptrval)
[ 0.000000] Zynq clock init
[ 0.000001] sched_clock: 64 bits at 166MHz, resolution 6ns, wraps every 4398046511103ns
[ 0.000024] clocksource: arm_global_timer: freq: 166666665 Hz, mask: 0xffffffffffffffff max_cycles: 0x26703d7dd8, max_idle_ns: 440795208065 ns
[ 0.000061] Switching to timer-based delay loop, resolution 6ns
[ 0.000704] Console: colour dummy device 80x30
[ 0.000781] Calibrating delay loop (skipped), value calculated using timer frequency.. 333.33 BogoMIPS (lpj=1666666)
[ 0.000804] CPU: Testing write buffer coherency: ok
[ 0.000858] CPU0: Spectre v2: using BPIALL workaround
[ 0.000872] pid_max: default: 32768 minimum: 301
[ 0.001030] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.001054] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.001911] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.002716] Setting up static identity map for 0x100000 - 0x10003c
[ 0.002900] rcu: Hierarchical SRCU implementation.
[ 0.003325] smp: Bringing up secondary CPUs ...
[ 0.004106] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.004124] CPU1: Spectre v2: using BPIALL workaround
[ 0.004267] smp: Brought up 1 node, 2 CPUs
[ 0.004296] SMP: Total of 2 processors activated (666.66 BogoMIPS).
[ 0.004312] CPU: All CPU(s) started in SVC mode.
[ 0.004888] devtmpfs: initialized
[ 0.012821] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.012972] clocksource: jiffies: freq: 0 Hz, mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.013006] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[ 0.016843] pinctrl core: initialized pinctrl subsystem
[ 0.017755] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.021165] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.022206] thermal_sys: Registered thermal governor 'step_wise'
[ 0.033256] amba f8801000.etb: Fixing up cyclic dependency with replicator
[ 0.033620] amba f8803000.tpiu: Fixing up cyclic dependency with replicator
[ 0.034035] amba f8804000.funnel: Fixing up cyclic dependency with replicator
[ 0.034394] amba f889c000.ptm: Fixing up cyclic dependency with f8804000.funnel
[ 0.034743] amba f889d000.ptm: Fixing up cyclic dependency with f8804000.funnel
[ 0.047815] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.047840] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.048451] zynq-pinctrl 700.pinctrl: zynq pinctrl initialized
[ 0.049335] e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 35, base_baud = 6249999) is a xuartps
[ 0.545301] printk: console [ttyPS0] enabled
[ 0.550193] xuartps e0001000.serial: uart_add_one_port() failed; err=-22
[ 0.556970] xuartps: probe of e0001000.serial failed with error -22
[ 0.571539] cryptd: max_cpu_qlen set to 1000
[ 0.580052] SCSI subsystem initialized
[ 0.585032] clocksource: Switched to clocksource arm_global_timer
[ 0.598978] NET: Registered PF_INET protocol family
[ 0.604134] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[ 0.612607] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[ 0.621024] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.628773] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[ 0.636604] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.643974] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.650433] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.657092] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.664375] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.670813] RPC: Registered named UNIX socket transport module.
[ 0.676734] RPC: Registered udp transport module.
[ 0.681464] RPC: Registered tcp transport module.
[ 0.686160] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.693416] [Xenomai] scheduling class idle registered.
[ 0.698642] [Xenomai] scheduling class rt registered.
[ 0.703754] IRQ pipeline: high-priority Xenomai stage added.
[ 0.711086] CPU0: proxy tick device registered (333.33MHz)
[ 0.711088] CPU1: proxy tick device registered (333.33MHz)
[ 0.723154] [Xenomai] Cobalt v3.3
[ 0.726744] workingset: timestamp_bits=30 max_order=18 bucket_order=0
[ 0.849494] NET: Registered PF_ALG protocol family
[ 0.854417] bounce: pool size: 64 pages
[ 0.858271] io scheduler mq-deadline registered
[ 0.866524] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.873235] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.890652] brd: module loaded
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-18 13:21 ` François Legal
@ 2024-11-18 13:37 ` Philippe Gerum
2024-11-18 13:57 ` Florian Bezdeka
0 siblings, 1 reply; 23+ messages in thread
From: Philippe Gerum @ 2024-11-18 13:37 UTC (permalink / raw)
To: François Legal
Cc: Florian Bezdeka, Jan Kiszka, xenomai, 孙涛
François Legal <devel@thom.fr.eu.org> writes:
> Le Lundi, Novembre 18, 2024 13:06 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
>
>>
>> [ Updated CC list to merge both mail threads ]
>>
>> On Mon, 2024-11-18 at 12:37 +0100, Philippe Gerum wrote:
>> > François Legal <devel@thom.fr.eu.org> writes:
>> >
>> > > Le Lundi, Novembre 18, 2024 11:32 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
>> > >
>> > > > On Mon, 2024-11-18 at 11:21 +0100, François Legal wrote:
>> > > > > Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit:
>> > > > >
>> > > > > > On 18.11.24 09:50, François Legal wrote:
>> > > > > > > Hello,
>> > > > > > >
>> > > > > > > running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
>> > > > > > >
>> > > > > > > I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
>> > > > > > >
>> > > > > > > Attached is my config.
>> > > > > >
>> > > > > > Can you factor out from it what the SoC is, if you patched the kernel
>> > > > > > for it (in the past and now), if you had to adopt Dovetail etc.?
>> > > > > >
>> > > > > > Jan
>> > > > >
>> > > > > The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
>> > > >
>> > > > We had a similar report for the zynq 7020 a couple of days ago.
>> > > > See [1].
>> > > >
>> > > > What happens if you disable CONFIG_SMP? (Not that this should be the
>> > > > final solution, but it might help to track the issue down...)
>> > > >
>> > > > Florian
>> > > >
>> > >
>> > > Disabling config SMP makes my system boot again.
>> > > How can I help working this out ?
>> > >
>> > > François
>> > >
>> >
>> > This looks like an issue with the proxy tick device. First thing is to
>> > disable CONFIG_XENOMAI, enabling CONFIG_IRQ_PIPELINE_TORTURE_TEST. If
>> > the kernel still hangs, we may have a hint about the reason
>> > why. Alternatively, you could keep CONFIG_XENOMAI in, booting the kernel
>> > with "xenomai.state=stopped". If no hang occurs at boot anymore, there
>> > may be an issue with proxying the timer device on this SoC.
>> >
>
> CONFIG_IRQ_PIPELINE_TORTURE_TEST seems to report OK (attached bootlog CONFIG_IRQ_PIPELINE_TORTURE_TEST.boot
>
> Starting with "xenomai.state=stopped" works (attached boolog xenomai.state-stopped.boot)
> Starting up xenomai with coreclk afterwards seem to work and not hang system :
> root@Arkens_SV:~# /usr/xenomai/sbin/corectl -start
> [ 117.328878] CPU1: proxy tick device registered (333.33MHz)
> [ 117.328883] CPU0: proxy tick device registered (333.33MHz)
> [ 117.339995] [Xenomai] services started
>
>
Ok, so another usual suspect for this issue: some weirdness in the CPU
idling code, which causes a (timer) interrupt to linger indefinitely in
some per-CPU interrupt log. A typical scenario is as follows:
CPUx
----
default_idle_call() {
...
<IRQ> -> logged because local_irq_disable() in effect, _however_ we do NOT
expect hard irqs to be enabled [1] before entering the idle call
next => issue is there.
arch_cpu_idle();
...
/* per-CPU log is not flushed, because of [1] */
}
At the end of the day, the (most likely) timer IRQ is marked as pending
in the log, but never played, so the kernel activity stalls on that CPU,
especially if the boot CPU is involved.
--
Philippe.
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-18 12:06 ` Florian Bezdeka
2024-11-18 13:21 ` François Legal
@ 2024-11-18 13:38 ` François Legal
1 sibling, 0 replies; 23+ messages in thread
From: François Legal @ 2024-11-18 13:38 UTC (permalink / raw)
To: Florian Bezdeka; +Cc: Philippe Gerum, Jan Kiszka, xenomai, 孙涛
Le Lundi, Novembre 18, 2024 13:06 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
>
> [ Updated CC list to merge both mail threads ]
>
> On Mon, 2024-11-18 at 12:37 +0100, Philippe Gerum wrote:
> > François Legal <devel@thom.fr.eu.org> writes:
> >
> > > Le Lundi, Novembre 18, 2024 11:32 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
> > >
> > > > On Mon, 2024-11-18 at 11:21 +0100, François Legal wrote:
> > > > > Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit:
> > > > >
> > > > > > On 18.11.24 09:50, François Legal wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > > > running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
> > > > > > >
> > > > > > > I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
> > > > > > >
> > > > > > > Attached is my config.
> > > > > >
> > > > > > Can you factor out from it what the SoC is, if you patched the kernel
> > > > > > for it (in the past and now), if you had to adopt Dovetail etc.?
> > > > > >
> > > > > > Jan
> > > > >
> > > > > The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
> > > >
> > > > We had a similar report for the zynq 7020 a couple of days ago.
> > > > See [1].
> > > >
> > > > What happens if you disable CONFIG_SMP? (Not that this should be the
> > > > final solution, but it might help to track the issue down...)
> > > >
> > > > Florian
> > > >
> > >
> > > Disabling config SMP makes my system boot again.
> > > How can I help working this out ?
> > >
> > > François
> > >
> >
> > This looks like an issue with the proxy tick device. First thing is to
> > disable CONFIG_XENOMAI, enabling CONFIG_IRQ_PIPELINE_TORTURE_TEST. If
> > the kernel still hangs, we may have a hint about the reason
> > why. Alternatively, you could keep CONFIG_XENOMAI in, booting the kernel
> > with "xenomai.state=stopped". If no hang occurs at boot anymore, there
> > may be an issue with proxying the timer device on this SoC.
> >
> > [1] https://v4.xenomai.org/dovetail/porting/timer/
> > [2] https://v4.xenomai.org/dovetail/porting/devnotes/#check-that-the-pipeline-torture-tests-pass
> >
Plus, I have both ARM global timer and architected timer (I can't seem to be able to disable it) activated in config
Kernel/dovetail from https://source.denx.de/Xenomai/linux-dovetail.git branch v5.15.y-dovetail
François
> > --
> > Philippe.
>
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-18 13:37 ` Philippe Gerum
@ 2024-11-18 13:57 ` Florian Bezdeka
2024-11-18 14:49 ` Philippe Gerum
0 siblings, 1 reply; 23+ messages in thread
From: Florian Bezdeka @ 2024-11-18 13:57 UTC (permalink / raw)
To: Philippe Gerum, François Legal; +Cc: Jan Kiszka, xenomai, 孙涛
On Mon, 2024-11-18 at 14:37 +0100, Philippe Gerum wrote:
> François Legal <devel@thom.fr.eu.org> writes:
>
> > Le Lundi, Novembre 18, 2024 13:06 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
> >
> > >
> > > [ Updated CC list to merge both mail threads ]
> > >
> > > On Mon, 2024-11-18 at 12:37 +0100, Philippe Gerum wrote:
> > > > François Legal <devel@thom.fr.eu.org> writes:
> > > >
> > > > > Le Lundi, Novembre 18, 2024 11:32 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
> > > > >
> > > > > > On Mon, 2024-11-18 at 11:21 +0100, François Legal wrote:
> > > > > > > Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit:
> > > > > > >
> > > > > > > > On 18.11.24 09:50, François Legal wrote:
> > > > > > > > > Hello,
> > > > > > > > >
> > > > > > > > > running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
> > > > > > > > >
> > > > > > > > > I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
> > > > > > > > >
> > > > > > > > > Attached is my config.
> > > > > > > >
> > > > > > > > Can you factor out from it what the SoC is, if you patched the kernel
> > > > > > > > for it (in the past and now), if you had to adopt Dovetail etc.?
> > > > > > > >
> > > > > > > > Jan
> > > > > > >
> > > > > > > The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
> > > > > >
> > > > > > We had a similar report for the zynq 7020 a couple of days ago.
> > > > > > See [1].
> > > > > >
> > > > > > What happens if you disable CONFIG_SMP? (Not that this should be the
> > > > > > final solution, but it might help to track the issue down...)
> > > > > >
> > > > > > Florian
> > > > > >
> > > > >
> > > > > Disabling config SMP makes my system boot again.
> > > > > How can I help working this out ?
> > > > >
> > > > > François
> > > > >
> > > >
> > > > This looks like an issue with the proxy tick device. First thing is to
> > > > disable CONFIG_XENOMAI, enabling CONFIG_IRQ_PIPELINE_TORTURE_TEST. If
> > > > the kernel still hangs, we may have a hint about the reason
> > > > why. Alternatively, you could keep CONFIG_XENOMAI in, booting the kernel
> > > > with "xenomai.state=stopped". If no hang occurs at boot anymore, there
> > > > may be an issue with proxying the timer device on this SoC.
> > > >
> >
> > CONFIG_IRQ_PIPELINE_TORTURE_TEST seems to report OK (attached bootlog CONFIG_IRQ_PIPELINE_TORTURE_TEST.boot
> >
> > Starting with "xenomai.state=stopped" works (attached boolog xenomai.state-stopped.boot)
> > Starting up xenomai with coreclk afterwards seem to work and not hang system :
> > root@Arkens_SV:~# /usr/xenomai/sbin/corectl -start
> > [ 117.328878] CPU1: proxy tick device registered (333.33MHz)
> > [ 117.328883] CPU0: proxy tick device registered (333.33MHz)
> > [ 117.339995] [Xenomai] services started
> >
> >
>
> Ok, so another usual suspect for this issue: some weirdness in the CPU
> idling code, which causes a (timer) interrupt to linger indefinitely in
> some per-CPU interrupt log. A typical scenario is as follows:
>
> CPUx
> ----
>
> default_idle_call() {
>
> ...
> <IRQ> -> logged because local_irq_disable() in effect, _however_ we do NOT
> expect hard irqs to be enabled [1] before entering the idle call
> next => issue is there.
> arch_cpu_idle();
> ...
> /* per-CPU log is not flushed, because of [1] */
> }
>
> At the end of the day, the (most likely) timer IRQ is marked as pending
> in the log, but never played, so the kernel activity stalls on that CPU,
> especially if the boot CPU is involved.
>
Taken from the boot log:
[ 0.000024] clocksource: arm_global_timer: freq: 166666665 Hz, mask: 0xffffffffffffffff max_cycles: 0x26703d7dd8, max_idle_ns: 440795208065 ns
[ 0.012959] clocksource: jiffies: freq: 0 Hz, mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.587268] clocksource: Switched to clocksource arm_global_timer
[ 1.065121] clocksource: ttc_clocksource: freq: 54253 Hz, mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
So the last active clocksource is ttc_clocksource
(drivers/clocksource/timer-cadence-ttc.c).
If I'm correct the OOB enablement is missing for this driver.
Philippe already pointed us to
https://v4.xenomai.org/dovetail/porting/timer/.
Could someone try that? I have matching HW at hand...
Florian
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-18 13:57 ` Florian Bezdeka
@ 2024-11-18 14:49 ` Philippe Gerum
2024-11-18 15:22 ` François Legal
0 siblings, 1 reply; 23+ messages in thread
From: Philippe Gerum @ 2024-11-18 14:49 UTC (permalink / raw)
To: Florian Bezdeka
Cc: François Legal, Jan Kiszka, xenomai, 孙涛
Florian Bezdeka <florian.bezdeka@siemens.com> writes:
> On Mon, 2024-11-18 at 14:37 +0100, Philippe Gerum wrote:
>> François Legal <devel@thom.fr.eu.org> writes:
>>
>> > Le Lundi, Novembre 18, 2024 13:06 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
>> >
>> > >
>> > > [ Updated CC list to merge both mail threads ]
>> > >
>> > > On Mon, 2024-11-18 at 12:37 +0100, Philippe Gerum wrote:
>> > > > François Legal <devel@thom.fr.eu.org> writes:
>> > > >
>> > > > > Le Lundi, Novembre 18, 2024 11:32 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
>> > > > >
>> > > > > > On Mon, 2024-11-18 at 11:21 +0100, François Legal wrote:
>> > > > > > > Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit:
>> > > > > > >
>> > > > > > > > On 18.11.24 09:50, François Legal wrote:
>> > > > > > > > > Hello,
>> > > > > > > > >
>> > > > > > > > > running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
>> > > > > > > > >
>> > > > > > > > > I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
>> > > > > > > > >
>> > > > > > > > > Attached is my config.
>> > > > > > > >
>> > > > > > > > Can you factor out from it what the SoC is, if you patched the kernel
>> > > > > > > > for it (in the past and now), if you had to adopt Dovetail etc.?
>> > > > > > > >
>> > > > > > > > Jan
>> > > > > > >
>> > > > > > > The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
>> > > > > >
>> > > > > > We had a similar report for the zynq 7020 a couple of days ago.
>> > > > > > See [1].
>> > > > > >
>> > > > > > What happens if you disable CONFIG_SMP? (Not that this should be the
>> > > > > > final solution, but it might help to track the issue down...)
>> > > > > >
>> > > > > > Florian
>> > > > > >
>> > > > >
>> > > > > Disabling config SMP makes my system boot again.
>> > > > > How can I help working this out ?
>> > > > >
>> > > > > François
>> > > > >
>> > > >
>> > > > This looks like an issue with the proxy tick device. First thing is to
>> > > > disable CONFIG_XENOMAI, enabling CONFIG_IRQ_PIPELINE_TORTURE_TEST. If
>> > > > the kernel still hangs, we may have a hint about the reason
>> > > > why. Alternatively, you could keep CONFIG_XENOMAI in, booting the kernel
>> > > > with "xenomai.state=stopped". If no hang occurs at boot anymore, there
>> > > > may be an issue with proxying the timer device on this SoC.
>> > > >
>> >
>> > CONFIG_IRQ_PIPELINE_TORTURE_TEST seems to report OK (attached bootlog CONFIG_IRQ_PIPELINE_TORTURE_TEST.boot
>> >
>> > Starting with "xenomai.state=stopped" works (attached boolog xenomai.state-stopped.boot)
>> > Starting up xenomai with coreclk afterwards seem to work and not hang system :
>> > root@Arkens_SV:~# /usr/xenomai/sbin/corectl -start
>> > [ 117.328878] CPU1: proxy tick device registered (333.33MHz)
>> > [ 117.328883] CPU0: proxy tick device registered (333.33MHz)
>> > [ 117.339995] [Xenomai] services started
>> >
>> >
>>
>> Ok, so another usual suspect for this issue: some weirdness in the CPU
>> idling code, which causes a (timer) interrupt to linger indefinitely in
>> some per-CPU interrupt log. A typical scenario is as follows:
>>
>> CPUx
>> ----
>>
>> default_idle_call() {
>>
>> ...
>> <IRQ> -> logged because local_irq_disable() in effect, _however_ we do NOT
>> expect hard irqs to be enabled [1] before entering the idle call
>> next => issue is there.
>> arch_cpu_idle();
>> ...
>> /* per-CPU log is not flushed, because of [1] */
>> }
>>
>> At the end of the day, the (most likely) timer IRQ is marked as pending
>> in the log, but never played, so the kernel activity stalls on that CPU,
>> especially if the boot CPU is involved.
>>
>
> Taken from the boot log:
>
> [ 0.000024] clocksource: arm_global_timer: freq: 166666665 Hz, mask: 0xffffffffffffffff max_cycles: 0x26703d7dd8, max_idle_ns: 440795208065 ns
> [ 0.012959] clocksource: jiffies: freq: 0 Hz, mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
> [ 0.587268] clocksource: Switched to clocksource arm_global_timer
> [ 1.065121] clocksource: ttc_clocksource: freq: 54253 Hz, mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
>
> So the last active clocksource is ttc_clocksource
> (drivers/clocksource/timer-cadence-ttc.c).
> If I'm correct the OOB enablement is missing for this driver.
>
> Philippe already pointed us to
> https://v4.xenomai.org/dovetail/porting/timer/.
>
> Could someone try that? I have matching HW at hand...
>
The following code is a 100%, happily untested attempt to enable the ttc
device for pipelining (timer events and reading its clock source
directly from user-space via mmio as well). I don't have any zynq hw at
hand to test it either.
diff --git a/drivers/clocksource/timer-cadence-ttc.c b/drivers/clocksource/timer-cadence-ttc.c
index 0d52e28fea4de..fcab778448bba 100644
--- a/drivers/clocksource/timer-cadence-ttc.c
+++ b/drivers/clocksource/timer-cadence-ttc.c
@@ -84,11 +84,11 @@ struct ttc_timer_clocksource {
u32 scale_clk_ctrl_reg_old;
u32 scale_clk_ctrl_reg_new;
struct ttc_timer ttc;
- struct clocksource cs;
+ struct clocksource_user_mmio cs;
};
#define to_ttc_timer_clksrc(x) \
- container_of(x, struct ttc_timer_clocksource, cs)
+ container_of(x, struct ttc_timer_clocksource, cs.mmio.clksrc)
struct ttc_timer_clockevent {
struct ttc_timer ttc;
@@ -143,24 +143,11 @@ static irqreturn_t ttc_clock_event_interrupt(int irq, void *dev_id)
/* Acknowledge the interrupt and call event handler */
readl_relaxed(timer->base_addr + TTC_ISR_OFFSET);
- ttce->ce.event_handler(&ttce->ce);
+ clockevents_handle_event(&ttce->ce);
return IRQ_HANDLED;
}
-/**
- * __ttc_clocksource_read - Reads the timer counter register
- *
- * returns: Current timer counter register value
- **/
-static u64 __ttc_clocksource_read(struct clocksource *cs)
-{
- struct ttc_timer *timer = &to_ttc_timer_clksrc(cs)->ttc;
-
- return (u64)readl_relaxed(timer->base_addr +
- TTC_COUNT_VAL_OFFSET);
-}
-
static u64 notrace ttc_sched_clock_read(void)
{
return readl_relaxed(ttc_sched_clock_val_reg);
@@ -320,6 +307,7 @@ static int ttc_rate_change_clocksource_cb(struct notifier_block *nb,
static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
u32 timer_width)
{
+ struct clocksource_mmio_regs mmr = { 0 };
struct ttc_timer_clocksource *ttccs;
int err;
@@ -347,11 +335,11 @@ static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
pr_warn("Unable to register clock notifier.\n");
ttccs->ttc.base_addr = base;
- ttccs->cs.name = "ttc_clocksource";
- ttccs->cs.rating = 200;
- ttccs->cs.read = __ttc_clocksource_read;
- ttccs->cs.mask = CLOCKSOURCE_MASK(timer_width);
- ttccs->cs.flags = CLOCK_SOURCE_IS_CONTINUOUS;
+ ttccs->cs.mmio.clksrc.name = "ttc_clocksource";
+ ttccs->cs.mmio.clksrc.rating = 200;
+ ttccs->cs.mmio.clksrc.read = clocksource_mmio_readl_up,
+ ttccs->cs.mmio.clksrc.mask = CLOCKSOURCE_MASK(timer_width);
+ ttccs->cs.mmio.clksrc.flags = CLOCK_SOURCE_IS_CONTINUOUS;
/*
* Setup the clock source counter to be an incrementing counter
@@ -364,7 +352,10 @@ static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
writel_relaxed(CNT_CNTRL_RESET,
ttccs->ttc.base_addr + TTC_CNT_CNTRL_OFFSET);
- err = clocksource_register_hz(&ttccs->cs, ttccs->ttc.freq / PRESCALE);
+ mmr.reg_lower = ttccs->ttc.base_addr + TTC_COUNT_VAL_OFFSET;
+ mmr.bits_lower = 32;
+
+ err = clocksource_user_mmio_init(&ttccs->cs, &mmr, ttccs->ttc.freq / PRESCALE);
if (err) {
kfree(ttccs);
return err;
@@ -431,7 +422,8 @@ static int __init ttc_setup_clockevent(struct clk *clk,
ttcce->ttc.base_addr = base;
ttcce->ce.name = "ttc_clockevent";
- ttcce->ce.features = CLOCK_EVT_FEAT_PERIODIC | CLOCK_EVT_FEAT_ONESHOT;
+ ttcce->ce.features = CLOCK_EVT_FEAT_PERIODIC | \
+ CLOCK_EVT_FEAT_ONESHOT | CLOCK_EVT_FEAT_PIPELINE;
ttcce->ce.set_next_event = ttc_set_next_event;
ttcce->ce.set_state_shutdown = ttc_shutdown;
ttcce->ce.set_state_periodic = ttc_set_periodic;
--
Philippe.
^ permalink raw reply related [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-18 14:49 ` Philippe Gerum
@ 2024-11-18 15:22 ` François Legal
2024-11-18 15:33 ` Philippe Gerum
0 siblings, 1 reply; 23+ messages in thread
From: François Legal @ 2024-11-18 15:22 UTC (permalink / raw)
To: Philippe Gerum; +Cc: Florian Bezdeka, Jan Kiszka, xenomai, 孙涛
Le Lundi, Novembre 18, 2024 15:49 CET, Philippe Gerum <rpm@xenomai.org> a écrit:
> Florian Bezdeka <florian.bezdeka@siemens.com> writes:
>
> > On Mon, 2024-11-18 at 14:37 +0100, Philippe Gerum wrote:
> >> François Legal <devel@thom.fr.eu.org> writes:
> >>
> >> > Le Lundi, Novembre 18, 2024 13:06 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
> >> >
> >> > >
> >> > > [ Updated CC list to merge both mail threads ]
> >> > >
> >> > > On Mon, 2024-11-18 at 12:37 +0100, Philippe Gerum wrote:
> >> > > > François Legal <devel@thom.fr.eu.org> writes:
> >> > > >
> >> > > > > Le Lundi, Novembre 18, 2024 11:32 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
> >> > > > >
> >> > > > > > On Mon, 2024-11-18 at 11:21 +0100, François Legal wrote:
> >> > > > > > > Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit:
> >> > > > > > >
> >> > > > > > > > On 18.11.24 09:50, François Legal wrote:
> >> > > > > > > > > Hello,
> >> > > > > > > > >
> >> > > > > > > > > running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
> >> > > > > > > > >
> >> > > > > > > > > I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
> >> > > > > > > > >
> >> > > > > > > > > Attached is my config.
> >> > > > > > > >
> >> > > > > > > > Can you factor out from it what the SoC is, if you patched the kernel
> >> > > > > > > > for it (in the past and now), if you had to adopt Dovetail etc.?
> >> > > > > > > >
> >> > > > > > > > Jan
> >> > > > > > >
> >> > > > > > > The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
> >> > > > > >
> >> > > > > > We had a similar report for the zynq 7020 a couple of days ago.
> >> > > > > > See [1].
> >> > > > > >
> >> > > > > > What happens if you disable CONFIG_SMP? (Not that this should be the
> >> > > > > > final solution, but it might help to track the issue down...)
> >> > > > > >
> >> > > > > > Florian
> >> > > > > >
> >> > > > >
> >> > > > > Disabling config SMP makes my system boot again.
> >> > > > > How can I help working this out ?
> >> > > > >
> >> > > > > François
> >> > > > >
> >> > > >
> >> > > > This looks like an issue with the proxy tick device. First thing is to
> >> > > > disable CONFIG_XENOMAI, enabling CONFIG_IRQ_PIPELINE_TORTURE_TEST. If
> >> > > > the kernel still hangs, we may have a hint about the reason
> >> > > > why. Alternatively, you could keep CONFIG_XENOMAI in, booting the kernel
> >> > > > with "xenomai.state=stopped". If no hang occurs at boot anymore, there
> >> > > > may be an issue with proxying the timer device on this SoC.
> >> > > >
> >> >
> >> > CONFIG_IRQ_PIPELINE_TORTURE_TEST seems to report OK (attached bootlog CONFIG_IRQ_PIPELINE_TORTURE_TEST.boot
> >> >
> >> > Starting with "xenomai.state=stopped" works (attached boolog xenomai.state-stopped.boot)
> >> > Starting up xenomai with coreclk afterwards seem to work and not hang system :
> >> > root@Arkens_SV:~# /usr/xenomai/sbin/corectl -start
> >> > [ 117.328878] CPU1: proxy tick device registered (333.33MHz)
> >> > [ 117.328883] CPU0: proxy tick device registered (333.33MHz)
> >> > [ 117.339995] [Xenomai] services started
> >> >
> >> >
> >>
> >> Ok, so another usual suspect for this issue: some weirdness in the CPU
> >> idling code, which causes a (timer) interrupt to linger indefinitely in
> >> some per-CPU interrupt log. A typical scenario is as follows:
> >>
> >> CPUx
> >> ----
> >>
> >> default_idle_call() {
> >>
> >> ...
> >> <IRQ> -> logged because local_irq_disable() in effect, _however_ we do NOT
> >> expect hard irqs to be enabled [1] before entering the idle call
> >> next => issue is there.
> >> arch_cpu_idle();
> >> ...
> >> /* per-CPU log is not flushed, because of [1] */
> >> }
> >>
> >> At the end of the day, the (most likely) timer IRQ is marked as pending
> >> in the log, but never played, so the kernel activity stalls on that CPU,
> >> especially if the boot CPU is involved.
> >>
> >
> > Taken from the boot log:
> >
> > [ 0.000024] clocksource: arm_global_timer: freq: 166666665 Hz, mask: 0xffffffffffffffff max_cycles: 0x26703d7dd8, max_idle_ns: 440795208065 ns
> > [ 0.012959] clocksource: jiffies: freq: 0 Hz, mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
> > [ 0.587268] clocksource: Switched to clocksource arm_global_timer
> > [ 1.065121] clocksource: ttc_clocksource: freq: 54253 Hz, mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
> >
> > So the last active clocksource is ttc_clocksource
> > (drivers/clocksource/timer-cadence-ttc.c).
> > If I'm correct the OOB enablement is missing for this driver.
> >
> > Philippe already pointed us to
> > https://v4.xenomai.org/dovetail/porting/timer/.
> >
> > Could someone try that? I have matching HW at hand...
> >
>
> The following code is a 100%, happily untested attempt to enable the ttc
> device for pipelining (timer events and reading its clock source
> directly from user-space via mmio as well). I don't have any zynq hw at
> hand to test it either.
>
> diff --git a/drivers/clocksource/timer-cadence-ttc.c b/drivers/clocksource/timer-cadence-ttc.c
> index 0d52e28fea4de..fcab778448bba 100644
> --- a/drivers/clocksource/timer-cadence-ttc.c
> +++ b/drivers/clocksource/timer-cadence-ttc.c
> @@ -84,11 +84,11 @@ struct ttc_timer_clocksource {
> u32 scale_clk_ctrl_reg_old;
> u32 scale_clk_ctrl_reg_new;
> struct ttc_timer ttc;
> - struct clocksource cs;
> + struct clocksource_user_mmio cs;
> };
>
> #define to_ttc_timer_clksrc(x) \
> - container_of(x, struct ttc_timer_clocksource, cs)
> + container_of(x, struct ttc_timer_clocksource, cs.mmio.clksrc)
>
> struct ttc_timer_clockevent {
> struct ttc_timer ttc;
> @@ -143,24 +143,11 @@ static irqreturn_t ttc_clock_event_interrupt(int irq, void *dev_id)
> /* Acknowledge the interrupt and call event handler */
> readl_relaxed(timer->base_addr + TTC_ISR_OFFSET);
>
> - ttce->ce.event_handler(&ttce->ce);
> + clockevents_handle_event(&ttce->ce);
>
> return IRQ_HANDLED;
> }
>
> -/**
> - * __ttc_clocksource_read - Reads the timer counter register
> - *
> - * returns: Current timer counter register value
> - **/
> -static u64 __ttc_clocksource_read(struct clocksource *cs)
> -{
> - struct ttc_timer *timer = &to_ttc_timer_clksrc(cs)->ttc;
> -
> - return (u64)readl_relaxed(timer->base_addr +
> - TTC_COUNT_VAL_OFFSET);
> -}
> -
> static u64 notrace ttc_sched_clock_read(void)
> {
> return readl_relaxed(ttc_sched_clock_val_reg);
> @@ -320,6 +307,7 @@ static int ttc_rate_change_clocksource_cb(struct notifier_block *nb,
> static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
> u32 timer_width)
> {
> + struct clocksource_mmio_regs mmr = { 0 };
> struct ttc_timer_clocksource *ttccs;
> int err;
>
> @@ -347,11 +335,11 @@ static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
> pr_warn("Unable to register clock notifier.\n");
>
> ttccs->ttc.base_addr = base;
> - ttccs->cs.name = "ttc_clocksource";
> - ttccs->cs.rating = 200;
> - ttccs->cs.read = __ttc_clocksource_read;
> - ttccs->cs.mask = CLOCKSOURCE_MASK(timer_width);
> - ttccs->cs.flags = CLOCK_SOURCE_IS_CONTINUOUS;
> + ttccs->cs.mmio.clksrc.name = "ttc_clocksource";
> + ttccs->cs.mmio.clksrc.rating = 200;
> + ttccs->cs.mmio.clksrc.read = clocksource_mmio_readl_up,
> + ttccs->cs.mmio.clksrc.mask = CLOCKSOURCE_MASK(timer_width);
> + ttccs->cs.mmio.clksrc.flags = CLOCK_SOURCE_IS_CONTINUOUS;
>
> /*
> * Setup the clock source counter to be an incrementing counter
> @@ -364,7 +352,10 @@ static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
> writel_relaxed(CNT_CNTRL_RESET,
> ttccs->ttc.base_addr + TTC_CNT_CNTRL_OFFSET);
>
> - err = clocksource_register_hz(&ttccs->cs, ttccs->ttc.freq / PRESCALE);
> + mmr.reg_lower = ttccs->ttc.base_addr + TTC_COUNT_VAL_OFFSET;
> + mmr.bits_lower = 32;
> +
> + err = clocksource_user_mmio_init(&ttccs->cs, &mmr, ttccs->ttc.freq / PRESCALE);
> if (err) {
> kfree(ttccs);
> return err;
> @@ -431,7 +422,8 @@ static int __init ttc_setup_clockevent(struct clk *clk,
>
> ttcce->ttc.base_addr = base;
> ttcce->ce.name = "ttc_clockevent";
> - ttcce->ce.features = CLOCK_EVT_FEAT_PERIODIC | CLOCK_EVT_FEAT_ONESHOT;
> + ttcce->ce.features = CLOCK_EVT_FEAT_PERIODIC | \
> + CLOCK_EVT_FEAT_ONESHOT | CLOCK_EVT_FEAT_PIPELINE;
> ttcce->ce.set_next_event = ttc_set_next_event;
> ttcce->ce.set_state_shutdown = ttc_shutdown;
> ttcce->ce.set_state_periodic = ttc_set_periodic;
>
> --
I just gave it a try, but with no success. I hadtried a patch of mine too with the same result.
I wonder however if this is really the problem here as when I get stuck at boot, the last declare time source is the Arm GT :
Here :
[ 0.614817] clocksource: Switched to clocksource arm_global_timer
[ 0.628544] NET: Registered PF_INET protocol family
[ 0.633699] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[ 0.642170] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[ 0.650587] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.658339] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[ 0.666173] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.673540] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.679986] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.686665] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.693937] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.700355] RPC: Registered named UNIX socket transport module.
[ 0.706274] RPC: Registered udp transport module.
[ 0.710989] RPC: Registered tcp transport module.
[ 0.715691] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.722914] [Xenomai] scheduling class idle registered.
[ 0.728138] [Xenomai] scheduling class rt registered.
[ 0.733243] IRQ pipeline: high-priority Xenomai stage added.
[ 0.740572] CPU0: proxy tick device registered (333.33MHz)
[ 0.740575] CPU1: proxy tick device registered (333.33MHz)
[ 0.752600] [Xenomai] Cobalt v3.3
[ 0.756129] workingset: timestamp_bits=30 max_order=18 bucket_order=0
[ 0.879595] NET: Registered PF_ALG protocol family
[ 0.884507] bounce: pool size: 64 pages
[ 0.888358] io scheduler mq-deadline registered
[ 0.896523] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.903234] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.919795] brd: module loaded
then hung from here
François
> Philippe.
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-18 15:22 ` François Legal
@ 2024-11-18 15:33 ` Philippe Gerum
2024-11-19 7:26 ` François Legal
0 siblings, 1 reply; 23+ messages in thread
From: Philippe Gerum @ 2024-11-18 15:33 UTC (permalink / raw)
To: François Legal
Cc: Florian Bezdeka, Jan Kiszka, xenomai, 孙涛
François Legal <devel@thom.fr.eu.org> writes:
> Le Lundi, Novembre 18, 2024 15:49 CET, Philippe Gerum <rpm@xenomai.org> a écrit:
>
>> Florian Bezdeka <florian.bezdeka@siemens.com> writes:
>>
>> > On Mon, 2024-11-18 at 14:37 +0100, Philippe Gerum wrote:
>> >> François Legal <devel@thom.fr.eu.org> writes:
>> >>
>> >> > Le Lundi, Novembre 18, 2024 13:06 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
>> >> >
>> >> > >
>> >> > > [ Updated CC list to merge both mail threads ]
>> >> > >
>> >> > > On Mon, 2024-11-18 at 12:37 +0100, Philippe Gerum wrote:
>> >> > > > François Legal <devel@thom.fr.eu.org> writes:
>> >> > > >
>> >> > > > > Le Lundi, Novembre 18, 2024 11:32 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
>> >> > > > >
>> >> > > > > > On Mon, 2024-11-18 at 11:21 +0100, François Legal wrote:
>> >> > > > > > > Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit:
>> >> > > > > > >
>> >> > > > > > > > On 18.11.24 09:50, François Legal wrote:
>> >> > > > > > > > > Hello,
>> >> > > > > > > > >
>> >> > > > > > > > > running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
>> >> > > > > > > > >
>> >> > > > > > > > > I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
>> >> > > > > > > > >
>> >> > > > > > > > > Attached is my config.
>> >> > > > > > > >
>> >> > > > > > > > Can you factor out from it what the SoC is, if you patched the kernel
>> >> > > > > > > > for it (in the past and now), if you had to adopt Dovetail etc.?
>> >> > > > > > > >
>> >> > > > > > > > Jan
>> >> > > > > > >
>> >> > > > > > > The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
>> >> > > > > >
>> >> > > > > > We had a similar report for the zynq 7020 a couple of days ago.
>> >> > > > > > See [1].
>> >> > > > > >
>> >> > > > > > What happens if you disable CONFIG_SMP? (Not that this should be the
>> >> > > > > > final solution, but it might help to track the issue down...)
>> >> > > > > >
>> >> > > > > > Florian
>> >> > > > > >
>> >> > > > >
>> >> > > > > Disabling config SMP makes my system boot again.
>> >> > > > > How can I help working this out ?
>> >> > > > >
>> >> > > > > François
>> >> > > > >
>> >> > > >
>> >> > > > This looks like an issue with the proxy tick device. First thing is to
>> >> > > > disable CONFIG_XENOMAI, enabling CONFIG_IRQ_PIPELINE_TORTURE_TEST. If
>> >> > > > the kernel still hangs, we may have a hint about the reason
>> >> > > > why. Alternatively, you could keep CONFIG_XENOMAI in, booting the kernel
>> >> > > > with "xenomai.state=stopped". If no hang occurs at boot anymore, there
>> >> > > > may be an issue with proxying the timer device on this SoC.
>> >> > > >
>> >> >
>> >> > CONFIG_IRQ_PIPELINE_TORTURE_TEST seems to report OK (attached bootlog CONFIG_IRQ_PIPELINE_TORTURE_TEST.boot
>> >> >
>> >> > Starting with "xenomai.state=stopped" works (attached boolog xenomai.state-stopped.boot)
>> >> > Starting up xenomai with coreclk afterwards seem to work and not hang system :
>> >> > root@Arkens_SV:~# /usr/xenomai/sbin/corectl -start
>> >> > [ 117.328878] CPU1: proxy tick device registered (333.33MHz)
>> >> > [ 117.328883] CPU0: proxy tick device registered (333.33MHz)
>> >> > [ 117.339995] [Xenomai] services started
>> >> >
>> >> >
>> >>
>> >> Ok, so another usual suspect for this issue: some weirdness in the CPU
>> >> idling code, which causes a (timer) interrupt to linger indefinitely in
>> >> some per-CPU interrupt log. A typical scenario is as follows:
>> >>
>> >> CPUx
>> >> ----
>> >>
>> >> default_idle_call() {
>> >>
>> >> ...
>> >> <IRQ> -> logged because local_irq_disable() in effect, _however_ we do NOT
>> >> expect hard irqs to be enabled [1] before entering the idle call
>> >> next => issue is there.
>> >> arch_cpu_idle();
>> >> ...
>> >> /* per-CPU log is not flushed, because of [1] */
>> >> }
>> >>
>> >> At the end of the day, the (most likely) timer IRQ is marked as pending
>> >> in the log, but never played, so the kernel activity stalls on that CPU,
>> >> especially if the boot CPU is involved.
>> >>
>> >
>> > Taken from the boot log:
>> >
>> > [ 0.000024] clocksource: arm_global_timer: freq: 166666665 Hz, mask: 0xffffffffffffffff max_cycles: 0x26703d7dd8, max_idle_ns: 440795208065 ns
>> > [ 0.012959] clocksource: jiffies: freq: 0 Hz, mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
>> > [ 0.587268] clocksource: Switched to clocksource arm_global_timer
>> > [ 1.065121] clocksource: ttc_clocksource: freq: 54253 Hz, mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
>> >
>> > So the last active clocksource is ttc_clocksource
>> > (drivers/clocksource/timer-cadence-ttc.c).
>> > If I'm correct the OOB enablement is missing for this driver.
>> >
>> > Philippe already pointed us to
>> > https://v4.xenomai.org/dovetail/porting/timer/.
>> >
>> > Could someone try that? I have matching HW at hand...
>> >
>>
>> The following code is a 100%, happily untested attempt to enable the ttc
>> device for pipelining (timer events and reading its clock source
>> directly from user-space via mmio as well). I don't have any zynq hw at
>> hand to test it either.
>>
>> diff --git a/drivers/clocksource/timer-cadence-ttc.c b/drivers/clocksource/timer-cadence-ttc.c
>> index 0d52e28fea4de..fcab778448bba 100644
>> --- a/drivers/clocksource/timer-cadence-ttc.c
>> +++ b/drivers/clocksource/timer-cadence-ttc.c
>> @@ -84,11 +84,11 @@ struct ttc_timer_clocksource {
>> u32 scale_clk_ctrl_reg_old;
>> u32 scale_clk_ctrl_reg_new;
>> struct ttc_timer ttc;
>> - struct clocksource cs;
>> + struct clocksource_user_mmio cs;
>> };
>>
>> #define to_ttc_timer_clksrc(x) \
>> - container_of(x, struct ttc_timer_clocksource, cs)
>> + container_of(x, struct ttc_timer_clocksource, cs.mmio.clksrc)
>>
>> struct ttc_timer_clockevent {
>> struct ttc_timer ttc;
>> @@ -143,24 +143,11 @@ static irqreturn_t ttc_clock_event_interrupt(int irq, void *dev_id)
>> /* Acknowledge the interrupt and call event handler */
>> readl_relaxed(timer->base_addr + TTC_ISR_OFFSET);
>>
>> - ttce->ce.event_handler(&ttce->ce);
>> + clockevents_handle_event(&ttce->ce);
>>
>> return IRQ_HANDLED;
>> }
>>
>> -/**
>> - * __ttc_clocksource_read - Reads the timer counter register
>> - *
>> - * returns: Current timer counter register value
>> - **/
>> -static u64 __ttc_clocksource_read(struct clocksource *cs)
>> -{
>> - struct ttc_timer *timer = &to_ttc_timer_clksrc(cs)->ttc;
>> -
>> - return (u64)readl_relaxed(timer->base_addr +
>> - TTC_COUNT_VAL_OFFSET);
>> -}
>> -
>> static u64 notrace ttc_sched_clock_read(void)
>> {
>> return readl_relaxed(ttc_sched_clock_val_reg);
>> @@ -320,6 +307,7 @@ static int ttc_rate_change_clocksource_cb(struct notifier_block *nb,
>> static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
>> u32 timer_width)
>> {
>> + struct clocksource_mmio_regs mmr = { 0 };
>> struct ttc_timer_clocksource *ttccs;
>> int err;
>>
>> @@ -347,11 +335,11 @@ static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
>> pr_warn("Unable to register clock notifier.\n");
>>
>> ttccs->ttc.base_addr = base;
>> - ttccs->cs.name = "ttc_clocksource";
>> - ttccs->cs.rating = 200;
>> - ttccs->cs.read = __ttc_clocksource_read;
>> - ttccs->cs.mask = CLOCKSOURCE_MASK(timer_width);
>> - ttccs->cs.flags = CLOCK_SOURCE_IS_CONTINUOUS;
>> + ttccs->cs.mmio.clksrc.name = "ttc_clocksource";
>> + ttccs->cs.mmio.clksrc.rating = 200;
>> + ttccs->cs.mmio.clksrc.read = clocksource_mmio_readl_up,
>> + ttccs->cs.mmio.clksrc.mask = CLOCKSOURCE_MASK(timer_width);
>> + ttccs->cs.mmio.clksrc.flags = CLOCK_SOURCE_IS_CONTINUOUS;
>>
>> /*
>> * Setup the clock source counter to be an incrementing counter
>> @@ -364,7 +352,10 @@ static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
>> writel_relaxed(CNT_CNTRL_RESET,
>> ttccs->ttc.base_addr + TTC_CNT_CNTRL_OFFSET);
>>
>> - err = clocksource_register_hz(&ttccs->cs, ttccs->ttc.freq / PRESCALE);
>> + mmr.reg_lower = ttccs->ttc.base_addr + TTC_COUNT_VAL_OFFSET;
>> + mmr.bits_lower = 32;
>> +
>> + err = clocksource_user_mmio_init(&ttccs->cs, &mmr, ttccs->ttc.freq / PRESCALE);
>> if (err) {
>> kfree(ttccs);
>> return err;
>> @@ -431,7 +422,8 @@ static int __init ttc_setup_clockevent(struct clk *clk,
>>
>> ttcce->ttc.base_addr = base;
>> ttcce->ce.name = "ttc_clockevent";
>> - ttcce->ce.features = CLOCK_EVT_FEAT_PERIODIC | CLOCK_EVT_FEAT_ONESHOT;
>> + ttcce->ce.features = CLOCK_EVT_FEAT_PERIODIC | \
>> + CLOCK_EVT_FEAT_ONESHOT | CLOCK_EVT_FEAT_PIPELINE;
>> ttcce->ce.set_next_event = ttc_set_next_event;
>> ttcce->ce.set_state_shutdown = ttc_shutdown;
>> ttcce->ce.set_state_periodic = ttc_set_periodic;
>>
>> --
>
> I just gave it a try, but with no success. I hadtried a patch of mine too with the same result.
> I wonder however if this is really the problem here as when I get stuck at boot, the last declare time source is the Arm GT :
>
> Here :
> [ 0.614817] clocksource: Switched to clocksource arm_global_timer
>
> [ 0.628544] NET: Registered PF_INET protocol family
> [ 0.633699] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
> [ 0.642170] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
> [ 0.650587] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
> [ 0.658339] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
> [ 0.666173] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
> [ 0.673540] TCP: Hash tables configured (established 8192 bind 8192)
> [ 0.679986] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
> [ 0.686665] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
> [ 0.693937] NET: Registered PF_UNIX/PF_LOCAL protocol family
> [ 0.700355] RPC: Registered named UNIX socket transport module.
> [ 0.706274] RPC: Registered udp transport module.
> [ 0.710989] RPC: Registered tcp transport module.
> [ 0.715691] RPC: Registered tcp NFSv4.1 backchannel transport module.
> [ 0.722914] [Xenomai] scheduling class idle registered.
> [ 0.728138] [Xenomai] scheduling class rt registered.
> [ 0.733243] IRQ pipeline: high-priority Xenomai stage added.
> [ 0.740572] CPU0: proxy tick device registered (333.33MHz)
> [ 0.740575] CPU1: proxy tick device registered (333.33MHz)
> [ 0.752600] [Xenomai] Cobalt v3.3
> [ 0.756129] workingset: timestamp_bits=30 max_order=18 bucket_order=0
> [ 0.879595] NET: Registered PF_ALG protocol family
> [ 0.884507] bounce: pool size: 64 pages
> [ 0.888358] io scheduler mq-deadline registered
> [ 0.896523] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
> [ 0.903234] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
> [ 0.919795] brd: module loaded
>
> then hung from here
>
What if you disable CONFIG_CPUIDLE?
--
Philippe.
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-18 15:33 ` Philippe Gerum
@ 2024-11-19 7:26 ` François Legal
2024-11-19 9:26 ` Julien Aube
0 siblings, 1 reply; 23+ messages in thread
From: François Legal @ 2024-11-19 7:26 UTC (permalink / raw)
To: Philippe Gerum; +Cc: Florian Bezdeka, Jan Kiszka, xenomai, 孙涛
Le Lundi, Novembre 18, 2024 16:33 CET, Philippe Gerum <rpm@xenomai.org> a écrit:
> François Legal <devel@thom.fr.eu.org> writes:
>
> > Le Lundi, Novembre 18, 2024 15:49 CET, Philippe Gerum <rpm@xenomai.org> a écrit:
> >
> >> Florian Bezdeka <florian.bezdeka@siemens.com> writes:
> >>
> >> > On Mon, 2024-11-18 at 14:37 +0100, Philippe Gerum wrote:
> >> >> François Legal <devel@thom.fr.eu.org> writes:
> >> >>
> >> >> > Le Lundi, Novembre 18, 2024 13:06 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
> >> >> >
> >> >> > >
> >> >> > > [ Updated CC list to merge both mail threads ]
> >> >> > >
> >> >> > > On Mon, 2024-11-18 at 12:37 +0100, Philippe Gerum wrote:
> >> >> > > > François Legal <devel@thom.fr.eu.org> writes:
> >> >> > > >
> >> >> > > > > Le Lundi, Novembre 18, 2024 11:32 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit:
> >> >> > > > >
> >> >> > > > > > On Mon, 2024-11-18 at 11:21 +0100, François Legal wrote:
> >> >> > > > > > > Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit:
> >> >> > > > > > >
> >> >> > > > > > > > On 18.11.24 09:50, François Legal wrote:
> >> >> > > > > > > > > Hello,
> >> >> > > > > > > > >
> >> >> > > > > > > > > running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
> >> >> > > > > > > > >
> >> >> > > > > > > > > I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
> >> >> > > > > > > > >
> >> >> > > > > > > > > Attached is my config.
> >> >> > > > > > > >
> >> >> > > > > > > > Can you factor out from it what the SoC is, if you patched the kernel
> >> >> > > > > > > > for it (in the past and now), if you had to adopt Dovetail etc.?
> >> >> > > > > > > >
> >> >> > > > > > > > Jan
> >> >> > > > > > >
> >> >> > > > > > > The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
> >> >> > > > > >
> >> >> > > > > > We had a similar report for the zynq 7020 a couple of days ago.
> >> >> > > > > > See [1].
> >> >> > > > > >
> >> >> > > > > > What happens if you disable CONFIG_SMP? (Not that this should be the
> >> >> > > > > > final solution, but it might help to track the issue down...)
> >> >> > > > > >
> >> >> > > > > > Florian
> >> >> > > > > >
> >> >> > > > >
> >> >> > > > > Disabling config SMP makes my system boot again.
> >> >> > > > > How can I help working this out ?
> >> >> > > > >
> >> >> > > > > François
> >> >> > > > >
> >> >> > > >
> >> >> > > > This looks like an issue with the proxy tick device. First thing is to
> >> >> > > > disable CONFIG_XENOMAI, enabling CONFIG_IRQ_PIPELINE_TORTURE_TEST. If
> >> >> > > > the kernel still hangs, we may have a hint about the reason
> >> >> > > > why. Alternatively, you could keep CONFIG_XENOMAI in, booting the kernel
> >> >> > > > with "xenomai.state=stopped". If no hang occurs at boot anymore, there
> >> >> > > > may be an issue with proxying the timer device on this SoC.
> >> >> > > >
> >> >> >
> >> >> > CONFIG_IRQ_PIPELINE_TORTURE_TEST seems to report OK (attached bootlog CONFIG_IRQ_PIPELINE_TORTURE_TEST.boot
> >> >> >
> >> >> > Starting with "xenomai.state=stopped" works (attached boolog xenomai.state-stopped.boot)
> >> >> > Starting up xenomai with coreclk afterwards seem to work and not hang system :
> >> >> > root@Arkens_SV:~# /usr/xenomai/sbin/corectl -start
> >> >> > [ 117.328878] CPU1: proxy tick device registered (333.33MHz)
> >> >> > [ 117.328883] CPU0: proxy tick device registered (333.33MHz)
> >> >> > [ 117.339995] [Xenomai] services started
> >> >> >
> >> >> >
> >> >>
> >> >> Ok, so another usual suspect for this issue: some weirdness in the CPU
> >> >> idling code, which causes a (timer) interrupt to linger indefinitely in
> >> >> some per-CPU interrupt log. A typical scenario is as follows:
> >> >>
> >> >> CPUx
> >> >> ----
> >> >>
> >> >> default_idle_call() {
> >> >>
> >> >> ...
> >> >> <IRQ> -> logged because local_irq_disable() in effect, _however_ we do NOT
> >> >> expect hard irqs to be enabled [1] before entering the idle call
> >> >> next => issue is there.
> >> >> arch_cpu_idle();
> >> >> ...
> >> >> /* per-CPU log is not flushed, because of [1] */
> >> >> }
> >> >>
> >> >> At the end of the day, the (most likely) timer IRQ is marked as pending
> >> >> in the log, but never played, so the kernel activity stalls on that CPU,
> >> >> especially if the boot CPU is involved.
> >> >>
> >> >
> >> > Taken from the boot log:
> >> >
> >> > [ 0.000024] clocksource: arm_global_timer: freq: 166666665 Hz, mask: 0xffffffffffffffff max_cycles: 0x26703d7dd8, max_idle_ns: 440795208065 ns
> >> > [ 0.012959] clocksource: jiffies: freq: 0 Hz, mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
> >> > [ 0.587268] clocksource: Switched to clocksource arm_global_timer
> >> > [ 1.065121] clocksource: ttc_clocksource: freq: 54253 Hz, mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
> >> >
> >> > So the last active clocksource is ttc_clocksource
> >> > (drivers/clocksource/timer-cadence-ttc.c).
> >> > If I'm correct the OOB enablement is missing for this driver.
> >> >
> >> > Philippe already pointed us to
> >> > https://v4.xenomai.org/dovetail/porting/timer/.
> >> >
> >> > Could someone try that? I have matching HW at hand...
> >> >
> >>
> >> The following code is a 100%, happily untested attempt to enable the ttc
> >> device for pipelining (timer events and reading its clock source
> >> directly from user-space via mmio as well). I don't have any zynq hw at
> >> hand to test it either.
> >>
> >> diff --git a/drivers/clocksource/timer-cadence-ttc.c b/drivers/clocksource/timer-cadence-ttc.c
> >> index 0d52e28fea4de..fcab778448bba 100644
> >> --- a/drivers/clocksource/timer-cadence-ttc.c
> >> +++ b/drivers/clocksource/timer-cadence-ttc.c
> >> @@ -84,11 +84,11 @@ struct ttc_timer_clocksource {
> >> u32 scale_clk_ctrl_reg_old;
> >> u32 scale_clk_ctrl_reg_new;
> >> struct ttc_timer ttc;
> >> - struct clocksource cs;
> >> + struct clocksource_user_mmio cs;
> >> };
> >>
> >> #define to_ttc_timer_clksrc(x) \
> >> - container_of(x, struct ttc_timer_clocksource, cs)
> >> + container_of(x, struct ttc_timer_clocksource, cs.mmio.clksrc)
> >>
> >> struct ttc_timer_clockevent {
> >> struct ttc_timer ttc;
> >> @@ -143,24 +143,11 @@ static irqreturn_t ttc_clock_event_interrupt(int irq, void *dev_id)
> >> /* Acknowledge the interrupt and call event handler */
> >> readl_relaxed(timer->base_addr + TTC_ISR_OFFSET);
> >>
> >> - ttce->ce.event_handler(&ttce->ce);
> >> + clockevents_handle_event(&ttce->ce);
> >>
> >> return IRQ_HANDLED;
> >> }
> >>
> >> -/**
> >> - * __ttc_clocksource_read - Reads the timer counter register
> >> - *
> >> - * returns: Current timer counter register value
> >> - **/
> >> -static u64 __ttc_clocksource_read(struct clocksource *cs)
> >> -{
> >> - struct ttc_timer *timer = &to_ttc_timer_clksrc(cs)->ttc;
> >> -
> >> - return (u64)readl_relaxed(timer->base_addr +
> >> - TTC_COUNT_VAL_OFFSET);
> >> -}
> >> -
> >> static u64 notrace ttc_sched_clock_read(void)
> >> {
> >> return readl_relaxed(ttc_sched_clock_val_reg);
> >> @@ -320,6 +307,7 @@ static int ttc_rate_change_clocksource_cb(struct notifier_block *nb,
> >> static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
> >> u32 timer_width)
> >> {
> >> + struct clocksource_mmio_regs mmr = { 0 };
> >> struct ttc_timer_clocksource *ttccs;
> >> int err;
> >>
> >> @@ -347,11 +335,11 @@ static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
> >> pr_warn("Unable to register clock notifier.\n");
> >>
> >> ttccs->ttc.base_addr = base;
> >> - ttccs->cs.name = "ttc_clocksource";
> >> - ttccs->cs.rating = 200;
> >> - ttccs->cs.read = __ttc_clocksource_read;
> >> - ttccs->cs.mask = CLOCKSOURCE_MASK(timer_width);
> >> - ttccs->cs.flags = CLOCK_SOURCE_IS_CONTINUOUS;
> >> + ttccs->cs.mmio.clksrc.name = "ttc_clocksource";
> >> + ttccs->cs.mmio.clksrc.rating = 200;
> >> + ttccs->cs.mmio.clksrc.read = clocksource_mmio_readl_up,
> >> + ttccs->cs.mmio.clksrc.mask = CLOCKSOURCE_MASK(timer_width);
> >> + ttccs->cs.mmio.clksrc.flags = CLOCK_SOURCE_IS_CONTINUOUS;
> >>
> >> /*
> >> * Setup the clock source counter to be an incrementing counter
> >> @@ -364,7 +352,10 @@ static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
> >> writel_relaxed(CNT_CNTRL_RESET,
> >> ttccs->ttc.base_addr + TTC_CNT_CNTRL_OFFSET);
> >>
> >> - err = clocksource_register_hz(&ttccs->cs, ttccs->ttc.freq / PRESCALE);
> >> + mmr.reg_lower = ttccs->ttc.base_addr + TTC_COUNT_VAL_OFFSET;
> >> + mmr.bits_lower = 32;
> >> +
> >> + err = clocksource_user_mmio_init(&ttccs->cs, &mmr, ttccs->ttc.freq / PRESCALE);
> >> if (err) {
> >> kfree(ttccs);
> >> return err;
> >> @@ -431,7 +422,8 @@ static int __init ttc_setup_clockevent(struct clk *clk,
> >>
> >> ttcce->ttc.base_addr = base;
> >> ttcce->ce.name = "ttc_clockevent";
> >> - ttcce->ce.features = CLOCK_EVT_FEAT_PERIODIC | CLOCK_EVT_FEAT_ONESHOT;
> >> + ttcce->ce.features = CLOCK_EVT_FEAT_PERIODIC | \
> >> + CLOCK_EVT_FEAT_ONESHOT | CLOCK_EVT_FEAT_PIPELINE;
> >> ttcce->ce.set_next_event = ttc_set_next_event;
> >> ttcce->ce.set_state_shutdown = ttc_shutdown;
> >> ttcce->ce.set_state_periodic = ttc_set_periodic;
> >>
> >> --
> >
> > I just gave it a try, but with no success. I hadtried a patch of mine too with the same result.
> > I wonder however if this is really the problem here as when I get stuck at boot, the last declare time source is the Arm GT :
> >
> > Here :
> > [ 0.614817] clocksource: Switched to clocksource arm_global_timer
> >
> > [ 0.628544] NET: Registered PF_INET protocol family
> > [ 0.633699] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
> > [ 0.642170] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
> > [ 0.650587] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
> > [ 0.658339] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
> > [ 0.666173] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
> > [ 0.673540] TCP: Hash tables configured (established 8192 bind 8192)
> > [ 0.679986] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
> > [ 0.686665] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
> > [ 0.693937] NET: Registered PF_UNIX/PF_LOCAL protocol family
> > [ 0.700355] RPC: Registered named UNIX socket transport module.
> > [ 0.706274] RPC: Registered udp transport module.
> > [ 0.710989] RPC: Registered tcp transport module.
> > [ 0.715691] RPC: Registered tcp NFSv4.1 backchannel transport module.
> > [ 0.722914] [Xenomai] scheduling class idle registered.
> > [ 0.728138] [Xenomai] scheduling class rt registered.
> > [ 0.733243] IRQ pipeline: high-priority Xenomai stage added.
> > [ 0.740572] CPU0: proxy tick device registered (333.33MHz)
> > [ 0.740575] CPU1: proxy tick device registered (333.33MHz)
> > [ 0.752600] [Xenomai] Cobalt v3.3
> > [ 0.756129] workingset: timestamp_bits=30 max_order=18 bucket_order=0
> > [ 0.879595] NET: Registered PF_ALG protocol family
> > [ 0.884507] bounce: pool size: 64 pages
> > [ 0.888358] io scheduler mq-deadline registered
> > [ 0.896523] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
> > [ 0.903234] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
> > [ 0.919795] brd: module loaded
> >
> > then hung from here
> >
>
> What if you disable CONFIG_CPUIDLE?
It's already disabled.
François
>
> --
> Philippe.
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-19 7:26 ` François Legal
@ 2024-11-19 9:26 ` Julien Aube
2024-11-19 10:06 ` François Legal
0 siblings, 1 reply; 23+ messages in thread
From: Julien Aube @ 2024-11-19 9:26 UTC (permalink / raw)
To: xenomai
Hello,
Reading this exchange it reminds me of a problem I had a few months ago
on the same platform.
Here is the thead :
https://lore.kernel.org/xenomai/6814fa90-015e-91df-6941-db643e4d4229@smile.fr/#r
Conclusion was that disabling the scutimer(*) on DTS level was enough to
restore the correct usage and I did not found
any bad behaviour after that. The product has passed all the rt-test
afterward.
(*)
&scutimer {
/* scutimer is forced to disabled since it does not work with
Xenomai */
status = "disabled";
};
Maybe i'm completely off the subject, but maybe it's worth having a look ?
Julien
Le 19/11/2024 à 08:26, François Legal a écrit :
> Le Lundi, Novembre 18, 2024 16:33 CET, Philippe Gerum<rpm@xenomai.org> a écrit:
>
>> François Legal<devel@thom.fr.eu.org> writes:
>>
>>> Le Lundi, Novembre 18, 2024 15:49 CET, Philippe Gerum<rpm@xenomai.org> a écrit:
>>>
>>>> Florian Bezdeka<florian.bezdeka@siemens.com> writes:
>>>>
>>>>> On Mon, 2024-11-18 at 14:37 +0100, Philippe Gerum wrote:
>>>>>> François Legal<devel@thom.fr.eu.org> writes:
>>>>>>
>>>>>>> Le Lundi, Novembre 18, 2024 13:06 CET, Florian Bezdeka<florian.bezdeka@siemens.com> a écrit:
>>>>>>>
>>>>>>>> [ Updated CC list to merge both mail threads ]
>>>>>>>>
>>>>>>>> On Mon, 2024-11-18 at 12:37 +0100, Philippe Gerum wrote:
>>>>>>>>> François Legal<devel@thom.fr.eu.org> writes:
>>>>>>>>>
>>>>>>>>>> Le Lundi, Novembre 18, 2024 11:32 CET, Florian Bezdeka<florian.bezdeka@siemens.com> a écrit:
>>>>>>>>>>
>>>>>>>>>>> On Mon, 2024-11-18 at 11:21 +0100, François Legal wrote:
>>>>>>>>>>>> Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka<jan.kiszka@siemens.com> a écrit:
>>>>>>>>>>>>
>>>>>>>>>>>>> On 18.11.24 09:50, François Legal wrote:
>>>>>>>>>>>>>> Hello,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Attached is my config.
>>>>>>>>>>>>> Can you factor out from it what the SoC is, if you patched the kernel
>>>>>>>>>>>>> for it (in the past and now), if you had to adopt Dovetail etc.?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Jan
>>>>>>>>>>>> The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
>>>>>>>>>>> We had a similar report for the zynq 7020 a couple of days ago.
>>>>>>>>>>> See [1].
>>>>>>>>>>>
>>>>>>>>>>> What happens if you disable CONFIG_SMP? (Not that this should be the
>>>>>>>>>>> final solution, but it might help to track the issue down...)
>>>>>>>>>>>
>>>>>>>>>>> Florian
>>>>>>>>>>>
>>>>>>>>>> Disabling config SMP makes my system boot again.
>>>>>>>>>> How can I help working this out ?
>>>>>>>>>>
>>>>>>>>>> François
>>>>>>>>>>
>>>>>>>>> This looks like an issue with the proxy tick device. First thing is to
>>>>>>>>> disable CONFIG_XENOMAI, enabling CONFIG_IRQ_PIPELINE_TORTURE_TEST. If
>>>>>>>>> the kernel still hangs, we may have a hint about the reason
>>>>>>>>> why. Alternatively, you could keep CONFIG_XENOMAI in, booting the kernel
>>>>>>>>> with "xenomai.state=stopped". If no hang occurs at boot anymore, there
>>>>>>>>> may be an issue with proxying the timer device on this SoC.
>>>>>>>>>
>>>>>>> CONFIG_IRQ_PIPELINE_TORTURE_TEST seems to report OK (attached bootlog CONFIG_IRQ_PIPELINE_TORTURE_TEST.boot
>>>>>>>
>>>>>>> Starting with "xenomai.state=stopped" works (attached boolog xenomai.state-stopped.boot)
>>>>>>> Starting up xenomai with coreclk afterwards seem to work and not hang system :
>>>>>>> root@Arkens_SV:~# /usr/xenomai/sbin/corectl -start
>>>>>>> [ 117.328878] CPU1: proxy tick device registered (333.33MHz)
>>>>>>> [ 117.328883] CPU0: proxy tick device registered (333.33MHz)
>>>>>>> [ 117.339995] [Xenomai] services started
>>>>>>>
>>>>>>>
>>>>>> Ok, so another usual suspect for this issue: some weirdness in the CPU
>>>>>> idling code, which causes a (timer) interrupt to linger indefinitely in
>>>>>> some per-CPU interrupt log. A typical scenario is as follows:
>>>>>>
>>>>>> CPUx
>>>>>> ----
>>>>>>
>>>>>> default_idle_call() {
>>>>>>
>>>>>> ...
>>>>>> <IRQ> -> logged because local_irq_disable() in effect, _however_ we do NOT
>>>>>> expect hard irqs to be enabled [1] before entering the idle call
>>>>>> next => issue is there.
>>>>>> arch_cpu_idle();
>>>>>> ...
>>>>>> /* per-CPU log is not flushed, because of [1] */
>>>>>> }
>>>>>>
>>>>>> At the end of the day, the (most likely) timer IRQ is marked as pending
>>>>>> in the log, but never played, so the kernel activity stalls on that CPU,
>>>>>> especially if the boot CPU is involved.
>>>>>>
>>>>> Taken from the boot log:
>>>>>
>>>>> [ 0.000024] clocksource: arm_global_timer: freq: 166666665 Hz, mask: 0xffffffffffffffff max_cycles: 0x26703d7dd8, max_idle_ns: 440795208065 ns
>>>>> [ 0.012959] clocksource: jiffies: freq: 0 Hz, mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
>>>>> [ 0.587268] clocksource: Switched to clocksource arm_global_timer
>>>>> [ 1.065121] clocksource: ttc_clocksource: freq: 54253 Hz, mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
>>>>>
>>>>> So the last active clocksource is ttc_clocksource
>>>>> (drivers/clocksource/timer-cadence-ttc.c).
>>>>> If I'm correct the OOB enablement is missing for this driver.
>>>>>
>>>>> Philippe already pointed us to
>>>>> https://v4.xenomai.org/dovetail/porting/timer/.
>>>>>
>>>>> Could someone try that? I have matching HW at hand...
>>>>>
>>>> The following code is a 100%, happily untested attempt to enable the ttc
>>>> device for pipelining (timer events and reading its clock source
>>>> directly from user-space via mmio as well). I don't have any zynq hw at
>>>> hand to test it either.
>>>>
>>>> diff --git a/drivers/clocksource/timer-cadence-ttc.c b/drivers/clocksource/timer-cadence-ttc.c
>>>> index 0d52e28fea4de..fcab778448bba 100644
>>>> --- a/drivers/clocksource/timer-cadence-ttc.c
>>>> +++ b/drivers/clocksource/timer-cadence-ttc.c
>>>> @@ -84,11 +84,11 @@ struct ttc_timer_clocksource {
>>>> u32 scale_clk_ctrl_reg_old;
>>>> u32 scale_clk_ctrl_reg_new;
>>>> struct ttc_timer ttc;
>>>> - struct clocksource cs;
>>>> + struct clocksource_user_mmio cs;
>>>> };
>>>>
>>>> #define to_ttc_timer_clksrc(x) \
>>>> - container_of(x, struct ttc_timer_clocksource, cs)
>>>> + container_of(x, struct ttc_timer_clocksource, cs.mmio.clksrc)
>>>>
>>>> struct ttc_timer_clockevent {
>>>> struct ttc_timer ttc;
>>>> @@ -143,24 +143,11 @@ static irqreturn_t ttc_clock_event_interrupt(int irq, void *dev_id)
>>>> /* Acknowledge the interrupt and call event handler */
>>>> readl_relaxed(timer->base_addr + TTC_ISR_OFFSET);
>>>>
>>>> - ttce->ce.event_handler(&ttce->ce);
>>>> + clockevents_handle_event(&ttce->ce);
>>>>
>>>> return IRQ_HANDLED;
>>>> }
>>>>
>>>> -/**
>>>> - * __ttc_clocksource_read - Reads the timer counter register
>>>> - *
>>>> - * returns: Current timer counter register value
>>>> - **/
>>>> -static u64 __ttc_clocksource_read(struct clocksource *cs)
>>>> -{
>>>> - struct ttc_timer *timer = &to_ttc_timer_clksrc(cs)->ttc;
>>>> -
>>>> - return (u64)readl_relaxed(timer->base_addr +
>>>> - TTC_COUNT_VAL_OFFSET);
>>>> -}
>>>> -
>>>> static u64 notrace ttc_sched_clock_read(void)
>>>> {
>>>> return readl_relaxed(ttc_sched_clock_val_reg);
>>>> @@ -320,6 +307,7 @@ static int ttc_rate_change_clocksource_cb(struct notifier_block *nb,
>>>> static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
>>>> u32 timer_width)
>>>> {
>>>> + struct clocksource_mmio_regs mmr = { 0 };
>>>> struct ttc_timer_clocksource *ttccs;
>>>> int err;
>>>>
>>>> @@ -347,11 +335,11 @@ static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
>>>> pr_warn("Unable to register clock notifier.\n");
>>>>
>>>> ttccs->ttc.base_addr = base;
>>>> - ttccs->cs.name = "ttc_clocksource";
>>>> - ttccs->cs.rating = 200;
>>>> - ttccs->cs.read = __ttc_clocksource_read;
>>>> - ttccs->cs.mask = CLOCKSOURCE_MASK(timer_width);
>>>> - ttccs->cs.flags = CLOCK_SOURCE_IS_CONTINUOUS;
>>>> + ttccs->cs.mmio.clksrc.name = "ttc_clocksource";
>>>> + ttccs->cs.mmio.clksrc.rating = 200;
>>>> + ttccs->cs.mmio.clksrc.read = clocksource_mmio_readl_up,
>>>> + ttccs->cs.mmio.clksrc.mask = CLOCKSOURCE_MASK(timer_width);
>>>> + ttccs->cs.mmio.clksrc.flags = CLOCK_SOURCE_IS_CONTINUOUS;
>>>>
>>>> /*
>>>> * Setup the clock source counter to be an incrementing counter
>>>> @@ -364,7 +352,10 @@ static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
>>>> writel_relaxed(CNT_CNTRL_RESET,
>>>> ttccs->ttc.base_addr + TTC_CNT_CNTRL_OFFSET);
>>>>
>>>> - err = clocksource_register_hz(&ttccs->cs, ttccs->ttc.freq / PRESCALE);
>>>> + mmr.reg_lower = ttccs->ttc.base_addr + TTC_COUNT_VAL_OFFSET;
>>>> + mmr.bits_lower = 32;
>>>> +
>>>> + err = clocksource_user_mmio_init(&ttccs->cs, &mmr, ttccs->ttc.freq / PRESCALE);
>>>> if (err) {
>>>> kfree(ttccs);
>>>> return err;
>>>> @@ -431,7 +422,8 @@ static int __init ttc_setup_clockevent(struct clk *clk,
>>>>
>>>> ttcce->ttc.base_addr = base;
>>>> ttcce->ce.name = "ttc_clockevent";
>>>> - ttcce->ce.features = CLOCK_EVT_FEAT_PERIODIC | CLOCK_EVT_FEAT_ONESHOT;
>>>> + ttcce->ce.features = CLOCK_EVT_FEAT_PERIODIC | \
>>>> + CLOCK_EVT_FEAT_ONESHOT | CLOCK_EVT_FEAT_PIPELINE;
>>>> ttcce->ce.set_next_event = ttc_set_next_event;
>>>> ttcce->ce.set_state_shutdown = ttc_shutdown;
>>>> ttcce->ce.set_state_periodic = ttc_set_periodic;
>>>>
>>>> --
>>> I just gave it a try, but with no success. I hadtried a patch of mine too with the same result.
>>> I wonder however if this is really the problem here as when I get stuck at boot, the last declare time source is the Arm GT :
>>>
>>> Here :
>>> [ 0.614817] clocksource: Switched to clocksource arm_global_timer
>>>
>>> [ 0.628544] NET: Registered PF_INET protocol family
>>> [ 0.633699] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
>>> [ 0.642170] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
>>> [ 0.650587] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
>>> [ 0.658339] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
>>> [ 0.666173] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
>>> [ 0.673540] TCP: Hash tables configured (established 8192 bind 8192)
>>> [ 0.679986] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
>>> [ 0.686665] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
>>> [ 0.693937] NET: Registered PF_UNIX/PF_LOCAL protocol family
>>> [ 0.700355] RPC: Registered named UNIX socket transport module.
>>> [ 0.706274] RPC: Registered udp transport module.
>>> [ 0.710989] RPC: Registered tcp transport module.
>>> [ 0.715691] RPC: Registered tcp NFSv4.1 backchannel transport module.
>>> [ 0.722914] [Xenomai] scheduling class idle registered.
>>> [ 0.728138] [Xenomai] scheduling class rt registered.
>>> [ 0.733243] IRQ pipeline: high-priority Xenomai stage added.
>>> [ 0.740572] CPU0: proxy tick device registered (333.33MHz)
>>> [ 0.740575] CPU1: proxy tick device registered (333.33MHz)
>>> [ 0.752600] [Xenomai] Cobalt v3.3
>>> [ 0.756129] workingset: timestamp_bits=30 max_order=18 bucket_order=0
>>> [ 0.879595] NET: Registered PF_ALG protocol family
>>> [ 0.884507] bounce: pool size: 64 pages
>>> [ 0.888358] io scheduler mq-deadline registered
>>> [ 0.896523] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
>>> [ 0.903234] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
>>> [ 0.919795] brd: module loaded
>>>
>>> then hung from here
>>>
>> What if you disable CONFIG_CPUIDLE?
> It's already disabled.
>
> François
>
>> --
>> Philippe.
--
SMILE <https://www.smile.eu/>
*Julien AUBÉ*
Tech Expert 1
email julien.aube@smile.fr
phone +33 6 99 11 76 08
Twitter Facebook LinkedIn Github
eco Pour la planète, n'imprimez ce mail que si c'est nécessaire
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-19 9:26 ` Julien Aube
@ 2024-11-19 10:06 ` François Legal
2024-11-19 10:23 ` Philippe Gerum
0 siblings, 1 reply; 23+ messages in thread
From: François Legal @ 2024-11-19 10:06 UTC (permalink / raw)
To: Julien Aube; +Cc: xenomai
Le Mardi, Novembre 19, 2024 10:26 CET, Julien Aube <julien.aube@smile.fr> a écrit:
> Hello,
>
> Reading this exchange it reminds me of a problem I had a few months ago
> on the same platform.
>
> Here is the thead :
>
> https://lore.kernel.org/xenomai/6814fa90-015e-91df-6941-db643e4d4229@smile.fr/#r
>
>
> Conclusion was that disabling the scutimer(*) on DTS level was enough to
> restore the correct usage and I did not found
> any bad behaviour after that. The product has passed all the rt-test
> afterward.
>
>
> (*)
> &scutimer {
> /* scutimer is forced to disabled since it does not work with
> Xenomai */
> status = "disabled";
> };
>
> Maybe i'm completely off the subject, but maybe it's worth having a look ?
>
> Julien
>
>
Thanks. That fixes the problem. I'll dig into that driver to try to fix it and submit a patch then.
François
>
> Le 19/11/2024 à 08:26, François Legal a écrit :
> > Le Lundi, Novembre 18, 2024 16:33 CET, Philippe Gerum<rpm@xenomai.org> a écrit:
> >
> >> François Legal<devel@thom.fr.eu.org> writes:
> >>
> >>> Le Lundi, Novembre 18, 2024 15:49 CET, Philippe Gerum<rpm@xenomai.org> a écrit:
> >>>
> >>>> Florian Bezdeka<florian.bezdeka@siemens.com> writes:
> >>>>
> >>>>> On Mon, 2024-11-18 at 14:37 +0100, Philippe Gerum wrote:
> >>>>>> François Legal<devel@thom.fr.eu.org> writes:
> >>>>>>
> >>>>>>> Le Lundi, Novembre 18, 2024 13:06 CET, Florian Bezdeka<florian.bezdeka@siemens.com> a écrit:
> >>>>>>>
> >>>>>>>> [ Updated CC list to merge both mail threads ]
> >>>>>>>>
> >>>>>>>> On Mon, 2024-11-18 at 12:37 +0100, Philippe Gerum wrote:
> >>>>>>>>> François Legal<devel@thom.fr.eu.org> writes:
> >>>>>>>>>
> >>>>>>>>>> Le Lundi, Novembre 18, 2024 11:32 CET, Florian Bezdeka<florian.bezdeka@siemens.com> a écrit:
> >>>>>>>>>>
> >>>>>>>>>>> On Mon, 2024-11-18 at 11:21 +0100, François Legal wrote:
> >>>>>>>>>>>> Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka<jan.kiszka@siemens.com> a écrit:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> On 18.11.24 09:50, François Legal wrote:
> >>>>>>>>>>>>>> Hello,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Attached is my config.
> >>>>>>>>>>>>> Can you factor out from it what the SoC is, if you patched the kernel
> >>>>>>>>>>>>> for it (in the past and now), if you had to adopt Dovetail etc.?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Jan
> >>>>>>>>>>>> The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
> >>>>>>>>>>> We had a similar report for the zynq 7020 a couple of days ago.
> >>>>>>>>>>> See [1].
> >>>>>>>>>>>
> >>>>>>>>>>> What happens if you disable CONFIG_SMP? (Not that this should be the
> >>>>>>>>>>> final solution, but it might help to track the issue down...)
> >>>>>>>>>>>
> >>>>>>>>>>> Florian
> >>>>>>>>>>>
> >>>>>>>>>> Disabling config SMP makes my system boot again.
> >>>>>>>>>> How can I help working this out ?
> >>>>>>>>>>
> >>>>>>>>>> François
> >>>>>>>>>>
> >>>>>>>>> This looks like an issue with the proxy tick device. First thing is to
> >>>>>>>>> disable CONFIG_XENOMAI, enabling CONFIG_IRQ_PIPELINE_TORTURE_TEST. If
> >>>>>>>>> the kernel still hangs, we may have a hint about the reason
> >>>>>>>>> why. Alternatively, you could keep CONFIG_XENOMAI in, booting the kernel
> >>>>>>>>> with "xenomai.state=stopped". If no hang occurs at boot anymore, there
> >>>>>>>>> may be an issue with proxying the timer device on this SoC.
> >>>>>>>>>
> >>>>>>> CONFIG_IRQ_PIPELINE_TORTURE_TEST seems to report OK (attached bootlog CONFIG_IRQ_PIPELINE_TORTURE_TEST.boot
> >>>>>>>
> >>>>>>> Starting with "xenomai.state=stopped" works (attached boolog xenomai.state-stopped.boot)
> >>>>>>> Starting up xenomai with coreclk afterwards seem to work and not hang system :
> >>>>>>> root@Arkens_SV:~# /usr/xenomai/sbin/corectl -start
> >>>>>>> [ 117.328878] CPU1: proxy tick device registered (333.33MHz)
> >>>>>>> [ 117.328883] CPU0: proxy tick device registered (333.33MHz)
> >>>>>>> [ 117.339995] [Xenomai] services started
> >>>>>>>
> >>>>>>>
> >>>>>> Ok, so another usual suspect for this issue: some weirdness in the CPU
> >>>>>> idling code, which causes a (timer) interrupt to linger indefinitely in
> >>>>>> some per-CPU interrupt log. A typical scenario is as follows:
> >>>>>>
> >>>>>> CPUx
> >>>>>> ----
> >>>>>>
> >>>>>> default_idle_call() {
> >>>>>>
> >>>>>> ...
> >>>>>> <IRQ> -> logged because local_irq_disable() in effect, _however_ we do NOT
> >>>>>> expect hard irqs to be enabled [1] before entering the idle call
> >>>>>> next => issue is there.
> >>>>>> arch_cpu_idle();
> >>>>>> ...
> >>>>>> /* per-CPU log is not flushed, because of [1] */
> >>>>>> }
> >>>>>>
> >>>>>> At the end of the day, the (most likely) timer IRQ is marked as pending
> >>>>>> in the log, but never played, so the kernel activity stalls on that CPU,
> >>>>>> especially if the boot CPU is involved.
> >>>>>>
> >>>>> Taken from the boot log:
> >>>>>
> >>>>> [ 0.000024] clocksource: arm_global_timer: freq: 166666665 Hz, mask: 0xffffffffffffffff max_cycles: 0x26703d7dd8, max_idle_ns: 440795208065 ns
> >>>>> [ 0.012959] clocksource: jiffies: freq: 0 Hz, mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
> >>>>> [ 0.587268] clocksource: Switched to clocksource arm_global_timer
> >>>>> [ 1.065121] clocksource: ttc_clocksource: freq: 54253 Hz, mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
> >>>>>
> >>>>> So the last active clocksource is ttc_clocksource
> >>>>> (drivers/clocksource/timer-cadence-ttc.c).
> >>>>> If I'm correct the OOB enablement is missing for this driver.
> >>>>>
> >>>>> Philippe already pointed us to
> >>>>> https://v4.xenomai.org/dovetail/porting/timer/.
> >>>>>
> >>>>> Could someone try that? I have matching HW at hand...
> >>>>>
> >>>> The following code is a 100%, happily untested attempt to enable the ttc
> >>>> device for pipelining (timer events and reading its clock source
> >>>> directly from user-space via mmio as well). I don't have any zynq hw at
> >>>> hand to test it either.
> >>>>
> >>>> diff --git a/drivers/clocksource/timer-cadence-ttc.c b/drivers/clocksource/timer-cadence-ttc.c
> >>>> index 0d52e28fea4de..fcab778448bba 100644
> >>>> --- a/drivers/clocksource/timer-cadence-ttc.c
> >>>> +++ b/drivers/clocksource/timer-cadence-ttc.c
> >>>> @@ -84,11 +84,11 @@ struct ttc_timer_clocksource {
> >>>> u32 scale_clk_ctrl_reg_old;
> >>>> u32 scale_clk_ctrl_reg_new;
> >>>> struct ttc_timer ttc;
> >>>> - struct clocksource cs;
> >>>> + struct clocksource_user_mmio cs;
> >>>> };
> >>>>
> >>>> #define to_ttc_timer_clksrc(x) \
> >>>> - container_of(x, struct ttc_timer_clocksource, cs)
> >>>> + container_of(x, struct ttc_timer_clocksource, cs.mmio.clksrc)
> >>>>
> >>>> struct ttc_timer_clockevent {
> >>>> struct ttc_timer ttc;
> >>>> @@ -143,24 +143,11 @@ static irqreturn_t ttc_clock_event_interrupt(int irq, void *dev_id)
> >>>> /* Acknowledge the interrupt and call event handler */
> >>>> readl_relaxed(timer->base_addr + TTC_ISR_OFFSET);
> >>>>
> >>>> - ttce->ce.event_handler(&ttce->ce);
> >>>> + clockevents_handle_event(&ttce->ce);
> >>>>
> >>>> return IRQ_HANDLED;
> >>>> }
> >>>>
> >>>> -/**
> >>>> - * __ttc_clocksource_read - Reads the timer counter register
> >>>> - *
> >>>> - * returns: Current timer counter register value
> >>>> - **/
> >>>> -static u64 __ttc_clocksource_read(struct clocksource *cs)
> >>>> -{
> >>>> - struct ttc_timer *timer = &to_ttc_timer_clksrc(cs)->ttc;
> >>>> -
> >>>> - return (u64)readl_relaxed(timer->base_addr +
> >>>> - TTC_COUNT_VAL_OFFSET);
> >>>> -}
> >>>> -
> >>>> static u64 notrace ttc_sched_clock_read(void)
> >>>> {
> >>>> return readl_relaxed(ttc_sched_clock_val_reg);
> >>>> @@ -320,6 +307,7 @@ static int ttc_rate_change_clocksource_cb(struct notifier_block *nb,
> >>>> static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
> >>>> u32 timer_width)
> >>>> {
> >>>> + struct clocksource_mmio_regs mmr = { 0 };
> >>>> struct ttc_timer_clocksource *ttccs;
> >>>> int err;
> >>>>
> >>>> @@ -347,11 +335,11 @@ static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
> >>>> pr_warn("Unable to register clock notifier.\n");
> >>>>
> >>>> ttccs->ttc.base_addr = base;
> >>>> - ttccs->cs.name = "ttc_clocksource";
> >>>> - ttccs->cs.rating = 200;
> >>>> - ttccs->cs.read = __ttc_clocksource_read;
> >>>> - ttccs->cs.mask = CLOCKSOURCE_MASK(timer_width);
> >>>> - ttccs->cs.flags = CLOCK_SOURCE_IS_CONTINUOUS;
> >>>> + ttccs->cs.mmio.clksrc.name = "ttc_clocksource";
> >>>> + ttccs->cs.mmio.clksrc.rating = 200;
> >>>> + ttccs->cs.mmio.clksrc.read = clocksource_mmio_readl_up,
> >>>> + ttccs->cs.mmio.clksrc.mask = CLOCKSOURCE_MASK(timer_width);
> >>>> + ttccs->cs.mmio.clksrc.flags = CLOCK_SOURCE_IS_CONTINUOUS;
> >>>>
> >>>> /*
> >>>> * Setup the clock source counter to be an incrementing counter
> >>>> @@ -364,7 +352,10 @@ static int __init ttc_setup_clocksource(struct clk *clk, void __iomem *base,
> >>>> writel_relaxed(CNT_CNTRL_RESET,
> >>>> ttccs->ttc.base_addr + TTC_CNT_CNTRL_OFFSET);
> >>>>
> >>>> - err = clocksource_register_hz(&ttccs->cs, ttccs->ttc.freq / PRESCALE);
> >>>> + mmr.reg_lower = ttccs->ttc.base_addr + TTC_COUNT_VAL_OFFSET;
> >>>> + mmr.bits_lower = 32;
> >>>> +
> >>>> + err = clocksource_user_mmio_init(&ttccs->cs, &mmr, ttccs->ttc.freq / PRESCALE);
> >>>> if (err) {
> >>>> kfree(ttccs);
> >>>> return err;
> >>>> @@ -431,7 +422,8 @@ static int __init ttc_setup_clockevent(struct clk *clk,
> >>>>
> >>>> ttcce->ttc.base_addr = base;
> >>>> ttcce->ce.name = "ttc_clockevent";
> >>>> - ttcce->ce.features = CLOCK_EVT_FEAT_PERIODIC | CLOCK_EVT_FEAT_ONESHOT;
> >>>> + ttcce->ce.features = CLOCK_EVT_FEAT_PERIODIC | \
> >>>> + CLOCK_EVT_FEAT_ONESHOT | CLOCK_EVT_FEAT_PIPELINE;
> >>>> ttcce->ce.set_next_event = ttc_set_next_event;
> >>>> ttcce->ce.set_state_shutdown = ttc_shutdown;
> >>>> ttcce->ce.set_state_periodic = ttc_set_periodic;
> >>>>
> >>>> --
> >>> I just gave it a try, but with no success. I hadtried a patch of mine too with the same result.
> >>> I wonder however if this is really the problem here as when I get stuck at boot, the last declare time source is the Arm GT :
> >>>
> >>> Here :
> >>> [ 0.614817] clocksource: Switched to clocksource arm_global_timer
> >>>
> >>> [ 0.628544] NET: Registered PF_INET protocol family
> >>> [ 0.633699] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
> >>> [ 0.642170] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
> >>> [ 0.650587] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
> >>> [ 0.658339] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
> >>> [ 0.666173] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
> >>> [ 0.673540] TCP: Hash tables configured (established 8192 bind 8192)
> >>> [ 0.679986] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
> >>> [ 0.686665] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
> >>> [ 0.693937] NET: Registered PF_UNIX/PF_LOCAL protocol family
> >>> [ 0.700355] RPC: Registered named UNIX socket transport module.
> >>> [ 0.706274] RPC: Registered udp transport module.
> >>> [ 0.710989] RPC: Registered tcp transport module.
> >>> [ 0.715691] RPC: Registered tcp NFSv4.1 backchannel transport module.
> >>> [ 0.722914] [Xenomai] scheduling class idle registered.
> >>> [ 0.728138] [Xenomai] scheduling class rt registered.
> >>> [ 0.733243] IRQ pipeline: high-priority Xenomai stage added.
> >>> [ 0.740572] CPU0: proxy tick device registered (333.33MHz)
> >>> [ 0.740575] CPU1: proxy tick device registered (333.33MHz)
> >>> [ 0.752600] [Xenomai] Cobalt v3.3
> >>> [ 0.756129] workingset: timestamp_bits=30 max_order=18 bucket_order=0
> >>> [ 0.879595] NET: Registered PF_ALG protocol family
> >>> [ 0.884507] bounce: pool size: 64 pages
> >>> [ 0.888358] io scheduler mq-deadline registered
> >>> [ 0.896523] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
> >>> [ 0.903234] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
> >>> [ 0.919795] brd: module loaded
> >>>
> >>> then hung from here
> >>>
> >> What if you disable CONFIG_CPUIDLE?
> > It's already disabled.
> >
> > François
> >
> >> --
> >> Philippe.
> --
> SMILE <https://www.smile.eu/>
>
>
> *Julien AUBÉ*
> Tech Expert 1
>
> email julien.aube@smile.fr
> phone +33 6 99 11 76 08
>
> Twitter Facebook LinkedIn Github
>
>
>
> eco Pour la planète, n'imprimez ce mail que si c'est nécessaire
>
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-19 10:06 ` François Legal
@ 2024-11-19 10:23 ` Philippe Gerum
2024-11-19 14:30 ` Philippe Gerum
2024-11-19 14:36 ` François Legal
0 siblings, 2 replies; 23+ messages in thread
From: Philippe Gerum @ 2024-11-19 10:23 UTC (permalink / raw)
To: François Legal; +Cc: Julien Aube, xenomai
François Legal <francois.legal@thom.fr.eu.org> writes:
> Le Mardi, Novembre 19, 2024 10:26 CET, Julien Aube <julien.aube@smile.fr> a écrit:
>
>> Hello,
>>
>> Reading this exchange it reminds me of a problem I had a few months ago
>> on the same platform.
>>
>> Here is the thead :
>>
>> https://lore.kernel.org/xenomai/6814fa90-015e-91df-6941-db643e4d4229@smile.fr/#r
>>
>>
>> Conclusion was that disabling the scutimer(*) on DTS level was enough to
>> restore the correct usage and I did not found
>> any bad behaviour after that. The product has passed all the rt-test
>> afterward.
>>
>>
>> (*)
>> &scutimer {
>> /* scutimer is forced to disabled since it does not work with
>> Xenomai */
>> status = "disabled";
>> };
>>
>> Maybe i'm completely off the subject, but maybe it's worth having a look ?
>>
>> Julien
>>
>>
>
> Thanks. That fixes the problem. I'll dig into that driver to try to fix it and submit a patch then.
>
This may help:
diff --git a/arch/arm/kernel/smp_twd.c b/arch/arm/kernel/smp_twd.c
index 8377f1d030c3a..a28f6b7f7eabc 100644
--- a/arch/arm/kernel/smp_twd.c
+++ b/arch/arm/kernel/smp_twd.c
@@ -181,7 +181,7 @@ static irqreturn_t twd_handler(int irq, void *dev_id)
{
struct clock_event_device *evt = dev_id;
- if (twd_timer_ack()) {
+ if (!clockevent_is_oob(evt) || twd_timer_ack()) {
clockevents_handle_event(evt);
return IRQ_HANDLED;
}
--
Philippe.
^ permalink raw reply related [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-19 10:23 ` Philippe Gerum
@ 2024-11-19 14:30 ` Philippe Gerum
2024-11-19 14:36 ` François Legal
1 sibling, 0 replies; 23+ messages in thread
From: Philippe Gerum @ 2024-11-19 14:30 UTC (permalink / raw)
To: François Legal; +Cc: Julien Aube, xenomai
Philippe Gerum <rpm@xenomai.org> writes:
> François Legal <francois.legal@thom.fr.eu.org> writes:
>
>> Le Mardi, Novembre 19, 2024 10:26 CET, Julien Aube <julien.aube@smile.fr> a écrit:
>>
>>> Hello,
>>>
>>> Reading this exchange it reminds me of a problem I had a few months ago
>>> on the same platform.
>>>
>>> Here is the thead :
>>>
>>> https://lore.kernel.org/xenomai/6814fa90-015e-91df-6941-db643e4d4229@smile.fr/#r
>>>
>>>
>>> Conclusion was that disabling the scutimer(*) on DTS level was enough to
>>> restore the correct usage and I did not found
>>> any bad behaviour after that. The product has passed all the rt-test
>>> afterward.
>>>
>>>
>>> (*)
>>> &scutimer {
>>> /* scutimer is forced to disabled since it does not work with
>>> Xenomai */
>>> status = "disabled";
>>> };
>>>
>>> Maybe i'm completely off the subject, but maybe it's worth having a look ?
>>>
>>> Julien
>>>
>>>
>>
>> Thanks. That fixes the problem. I'll dig into that driver to try to fix it and submit a patch then.
>>
>
> This may help:
>
Not that much actually. This does fix an issue but introduces a
different one. More on this later.
> diff --git a/arch/arm/kernel/smp_twd.c b/arch/arm/kernel/smp_twd.c
> index 8377f1d030c3a..a28f6b7f7eabc 100644
> --- a/arch/arm/kernel/smp_twd.c
> +++ b/arch/arm/kernel/smp_twd.c
> @@ -181,7 +181,7 @@ static irqreturn_t twd_handler(int irq, void *dev_id)
> {
> struct clock_event_device *evt = dev_id;
>
> - if (twd_timer_ack()) {
> + if (!clockevent_is_oob(evt) || twd_timer_ack()) {
> clockevents_handle_event(evt);
> return IRQ_HANDLED;
> }
--
Philippe.
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-19 10:23 ` Philippe Gerum
2024-11-19 14:30 ` Philippe Gerum
@ 2024-11-19 14:36 ` François Legal
2024-11-19 14:55 ` Philippe Gerum
1 sibling, 1 reply; 23+ messages in thread
From: François Legal @ 2024-11-19 14:36 UTC (permalink / raw)
To: Philippe Gerum; +Cc: Julien Aube, xenomai
Le Mardi, Novembre 19, 2024 11:23 CET, Philippe Gerum <rpm@xenomai.org> a écrit:
> François Legal <francois.legal@thom.fr.eu.org> writes:
>
> > Le Mardi, Novembre 19, 2024 10:26 CET, Julien Aube <julien.aube@smile.fr> a écrit:
> >
> >> Hello,
> >>
> >> Reading this exchange it reminds me of a problem I had a few months ago
> >> on the same platform.
> >>
> >> Here is the thead :
> >>
> >> https://lore.kernel.org/xenomai/6814fa90-015e-91df-6941-db643e4d4229@smile.fr/#r
> >>
> >>
> >> Conclusion was that disabling the scutimer(*) on DTS level was enough to
> >> restore the correct usage and I did not found
> >> any bad behaviour after that. The product has passed all the rt-test
> >> afterward.
> >>
> >>
> >> (*)
> >> &scutimer {
> >> /* scutimer is forced to disabled since it does not work with
> >> Xenomai */
> >> status = "disabled";
> >> };
> >>
> >> Maybe i'm completely off the subject, but maybe it's worth having a look ?
> >>
> >> Julien
> >>
> >>
> >
> > Thanks. That fixes the problem. I'll dig into that driver to try to fix it and submit a patch then.
> >
>
> This may help:
>
> diff --git a/arch/arm/kernel/smp_twd.c b/arch/arm/kernel/smp_twd.c
> index 8377f1d030c3a..a28f6b7f7eabc 100644
> --- a/arch/arm/kernel/smp_twd.c
> +++ b/arch/arm/kernel/smp_twd.c
> @@ -181,7 +181,7 @@ static irqreturn_t twd_handler(int irq, void *dev_id)
> {
> struct clock_event_device *evt = dev_id;
>
> - if (twd_timer_ack()) {
> + if (!clockevent_is_oob(evt) || twd_timer_ack()) {
> clockevents_handle_event(evt);
> return IRQ_HANDLED;
> }
>
No noticeable effect here. I tried to dig a little more into this, but I can't find anything.
What I can tell, is that the TWD interrupts triggers on both cores when hung at boot. TWD registers settings seems OK in terms of prescaler and everything. By checking with JTAG debugger, I can see that xnintr_core_clock_handler is being called in the TWD service routine (twd_handler).
I'm trying a little harder, but don't really know from which angle !
François
> --
> Philippe.
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-19 14:36 ` François Legal
@ 2024-11-19 14:55 ` Philippe Gerum
2024-11-19 16:10 ` Philippe Gerum
0 siblings, 1 reply; 23+ messages in thread
From: Philippe Gerum @ 2024-11-19 14:55 UTC (permalink / raw)
To: François Legal; +Cc: Julien Aube, xenomai
François Legal <devel@thom.fr.eu.org> writes:
> Le Mardi, Novembre 19, 2024 11:23 CET, Philippe Gerum <rpm@xenomai.org> a écrit:
>
>> François Legal <francois.legal@thom.fr.eu.org> writes:
>>
>> > Le Mardi, Novembre 19, 2024 10:26 CET, Julien Aube <julien.aube@smile.fr> a écrit:
>> >
>> >> Hello,
>> >>
>> >> Reading this exchange it reminds me of a problem I had a few months ago
>> >> on the same platform.
>> >>
>> >> Here is the thead :
>> >>
>> >> https://lore.kernel.org/xenomai/6814fa90-015e-91df-6941-db643e4d4229@smile.fr/#r
>> >>
>> >>
>> >> Conclusion was that disabling the scutimer(*) on DTS level was enough to
>> >> restore the correct usage and I did not found
>> >> any bad behaviour after that. The product has passed all the rt-test
>> >> afterward.
>> >>
>> >>
>> >> (*)
>> >> &scutimer {
>> >> /* scutimer is forced to disabled since it does not work with
>> >> Xenomai */
>> >> status = "disabled";
>> >> };
>> >>
>> >> Maybe i'm completely off the subject, but maybe it's worth having a look ?
>> >>
>> >> Julien
>> >>
>> >>
>> >
>> > Thanks. That fixes the problem. I'll dig into that driver to try to fix it and submit a patch then.
>> >
>>
>> This may help:
>>
>> diff --git a/arch/arm/kernel/smp_twd.c b/arch/arm/kernel/smp_twd.c
>> index 8377f1d030c3a..a28f6b7f7eabc 100644
>> --- a/arch/arm/kernel/smp_twd.c
>> +++ b/arch/arm/kernel/smp_twd.c
>> @@ -181,7 +181,7 @@ static irqreturn_t twd_handler(int irq, void *dev_id)
>> {
>> struct clock_event_device *evt = dev_id;
>>
>> - if (twd_timer_ack()) {
>> + if (!clockevent_is_oob(evt) || twd_timer_ack()) {
>> clockevents_handle_event(evt);
>> return IRQ_HANDLED;
>> }
>>
>
> No noticeable effect here. I tried to dig a little more into this, but I can't find anything.
> What I can tell, is that the TWD interrupts triggers on both cores when hung at boot. TWD registers settings seems OK in terms of prescaler and everything. By checking with JTAG debugger, I can see that xnintr_core_clock_handler is being called in the TWD service routine (twd_handler).
>
> I'm trying a little harder, but don't really know from which angle !
The issue is as follows:
When the proxy tick hijacks the timer to hand over its control to
Xenomai, twd_handler() may be called either from the oob stage upon a
real tick coming from the hardware, _and_ from the in-band stage as a
consequence of emulating a common kernel tick, see [1] in the "Under the
hood" section.
The way twd_handler() operates ATM causes the hardware to be sent an ack
on every invocation, which is wrong wrt the in-band tick emulation,
which is most likely wrecking the logic afterwards.
[1] https://v4.xenomai.org/dovetail/porting/timer/#proxy-tick-logic
--
Philippe.
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-19 14:55 ` Philippe Gerum
@ 2024-11-19 16:10 ` Philippe Gerum
2024-11-19 17:04 ` François Legal
0 siblings, 1 reply; 23+ messages in thread
From: Philippe Gerum @ 2024-11-19 16:10 UTC (permalink / raw)
To: François Legal; +Cc: Julien Aube, xenomai
Philippe Gerum <rpm@xenomai.org> writes:
> François Legal <devel@thom.fr.eu.org> writes:
>
>> Le Mardi, Novembre 19, 2024 11:23 CET, Philippe Gerum <rpm@xenomai.org> a écrit:
>>
>>> François Legal <francois.legal@thom.fr.eu.org> writes:
>>>
>>> > Le Mardi, Novembre 19, 2024 10:26 CET, Julien Aube <julien.aube@smile.fr> a écrit:
>>> >
>>> >> Hello,
>>> >>
>>> >> Reading this exchange it reminds me of a problem I had a few months ago
>>> >> on the same platform.
>>> >>
>>> >> Here is the thead :
>>> >>
>>> >> https://lore.kernel.org/xenomai/6814fa90-015e-91df-6941-db643e4d4229@smile.fr/#r
>>> >>
>>> >>
>>> >> Conclusion was that disabling the scutimer(*) on DTS level was enough to
>>> >> restore the correct usage and I did not found
>>> >> any bad behaviour after that. The product has passed all the rt-test
>>> >> afterward.
>>> >>
>>> >>
>>> >> (*)
>>> >> &scutimer {
>>> >> /* scutimer is forced to disabled since it does not work with
>>> >> Xenomai */
>>> >> status = "disabled";
>>> >> };
>>> >>
>>> >> Maybe i'm completely off the subject, but maybe it's worth having a look ?
>>> >>
>>> >> Julien
>>> >>
>>> >>
>>> >
>>> > Thanks. That fixes the problem. I'll dig into that driver to try to fix it and submit a patch then.
>>> >
>>>
>>> This may help:
>>>
>>> diff --git a/arch/arm/kernel/smp_twd.c b/arch/arm/kernel/smp_twd.c
>>> index 8377f1d030c3a..a28f6b7f7eabc 100644
>>> --- a/arch/arm/kernel/smp_twd.c
>>> +++ b/arch/arm/kernel/smp_twd.c
>>> @@ -181,7 +181,7 @@ static irqreturn_t twd_handler(int irq, void *dev_id)
>>> {
>>> struct clock_event_device *evt = dev_id;
>>>
>>> - if (twd_timer_ack()) {
>>> + if (!clockevent_is_oob(evt) || twd_timer_ack()) {
>>> clockevents_handle_event(evt);
>>> return IRQ_HANDLED;
>>> }
>>>
>>
>> No noticeable effect here. I tried to dig a little more into this, but I can't find anything.
>> What I can tell, is that the TWD interrupts triggers on both cores when hung at boot. TWD registers settings seems OK in terms of prescaler and everything. By checking with JTAG debugger, I can see that xnintr_core_clock_handler is being called in the TWD service routine (twd_handler).
>>
>> I'm trying a little harder, but don't really know from which angle !
>
> The issue is as follows:
>
> When the proxy tick hijacks the timer to hand over its control to
> Xenomai, twd_handler() may be called either from the oob stage upon a
> real tick coming from the hardware, _and_ from the in-band stage as a
> consequence of emulating a common kernel tick, see [1] in the "Under the
> hood" section.
>
> The way twd_handler() operates ATM causes the hardware to be sent an ack
> on every invocation, which is wrong wrt the in-band tick emulation,
> which is most likely wrecking the logic afterwards.
>
> [1] https://v4.xenomai.org/dovetail/porting/timer/#proxy-tick-logic
diff --git a/arch/arm/kernel/smp_twd.c b/arch/arm/kernel/smp_twd.c
index 8377f1d030c3a..194d3cc7ca2c8 100644
--- a/arch/arm/kernel/smp_twd.c
+++ b/arch/arm/kernel/smp_twd.c
@@ -181,7 +181,7 @@ static irqreturn_t twd_handler(int irq, void *dev_id)
{
struct clock_event_device *evt = dev_id;
- if (twd_timer_ack()) {
+ if ((running_inband() && clockevent_is_oob(evt)) || twd_timer_ack()) {
clockevents_handle_event(evt);
return IRQ_HANDLED;
}
--
Philippe.
^ permalink raw reply related [flat|nested] 23+ messages in thread
* Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
2024-11-19 16:10 ` Philippe Gerum
@ 2024-11-19 17:04 ` François Legal
0 siblings, 0 replies; 23+ messages in thread
From: François Legal @ 2024-11-19 17:04 UTC (permalink / raw)
To: Philippe Gerum; +Cc: Julien Aube, xenomai
Le Mardi, Novembre 19, 2024 17:10 CET, Philippe Gerum <rpm@xenomai.org> a écrit:
> Philippe Gerum <rpm@xenomai.org> writes:
>
> > François Legal <devel@thom.fr.eu.org> writes:
> >
> >> Le Mardi, Novembre 19, 2024 11:23 CET, Philippe Gerum <rpm@xenomai.org> a écrit:
> >>
> >>> François Legal <francois.legal@thom.fr.eu.org> writes:
> >>>
> >>> > Le Mardi, Novembre 19, 2024 10:26 CET, Julien Aube <julien.aube@smile.fr> a écrit:
> >>> >
> >>> >> Hello,
> >>> >>
> >>> >> Reading this exchange it reminds me of a problem I had a few months ago
> >>> >> on the same platform.
> >>> >>
> >>> >> Here is the thead :
> >>> >>
> >>> >> https://lore.kernel.org/xenomai/6814fa90-015e-91df-6941-db643e4d4229@smile.fr/#r
> >>> >>
> >>> >>
> >>> >> Conclusion was that disabling the scutimer(*) on DTS level was enough to
> >>> >> restore the correct usage and I did not found
> >>> >> any bad behaviour after that. The product has passed all the rt-test
> >>> >> afterward.
> >>> >>
> >>> >>
> >>> >> (*)
> >>> >> &scutimer {
> >>> >> /* scutimer is forced to disabled since it does not work with
> >>> >> Xenomai */
> >>> >> status = "disabled";
> >>> >> };
> >>> >>
> >>> >> Maybe i'm completely off the subject, but maybe it's worth having a look ?
> >>> >>
> >>> >> Julien
> >>> >>
> >>> >>
> >>> >
> >>> > Thanks. That fixes the problem. I'll dig into that driver to try to fix it and submit a patch then.
> >>> >
> >>>
> >>> This may help:
> >>>
> >>> diff --git a/arch/arm/kernel/smp_twd.c b/arch/arm/kernel/smp_twd.c
> >>> index 8377f1d030c3a..a28f6b7f7eabc 100644
> >>> --- a/arch/arm/kernel/smp_twd.c
> >>> +++ b/arch/arm/kernel/smp_twd.c
> >>> @@ -181,7 +181,7 @@ static irqreturn_t twd_handler(int irq, void *dev_id)
> >>> {
> >>> struct clock_event_device *evt = dev_id;
> >>>
> >>> - if (twd_timer_ack()) {
> >>> + if (!clockevent_is_oob(evt) || twd_timer_ack()) {
> >>> clockevents_handle_event(evt);
> >>> return IRQ_HANDLED;
> >>> }
> >>>
> >>
> >> No noticeable effect here. I tried to dig a little more into this, but I can't find anything.
> >> What I can tell, is that the TWD interrupts triggers on both cores when hung at boot. TWD registers settings seems OK in terms of prescaler and everything. By checking with JTAG debugger, I can see that xnintr_core_clock_handler is being called in the TWD service routine (twd_handler).
> >>
> >> I'm trying a little harder, but don't really know from which angle !
> >
> > The issue is as follows:
> >
> > When the proxy tick hijacks the timer to hand over its control to
> > Xenomai, twd_handler() may be called either from the oob stage upon a
> > real tick coming from the hardware, _and_ from the in-band stage as a
> > consequence of emulating a common kernel tick, see [1] in the "Under the
> > hood" section.
> >
> > The way twd_handler() operates ATM causes the hardware to be sent an ack
> > on every invocation, which is wrong wrt the in-band tick emulation,
> > which is most likely wrecking the logic afterwards.
> >
> > [1] https://v4.xenomai.org/dovetail/porting/timer/#proxy-tick-logic
>
> diff --git a/arch/arm/kernel/smp_twd.c b/arch/arm/kernel/smp_twd.c
> index 8377f1d030c3a..194d3cc7ca2c8 100644
> --- a/arch/arm/kernel/smp_twd.c
> +++ b/arch/arm/kernel/smp_twd.c
> @@ -181,7 +181,7 @@ static irqreturn_t twd_handler(int irq, void *dev_id)
> {
> struct clock_event_device *evt = dev_id;
>
> - if (twd_timer_ack()) {
> + if ((running_inband() && clockevent_is_oob(evt)) || twd_timer_ack()) {
> clockevents_handle_event(evt);
> return IRQ_HANDLED;
> }
>
No noticeable effect here too.
I tried to modify the code on my side to "mimick" the behaviour of global_timer without luck.
François
> --
> Philippe.
^ permalink raw reply [flat|nested] 23+ messages in thread
end of thread, other threads:[~2024-11-19 17:04 UTC | newest]
Thread overview: 23+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-11-18 8:50 Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail François Legal
2024-11-18 9:01 ` Jan Kiszka
2024-11-18 10:21 ` François Legal
2024-11-18 10:32 ` Florian Bezdeka
2024-11-18 11:18 ` François Legal
2024-11-18 11:37 ` Philippe Gerum
2024-11-18 12:06 ` Florian Bezdeka
2024-11-18 13:21 ` François Legal
2024-11-18 13:37 ` Philippe Gerum
2024-11-18 13:57 ` Florian Bezdeka
2024-11-18 14:49 ` Philippe Gerum
2024-11-18 15:22 ` François Legal
2024-11-18 15:33 ` Philippe Gerum
2024-11-19 7:26 ` François Legal
2024-11-19 9:26 ` Julien Aube
2024-11-19 10:06 ` François Legal
2024-11-19 10:23 ` Philippe Gerum
2024-11-19 14:30 ` Philippe Gerum
2024-11-19 14:36 ` François Legal
2024-11-19 14:55 ` Philippe Gerum
2024-11-19 16:10 ` Philippe Gerum
2024-11-19 17:04 ` François Legal
2024-11-18 13:38 ` François Legal
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.