On Tue, Nov 25, 2025 at 04:42:15PM +0200, Dmitry Baryshkov wrote: > On Tue, Nov 25, 2025 at 10:29:23AM +0100, David Heidelberg wrote: > > On 10/11/2025 21:41, Dmitry Baryshkov wrote: > > > > [...] > > > > > I think this should go to the firmware-N file. SNOC platforms now allow > > > per-platform firmware description files, so it's possible to describe > > > quirks for the particular firmware file. > > > > Since the approach to put it into the firmware failed due to early > > initialization, see > > https://lore.kernel.org/linux-wireless/[email protected]/ > > Is it required before we load the firmware? If so, it must be clearly > explained in the commit messages. In the end, if it happens before > firmware load, there is little you can do. That was the reason why > qcom,no-msa-ready-indicator was implemented as a DT property.
David, gracious ping. Could you please describe your findings in the commit messages and repost? Please explain that there is no other sensible way to provide this information to the driver since this happens before we load firmware-N.bin / board-M.bin). -- With best wishes Dmitry
