On Wed, Sep 16, 2015 at 12:47:42PM +0200, Jacek Anaszewski wrote: > The initial purpose of brightness_set_sync op, introduced along with > the LED flash class extension, was to add a means for setting torch LED > brightness as soon as possible, which couldn't have been guaranteed by > brightness_set op. This patch renames the op to brightness_set_blocking, > which describes its purpose in a more generic way, and is beneficial > in view of the prospective changes in the core related to using > LED core's set_brightness_work for setting brightness for LED class > drivers that can sleep or use delays while setting brightness. ... > - /* > - * Set LED brightness level immediately - it can block the caller for > - * the time required for accessing a LED device register. > - */ > - int (*brightness_set_sync)(struct led_classdev *led_cdev, > - enum led_brightness brightness); > + /* Can sleep or use delays */ > + int (*brightness_set_blocking)(struct led_classdev *led_cdev, I'm no expert when it comes to flash photography with digital cameras. But to me the old comment seems better. Doesn't the caller want to know the flash is now giving out light? The new comment gives no indication of this, where as the old one does? Andrew > /* Get LED brightness level */ > enum led_brightness (*brightness_get)(struct led_classdev *led_cdev); > > -- > 1.7.9.5 > -- To unsubscribe from this list: send the line "unsubscribe linux-leds" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
