Skip to content

Conversation

@jwang12340
Copy link

Note: Please adhere to Contributing Guidelines.

Summary

This change is to allow errmask to be set to CAN_ERR_FLAG, so that error frames with id 0 can also pass the err filter.
e,g, for LIN protocol, the error frame ID can be 0.

Impact

socketcan err mask

For the LIN protocol, the error frame ID can be 0. This change is to ensure that all LIN error frames can pass the filter.

Signed-off-by: wangjinjing1 <[email protected]>
@github-actions github-actions bot added Area: Networking Effects networking subsystem Size: XS The size of the change in this PR is very small labels Jan 14, 2026
}

conn->err_mask = *(FAR can_err_mask_t *)value & CAN_ERR_MASK;
conn->err_mask = *(FAR can_err_mask_t *)value;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jwang12340 what is the relation between LIN and the CAN driver? I think this are different things. BTW where is the LIN support you are referring to?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LIN and CAN are different on driver level, but above in software protocal level the lin frame can be process by socket CAN with standard CAN protocal, LIN related flags are defined in "include/nuttx/lin.h".

@acassis acassis requested a review from pkarashchenko January 14, 2026 14:06
@acassis
Copy link
Contributor

acassis commented Jan 14, 2026

@pkarashchenko since you working with LIN, could you please a look? I'm confuse about this CAN and LIN correlation. I think they should be different things

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: Networking Effects networking subsystem Size: XS The size of the change in this PR is very small

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants