From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752391AbcBWKb5 (ORCPT <rfc822;w@1wt.eu>);
	Tue, 23 Feb 2016 05:31:57 -0500
Received: from mout.kundenserver.de ([212.227.126.187]:61756 "EHLO
	mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751791AbcBWKbw (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 23 Feb 2016 05:31:52 -0500
From: Arnd Bergmann <arnd@arndb.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Thierry Reding <thierry.reding@gmail.com>,
        Heikki Krogerus <heikki.krogerus@linux.intel.com>,
        linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
        Alexandre Courbot <gnurou@gmail.com>,
        Stephen Warren <swarren@wwwdotorg.org>,
        Marc Dietrich <marvin24@gmx.de>
Subject: Re: [PATCHv2 3/4] ARM: tegra: use build-in device properties with rfkill_gpio
Date: Tue, 23 Feb 2016 11:31:40 +0100
Message-ID: <3086257.esvHq8Yk9N@wuerfel>
User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <5438459.Mb6Ga2Xhyq@wuerfel>
References: <1453712629-143317-1-git-send-email-heikki.krogerus@linux.intel.com> <1455825889.2084.16.camel@sipsolutions.net> <5438459.Mb6Ga2Xhyq@wuerfel>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V03:K0:ubxuL5S1YJg+F41C4s9VGCR/jaI2pgN+5AClhx6qVnjSIotjzef
 cLg7zKcuAWaWuL83xdOLsu9f7nzvOWDTvXjHKKMZ0qn3lNbx1pu0B9QqaNNe1775Cj3+Ysf
 eOw/2wzrlgmZxI5g9umhoygyKEouJgY5c5LWSrS5bcgv9qcdBUWitwnJCS2xBOQBzbYTNNb
 Te2hqVazWlusOhypuKY5A==
X-UI-Out-Filterresults: notjunk:1;V01:K0:Bwqn8rEUrYw=:aqn9ljxeFghyX+KThvvhw/
 gd7BdhAZnHa6utK1eR79Trn9y9Q4eDHL/ssgGu1yZRSeXevJPaJYWu+ICE/TtpMqgF5K+qwIA
 FOzZXII23iDjnrGrfgambS5nU3IIaI9CL9BAxJKK1EGBUGIFhOi65bn1dV354WLL2sWmhjqWO
 8VNJ19Y7DgcotGXlmgKFDAVnwZtEYSggxaup3N+6CVXkrWpnoqDc4ROqRhiwrHxuD++fteIbw
 0b5Ft4pkTBy39ldNBiA2rajNJPgdP34esNtpVT6dyp/bV8n44QqNMnumDT99CAX8dT7XVISGS
 43JVSUpUyt5GFcZlay/K//C4yd3CFsBtlNHjfkZZDSx7qD253uTqhV2C3NJlhkAPM5uFS8owP
 R9XbzGSDvN7ugZK0h+Ma9dv8zCd0mjVVXEBhNdwHK+rfc+XiHCII9CNynPfHEjR/eaI0YrHva
 24TOIBcKQbOrku7zlaxXbCaNMhVCdt55pieM5yX+gOf2Aj+MsPQbxtcpn/+TL9iu4LoMWDPlg
 /CenJRpPcITUm28KRRzFtC60BQrvONBDzlA7bCCHq8yDtPHNMkqOQVCKRYxPdmZHe5TMqtzxr
 WYhY1FcVb+ebQRA1Zcz9OZvVX/CrGOEsfBCu5nL7QiOhm9Ttfl/8ZbyBWn8KKjVK8g8xRvpZU
 14Ubx05VZSEOO0p9o/IiJX53uI5Dck3oYPd8uhCt3imJ8ZMSmAUCGlgBiciWAEGRTDypEM2KL
 YGlAb85pHZYqPm15
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tuesday 23 February 2016 11:15:31 Arnd Bergmann wrote:
> On Thursday 18 February 2016 21:04:49 Johannes Berg wrote:
> > On Tue, 2016-01-26 at 09:42 +0100, Johannes Berg wrote:

> Just for my curiosity: what is the difference between a rfkill-gpio
> device and a gpio-keys device with a KEY_RFKILL code?
> 
> arch/arm/boot/dts/bcm4708-netgear-r6250.dts and others seem to
> do the second approach in DT so they don't need to create the
> platform device.

I found the answer now (after discussing on IRC): just
for reference: KEY_RFKILL is for sending the event to the kernel
when a user presses the gpio butting, this rfkill-gpio turns
the devices on or off when after an RFKILL event is received.

	Arnd