Linux wireless drivers development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Miaoqing Pan <quic_miaoqing@quicinc.com>
Cc: jjohnson@kernel.org, johannes@sipsolutions.net, robh@kernel.org,
	 krzk+dt@kernel.org, conor+dt@kernel.org,
	ath12k@lists.infradead.org,  linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [RESEND ath-next 1/2] dt-bindings: net: wireless: ath12k: describe firmware-name property
Date: Mon, 28 Apr 2025 10:25:38 +0200	[thread overview]
Message-ID: <20250428-ruddy-bold-macaw-9ffd28@kuoka> (raw)
In-Reply-To: <20250424005703.2479907-2-quic_miaoqing@quicinc.com>

On Thu, Apr 24, 2025 at 08:57:02AM GMT, Miaoqing Pan wrote:
> Introduce 'firmware-name' property to allow end-users and/or integrators
> to decide which usecase-specific firmware to run on the WCN7850 platform.
> This is necessary due to resource limitations such as memory capacity and
> CPU capability, or performance and power optimization for different
> application scenarios.
> 
> Two firmwares are supported: 'WCN7850/hw2.0' and 'WCN7850/hw2.0/ncm825'.
> The former is the default firmware, suitable for most WiFi 7 STA
> functions. The latter adds support for commercial-quality SAP and
> optimizes power consumption for IoT applications.
> 
> Signed-off-by: Miaoqing Pan <quic_miaoqing@quicinc.com>
> ---
>  .../devicetree/bindings/net/wireless/qcom,ath12k.yaml       | 6 ++++++
>  1 file changed, 6 insertions(+)

<form letter>
This is a friendly reminder during the review process.

It looks like you received a tag and forgot to add it.

If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new
versions of patchset, under or above your Signed-off-by tag, unless
patch changed significantly (e.g. new properties added to the DT
bindings). Tag is "received", when provided in a message replied to you
on the mailing list. Tools like b4 can help here. However, there's no
need to repost patches *only* to add the tags. The upstream maintainer
will do that for tags received on the version they apply.

Please read:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577

If a tag was not added on purpose, please state why and what changed.
</form letter>

Best regards,
Krzysztof


  reply	other threads:[~2025-04-28  8:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24  0:57 [RESEND ath-next 0/2] wifi: ath12k: support usercase-specific firmware overrides Miaoqing Pan
2025-04-24  0:57 ` [RESEND ath-next 1/2] dt-bindings: net: wireless: ath12k: describe firmware-name property Miaoqing Pan
2025-04-28  8:25   ` Krzysztof Kozlowski [this message]
2025-04-28  9:48     ` Miaoqing Pan
2025-04-28  9:55       ` Krzysztof Kozlowski
2025-04-28  9:56   ` Krzysztof Kozlowski
2025-04-24  0:57 ` [RESEND ath-next 2/2] wifi: ath12k: support usercase-specific firmware overrides Miaoqing Pan
2025-05-06  3:56   ` Vasanthakumar Thiagarajan
2025-05-19 17:48 ` [RESEND ath-next 0/2] " Jeff Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250428-ruddy-bold-macaw-9ffd28@kuoka \
    --to=krzk@kernel.org \
    --cc=ath12k@lists.infradead.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jjohnson@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_miaoqing@quicinc.com \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox