cscfg_csdev_...ctive_config(9)
β¨ NAME β¨
This is the cscfg_csdev_...ctive_config(9) page from the Kernel API Manual, bestie π. The function is cscfg_csdev_enable_active_config β it enables the matching active configuration for a device. Periodt.
π οΈ SYNOPSIS π οΈ
int cscfg_csdev_enable_active_config (struct coresight_device *csdev ,
unsigned long cfg_hash , int preset );
π ARGUMENTS π
csdevβ the CoreSight device to program. Like, the actual device getting the config treatment π«Άcfg_hashβ the selector for the configuration. It's giving "which config are we talking about?" energy πpresetβ preset parameter values to use, with0meaning current / default values. So0is the chill "use what's already there" option β¨
πΈ DESCRIPTION πΈ
Okay so this function enables the configuration selected by cfg_hash if that configuration is supported on the device and has been activated. Both boxes checked, bestie π
If it's active and supported, the CoreSight device csdev will be programmed with the configuration, using preset parameters. Slay π₯
Timing check, no cap: this should be called before driver hardware enable for the requested device, prior to programming and enabling the physical hardware. So yeah β before the hardware gets switched on and programmed, this needs its moment π
π¦ SEE ALSO π¦
Kernel file: ./drivers/hwtracing/coresight/coresight-syscfg.c
cscfg_load_config_sets(9)cscfg_unload_config_sets(9)cscfg_register_csdev(9)cscfg_unregister_csdev(9)cscfg_csdev_reset_feats(9)cscfg_activate_config(9)cscfg_deactivate_config(9)cscfg_csdev_disable_active_config(9)
That's the whole page, bestie π
Signing off from ./drivers/hwtracing/coresight, dated October 2026, with page cscfg_csdev_...ctive_config(9) β mwah π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms