pch_i2c_repstart(9)

📦 version 7.3.1, in nixpkgs unstable

💅 pch_i2c_repstart — the "okay we're starting again, but make it a vibe" page

Hey bestie, welcome to the pch_i2c_repstart(9) glow-up ✨ — it's a Kernel API Manual entry, section 9, and it's lowkey one of the most dramatic little functions in the i2c-eg20t world.

🌸 NAME 🌸

pch_i2c_repstart — generate a repeated start condition in normal mode. Yeah. A repeated start. Like when the convo isn't over but someone hits "new topic" in the group chat 🫶

✨ SYNOPSIS ✨

void pch_i2c_repstart (struct i2c_algo_pch_data *adap );

It returns void, meaning it gives you nothing back — no return value, no exit status, just pure main-character action 💅 Not me calling a function that doesn't even say "you're welcome" 😭

🎀 ARGUMENTS 🎀

  • adap — a pointer to struct i2c_algo_pch_data. That's it. That's the whole thing. Hand it the adapter data and let it cook 🔥

🦋 SEE ALSO 🦋

Okay so this is the part where I introduce you to the whole friend group, because pch_i2c_repstart(9) is not solo — it's giving ensemble cast energy 👑

The kernel file lives at ./drivers/i2c/busses/i2c-eg20t.c, and here's everyone who hangs out with this function:

Like, that's the whole roster — start, stop, restart, ack, nack, read, write, the callback, the handler, the transfer, the func, the interrupt disable… every single one of them is linked here and you will be clicking through all of them, iykyk 💀

🌈 Quick vibe check: this page gives you exactly one argument pointer and one void, and zero extra lore. No defaults, no environment variables, no files beyond that one source path, no exit statuses, no signals — if you were waiting for a twist, the twist is that it's genuinely that straightforward. Slay for being thorough though 🥰

Okay bye bestie, go generate that repeated start 💖

— source: ./drivers/i2c/busses · dated October 2026 · pch_i2c_repstart(9) signing off, periodt 🎀⭐🧚

📦 where this page comes from