Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936587Ab3DJUpy (ORCPT ); Wed, 10 Apr 2013 16:45:54 -0400 Received: from mail-ie0-f174.google.com ([209.85.223.174]:61962 "EHLO mail-ie0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752655Ab3DJUpw (ORCPT ); Wed, 10 Apr 2013 16:45:52 -0400 MIME-Version: 1.0 In-Reply-To: <1365441321-21952-3-git-send-email-kevin.strasser@linux.intel.com> References: <1365441321-21952-1-git-send-email-kevin.strasser@linux.intel.com> <1365441321-21952-3-git-send-email-kevin.strasser@linux.intel.com> Date: Wed, 10 Apr 2013 22:45:51 +0200 Message-ID: Subject: Re: [PATCH 3/4] gpio: Kontron PLD gpio driver From: Linus Walleij To: Kevin Strasser Cc: "linux-kernel@vger.kernel.org" , Michael Brunner , Samuel Ortiz , Wolfram Sang , Ben Dooks , "linux-i2c@vger.kernel.org" , Grant Likely , Wim Van Sebroeck , linux-watchdog@vger.kernel.org, Darren Hart , Michael Brunner , Greg Kroah-Hartman , Thomas Gleixner Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4768 Lines: 158 On Mon, Apr 8, 2013 at 7:15 PM, Kevin Strasser wrote: > From: Michael Brunner > > Add gpio support for the on-board PLD found on some Kontron embedded > modules. > > Signed-off-by: Michael Brunner > Signed-off-by: Kevin Strasser Trying to do some real review... (...) > +++ b/drivers/gpio/gpio-kempld.c > +#include Is this used? > +#include > +#include > +#include > +#include > + > +#include "gpio-kempld.h" > + > +static int gpiobase = -1; > +static int gpioien = 0x00; > +static int gpioevt_lvl_edge = -1; > +static int gpioevt_low_high = -1; > +static int gpionmien = 0x00; (...) +static int kempld_gpio_to_irq(struct gpio_chip *chip, unsigned offset) +{ + struct kempld_gpio_data *gpio + = container_of(chip, struct kempld_gpio_data, chip); + return gpio->irq; +} I don't understand this *at all* so help me out here. .gpio_to_irq() should return a *Linux* IRQ number, usually we take the event offset (in this case) and map to a Linux IRQ using the irqdomain helper library. Can you explain how we can be sure that this number (apparently just a read from a register on the device) can be made to correspond to a Linux IRQ? Also if this thing can generate IRQs, are these one line to the CPU per IRQ really? Don't you need to demux the status register and create a cascades irqchip? Maybe it's just me not understanding x86 & ACPI so bear with me... > +static int kempld_gpio_setup_event(struct kempld_gpio_data *gpio) > +{ > + struct kempld_device_data *pld = gpio->pld; > + struct gpio_chip *chip = &gpio->chip; > + int irq; > + > + irq = gpio->irq; > + > + kempld_get_mutex_set_index(pld, KEMPLD_IRQ_GPIO); > + irq = kempld_read8(pld, KEMPLD_IRQ_GPIO); > + > + /* Leave if interrupts are not supported by the GPIO core */ > + if ((irq & 0xf0) == 0xf0) > + return 0; > + > + gpio->irq = irq & 0x0f; So you read the IRQ from some plug-n-play here, and it's some system-wide IRQ number? (...) > + if (gpio->irq) > + chip->to_irq = kempld_gpio_to_irq; So that is this mystery with the IRQs and how they turn into Linux IRQs. > +module_param(gpiobase, int, 0444); Why do you need to be able to configure this? It must be a real usecase, debugging can be done by patching the code. > +module_param(gpioien, int, 0444); > +module_param(gpioevt_lvl_edge, int, 0444); > +module_param(gpioevt_low_high, int, 0444); > +module_param(gpionmien, int, 0444); Argh how can anyone possibly make this out ... do you really need them or can we get rid of some and rely on autodetect? > +MODULE_DESCRIPTION("KEM PLD GPIO Driver"); > +MODULE_AUTHOR("Michael Brunner "); > +MODULE_LICENSE("GPL"); > +MODULE_ALIAS("platform:kempld_gpio"); > +MODULE_PARM_DESC(gpiobase, "Set GPIO base (default -1=dynamic)"); > +MODULE_PARM_DESC(gpioien, "Set GPIO IEN register (default 0x00)"); > +MODULE_PARM_DESC(gpioevt_lvl_edge, > + "Set GPIO EVT_LVL_EDGE register (default -1=no change)"); > +MODULE_PARM_DESC(gpioevt_low_high, > + "Set GPIO EVT_LOW_HIGH register (default -1=no change)"); > +MODULE_PARM_DESC(gpionmien, "Set GPIO NMIEN register (default 0x00)"); So I don't really like that interrupt enablement and edge and low/high is done with module parameters instead of just creating an irqchip and have it implement the operations to do exactly these things at runtime instead. Again maybe some x86 thing I don't get... > diff --git a/drivers/gpio/gpio-kempld.h b/drivers/gpio/gpio-kempld.h (...) > +struct kempld_gpio_data { > + struct gpio_chip chip; > + int irq; > + struct kempld_device_data *pld; > + uint16_t mask; Just u16? > +}; (...) > diff --git a/drivers/gpio/gpio-kempld_now1.c b/drivers/gpio/gpio-kempld_now1.c > +#include Do you use this? > +#include > +#include > +#include And this? > +#include > +#include > +#include > +#include > + > +#include "gpio-kempld.h" (...) > + Most comments concern the other driver too. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/