Silicon Labs QSPI HAL implementation

[stevew817]

Description

Implemented the QSPI HAL on EFM32GG11, since that is our target which has QSPI available today. The port was verified working on the STK3701 and its on-board QSPI flash, using the supplied hal-qspi test.

Pull request type

[ ] Fix
[ ] Refactor
[X] Target update
[ ] Functionality change
[ ] Breaking change

[stevew817]

Can be redirected to master once #7783 lands.

[maciejbocianski]

@stevew817 Did you run mbed_hal-qspi test on it?

[stevew817]

@maciejbocianski Yes, I did. It passed all tests (43 of them).

[cmonr]

@OPpuolitaival @ARMmbed/mbed-os-test How can jenkins-ci/cloud_client_smoke_test be restarted?

[stevew817]

@maciejbocianski Can you formally approve this PR if you're happy with it?
@cmonr @0xc0170 Rebased on master now that #7783 has been merged. I'd appreciate it if this came into the same release as #7783.

[maciejbocianski]

@stevew817
It could require another rebase, and pin names modification if #7817 will go in first

[cmonr]

@maciejbocianski It looks like it doesn't need a rebase this time around.

/morph build

[mbed-ci]

Build : FAILURE

Build number : 2902
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7825/

[cmonr]

@stevew817 Looks like I spoke too soon, but on the plus side, the fixes look simple.

[maciejbocianski]

@stevew817 pin names should be changed to QSPI_FLASH1_XXX

[stevew817]

@cmonr @0xc0170 Rebased and updated pinnames, should now be according to spec.

@maciejbocianski Feedback post-mortem: It would've been nice to only have one pull request to have to look at when implementing a new feature PR. What was the reason for adding a change PR when the original feature PR wasn't even merged yet?

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 2919
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7825/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build
/morph mbed2-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 2538
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/7825/

[mbed-ci]

Test : SUCCESS

Build number : 2668
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/7825/2668

[maciejbocianski]

Feedback post-mortem: It would've been nice to only have one pull request to have to look at when implementing a new feature PR. What was the reason for adding a change PR when the original feature PR wasn't even merged yet?

@stevew817 you are right this should go this way, (the reason was to busy schedule)