parport_read(9)

💖 parport_read(9) — straight from the Kernel API Manual 💖

okay bestie, welcome to the page for parport_read(9) in the Kernel API Manual. It’s giving read a block of data from a parallel port and I’m obsessed. Let’s go ✨

🎀 NAME 🎀

parport_read — read a block of data from a parallel port. no cap, that’s the whole name vibe 💅

🌟 SYNOPSIS 🌟

ssize_t parport_read (struct parport *port , void *buffer , size_t len
);

💅 ARGUMENTS 💅

• port — the port to read from, bestie. pick your parallel port 🫶
• buffer — the data buffer, and yes it’s in kernel space 💖
• len — how many bytes of data to transfer.

🦋 DESCRIPTION 🦋

So this function will read up to len bytes of buffer to the port specified, using the IEEE 1284 transfer mode most recently negotiated to (using parport_negotiate), as long as that mode supports reverse transfers (peripheral to host). iconic behavior, honestly 🌈

It is the caller’s responsibility to ensure that the first len bytes of buffer are available to write to. That’s on you, not me 💀

This function returns the number of bytes transferred (if zero or positive), or else an error code. slay, but keep an eye on that error code 👑

🍓 SEE ALSO 🍓

The Kernel file ./drivers/parport/ieee1284.c is where the squad lives. Go say hi to:

• parport_wait_event(9)
• parport_poll_peripheral(9)
• parport_wait_peripheral(9)
• parport_negotiate(9)
• parport_write(9)
• parport_set_timeout(9)

byeee bestie, the source/version footer is ./drivers/parport, dated October 2026 💜✨