smsm_inbound_entry(9)
πΈ NAME πΈ
Okay bestie, meet smsm_inbound_entry from the Kernel API Manual π β itβs literally here to parse DT and set up an entry representing a remote system. No cap, thatβs the whole vibe. π
β¨ SYNOPSIS β¨
int smsm_inbound_entry (struct qcom_smsm *smsm , struct smsm_entry
*entry , struct device_node *node );
π ARGUMENTS π
smsmβ the smsm driver context, aka the driverβs little home base π«Άentryβ the entry context to be set up; this is the glow-up in progress β¨nodeβ the dt node containing the entryβs properties; all the deets live here π¦
π¦ SEE ALSO π¦
Kernel file ./drivers/soc/qcom/smsm.c β yes, thatβs the spot π
struct qcom_smsm(9)struct smsm_entry(9)struct smsm_host(9)smsm_update_bits(9)smsm_intr(9)smsm_mask_irq(9)smsm_unmask_irq(9)smsm_set_irq_type(9)smsm_irq_map(9)smsm_parse_mbox(9)smsm_parse_ipc(9)smsm_get_size_info(9)
Thatβs the whole page, bestie β iconic, honestly ππ Signing off from ./drivers/soc/qcom in October 2026, page smsm_inbound_entry(9) πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms