cscfg_csdev_...ctive_config(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ 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, with 0 meaning current / default values. So 0 is 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


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