From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_PASS,URIBL_BLOCKED,URIBL_DBL_ABUSE_MALW, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E3BD5ECE560 for ; Fri, 21 Sep 2018 21:12:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8FF392156E for ; Fri, 21 Sep 2018 21:12:25 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8FF392156E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ucw.cz Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391521AbeIVDDC (ORCPT ); Fri, 21 Sep 2018 23:03:02 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:59142 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2391323AbeIVDDC (ORCPT ); Fri, 21 Sep 2018 23:03:02 -0400 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id 09A3480736; Fri, 21 Sep 2018 23:12:21 +0200 (CEST) Date: Fri, 21 Sep 2018 23:12:21 +0200 From: Pavel Machek To: Jacek Anaszewski Cc: Baolin Wang , rteysseyre@gmail.com, Bjorn Andersson , Mark Brown , Linus Walleij , Linux LED Subsystem , LKML Subject: Re: [PATCH v12 1/2] leds: core: Introduce LED pattern trigger Message-ID: <20180921211221.GB18062@amd> References: <67ebebf02edd6d8ee42a13b139733e9cc680ea86.1536631975.git.baolin.wang@linaro.org> <324778a9-a32c-ae6e-337a-39845f214bfc@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1UWUbFP1cBYEclgG" Content-Disposition: inline In-Reply-To: <324778a9-a32c-ae6e-337a-39845f214bfc@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --1UWUbFP1cBYEclgG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri 2018-09-21 22:59:40, Jacek Anaszewski wrote: > Hi Baolin, >=20 > On 09/21/2018 05:31 AM, Baolin Wang wrote: > > Hi Jacek and Pavel, > >=20 > > On 11 September 2018 at 10:47, Baolin Wang wro= te: > >> This patch adds one new led trigger that LED device can configure > >> the software or hardware pattern and trigger it. > >> > >> Consumers can write 'pattern' file to enable the software pattern > >> which alters the brightness for the specified duration with one > >> software timer. > >> > >> Moreover consumers can write 'hw_pattern' file to enable the hardware > >> pattern for some LED controllers which can autonomously control > >> brightness over time, according to some preprogrammed hardware > >> patterns. > >> > >> Signed-off-by: Raphael Teysseyre > >> Signed-off-by: Baolin Wang > > Do you have any comments for the v12 patch set? Thanks. >=20 > We will probably have to remove hw_pattern from ledtrig-pattern > since we are unable to come up with generic interface for it. > Unless thread [0] will end up with some brilliant ideas. So far > we're waiting for Pavel's reply. >=20 > [0] https://lkml.org/lkml/2018/9/13/1216 Patch 1/2 is not controversial; I believe we can apply it now. 2/2: Non-linear or not, can we just ignore that for now? We don't have well-defined meaning of what brightness 128 means, so... I believe we can do that reasonably safely. I don't exactly understand what you are saying with the four tuples. Yes, sc27xx currently has a limit where it can do single rise, hold, lower, hold at zero. That is described by pattern: "0 rise_duration brightness high_duration brightness fall_duration 0 low_= duration" We should add this to sc27xx handler: > I'd actually like to see this at begining of function: > if (pattern[0].brightness !=3D 0) > return -EINVAL; > if (pattern[2].brightness !=3D 0) > return -EINVAL; > if (pattern[3].brightness !=3D 0) > return -EINVAL; > if (pattern[1].brightness !=3D pattern[2].brightness) > return -EINVAL; >=20 > ..so if user writes something unexpected, he gets the error back. Then it is compatible -- or should be. Pattern trigger should do the same -- rise, hold, lower, hold at zero. I don't really see the problem. Best regards, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --1UWUbFP1cBYEclgG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlulXrUACgkQMOfwapXb+vJjxwCfShrrN7WuiyD03m4OCK62wOJr tawAoMTx6qvVG0GNl5/Ei3a78aTJTMuE =3PAe -----END PGP SIGNATURE----- --1UWUbFP1cBYEclgG--