Marc Gonzalez <mgonzalez@xxxxxxxxxx> writes: > The driver waits for this indicator before proceeding, > yet some WCNSS firmwares apparently do not send it. > On those devices, it seems safe to ignore the indicator, > and continue loading the firmware. > > Signed-off-by: Pierre-Hugues Husson <phhusson@xxxxxxxxxx> > Signed-off-by: Marc Gonzalez <mgonzalez@xxxxxxxxxx> > --- > Documentation/devicetree/bindings/net/wireless/qcom,ath10k.yaml | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.yaml b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.yaml > index 7758a55dd3286..145fa1a3c1c6a 100644 > --- a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.yaml > +++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.yaml > @@ -121,6 +121,14 @@ properties: > Whether to skip executing an SCM call that reassigns the memory > region ownership. > > + qcom,no-msa-ready-indicator: > + type: boolean > + description: > + The driver waits for this indicator before proceeding, > + yet some WCNSS firmwares apparently do not send it. > + On those devices, it seems safe to ignore the indicator, > + and continue loading the firmware. This sounds more like a firmware feature, not a hardware feature. What about having a flag in enum ath10k_fw_features in firmware-2.bin? -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
