STRUCT L3_FLAGMUX_DATA(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct l3_flagmux_data(9) β€” Flag Mux information

okay bestie, so this is a Kernel API Manual page and today's main character is struct l3_flagmux_data β€” literally just the Flag Mux information. that's the whole vibe. ✨


πŸŽ€ SYNOPSIS πŸŽ€

here's the whole struct, exactly as it lives, no cap:

struct l3_flagmux_data {
    u32 offset;
    struct l3_target_data *l3_targ;
    u8 num_targ_data;
    u32 mask_app_bits;
    u32 mask_dbg_bits;
 };

πŸ¦‹ Members πŸ¦‹

  • offset β€” how far you gotta scoot from base to reach the flagmux register. it's giving "starting coordinates" energy πŸ’«
  • l3_targ β€” an array indexed by the flagmux index (that's the bit offset, iykyk) and each slot points at the target data. the ones that just don't get support are marked with L3_TARGET_NOT_SUPPORTED β€” not everyone gets an invite to the party πŸ™ˆ
  • num_targ_data β€” literally the number of entries in the target data. the headcount. the guest list length πŸŽ€
  • mask_app_bits β€” ignore these bits from the raw application irq status. we do not perceive them. we do not see them. πŸ’…
  • mask_dbg_bits β€” same deal but for the raw debug irq status. also ignored, also unperceived. 🫢

🌈 SEE ALSO 🌈

  • the kernel file ./drivers/bus/omap_l3_noc.h
  • struct l3_masters_data(9)
  • struct l3_target_data(9)
  • struct omap_l3(9)

go read those, they're the friend group πŸ‘‘


okay that's the whole page, slay πŸ¦‹ this little icon came from the ./drivers/bus directory, dated October 2026, and the man page goes by struct l3_flagmux_data(9) β€” mwah, periodt πŸ’–πŸŽ€

πŸ“¦ where this page comes from