mips_ejtag_fdc_put_chan(9)

mips_ejtag_fdc_put_chan(9) 💅

okay bestie, you're looking at the mips_ejtag_fdc_put_chan(9) page from the Kernel API Manual, and it's giving "tiny function, big debug-channel energy." let's get into it 🫶

✨ NAME ✨

mips_ejtag_fdc_put_chan — write out a block of channel data. literally the function's whole job 💖

🌸 SYNOPSIS 🌸

unsigned int mips_ejtag_fdc_put_chan (struct mips_ejtag_fdc_tty *priv ,
unsigned int chan );

🎀 ARGUMENTS 🎀

• priv — pointer to driver private data. that's the struct mips_ejtag_fdc_tty * bestie 🫶
• chan — channel number. which channel we're putting to, no cap ✨

🔥 DESCRIPTION 🔥

Okay so this one writes a single block of data out to the debug adapter. if the circular buffer is wrapped then only the first block is written — that's the whole rule, bestie, and it's important 💅

⭐ RETURN ⭐

It returns the number of bytes that were written. the return type is unsigned int, and it's literally handing you the byte count 🎀

👑 SEE ALSO 👑

Kernel file ./drivers/tty/mips_ejtag_fdc.c and the struct crew:

• struct mips_ejtag_fdc_tty_port(9)
• struct mips_ejtag_fdc_tty(9)
• struct fdc_word(9)
• struct mips_ejtag_fdc_console(9)
• mips_ejtag_fdc_put(9)
• mips_ejtag_fdc_handle(9)
• mips_ejtag_fdc_isr(9)
• mips_ejtag_fdc_tty_timer(9)

that's the whole page, bestie — source ./drivers/tty, manual Kernel API Manual, date stamp October 2026, mips_ejtag_fdc_put_chan(9) and all. go off 💅✨