pdcs_register_pathentries(9)
π NAME π
pdcs_register_pathentries β bestie, this is the one that preps your path entries' kobjects so sysfs can actually use them β¨
πΈ SYNOPSIS πΈ
int pdcs_register_pathentries (void );
π ARGUMENTS π
voidβ no arguments, not a single one, she takes nothing and gives everything π«Ά
π¦ DESCRIPTION π¦
Okay so here's the tea β β this function creates a kobject for each path entry, and it gives every one of them nice sysfs links pointing back at the real device. Iconic behavior, honestly.
This is where the magic takes place, like literally the main-character moment: when you register the subsystem attributes during module init, each kobject created here will show up in the sysfs tree as a folder π β and that folder contains files as defined by path_subsys_attr[]. That's the whole vibe. No cap.
π SEE ALSO π
The kernel file lives at ./drivers/parisc/pdc_stable.c, and the whole friend group is here π:
pdcspath_fetch(9)pdcspath_store(9)pdcspath_hwpath_read(9)pdcspath_hwpath_write(9)pdcspath_layer_read(9)pdcspath_layer_write(9)pdcspath_attr_show(9)pdcspath_attr_store(9)pdcs_size_read(9)pdcs_auto_read(9)pdcs_autoboot_read(9)pdcs_autosearch_read(9)pdcs_timer_read(9)pdcs_osid_read(9)pdcs_osdep1_read(9)pdcs_diagnostic_read(9)pdcs_fastsize_read(9)pdcs_osdep2_read(9)pdcs_auto_write(9)pdcs_autoboot_write(9)pdcs_autosearch_write(9)pdcs_osdep1_write(9)pdcs_osdep2_write(9)pdcs_unregister_pathentries(9)
That's the whole page, bestie β brought to you by the Kernel API Manual π
from ./drivers/parisc, dated October 2026. Go forth and register those pathentries, periodt. π§π
π¦ 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