Nuvoton: Fix degrading QSPI to SPI

[ccli8]

Summary of changes

This PR tries to fix logic with degrading QSPI to SPI. In most cases, we can control degraded QSPI H/W to standard through BSP SPI driver directly as if it is just SPI H/W. However, BSP SPI driver distinguishes among SPI H/W instances in functions:

• SPI_Open
• SPI_Close
• SPI_SetBusClock
• SPI_GetBusClock

In these cases, we must change to QSPI version instead for QSPI H/W.

---

Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

[ciarmcom]

@ccli8, thank you for your changes.
@ARMmbed/mbed-os-maintainers please review.

[0xc0170]

How does this work if SPI and QSPI are used in the app (they could share QSPI if SPI is using qspi hw) ?

[ccli8]

How does this work if SPI and QSPI are used in the app (they could share QSPI if SPI is using qspi hw) ?

@0xc0170 Currently, DEVICE_QSPI is not supported on Nuvoton targets. If DEVICE_QSPI is supported in the feature, the collision iis actually an issue. To fix it, SPI/QSPI HAL need to add QSPI H/W resource management. Or just leave it to application note to not complicate this logic.

[0xc0170]

CI started

[mbed-ci]

Jenkins CI Test : ✔️ SUCCESS

Build Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

CLICK for Detailed Summary

jobs	Status
jenkins-ci/mbed-os-ci_unittests	✔️
jenkins-ci/mbed-os-ci_build-ARM	✔️
jenkins-ci/mbed-os-ci_build-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️
jenkins-ci/mbed-os-ci_dynamic-memory-usage	✔️
jenkins-ci/mbed-os-ci_cloud-client-pytest	✔️