From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 94D684071DF; Tue, 9 Jun 2026 03:04:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780974283; cv=none; b=tU8YS2EzCyUm16P64p13yZ6KkftlFxVJl8NMnxJKZgxfalndROQNwAWwfD5dB0Rt7irNE7eVBDv4FnPo7wnLMQndSYHwBKljLbskbeg4UD+cZULEC2DBXv578zzrrgJU1/9WRWMwEpn/M2mhuAIAsF5fbUPbXYQ3u6J0SFJZn/Q= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780974283; c=relaxed/simple; bh=yVoGTjwqbsGhqDmyNl4VIBapHM7wIP1YE9nW5TAH7FU=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=jyxpZisJZ1fUHwrqYEV38JoNAVfFASrkKsQyuqZs7ctkBpBNxFULyjRC2lGvi8U4rPjtreVOQCveov4kNx0xAg4QrYVt5Xla23d+FcX1z7ag7js1B8iwtNyFtPIzgV3IeLck5p0winCXhSD+8LK8h0xL1yoYjM2gecmgRp5AyGg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=ouZp1fRc; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="ouZp1fRc" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3F6241F00893; Tue, 9 Jun 2026 03:04:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1780974282; bh=5myXXeDCn5YVmIBgFVer+wIhNkBS248w938HxQWUeXs=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=ouZp1fRcPQ/DaYVMHo8ivh9mNFLKsdlvnJsWyTFWnr8N+QkAHMa/OJwopdRkKpjLL IWeJM8USUMEIPOz2EfqlSyLljjU4KloeKw5MMw7rMerBFs1OFq+j9fpddGM/Ijct8G cRmusTWLaaLz5aJOD7pq08kUQgU1qe9+8q08dz0GcmZIVO8rbuZ1FQjvZ8hIovKErV aUrjzISO0FYMvZMlvPhMNohJ+vCeglUrqUMOtUMdDzSInMzCPWFHdFOpfoXm/rAQGX tqz4AXZUgU6KseCMGRQskG12td3D1EeKxIX7pD8unvJQdbsxER6tc45K44ejOdGLUu UvvgTlpjVH/nQ== Date: Mon, 8 Jun 2026 22:04:38 -0500 From: Bjorn Andersson To: Jeff Johnson Cc: Krzysztof Kozlowski , Kerigan Creighton , linux-wireless@vger.kernel.org, loic.poulain@oss.qualcomm.com, wcn36xx@lists.infradead.org, mathieu.poirier@linaro.org, linux-remoteproc@vger.kernel.org, linux-arm-msm@vger.kernel.org, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Dmitry Baryshkov Subject: Re: [PATCH v3 2/3] remoteproc: qcom_wcnss_iris: Add support for WCN3610 Message-ID: References: <20260306004344.10968-1-kerigancreighton@gmail.com> <20260306004344.10968-3-kerigancreighton@gmail.com> <4f94c20c-d06f-48e5-95fb-5380c84a1b99@kernel.org> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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