UNION NPS_PKT_IN_INSTR_CTL(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– union nps_pkt_in_instr_ctl(9) πŸ’–

okay so welcome to the Kernel API Manual, bestie ✨. This page is all about union nps_pkt_in_instr_ctl, and it is literally giving Input Instruction Ring Control Registers energy. no cap, it’s a whole union situation and we’re gonna read it together 🫢.


🌸 NAME 🌸

union nps_pkt_in_instr_ctl β€” Input Instruction Ring Control Registers. πŸŽ€


✨ SYNOPSIS ✨

here’s the exact shape, bestie β€” same fields, same order, same preprocessor drama:

       union nps_pkt_in_instr_ctl {
           u64 value;
           struct {
         #if (defined(__BIG_ENDIAN_BITFIELD));
             u64 raz : 62;
             u64 is64b : 1;
             u64 enb : 1;
         #else;
             u64 enb : 1;
             u64 is64b : 1;
             u64 raz : 62;
         #endif;
           } s;
        };

the way this union is set up is lowkey straightforward on the surface: there’s value as a u64, and there’s s, a struct holding bitfields. when __BIG_ENDIAN_BITFIELD is defined, the order inside s is raz : 62, then is64b : 1, then enb : 1. in the #else branch it flips to enb : 1, then is64b : 1, then raz : 62. that’s the whole synopsis vibe πŸ¦‹.


πŸŽ€ Members πŸŽ€

okay bestie, this section is literally empty in the original β€” there are no member descriptions listed under Members to spill. the fields themselves are up in the SYNOPSIS code block, being iconic. don’t come for me, I’m just reporting the vibe πŸ’….


πŸ”— SEE ALSO πŸ”—

the kernel file for this one is ./drivers/crypto/cavium/nitrox/nitrox_csr.h 🫢. also, the source serves up this whole friend group of union pages:

  • union ucd_core_eid_ucode_block_num(9)
  • union aqm_grp_execmsk_lo(9)
  • union aqm_grp_execmsk_hi(9)
  • union aqmq_drbl(9)
  • union aqmq_qsz(9)
  • union aqmq_cmp_thr(9)
  • union aqmq_cmp_cnt(9)
  • union aqmq_en(9)
  • union aqmq_activity_stat(9)
  • union emu_fuse_map(9)
  • union emu_se_enable(9)
  • union emu_ae_enable(9)
  • union emu_wd_int_ena_w1s(9)
  • union emu_ge_int_ena_w1s(9)
  • union nps_pkt_slc_ctl(9)
  • union nps_pkt_slc_cnts(9)
  • union nps_pkt_slc_int_levels(9)
  • union nps_pkt_in_done_cnts(9)
  • union nps_pkt_in_instr_rsize(9)
  • union nps_pkt_in_instr_baoff_dbell(9)
  • union nps_core_int_ena_w1s(9)
  • union nps_core_gbl_vfcfg(9)
  • union nps_core_int_active(9)
  • union efl_core_int(9)
  • union efl_core_int_ena_w1s(9)
  • union efl_rnm_ctl_status(9)
  • union bmi_ctl(9)
  • union bmi_int_ena_w1s(9)
  • union bmo_ctl2(9)
  • union pom_int_ena_w1s(9)
  • union lbc_inval_ctl(9)
  • union lbc_int_ena_w1s(9)
  • union lbc_int(9)
  • union lbc_inval_status(9)
  • union rst_boot(9)
  • union fus_dat1(9)

final sign-off bestie: the footer gives the source/version as ./drivers/crypto/cavium/nitrox, the date as October 2026, and it still says union nps_pkt_in_instr_ctl(9) at the very end. mwah, bye πŸ’‹πŸŒ™

πŸ“¦ where this page comes from