From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from s3.sipsolutions.net ([5.9.151.49]:40404 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933053AbdABPD7 (ORCPT ); Mon, 2 Jan 2017 10:03:59 -0500 Message-ID: <1483369436.21014.12.camel@sipsolutions.net> (sfid-20170102_160414_006373_3DC505AE) Subject: Re: [PATCH] rfkill: remove rfkill-regulator From: Johannes Berg To: linux-wireless@vger.kernel.org Cc: netdev@vger.kernel.org, Guiming Zhuo , Antonio Ospite , Paul Cercueil , Rob Herring , Maarten ter Huurne Date: Mon, 02 Jan 2017 16:03:56 +0100 In-Reply-To: <20170102150157.26745-1-johannes@sipsolutions.net> (sfid-20170102_160217_157310_15217E5D) References: <20170102150157.26745-1-johannes@sipsolutions.net> (sfid-20170102_160217_157310_15217E5D) Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, 2017-01-02 at 16:01 +0100, Johannes Berg wrote: > From: Johannes Berg > > There are no users of this ("vrfkill") in the tree, so it's just > dead code - remove it. > > This also isn't really how rfkill is supposed to be used - it's > intended as a signalling mechanism to/from the device, which the > driver (and partially cfg80211) will handle - having a separate > rfkill instance for a regulator is confusing, the driver should > use the regulator instead to turn off the device when requested. OTOH, the rfkill-gpio is essentially the same thing, and it *does* get used - by ACPI even, to control a GPS chip. And I'm not even sure that there's a clear place to put this since there probably aren't any GPS drivers? johannes