Re: [PATCH v5 0/7] can: refactoring of can-dev module and of Kbuild

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Vincent,

great work!

On 04.06.22 18:29, Vincent Mailhol wrote:

* menu after this series *

Network device support
   symbol: CONFIG_NETDEVICES
   |
   +-> CAN Device Drivers
       symbol: CONFIG_CAN_DEV
       |
       +-> software/virtual CAN device drivers
       |   (at time of writing: slcan, vcan, vxcan)
       |
       +-> CAN device drivers with Netlink support
           symbol: CONFIG_CAN_NETLINK (matches previous CONFIG_CAN_DEV)
           |
           +-> CAN bit-timing calculation (optional for all drivers)
           |   symbol: CONFIG_CAN_BITTIMING
           |
           +-> All other CAN devices not relying on RX offload
           |
           +-> CAN rx offload
               symbol: CONFIG_CAN_RX_OFFLOAD

Is this still true in patch series 5?

If I understood it correctly CONFIG_CAN_BITTIMING and CONFIG_CAN_RX_OFFLOAD can be enabled by the user and (alternatively/additionally) the selection of "flexcan, m_can, mcp251xfd and ti_hecc" enables CONFIG_CAN_RX_OFFLOAD too.

Right?

               |
               +-> CAN devices relying on rx offload
                   (at time of writing: flexcan, m_can, mcp251xfd and ti_hecc)

Best regards,
Oliver



[Index of Archives]     [Automotive Discussions]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [CAN Bus]

  Powered by Linux