boards: frdm_mcxn947: Add clock setup for FlexSPI

[mmahadevan108]

The MEMC driver is initialized before the FlexSPI driver and hangs during FlexSPI init. Initialize the FlexSPI clock to 50MHz before the speed is set to the optimum speed by the FlexSPI driver.

[decsny]

which memc driver are you talking about? it should be clarified in the commit message first of all, and need to know if we need to find a better solution if this problem will occur generally

[danieldegrasse]

The MEMC driver is initialized before the FlexSPI driver and hangs during FlexSPI init. Initialize the FlexSPI clock to 50MHz before the speed is set to the optimum speed by the FlexSPI driver.

Is the issue here that the FlexSPI was previously not being clocked prior to memc init, causing a hang? If so, I think this solution generally follows the pattern we are currently using for other peripheral clocking

[mmahadevan108]

which memc driver are you talking about? it should be clarified in the commit message first of all, and need to know if we need to find a better solution if this problem will occur generally

Commit message updated to include the memc driver details.

[mmahadevan108]

The MEMC driver is initialized before the FlexSPI driver and hangs during FlexSPI init. Initialize the FlexSPI clock to 50MHz before the speed is set to the optimum speed by the FlexSPI driver.

Is the issue here that the FlexSPI was previously not being clocked prior to memc init, causing a hang? If so, I think this solution generally follows the pattern we are currently using for other peripheral clocking

Yes. FlexSPI clock is left un initialized at boot time causing a hang.

[decsny]

which memc driver are you talking about? it should be clarified in the commit message first of all, and need to know if we need to find a better solution if this problem will occur generally

Commit message updated to include the memc driver details.

The commit message should also say what the "flexspi driver" is, as there are multiple flexspi drivers just like there are multiple memc drivers.

[mmahadevan108]

@decsny, kindly re-review

[decsny]

I still think this should not have to be done in board code but don't know the complications so not blocking it right now

[mmahadevan108]

@dleach02, can you please review and approve

[decsny]

reapprove

[henrikbrixandersen]

I take it this (board.c used for clock setup) is an interim solution until we have something like #70467 available?