* Stephen Warren <[email protected]> [130624 08:32]: > On 06/24/2013 07:15 AM, Linus Walleij wrote: > > From: Linus Walleij <[email protected]> > > > > From the inception ot the pin config API there has been the > > possibility to get a handle at a pin directly and configure > > its electrical characteristics. For this reason we had: > > > > int pin_config_get(const char *dev_name, const char *name, > > unsigned long *config); > > int pin_config_set(const char *dev_name, const char *name, > > unsigned long config); > > int pin_config_group_get(const char *dev_name, > > const char *pin_group, > > unsigned long *config); > > int pin_config_group_set(const char *dev_name, > > const char *pin_group, > > unsigned long config); > > > > After the intruction of the pin control states that will > > control pins associated with devices, and its subsequent > > introduction to the device core, as well as the > > introduction of pin control hogs that can set up states on > > boot and optionally also at sleep, this direct pin control > > API is a thing of the past. > > > > As could be expected, it has zero in-kernel users. > > Let's delete this API and make our world simpler. > > Reviewed-by: Stephen Warren <[email protected]>
Acked-by: Tony Lindgren <[email protected]> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
