SVC_NUM_DATA_IN_FIFO(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… SVC_NUM_DATA_IN_FIFO πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” this is the page for SVC_NUM_DATA_IN_FIFO, and it is literally the shortest little icon in the stratix10 firmware universe, so grab a boba and let's go πŸ§‹βœ¨


🌸 NAME 🌸

SVC_NUM_DATA_IN_FIFO β€” number of struct stratix10_svc_data in the FIFO πŸŽ€


✨ SYNOPSIS ✨

SVC_NUM_DATA_IN_FIFO

that's it. that's the whole synopsis. no arguments, no flags, no drama. she's a constant and she knows it πŸ’…


πŸ’– DESCRIPTION πŸ’–

so the headline says this one is the number of struct stratix10_svc_data in the FIFO β€” but the description goes off and introduces the rest of the little constant friend group instead, and honestly? slay. here's who's who in the group chat 🫢

  • SVC_NUM_CHANNEL β€” number of channel supported by service layer driver. that's her. that's the count of channels the service layer driver can handle 🌈
  • FPGA_CONFIG_DATA_CLAIM_TIMEOUT_MS β€” this is the "claim it back" timeout, ms edition ⏱️ it's how you claim back the submitted buffer(s) from the secure world so the FPGA manager can reuse them, or so the buffer(s) get freed when all bit-stream data had be send πŸ”₯
  • FPGA_CONFIG_STATUS_TIMEOUT_SEC β€” the poll timer for the FPGA configuration status πŸ‘‘ the service layer will return error to FPGA manager when timeout occurs. and the timeout is set to 30 seconds (30 * 1000) at Intel Stratix10 SoC. no cap, that's the number πŸ“
ngl, this page's NAME and DESCRIPTION are kind of a vibe check mismatch β€” the description is out here documenting the sibling constants. but every one of them is real and every one is listed, so we keep them all πŸ’€πŸ’œ

πŸ¦‹ SEE ALSO πŸ¦‹

everything below is in the kernel file ./drivers/firmware/stratix10-svc.c, plus a truly iconic amount of sibling functions β€” keep the whole list, it's giving "the entire extended family showed up to the function" 😭

Kernel file ./drivers/firmware/stratix10-svc.c struct stratix10_svc(9),
struct stratix10_svc_sh_memory(9), struct stratix10_svc_data_mem(9),
struct stratix10_svc_data(9), struct stratix10_svc_async_handler(9),
struct stratix10_async_chan(9), struct stratix10_async_ctrl(9), struct
stratix10_svc_chan(9), struct stratix10_svc_controller(9),
svc_pa_to_va(9), svc_thread_cmd_data_claim(9),
svc_thread_cmd_config_status(9), svc_thread_recv_status_ok(9),
svc_normal_to_secure_thread(9), svc_normal_to_secure_shm_thread(9),
svc_get_sh_memory(9), svc_create_memory_pool(9), svc_smccc_smc(9),
svc_smccc_hvc(9), svc_smccc_1_2_full(9), get_invoke_func(9),
stratix10_svc_request_channel_byname(9),
stratix10_svc_add_async_client(9), stratix10_svc_remove_async_client(9),
stratix10_svc_async_send(9), stratix10_svc_async_prepare_response(9),
stratix10_svc_async_poll(9), stratix10_svc_async_done(9),
stratix10_svc_async_init(9), stratix10_svc_async_exit(9),
stratix10_svc_free_channel(9), stratix10_svc_send(9),
stratix10_svc_done(9), stratix10_svc_allocate_memory(9),
stratix10_svc_free_memory(9)

and that's the whole page, bestie πŸŽ€ it lives in ./drivers/firmware, dated October 2026, and it's part of the SVC_NUM_DATA_IN_FIFO(9) manual. go read a struct, ily, drink water πŸ’œπŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from