From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [PATCH v2 2/3] leds: upboard: Add LED support Date: Tue, 23 Oct 2018 21:30:14 +0200 Message-ID: <20181023193014.GA32003@amd> References: <20180421085009.28773-1-javier@emutex.com> <1539969334-24577-1-git-send-email-dan@emutex.com> <1539969334-24577-3-git-send-email-dan@emutex.com> <20181023185453.GA27397@amd> <226e0df2-83f9-bee5-f359-a3e040d12311@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Return-path: Content-Disposition: inline In-Reply-To: <226e0df2-83f9-bee5-f359-a3e040d12311@gmail.com> Sender: linux-kernel-owner@vger.kernel.org To: Jacek Anaszewski Cc: Dan O'Donovan , linux-kernel@vger.kernel.org, Andy Shevchenko , Mika Westerberg , Heikki Krogerus , Lee Jones , Linus Walleij , linux-gpio@vger.kernel.org, linux-leds@vger.kernel.org, Carlos Iglesias , Javier Arteaga List-Id: linux-gpio@vger.kernel.org --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue 2018-10-23 21:09:54, Jacek Anaszewski wrote: > On 10/23/2018 08:54 PM, Pavel Machek wrote: > > Hi! > >=20 > >>> + led->field =3D devm_regmap_field_alloc(dev, regmap, conf); > >>> + if (IS_ERR(led->field)) > >>> + return PTR_ERR(led->field); > >>> + > >>> + led->cdev.max_brightness =3D 1; > >> > >> s/1/LED_ON/ > >=20 > > Actually, I prefer constant 1 here, as it makes it immediately obvious > > this supports just 0/1. > >=20 > > Yes, LED_ON is also 1, but I had to grep the header files for > > that... (I thought it was 255). >=20 > If we have the enum for that, let's use it. > Here's the commit message of the patch adding LED_ON - it should > be somehow familiar to you - see the ack. Well .. brightness =3D LED_ON; is good usage. max_brightness =3D LED_ON is IMO less readable than max_brightness =3D 1. Looking at situation again... Having LED_ON and LED_FULL, with some leds having max brightness of 1023, so LED_FULL is not really full brightness any more... Maybe it is time to get rid of the enum, and make it plain int. It does not really enumarate anything, and it does not help readability, either. Pavel > commit 4e552c8cb5bc9137e67e035bab8df6dddbca7384 > Author: Andi Shyti > Date: Thu Jan 5 11:34:12 2017 +0900 >=20 > leds: add LED_ON brightness as boolean value >=20 > Some devices do not handle the led brightness or simply don't > care about it. Conceptually said devices want to just switch on > or off the led. It is useless in this case to have a 255 range > of brightness, while just having an LED_ON and LED_OFF improves > the boolean meaning of the led status. >=20 > Signed-off-by: Andi Shyti > Acked-by: Pavel Machek > Signed-off-by: Jacek Anaszewski >=20 >=20 --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlvPdsYACgkQMOfwapXb+vImMACeKoO4h32MomIbcsmGThXHjn0m JpMAoIRistLuJPRkZMrx48Yq29zep+xm =MitW -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62--