Received: by 2002:a25:b794:0:0:0:0:0 with SMTP id n20csp5669729ybh; Wed, 7 Aug 2019 09:29:11 -0700 (PDT) X-Google-Smtp-Source: APXvYqxys0Nxx0oKTUW0V25YHoQhXZnXxnooMeo4Y9vh/jljPOyUTTShvbLNXHdll5JobwMy8Tk0 X-Received: by 2002:a63:4461:: with SMTP id t33mr8288828pgk.124.1565195351144; Wed, 07 Aug 2019 09:29:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565195351; cv=none; d=google.com; s=arc-20160816; b=atmlpG8sod/xpORXGuV6l8+v+uA9rEgc2IzV37zqP3p8BH+DZii6M93W+rY5e/nbZ3 jo5HgYa3/Li3aqySQ+3DZqw4C2qs9eSRPjge0szsMbnjOUBbSMeU8dlJXqPtd37XON7a GjeowH4ac1pT0tst0Tme9hgkgUL9Ttw82aR+jpLXVIPQpYMBeAKnA47qrLkdnYdpE1Fx J+ySEqOonbcIFR/SfQ59aHSkwAvznoOOyDE+3ahli/gVN9Hz6wWCbNhW7iDHg0Nj155L AHxdTPoJWUTpkXuCid2RT+0zn8Chy7ZGx1yXE/+wUzja3cgDbZSe0MDIO/GfarkzyN92 zijg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=f5VSo5Nv0mT0hicaC2+W6BwnB9u1CUx1Ic7lZ+mwFvI=; b=gUUDBZgWPf5VkmwUSPvR67D4ZIj41jvmRyeUsEKMwQtEOZfbcTKb7rp9woJKr4tXfN fRlppNNwD6xSCXtYPPUHUkU83REQKDZLhkxbGMjk9F8VXKVHvXjNn90aOc4RnP7vd3wI v55CpSp4r48kW2t8QNHewFtPH+A+ckr3Qcd8ZWgnoF7CIJKNSp7Oy/o0xE6DPUYvtrKG vvpasUrRo+oRIj2oCg4b7xqZgvQV2ZR354M5j0WoZzKX3iGjLEa3ziegltBTv86sAFdH MdUyFLGzPF27+Y8bLJU4/QQj27m/IgUXsTSvXFW49oATL8fF6hAO8wAbvXdXRL5wbzTS xSfA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=o1e8Va+8; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d9si50923830pgv.577.2019.08.07.09.28.45; Wed, 07 Aug 2019 09:29:11 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=o1e8Va+8; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388692AbfHGQU5 (ORCPT + 99 others); Wed, 7 Aug 2019 12:20:57 -0400 Received: from mail.kernel.org ([198.145.29.99]:56524 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387922AbfHGQU5 (ORCPT ); Wed, 7 Aug 2019 12:20:57 -0400 Received: from mail-qk1-f180.google.com (mail-qk1-f180.google.com [209.85.222.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 1A7C9222FC for ; Wed, 7 Aug 2019 16:20:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1565194856; bh=oPAKNVBLvVOYekNlp4K5LNtM6tv5QzJcTPrxkrhmPD4=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=o1e8Va+8G7trBYQXukc5n+bkxLZitYguotrp97cC4/buFp7Vgc/9+LXwkqpL1P5CF +qyMz0yoynVzyAMGjG4dWqcF5ZXfpOm+n789jlmVD2up2dHVsSe7vUxZhUnKoEq+sA LJ+wXX887D2r2W1cHELg5oB26OgHPJzEkAOfBlDY= Received: by mail-qk1-f180.google.com with SMTP id r6so66306004qkc.0 for ; Wed, 07 Aug 2019 09:20:56 -0700 (PDT) X-Gm-Message-State: APjAAAXhc1SrovIXlfT5cYLulRl6/fwXqlNDKMlZMPgA3i5WFR0O7g6w PYSLCMiC2oWYRuCrpYF1gNxKcVBSVUscLZvcweU= X-Received: by 2002:a05:620a:1329:: with SMTP id p9mr9187371qkj.224.1565194855263; Wed, 07 Aug 2019 09:20:55 -0700 (PDT) MIME-Version: 1.0 References: <1565167700-22501-1-git-send-email-yhchuang@realtek.com> <1565167700-22501-2-git-send-email-yhchuang@realtek.com> <3307e4b7-c92d-e1d2-b896-26e45fb69a9b@broadcom.com> <7bbbe3be-1f6f-8f38-45f3-54f25a5b2f38@broadcom.com> In-Reply-To: <7bbbe3be-1f6f-8f38-45f3-54f25a5b2f38@broadcom.com> From: Josh Boyer Date: Wed, 7 Aug 2019 12:20:44 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 2/2] rtw88: RTL8822C: add WoW firmware v7.3 To: Arend Van Spriel Cc: Tony Chuang , "linux-firmware@kernel.org" , "linux-wireless@vger.kernel.org" , "Larry.Finger@lwfinger.net" , "briannorris@chromium.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Wed, Aug 7, 2019 at 6:15 AM Arend Van Spriel wrote: > > > > On 8/7/2019 11:53 AM, Tony Chuang wrote: > >> From: Arend Van Spriel [mailto:arend.vanspriel@broadcom.com] > >> > >> On 8/7/2019 10:48 AM, yhchuang@realtek.com wrote: > >>> From: Yan-Hsuan Chuang > >>> > >>> Add WoW firmware to support entering Wake on WirelessLAN mode > >>> > >>> Signed-off-by: Yan-Hsuan Chuang > >>> --- > >>> > >>> v1 -> v2 > >>> * update WHENCE file for new added firmware > >>> > >>> WHENCE | 1 + > >>> rtw88/rtw8822c_wow_fw.bin | Bin 0 -> 138720 bytes > >>> 2 files changed, 1 insertion(+) > >>> create mode 100755 rtw88/rtw8822c_wow_fw.bin > >> > >> Just wondering: Is this a good approach? What firmware should distros > >> pick? Is there a trade-off affecting other wifi functionality when using > >> WoW firmware? > >> > > > > If distros want to use WOW, they should pick both. > > > > For Realtek devices such as RTL8822CE, it needs to "change/re-download" > > the wow firmware to suspend with WOW functionalities. When resume, > > switch back to normal firmware to run "normally". > > > > I think the reason is the firmware size restriction. For newer devices, > > maybe there is a larger space for firmware, and we don't need to swap > > the FW like this :) > > Interesting approach and I would mention this in the commit message or > add a README in rtw88 folder explaining it. Not sure whether distros > look at commit messages. A README would indeed be nice. Can you do a v3 with that included? josh