ctucan_chip_start(9)
π ctucan_chip_start(9) β Kernel API Manual energy π
okay so bestie, we're in the Kernel API Manual and this page is literally about ctucan_chip_start(9). It's giving "kernel routine that starts the driver" and I'm obsessed. π
πΈ NAME πΈ
ctucan_chip_start β this routine starts the driver. periodt. π
β¨ SYNOPSIS β¨
int ctucan_chip_start (struct net_device *ndev );
π¦ ARGUMENTS π¦
ndevβ pointer to thenet_devicestructure. That's the whole argument list, bestie. π«Ά
π DESCRIPTION π
Okay so this routine expects that the chip is in reset state. Heads up, that part matters. β οΈ
Then it does its little main-character sequence: it sets up initial Tx buffers for FIFO priorities, sets bittiming, enables interrupts, switches the core to operational mode, and changes the controller state to CAN_STATE_STOPPED. Slay. β¨
π₯ RETURN π₯
0 on success, and a failure value on error. no cap. π
π SEE ALSO π
Kernel file: ./drivers/net/can/ctucanfd/ctucanfd_base.c
ctucan_state_to_str(9)ctucan_reset(9)ctucan_set_btr(9)ctucan_set_bittiming(9)ctucan_set_data_bittiming(9)ctucan_set_secondary_sample_point(9)ctucan_set_mode(9)ctucan_do_set_mode(9)ctucan_get_tx_status(9)ctucan_is_txt_buf_writable(9)ctucan_insert_frame(9)ctucan_give_txtb_cmd(9)ctucan_start_xmit(9)ctucan_read_rx_frame(9)ctucan_rx(9)ctucan_read_fault_state(9)ctucan_get_rec_tec(9)ctucan_err_interrupt(9)ctucan_rx_poll(9)ctucan_rotate_txb_prio(9)ctucan_tx_interrupt(9)ctucan_interrupt(9)ctucan_chip_stop(9)ctucan_open(9)ctucan_close(9)ctucan_get_berr_counter(9)
mwah π β source: ./drivers/net/can/ctucanfd, date: October 2026, manual: ctucan_chip_start(9). byeeee π§
π¦ 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