On Donnerstag, 12. April 2018 14:48:56 CEST Linus Walleij wrote: > On Wed, Mar 28, 2018 at 8:07 PM, Christian Lamparter <chunkeey@xxxxxxxxx> wrote: > > > - ret = gpiochip_add_pin_range(&pctrl->chip, dev_name(pctrl->dev), 0, 0, chip->ngpio); > > - if (ret) { > > - dev_err(pctrl->dev, "Failed to add pin range\n"); > > - gpiochip_remove(&pctrl->chip); > > - return ret; > > - } > > If you instead of deleteing this, just wrap it inside > something like: > > if (!of_property_read_bool(np, "gpio-ranges") { > (...) > } > > You will stay compatible with elder device trees, solving Björns > issue. You will only be adding hogs to newer device trees with > the ranges defined anyway. > > Be genereous with comments in the code if you choose this > approach so everyone realize what is going on. Thank you for your insightful advice. I just sent out v4 which goes the of_property_read_bool route. Let's wait and see what kbuilt-bot has to say. Best Regards, Christian -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html