From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Heiny Subject: Re: [RFC PATCH 14/17] input: RMI4 F30 GPIO/LED control Date: Tue, 4 Sep 2012 17:28:28 -0700 Message-ID: <50469CAC.7050608@synaptics.com> References: <1345241877-16200-1-git-send-email-cheiny@synaptics.com> <1345241877-16200-15-git-send-email-cheiny@synaptics.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from us-mx3.synaptics.com ([12.239.217.85]:63441 "EHLO us-mx3.synaptics.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752889Ab2IEA23 (ORCPT ); Tue, 4 Sep 2012 20:28:29 -0400 In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Linus Walleij Cc: Dmitry Torokhov , Jean Delvare , Linux Kernel , Linux Input , Allie Xiong , William Manson , Joerie de Gram , Wolfram Sang , Mathieu Poirier , Linus Walleij , Naveen Kumar Gaddipati On 08/27/2012 03:58 PM, Linus Walleij wrote: > GPIO/LED, nice since I'm a GPIO maintainer I'll take a closer look. > > If the bus will start doing a lot of non-input business it should live under > drivers/mfd but I think this is just one exception, right? > > On Fri, Aug 17, 2012 at 3:17 PM, Christopher Heiny wrote: > > (...) >> diff --git a/drivers/input/rmi4/rmi_f30.c b/drivers/input/rmi4/rmi_f30.c > >> +#include >> +#include >> +#include >> +#include >> +#include "rmi_driver.h" > > The non-existance of and tells us that something > is very wrong. > > You should not model these GPIOs and LEDs by a set of obscure > sysfs attributes, instead use the proper kernel subsystems that > already exist for handling this! LEDs and GPIOs already have their > own (standardized) userspace sysfs interfaces. > > Reading the code I see that this is what happens here, so please rewrite > this to be a real GPIO+LED driver using struct gpio_chip and > the same for LEDs. > > Be inspired by drivers/gpio/* and drivers/leds/* Roger. We'll rework this and resubmit at a later date.