ENUM XSDFEC_AXIS_WORD_INCLUDE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… enum xsdfec_axis_word_include β€” Words Configuration πŸ’…

okay so bestie, this one's from the Kernel API Manual and it's literally just a little enum that tells the driver how the DIN_WORDS situation should be configured ✨ no cap, that's the whole vibe. Let's get into it 🫢


🌈 SYNOPSIS 🌈

enum xsdfec_axis_word_include {
    XSDFEC_FIXED_VALUE ,
    XSDFEC_IN_BLOCK ,
    XSDFEC_PER_AXI_TRANSACTION ,
    XSDFEC_AXIS_WORDS_INCLUDE_MAX

};

πŸŽ€ Constants πŸŽ€

  • XSDFEC_FIXED_VALUE β€” Fixed, bestie πŸ’… the DIN_WORDS AXI4-Stream interface is removed from the IP instance entirely, and it gets driven with the specified number of words instead. it's giving "we don't need that port, we already know the number" energy ✨
  • XSDFEC_IN_BLOCK β€” In Block 🧚 this configures the IP instance to expect a single DIN_WORDS value per input code block. and yes, the DIN_WORDS interface is present here 🫢
  • XSDFEC_PER_AXI_TRANSACTION β€” Per Transaction 🌸 this one configures the IP instance to expect one DIN_WORDS value per input transaction on the DIN interface. the DIN_WORDS interface is present for this one too πŸ’–
  • XSDFEC_AXIS_WORDS_INCLUDE_MAX β€” the boundary queen πŸ‘‘ used to indicate out-of-bound Words Configurations. she's the max, she marks the edge, that's her whole job πŸ’€

πŸ¦‹ Description πŸ¦‹

so what does this enum actually do? literally just this: it's used to specify the DIN_WORDS configuration ⭐ that's it. that's the tea β˜•


πŸ¦„ SEE ALSO πŸ¦„

<KERNEL FILE> β†’ ./include/uapi/misc/xilinx_sdfec.h πŸ“

and the whole friend group 🫢:


ngl bestie, if you ever see XSDFEC_AXIS_WORDS_INCLUDE_MAX coming back at you from a config, that's an out-of-bound value and it's not a valid setting πŸ™ˆ that's your vibe check failing πŸ’€

and that's the whole page, periodt πŸ’… this icon lives over in ./include/uapi/misc, dated October 2026 🌸 mwah, go read the header, ily, bye πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from