drivers/net/can/m_can/tcan4x5x.h
Source file repositories/reference/linux-study-clean/drivers/net/can/m_can/tcan4x5x.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/can/m_can/tcan4x5x.h- Extension
.h- Size
- 1149 bytes
- Lines
- 59
- Domain
- Driver Families
- Bucket
- drivers/net
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/gpio/consumer.hlinux/regmap.hlinux/regulator/consumer.hlinux/spi/spi.hm_can.h
Detected Declarations
struct tcan4x5x_map_bufstruct tcan4x5x_privfunction tcan4x5x_spi_cmd_set_len
Annotated Snippet
struct tcan4x5x_map_buf {
struct tcan4x5x_buf_cmd cmd;
u8 data[256 * sizeof(u32)];
} ____cacheline_aligned;
struct tcan4x5x_priv {
struct m_can_classdev cdev;
struct regmap *regmap;
struct spi_device *spi;
struct gpio_desc *reset_gpio;
struct gpio_desc *device_wake_gpio;
struct gpio_desc *device_state_gpio;
struct regulator *power;
struct tcan4x5x_map_buf map_buf_rx;
struct tcan4x5x_map_buf map_buf_tx;
bool nwkrq_voltage_vio;
};
static inline void
tcan4x5x_spi_cmd_set_len(struct tcan4x5x_buf_cmd *cmd, u8 len)
{
/* number of u32 */
cmd->len = len >> 2;
}
int tcan4x5x_regmap_init(struct tcan4x5x_priv *priv);
#endif
Annotation
- Immediate include surface: `linux/gpio/consumer.h`, `linux/regmap.h`, `linux/regulator/consumer.h`, `linux/spi/spi.h`, `m_can.h`.
- Detected declarations: `struct tcan4x5x_map_buf`, `struct tcan4x5x_priv`, `function tcan4x5x_spi_cmd_set_len`.
- Atlas domain: Driver Families / drivers/net.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.