ov9282_fill_pad_format(9)

✨ NAME ✨

okay bestie, welcome to the ov9282_fill_pad_format(9) page from the Kernel API Manual 💅✨ Its whole thing? Fill subdevice pad format from selected sensor mode. That’s the assignment, no cap 🎀

🌸 SYNOPSIS 🌸

here’s the exact signature, serving void realness:

void ov9282_fill_pad_format (struct ov9282 *ov9282 , const struct
       ov9282_mode *mode , u32 code , struct v4l2_subdev_format *fmt );

🎀 ARGUMENTS 🎀

okay so here’s the cast, bestie 🫶

• ov9282 — pointer to the ov9282 device 👑
• mode — pointer to the ov9282_mode sensor mode 🌈
• code — the mbus code to be stored 💾
• fmt — the V4L2 sub-device format that needs to be filled 🦋

🦋 SEE ALSO 🦋

go peek at the Kernel file ./drivers/media/i2c/ov9282.c and these icons, iykyk:

• struct ov9282_reg_list(9)
• struct ov9282_mode(9)
• struct ov9282(9)
• to_ov9282(9)
• ov9282_update_controls(9)
• ov9282_update_exp_gain(9)
• ov9282_enum_frame_size(9)
• ov9282_detect(9)
• ov9282_parse_hw_config(9)
• ov9282_init_controls(9)

mwah 💋 this page is brought to you by the source/version ./drivers/media/i2c, dated October 2026, and yes it’s still the ov9282_fill_pad_format(9) manual — slay and goodnight 💖🎀🦋