Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp441300ybi; Tue, 16 Jul 2019 23:17:17 -0700 (PDT) X-Google-Smtp-Source: APXvYqyghDBTJAkKQL52Qb6St13V0bSBZpovkGOcK3LypGF3Z0cIps+zvAPEj6YiimbauRW1G1/v X-Received: by 2002:a17:902:a5c7:: with SMTP id t7mr41637353plq.288.1563344237794; Tue, 16 Jul 2019 23:17:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563344237; cv=none; d=google.com; s=arc-20160816; b=oAUID2FTmhtpxflBVGet1pji85GKPdWar38kDDz2dR5RX5NcBxRh/aItnQbA/3+1k3 kQLfWe07bAvBJvBmsfXKReQfNG4wuxWcIM6wYrZiBvePbluK1LpsuhHWWzNhnXkCHeP9 sbkuRyvBHTpVZXqgRy7/eNO+3O1DyQf0t6izk4Myt3VW+c4QzflX/NSkDNWFi7yArs+9 kzziSThAGOk/d/abmXeF/yD7rbhFC/DcuArNfFS6VFVo8BOelRK5rJxEmpEga0Mil+h5 h9ax9NESn+1b3kgKym8fDE/8fx2pKV+BfXeD80NAIu+uWfZ5ovBDkt/jzchpbHVneRlB ysGQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:content-disposition :mime-version:message-id:subject:to:from:date; bh=wmyYXf+bIucrY19kra+XsshciM84vW7TvMPJQvWW3es=; b=I8PXwqmz550DtulAI0yYP29U7mZ5EeVhRfY2LQkqcsgbca//QmzTr7gn7r+qbp5f4s vmalw3660UicZp4gYhQEITJ3UtYRRpC4x+6Qur+lcw4yGoWmX26GFe+hyfKgpjwttIrv zMktxrZmvUtahQ8qzsjPYU3OGyTVOJmzPqPipXhesR627VmSoXG+x9g7qP1SoDWXe72c ixfYEhcNiYSaPwpO8BtlKsxCchIwADkL5KjbJ8fKjB/j26YNKBjaxzSUMOpcMo+PKxdx CExV2nzVyS8pIy9C144TxtsAveUyZ9biwkiuK1VeFBX1d+BTquLbCnGR1TnRElMKUo7Q CwkA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h1si15983150pls.183.2019.07.16.23.16.43; Tue, 16 Jul 2019 23:17:17 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726939AbfGQGNr (ORCPT + 99 others); Wed, 17 Jul 2019 02:13:47 -0400 Received: from picapica.im ([159.69.34.17]:60850 "EHLO picapica.im" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726282AbfGQGNr (ORCPT ); Wed, 17 Jul 2019 02:13:47 -0400 X-Greylist: delayed 454 seconds by postgrey-1.27 at vger.kernel.org; Wed, 17 Jul 2019 02:13:46 EDT Received: by picapica.im (Postfix, from userid 1000) id 1C03A3E8AB; Wed, 17 Jul 2019 08:06:09 +0200 (CEST) Date: Wed, 17 Jul 2019 08:06:09 +0200 From: Anton Sviridenko To: linux-wireless@vger.kernel.org Subject: RTL8188ETV chip, r8188eu module and power management Message-ID: <20190717060609.GA21298@picapica.im> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hello we are using FN-8112MET PCB module having RTL8188ETV chip on it. Device is running customized Linux version based on Linux 4.19 release. Driver module "r8188eu" is not modified, taken from vanilla sources as is. Wi-Fi connection is used occasionally, and rest of the time it is preferable to have minimal power consumption. Such situation is observed: 1) Linux kernel is started, driver module is not loaded 2) module "r8188eu" is loaded manually with parameters "rtw_power_mgnt=2 rtw_enusbss=1" 3) device starts consuming more current (+20mA) 3) after the module is unloaded, current consumption remains at the same level We still have to double-check this, but looks like driver module does not leave the device in the same state on module unload. Few questions: 1) Is "r8188eu" driver from the mainline kernel the best possible option available for this chip? 2) Where can I look for some documentation about kernel module parameters related to power management and their meanings? Source code is not very descriptive, and I was not able to google anything better, looks like this chip specifications are not available in public. 3) Is there some option to completely poweroff this chip using software and then bring it back when needed? Anton