Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933115AbbBIOlk (ORCPT ); Mon, 9 Feb 2015 09:41:40 -0500 Received: from mail-oi0-f49.google.com ([209.85.218.49]:50954 "EHLO mail-oi0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932842AbbBIOli (ORCPT ); Mon, 9 Feb 2015 09:41:38 -0500 MIME-Version: 1.0 In-Reply-To: <4B6D6D87A8FB62428BE0A3E38461A1AB18D6B200@irsmsx105.ger.corp.intel.com> References: <4B6D6D87A8FB62428BE0A3E38461A1AB18D6B200@irsmsx105.ger.corp.intel.com> From: Tyler Hall Date: Mon, 9 Feb 2015 09:41:17 -0500 Message-ID: Subject: Re: gpio-pxa: getting GPIOs by devicetree phandle broken To: "Holmberg, Hans" Cc: Alexandre Courbot , "linux-gpio@vger.kernel.org" , "devicetree@vger.kernel.org" , Daniel Mack , Linus Walleij , Linux Kernel Mailing List , Howard Cochran , Robert Jarzmik Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1513 Lines: 32 > The issue with multiple gpiochips per of-node could be worked around as followed I believe, comments? > > diff --git a/drivers/gpio/gpiolib-of.c b/drivers/gpio/gpiolib-of.c > index 08261f2..43984ab 100644 > --- a/drivers/gpio/gpiolib-of.c > +++ b/drivers/gpio/gpiolib-of.c > @@ -47,11 +47,12 @@ static int of_gpiochip_find_and_xlate(struct gpio_chip *gc, void *data) > ret = gc->of_xlate(gc, &gg_data->gpiospec, gg_data->flags); > if (ret < 0) { > /* We've found the gpio chip, but the translation failed. > - * Return true to stop looking and return the translation > - * error via out_gpio > + * Store translation error in out_gpio. > + * Return false to keep looking, as more than one GPIO chip > + * could be registered per of-node. > */ > gg_data->out_gpio = ERR_PTR(ret); > - return true; > + return false; > } > > gg_data->out_gpio = gpiochip_get_desc(gc, ret); As long as we're ok with multiple gpiochips per of-node, this would work for me. It'll change the preference of which chip returns the error in the case of multiple chips, but that's already undefined behavior. -- 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/