drivers: can: mchp_mss: New #95698
drivers: can: mchp_mss: New #95698
Conversation
|
@con-pax Please have a look at this pull request. |
zephyrbot
added
area: CAN
area: RISCV
zephyrbot
requested review from
albertofloyd,
alexanderwachter,
edersondisouza,
fkokosinski,
henrikbrixandersen,
jvasanth1,
katsuster,
kgugala,
martinjaeger,
mgielda,
npitre,
str4t0m,
tgorochowik,
VenkatKotakonda and
ycsin
sebhub
force-pushed
the
add-can-mchp-mss
branch
3 times, most recently
from
cb8a282 to
8209b29
Compare
@sebhub to expand on this, using the API as described in the official docs, e.g. calling due to type punning in mss_can_send. The controller sends out bytes MSB to LSB, hence the bus order inversion ( |
Add a CAN driver for Microchip's PolarFire SoC platform. Signed-off-by: Sebastian Huber <[email protected]>
sebhub
force-pushed
the
add-can-mchp-mss
branch
from
8209b29 to
556a01f
Compare
Enable the swap endian configuration of the controller to get the behavior expected by the Zephyr CAN API. Co-authored-by: Sebastian Huber <[email protected]> Signed-off-by: Sebastian Huber <[email protected]> Signed-off-by: Donato Brusamento <[email protected]>
|
I had a flaw in my test setup. I use an MPFS which is connected through a CAN bus to an STM32H7 running Zephyr. In my initial test setup, the STM32H7 simply retransmitted received CAN messages. This setup cannot detect these endian issues. I changed the test setup to check also transfers in one direction. Indeed, the swap endian configuration is required. I pushed a commit based on #96938 which fixes the issue. |
|
Add a CAN driver for Microchip's PolarFire SoC platform.