On 7/11/23 08:02, Krzysztof Kozlowski wrote:
), then it is not suitable DT
property. How it would even look like? You add here 500 ms for all known
firmwares and then someone comes with FW requiring delay of 600 ms.
I would say, some sane default and if some firmware is specifically
weird, just up the delay. It is better than no firmware working at all.
Do you have a better hint how to deal with this ?
Put some working value in the driver. If this does not help, complain to
NXP about their SDK firmware.I know how that would work - NXP does not
really care about customers and open-source - but that should not be
really an excuse for us.
Yes, so, I'll just stick half a second delay into the driver for now.