roll: third_party/pigweed pw_spi_mcuxpresso: Implement proper fix for fsl_spi_dma v2.2.2 This reverts fce05b3e882d31419edce031d4f62f2d0cfece3c. That previous attempt misunderstood the problem: SPI_SlaveTransferGetCountDMA() was _not_ changed to return the number of bytes remaining. Rather, a bug was introduced in v2.2.2 which caused it to return an incorrect value. That bug, coupled with the previous change, resulted in McuxpressoResponder always assuming that all bytes had been been transferred. The SDK bug is caused by the following line in SPI_MasterTransferDMA() being lost in v2.2.2: handle->transferSize = xfer->dataSize; See https://github.com/nxp-mcuxpresso/mcuxsdk-core/issues/19 handle->transferSize is only used by SPI_MasterTransferGetCountDMA() so this omission was probably not obvious and didn't affect any other code paths. To work around this bug, we simply set handle_.transferSize ourselves before calling SPI_SlaveTransferDMA(). Original-Bug: 449001277 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/340992 Original-Revision: 0741a19a69cafa0b6bb64fcb3525bb27fec3a400 Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 1f42b7bed7acb1..0741a19a69cafa Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8699013936067749201 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I16597956023e716be2e0cb91e080c456189a4889 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/341192 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
diff --git a/third_party/pigweed b/third_party/pigweed index 1f42b7b..0741a19 160000 --- a/third_party/pigweed +++ b/third_party/pigweed
@@ -1 +1 @@ -Subproject commit 1f42b7bed7acb1326ff9fefbf77e9f9c14e3796a +Subproject commit 0741a19a69cafa0b6bb64fcb3525bb27fec3a400