On Fri, Jun 05, 2026 at 05:33:22PM -0700, Jeff Johnson wrote:
> On 3/5/2026 11:25 PM, Krzysztof Kozlowski wrote:
> > On 06/03/2026 01:43, Kerigan Creighton wrote:
> >> WCN3610 has the same regulator requirements as
> >> WCN3620, so in qcom_wcnss_iris, we can use wcn3620_data.
> >>
> >> A separate compatible is needed for WCN3610 because the
> >> wcn36xx driver uses it for chip-specific configuration.
> >> Specifically, it sets BTC (Bluetooth Coexistence) CFGs,
> >> disables ENABLE_DYNAMIC_RA_START_RATE, and disables
> >> STA_POWERSAVE for this specific chip for stable
> >> functionality.
> >
> > This goes to the binding description where you describe the hardware,
> > how I asked.
> >
> > Please wrap commit message according to Linux coding style / submission
> > process (neither too early nor over the limit):
> > https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
> This series is sitting in my patchwork queue.
> Based upon Krzysztof's comments there should be a v4 that moves some
> descriptive text from 2/3 to 1/3.
>
> Bjorn: Once v4 lands, do you want to take this series or should I?
> (Need to know if I should wait for ACK of 2/3 or give ACK for 3/3).
>
I don't see any build-time dependencies between patch {1,2} and {3}. So
I'd suggest that I pick the two remoteproc patches and you pick the WiFi
patch.
Regards,
Bjorn
> /jeff
