Received: by 2002:a25:b794:0:0:0:0:0 with SMTP id n20csp5255069ybh; Wed, 7 Aug 2019 03:16:21 -0700 (PDT) X-Google-Smtp-Source: APXvYqyHdxYZHu0Z1GKj1SoANeS+qXSRv1GXhGzCgD6KLYe8EVZLLxRcWJaFCC4s+yoyxPmlBZ5I X-Received: by 2002:a17:90a:d80b:: with SMTP id a11mr7242182pjv.53.1565172981558; Wed, 07 Aug 2019 03:16:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565172981; cv=none; d=google.com; s=arc-20160816; b=rbMyrtC3BYNXDcEza3P0bM8WjSPBlPzuxBLpokZ3wUJ58dRMsLKr9qeZArefRTZPFB EpdKH3hoINBID7dQ1TIJ9O48uJAuQOnOb/nvbmRIFFRBHVNN2uR/Te1Cfb4hopEYaTml 2PXMMLuJkQPk230Wha41hGj0lAoxV2Q7ibsnUUeAU+mZLTBfpAiEBl+Y/hLDNB1V7LTR jsTjnQIkdm4r40NP+OlJhT6fJA9/VbLabc/TOMGKAoyxiLlH++uJ9zlnr4CZLziL7K3R N3/9i/2dWtemwdm6kvHHJUeO3jt4yYnznYJ7jcmoHcmTp3JkJ4Qr0NB71GBEXf6mPjb1 NbkA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=66mw8zgko1g9v95XH5VdtRjvtXtL8Yk9Tl0zDOaXYPo=; b=OOn48gAajo6IGX+3WdgrAJ2RcJTV84280ZcByrMOdJzBpmotos7hr1+774UFafxs20 7x0KkyshSzAFcBGABC8fohRIARdLdO+NUudYIgKzKlHEpiVy8RUvdiGvzh8QM/ttOIHX 4jMqMLX+AzYDqFxA5ouxqwrtnDJn7gVky1YtJiQu6j1FJQCYNDQWO3e0ppEIVZiTvtzf bswe5J+0XxfiHU0Phn9hwkx6XFTXrE+M5+QyoNoDudnkbZpx+y2K8fzCI3RuEH3O7uf4 5rY87eCu+AXYxnQu/r5dPFQQfjbU4QXGcKAlMYguLYvv757hrUQirTbUcC1eH+M9/cQ0 zu7w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@broadcom.com header.s=google header.b=NsGdbdBR; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=broadcom.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 72si44626116plc.415.2019.08.07.03.15.50; Wed, 07 Aug 2019 03:16:21 -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=@broadcom.com header.s=google header.b=NsGdbdBR; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=broadcom.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726663AbfHGKPI (ORCPT + 99 others); Wed, 7 Aug 2019 06:15:08 -0400 Received: from mail-wm1-f68.google.com ([209.85.128.68]:51497 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725991AbfHGKPH (ORCPT ); Wed, 7 Aug 2019 06:15:07 -0400 Received: by mail-wm1-f68.google.com with SMTP id 207so81238045wma.1 for ; Wed, 07 Aug 2019 03:15:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=66mw8zgko1g9v95XH5VdtRjvtXtL8Yk9Tl0zDOaXYPo=; b=NsGdbdBRkNwMiyTOR9/fgYM1OXj2xLmEQEQlpFBGIDLBElauI82i1FTHp4/qU9Exu4 duqMMdq6k/Dz042deO8DRqRpTswFOuInjem7WeLUCv7vgROe2ZwmTJfwmJqHHjviGj+5 WSc1HWrjzjRJncDty5wePpvmb2z4CG9mNbXlE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=66mw8zgko1g9v95XH5VdtRjvtXtL8Yk9Tl0zDOaXYPo=; b=aaWHxa/+AqiOyk3ogCa4fA8/R+kp2IW2zEUF5S7A3DFtkCpguMXZ+RffqZOD5XMNxS HNulJDJLX40WYigr2Dv/oqipSfmK8grjhZN7+OmeId8iOcpsPmr6uAyOrd2Uyb2JYpN1 vN0p/mehNJ375K/NX/6m9Q1mphIgSRqQaBWbDVh+7IMOhBf4rEb/mpuAJWwF1ptWHRJ5 hud91LyqBAaSGNYSF9FWDwkCP6v4+XYeZ1XxXa550p+UPvCRLlX5tWf/E2Royz/zEwAL 4sg8BLJ1WlMwkTLnJUAbDxLE5B7Kfbb4AesRLEWWpWl2lwWDpzZhjFzB0szEnC7qsF6b B+xA== X-Gm-Message-State: APjAAAWYDD1ZMvYCCvfKlCMwWbyd4qFr558YA0R20vXG5xxAjQv32QSf dDqnvyPkPKqDlfc9laANhCLoMw== X-Received: by 2002:a1c:20c8:: with SMTP id g191mr4680177wmg.55.1565172905545; Wed, 07 Aug 2019 03:15:05 -0700 (PDT) Received: from [10.176.68.244] ([192.19.248.250]) by smtp.gmail.com with ESMTPSA id f2sm82628673wrq.48.2019.08.07.03.15.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Aug 2019 03:15:04 -0700 (PDT) Subject: Re: [PATCH v2 2/2] rtw88: RTL8822C: add WoW firmware v7.3 To: Tony Chuang , "jwboyer@kernel.org" Cc: "linux-firmware@kernel.org" , "linux-wireless@vger.kernel.org" , "Larry.Finger@lwfinger.net" , "briannorris@chromium.org" 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> From: Arend Van Spriel Message-ID: <7bbbe3be-1f6f-8f38-45f3-54f25a5b2f38@broadcom.com> Date: Wed, 7 Aug 2019 12:15:03 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org 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. Regards, Arend