hns_dsaf_sbm...sram_init_en(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

Okay so this is one of those little kernel API manual pages β€” the kind that lives in the Linux kernel's man section 9 β€” and the file it's documented under is literally <rainbow>hns_dsaf_sbm...sram_init_en(9)</rainbow> because even the docs got tired of typing the whole thing out 😭. The real, full, un-truncated name is right below, no cap.


✨ NAME ✨

hns_dsaf_sbm_link_sram_init_en β€” config dsaf_sbm_init_en πŸŽ€

That's it. That's the whole pitch. It configs the dsaf_sbm_init_en thing. Iconic brevity, honestly.


πŸ¦‹ SYNOPSIS πŸ¦‹

void hns_dsaf_sbm_link_sram_init_en (struct dsaf_device *dsaf_dev );

Notice what's not there: no return value. It's void, bestie β€” it gives nothing back. It simply is 🧚


🌸 ARGUMENTS 🌸

  • dsaf_dev β€” the dsa fabric id πŸ’– (yes, the description really is just "dsa fabric id", four words, she said what she said)

That's the entire argument list. One pointer, one purpose, zero drama.


⭐ SEE ALSO ⭐

This is the part where it gets unhinged β€” the original rolls up with a whole friend group of 57 related functions, all section 9, and we're not leaving a single one behind 🫢. The kernel file to go look at is ./drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.c.

The whole squad, in the exact order they showed up:

hns_dsaf_reg_cnt_clr_ce(9), hns_dsaf_ppe_qid_cfg(9), hns_dsaf_sw_port_type_cfg(9), hns_dsaf_stp_port_type_cfg(9), hns_dsaf_sbm_cfg(9), hns_dsaf_sbm_cfg_mib_en(9), hns_dsaf_sbm_bp_wl_cfg(9), hns_dsaf_voq_bp_all_thrd_cfg(9), hns_dsaf_tbl_tcam_data_cfg(9), hns_dsaf_tbl_tcam_mcast_cfg(9), hns_dsaf_tbl_tcam_ucast_cfg(9), hns_dsaf_tbl_line_cfg(9), hns_dsaf_tbl_tcam_mcast_pul(9), hns_dsaf_tbl_line_pul(9), hns_dsaf_tbl_tcam_data_mcast_pul(9), hns_dsaf_tbl_tcam_data_ucast_pul(9), hns_dsaf_tbl_stat_en(9), hns_dsaf_rocee_bp_en(9), hns_dsaf_single_line_tbl_cfg(9), hns_dsaf_tcam_uc_cfg(9), hns_dsaf_tcam_mc_cfg(9), hns_dsaf_tcam_uc_cfg_vague(9), hns_dsaf_tcam_mc_cfg_vague(9), hns_dsaf_tcam_mc_invld(9), hns_dsaf_tcam_uc_get(9), hns_dsaf_tcam_mc_get(9), hns_dsaf_tbl_line_init(9), hns_dsaf_tbl_tcam_init(9), hns_dsaf_pfc_en_cfg(9), hns_dsaf_comm_init(9), hns_dsaf_inode_init(9), hns_dsaf_sbm_init(9), hns_dsaf_tbl_init(9), hns_dsaf_voq_init(9), hns_dsaf_init_hw(9), hns_dsaf_remove_hw(9), hns_dsaf_init(9), hns_dsaf_free(9), hns_dsaf_find_soft_mac_entry(9), hns_dsaf_find_empty_mac_entry(9), hns_dsaf_find_empty_mac_entry_reverse(9), hns_dsaf_set_mac_key(9), hns_dsaf_set_mac_uc_entry(9), hns_dsaf_add_mac_mc_port(9), hns_dsaf_del_mac_entry(9), hns_dsaf_del_mac_mc_port(9), hns_dsaf_free_dev(9), hns_dsaf_pfc_unit_cnt(9), hns_dsaf_port_work_rate_cfg(9), hns_dsaf_fix_mac_mode(9), hns_dsaf_get_regs(9), hns_dsaf_get_stats(9), hns_dsaf_get_sset_count(9), hns_dsaf_get_strings(9), hns_dsaf_get_regs_count(9), hns_dsaf_probe(9) and hns_dsaf_remove(9).

Like, why is hns_dsaf_probe(9) at the end? Main character energy of it all πŸ™ˆ go read them, they're all sitting right there in hns_dsaf_main.c β€” iykyk.

And that is the entire page, bestie β€” short, void, and to the point. It shipped under ./drivers/net/ethernet/hisilic... (the source path got cropped mid-word by the doc tooling, not by me, I would never 😭) and it's dated October 2026, footer and all. Slay. Periodt. πŸ’œπŸŽ€πŸ¦‹

πŸ“¦ where this page comes from