From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753964AbbIWJee (ORCPT ); Wed, 23 Sep 2015 05:34:34 -0400 Received: from mailout4.w1.samsung.com ([210.118.77.14]:62774 "EHLO mailout4.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753292AbbIWJeL (ORCPT ); Wed, 23 Sep 2015 05:34:11 -0400 X-AuditID: cbfec7f5-f794b6d000001495-e9-5602721092ad Message-id: <5602720F.7080405@samsung.com> Date: Wed, 23 Sep 2015 11:34:07 +0200 From: Jacek Anaszewski User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8 MIME-version: 1.0 To: Andrew Lunn Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org, sakari.ailus@linux.intel.com, stsp@users.sourceforge.net, pavel@ucw.cz, ospite@studenti.unina.it, davem@davemloft.net, linus.walleij@linaro.org, ricardo.ribalda@gmail.com, p.meerwald@bct-electronic.com Subject: Re: [PATCH 3/5] leds: Rename brightness_set_sync op to brightness_set_blocking References: <1442400464-27367-1-git-send-email-j.anaszewski@samsung.com> <1442400464-27367-4-git-send-email-j.anaszewski@samsung.com> <20150922185426.GC20029@lunn.ch> <5602648D.9040609@samsung.com> In-reply-to: <5602648D.9040609@samsung.com> Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupkkeLIzCtJLcpLzFFi42I5/e/4VV2BIqYwg9d7TS3O3z3EbDHnfAuL xZQ/y5ksLu+aw2ax9c06Rovf3btZLPoOSVrcPXWUzaKrex6Txact35gsOvumsThwe6y4d5fJ Y8vKm0weO2fdZfe4c20Pm8e8k4EeO3d8ZvI4dGEdi8eK1d/ZPZpOtbN6fN4kF8AVxWWTkpqT WZZapG+XwJVxeOFjpoIGoYrVW9qZGhj7+LoYOTkkBEwk2g98YoSwxSQu3FvP1sXIxSEksJRR 4ti0tewQzjNGiYau48wgVbwCWhLX9qwCs1kEVCWubL/OBmKzCRhK/HzxmgnEFhWIkPhzeh8r RL2gxI/J91hAbBEBBYkpJ/+wggxlFuhlkvj+bTNYs7BApMTy9pXMENtOMkpcm3cQrINTQFui cdY9sKnMAtYSKydtY4Sw5SU2r3nLPIFRYBaSJbOQlM1CUraAkXkVo2hqaXJBcVJ6rpFecWJu cWleul5yfu4mRkgEfd3BuPSY1SFGAQ5GJR5ei++MYUKsiWXFlbmHGCU4mJVEeJ8GMIUJ8aYk VlalFuXHF5XmpBYfYpTmYFES5525632IkEB6YklqdmpqQWoRTJaJg1OqgTHswlbvondrhGcI HPx59deKAOGkitNsXz/0el51VvnCffp7h/CWkCUBOue3nTulZHVySjmXr177Iwv9dCFenS9L znE/Y57eNtWvhTPiFNO6V/ct7l+//59D1JA9ocGOq8H0Javbx3oFzYmKFXdZ7D4aCm2XNtu9 dwNTu8Eq860zs/iVhRfU6yuxFGckGmoxFxUnAgBwqIkRnAIAAA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/23/2015 10:36 AM, Jacek Anaszewski wrote: > On 09/22/2015 08:54 PM, Andrew Lunn wrote: >> 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. > > This op is now not specific to flash LEDs. The last sentence in the > commit message explains this, but now I see that it is too long. > Let's change it to: > > "This patch renames the op to brightness_set_blocking, > which describes its purpose in a more generic way. It is beneficial > in view of the prospective changes in the LED core, aiming at removing > the need for using work queues in LED class drivers that can sleep > or use delays while setting brightness." > >> But to me the old comment seems better. > > I changed it to highlight the essence of how it differs from > brightness_set. > >> Doesn't the caller >> want to know the flash is now giving out light? > > We have strobe_get op for this, but it is in led-class-flash extension. > This is irrelevant here. I focused myself on flash mode of flash LED, but you asked probably about brightness in torch mode, which can be obtained with brightness_get op, if implemented by the driver. -- Best Regards, Jacek Anaszewski