Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752728AbbHTQRB (ORCPT ); Thu, 20 Aug 2015 12:17:01 -0400 Received: from vps0.lunn.ch ([178.209.37.122]:37110 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752308AbbHTQQ7 (ORCPT ); Thu, 20 Aug 2015 12:16:59 -0400 Date: Thu, 20 Aug 2015 18:09:38 +0200 From: Andrew Lunn To: Jacek Anaszewski Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org, Sakari Ailus , Pavel Machek , Stas Sergeev Subject: Re: [PATCH/RFC v6 05/36] leds: Improve setting brightness in a non sleeping way Message-ID: <20150820160938.GF27457@lunn.ch> References: <1440081846-11697-1-git-send-email-j.anaszewski@samsung.com> <1440081846-11697-6-git-send-email-j.anaszewski@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1440081846-11697-6-git-send-email-j.anaszewski@samsung.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1107 Lines: 26 On Thu, Aug 20, 2015 at 04:43:35PM +0200, Jacek Anaszewski wrote: > This patch replaces led_set_brightness_async with > led_set_brightness_nosleep in all places where the most vital was setting > brightness in a non sleeping way but not necessarily asynchronously, which > is not needed for non-blocking drivers. O.K, so i've lost the plot. _sync, _asymc, _nosleep, etc. Too many changes without a clearly documented vision of what you are trying to achieve. How about splitting this up into at least two patch sets. 1) Add the brightness_set_blocking op and the minimum of changes needed to the core to make it work, and the driver changes taking out the work queue. 2) A set of patches cleaning up the core and its API. We want a well documented linux/leds.h and drivers/led/leds.h defining the APIs which users and triggers should be using. Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/