On Thu, Dec 14, 2017 at 12:54 PM, Christophe LEROY <christophe.leroy@xxxxxx> wrote: > Why is it necessary now to set a parent to the GPIO chip whereas it was not > necessary before ? (...) > Is there an easy modification that can be done to your new function > devprop_gpiochip_set_names() in order to have the GPIO drivers work as > before ? I am also worried about this. I have felt that the device property paradigm is too ambitious and assume too much about the subtle semantic differences between DT and ACPI DSDT. But maybe I'm just whiney. Looking forward to good ideas on how to solve this! Mika: is is possible to revert this without breaking something else, if we need to? Yours, Linus Walleij -- 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