ENUM ES58X_SYNC_EDGE(9)
π NAME π
okay so bestie, this is the enum es58x_sync_edge(9) page from the Kernel API Manual, and it's literally about the synchronization method. that's it, that's the vibe. β¨
enum es58x_sync_edgeβ the synchronization method. periodt. π
π¦ SYNOPSIS π¦
here's the enum in all its exact glory β do not come for the formatting, it's copied character for character π«Ά
enum es58x_sync_edge {
ES58X_SYNC_EDGE_SINGLE
};
π Constants π
ES58X_SYNC_EDGE_SINGLEβ okay so the ISO CAN specification defines the use of a single edge synchronization. the synchronization should be done on recessive to dominant level change. no cap. π
π Description π
just for information, bestie: ES582.1 and ES584.1 also support a double synchronization, requiring both recessive to dominant then dominant to recessive level change. however, this is not supported in SocketCAN framework, thus, the enum has only one member. it's giving βone member because the framework said noβ π
π SEE ALSO π
go peek at the kernel file ./drivers/net/can/usb/etas_es58x/es58x_core.h and these absolute icons:
enum es58x_driver_info(9)enum es58x_physical_layer(9)enum es58x_flag(9)enum es58x_err(9)enum es58x_event(9)struct es58x_priv(9)struct es58x_parameters(9)struct es58x_operators(9)struct es58x_sw_version(9)struct es58x_hw_revision(9)struct es58x_device(9)es58x_sizeof_es58x_device(9)es58x_check_msg_len(9)es58x_check_msg_max_len(9)es58x_msg_num_element(9)es58x_priv(9)ES58X_SIZEOF_URB_CMD(9)es58x_get_urb_cmd_len(9)es58x_get_netdev(9)es58x_get_raw_can_id(9)es58x_get_flags(9)
mwah π this page lives at ./drivers/net/can/usb/etas_es58x, October 2026 edition, and it's serving enum es58x_sync_edge(9) realness. bye bestie π«Ά
π¦ 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