-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Feature/stm32 usart wide data #54354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/stm32 usart wide data #54354
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this change.
To ease the review process, I'd suggest to split changes into multiple elementary commits.
There are too much changes impacting the driver in a single commit to allow a clear assessment of the change and impact.
For instance:
- all changes that are not directly linked to WIDE_DATA introduction should be
split from the changes introducing WIDE_DATA - formating changes should be done in a dedicated commit
- ...
Also, I suggest submitting the non STM32 related changes in a dedicated PR to get a broader audience.
95a6d97 to
957170f
Compare
I guess you're addressing the dts binding change? I made that change because I saw we're slowly moving from runtime configuration to devicetree configuration and these were missing. Shall I split that off into a dedicated PR and keep the change here? Because this PR doesn't build without it. |
957170f to
06b5040
Compare
DTS indeed but also test changes (which are btw welcome so that we are able to verify functional status).
Sure, but you can put them in a stand alone PR which commits are also included in current PR. |
06b5040 to
65d5fcb
Compare
Added another PR for only the binding change: binding |
65d5fcb to
e8468ec
Compare
Thanks. |
To make it simple: |
e8468ec to
4c2e703
Compare
4c2e703 to
1545dee
Compare
Ok, splitted the single commit into 4 separate ones. |
|
DNM until author is back (@JvanDooren don't hesitate to remove label when needed) |
|
Nice initiative @JvanDooren. Can't wait for it to be merged. |
a46fe73 to
0cad81f
Compare
|
Rebased, and fixed small conflict to |
0cad81f to
3c801b5
Compare
…ation Preventing code duplication of macros checking for HW support on stop bits and data-bits during runtime configuration. Validated runtime configuration on an STM32H743. Signed-off-by: Jeroen van Dooren <[email protected]>
Restructuring code for poll_in/poll_out/fifo_fill/fifo_read because for
wide data support, all code is identical except the calls to
LL_USART_{ReceiveData8/TransmitData8}.
This allows both implementations, 8 and 9 bit data-width to call a
visitor function, passing the either the 8 bit or 9 bit data-width
function pointer.
Signed-off-by: Jeroen van Dooren <[email protected]>
Add wide data support to STM32. Validated interrupt driven code on an STM32H743. Signed-off-by: Jeroen van Dooren <[email protected]>
Moving struct in preparation of wide test. Signed-off-by: Jeroen van Dooren <[email protected]>
Extending configuration tests with wide data support. Signed-off-by: Jeroen van Dooren <[email protected]>
Resetting uart state before every testcase. Signed-off-by: Jeroen van Dooren <[email protected]>
Extending async tests with wide data support. Signed-off-by: Jeroen van Dooren <[email protected]>
3c801b5 to
cd89942
Compare
Nope, the tests were basically the main culprit. So should be fine if all tests pass. |
Doesn't seem I'm authorized to edit labels? |
|
@erwango As far as I can see all comments are addressed. So now we only have to wait for approvals. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes in tests LGTM.
drivers: serial: stm32: add wide data support
Add wide data support to STM32 into
Adds 9 bit datawidth support to serial driver.
Validated interrupt driven code on an STM32H743.
Signed-off-by: Jeroen van Dooren [email protected]