Refactor storage COMPONENT_xx directory

[rajkan01]

Summary of changes

Restructured storage/blockdevice/COMPONENT_xx as per the new directory structure proposal:

storage
├── blockdevice
│   ├── COMPONENT_DATAFLASH
│   │      ├── mbed_lib.json
│   │      ├── include
│   │      │   └── DataFlash
│   │      │            └── *.h
│   │      ├── source
│   │      └── tests           
│   │             └── TESTS
│   ├── COMPONENT_FLASHIAP
│   └── [...]

Impact of changes

None.

Migration actions required

None.

Documentation

To Be Updated.

---

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)
[x] Tests / results supplied as part of this PR

Manual testing: (Build for K64F target with GCC_ARM toolchain)

• mbed-os-example-blockdevice
• Greentea tests: Full profile
• Unit tests build and run

---

Reviewers

@0xc0170 @ARMmbed/mbed-os-core

---

[ciarmcom]

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

[LDong-Arm]

COMPONENT_** are magic keywords of the build system - the library path is unavoidably like that for now. But the include paths can be more readable e.g. include/DataFlashBlockDevice or include/DataFlash instead of include/COMPONENT_DATAFLASH.

For example, in BLE we have FEATURE_BLE/include/ble/.

[rajkan01]

COMPONENT_** are magic keywords of the build system - the library path is unavoidably like that for now. But the include paths can be more readable e.g. include/DataFlashBlockDevice or include/DataFlash instead of include/COMPONENT_DATAFLASH.

For example, in BLE we have FEATURE_BLE/include/ble/.

Yes, I agree that will be more readable, but directory restructures confluence page suggested like 'component name' is same as 'include/[component name]' so I just followed the similar fashion as 'include/COMPONENT_xx'

Confluence page reference:
[component name]
         ├── include                           // The top-level include path
         │   └── [component name]              // Public headers that can be accessed by the developers - `#include [component 

@evedon Could you confirm, which one to follow either Lingkai suggested directory name like include/DataFlash or include/COMPONENT_DATAFLASH

[LDong-Arm]

Confluence page reference:
[component name]
         ├── include                           // The top-level include path
         │   └── [component name]              // Public headers that can be accessed by the developers - `#include [component 

This is the final version when the new build system is in place. For now magic words (e.g. COMPONENT_xx) are needed but should appear in as few places as possible while things still work, in my opinion.

[rajkan01]

Confluence page reference:
[component name]
         ├── include                           // The top-level include path
         │   └── [component name]              // Public headers that can be accessed by the developers - `#include [component 

This is the final version when the new build system is in place. For now magic words (e.g. COMPONENT_xx) are needed but >>should appear in as few places as possible while things still work, in my opinion.

I have made header include header directory more readable as suggested, please re-review

[LDong-Arm]

Thanks, LGTM

[rajkan01]

@0xc0170 Could you review and start the CI

[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_dynamic-memory-usage	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️
jenkins-ci/mbed-os-ci_cloud-client-pytest	✔️

[rajkan01]

@0xc0170 CI passed for this PR, please merge

[0xc0170]

We will merge as soon as 6.2.1 is released (later today).