chardriver upperCAN: support to independent set TX/RX FIFO size.

[OceanfromXiaomi]

Summary

support to independent set TX/RX FIFO size

Impact

Testing

[nuttxpr]

[Experimental Bot, please feedback here]

This PR summary is too short and lacks the necessary details for a proper review.

Here's a breakdown of what's missing and how to improve it:

Summary

• Why is this change necessary?
  • Is it a fix for a bug?
  • Is it an optimization for performance?
  • Is it a new feature request?
• What functional part of the code is being changed?
  • Be specific. Mention the driver, module, or subsystem affected. For example: "This PR adds support to independently set TX/RX FIFO sizes for the UART driver."
• How does the change exactly work?
  • Provide a technical explanation. For example:
    • "Two new configuration options are introduced to specify the desired FIFO sizes."
    • "The driver now allocates memory dynamically based on these configurations."
• Related Issues:
  • Are there any related issues on the NuttX or NuttX Apps repositories? If so, provide links.

Impact

You need to address each point in the impact section:

• New/Changed Feature: YES - Briefly describe the new feature.
• Impact on user: Likely YES - How will users interact with this new feature? Will they need to modify their configurations?
• Impact on build: Possibly YES - Are there any new build options users need to be aware of?
• Impact on hardware: Possibly YES - Does this change affect specific architectures or boards?
• Impact on documentation: YES - Documentation needs to be updated to explain the new feature and how to use it.
• Impact on security: Maybe NO - Consider if there are any security implications.
• Impact on compatibility: Possibly YES - Does this change break compatibility with any existing code or configurations?
• Anything else to consider: Mention any other noteworthy aspects of the change.

Testing

• Provide more details: List the specific operating systems, compilers, target architectures, boards, and configurations you tested on.
• Show your logs: Include relevant snippets from your testing logs that demonstrate the change's functionality both before and after the modification.

In short, you need to expand each section of your PR with specific details about your changes to make it easier for reviewers to understand and approve.

[pkarashchenko]

All is good except point highlighted by Alan