Hello, On Thu, Mar 23, 2017 at 11:20:39AM +0100, Geert Uytterhoeven wrote: > But having the error breaks setups where the GPIO is optional and does > not exist. so the right way forward is to check harder in the situation where -ENOSYS was returned before to determine if there is really no GPIO to be used. "Oh, there are hints that there is no GPIO (GPIOLIB=n), so lets assume there isn't." is wrong. Can we please properly fix the problem instead of papering over it? > Make sure to enable all drivers and subsystems you need when building > your kernel. That's always true. And may indeed be hard to debug (e.g. what > kernel options do I need to make systemd work?). It's worse here. If you forget to enable a driver the device isn't bound and that's obvious to diagnose. When ignoring an optional GPIO there might be a device that claims to work but fails to do so. (e.g. you write to memory, write() returns 0, but the data never landed there.) > > write(2) and close(2) succeed most of the time, too. Still it's not a > > good idea to not check the return value. Or let the kernel return > > success unconditionally. > > Writing all bytes passed in the buffer is "optional" in another sense than > an "optional" GPIO: you must retry the write, while you can continue if > an optional GPIO is not present. And that is the point. You can continue *iff* the optional GPIO is not present. The patch in question removes the ability to determine if that GPIO is present and claims it is not present. > > So you exchanged many obvious and easy to fix problems with a few hard > > ones. I don't agree that's a good idea, but you seem to be willing to > > try it. Good luck. > > Yeah, before drivers had to explicitly ignore -ENOSYS if they want to > support platforms with and without GPIOLIB. Bad... Doing things right is sometimes not maximally easy. But that is no excuse to do it wrong. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ | -- 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