ENUM MEDIA_PAD_SIGNAL_TYPE(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

enum media_pad_signal_type — bestie, it's literally the type of the signal flowing inside a media pad ✨ (this is from the Kernel API Manual, iykyk)

🎀 SYNOPSIS 🎀

enum media_pad_signal_type {
    PAD_SIGNAL_DEFAULT ,
    PAD_SIGNAL_ANALOG ,
    PAD_SIGNAL_DV ,
    PAD_SIGNAL_AUDIO

};

Ok so that's the whole vibe: one enum, four constants, no cap 💅

🦋 Constants 🦋

  • PAD_SIGNAL_DEFAULT — the default signal, the "no thoughts head empty" option 🫶. Use this one when all your inputs or all your outputs are uniquely identified by the pad number. That's it, that's the whole condition.
  • PAD_SIGNAL_ANALOG — the pad is carrying an analog signal 🔥. That can be Radio Frequency, Intermediate Frequency, a baseband signal, or sub-carriers. Tuner inputs, IF-PLL demodulators, and composite and s-video signals should use it. (yes, all of those, she contains multitudes 💜)
  • PAD_SIGNAL_DV — digital video signal energy 🎀. It can be a bitstream of samples taken from an analog TV video source. In that case, it usually contains the VBI data on it. It's giving "digital glow-up of an analog situation" ✨
  • PAD_SIGNAL_AUDIO — audio moment 🍓. It contains an Intermediate Frequency analog signal from an audio sub-carrier, or an audio bitstream. IF signals are provided by tuners and consumed by audio AM/FM decoders. Bitstream audio is provided by an audio decoder. Two paths, same iconic enum value 👑
ngl bestie, picking the right constant here is a whole vibe check — the wrong one and your pad is lying about what it's carrying 😭

🌈 SEE ALSO 🌈

Kernel file ./include/media/media-entity.h and, like, the entire friend group 💖:

okay that's the whole page, go forth and annotate your pads correctly bestie 💅✨

mwah 💋 — this one lives in ./include/media, dated October 2026, and it's brought to you by the Kernel API Manual. slay 🫶

📦 where this page comes from