drivers: flash: Read/write arbitary commands via ex_op API

[utsavm9]

Some of the drivers in Zephyr are bus-HAL-specific drivers. Example: Zephyr SPI, Zephyr MSPI, NRFX QSPI, STM QSPI. When users want to write flash-part specific driver with the command set of their particular flash part, they should not need to reimplment or copy everything the bus-specific driver is doing. It would be easier for users to compose their flash-vendor specific driver using the bus-specific driver already in tree.

This PR introduces the flash_ex_op API for the above goal. npcx_flash already implements similar function in their vendor extended operations:

zephyr/include/zephyr/drivers/flash/npcx_flash_api_ex.h

Line 57 in 0f5e03f

FLASH_NPCX_EX_OP_SET_QSPI_OPER,

zephyr/include/zephyr/drivers/flash/npcx_flash_api_ex.h

Line 66 in 0f5e03f

FLASH_NPCX_EX_OP_GET_QSPI_OPER,

I want this for Flash MSPI driver at least because setting up the MSPI transaction is not trivial, but I believe this extended operation will be relevant for more drivers too. Implementation for Flash MSPI driver to follow after a RFC on this: #98621

[utsavm9]

Also requesting review from @anangl @swift-tk @rruuaanng because they have been helpful in other similar PRs.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[swift-tk]

Not sure this is the right way to do this, the cmds are pretty much SPI specific and they should be either resolved by SFDP or vendor specific quirks in the flash_mspi_nor driver if it is none standard. See #88920

[anangl]

Not sure this is the right way to do this, the cmds are pretty much SPI specific and they should be either resolved by SFDP or vendor specific quirks in the flash_mspi_nor driver if it is none standard. See #88920

I agree. To me this does not look like a proper solution, more like a hack. What @swift-tk suggests seems more appropriate.

[github-actions]

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.