Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp884823imm; Sat, 14 Jul 2018 15:30:22 -0700 (PDT) X-Google-Smtp-Source: AAOMgpf8qWn+WPg58ycauhYUrlNgQDLQZtW8IAiLt8ocbM9p/SoZqO62jGSSmtBQYl17fThQQJTl X-Received: by 2002:a17:902:a24:: with SMTP id 33-v6mr11341832plo.88.1531607422061; Sat, 14 Jul 2018 15:30:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531607422; cv=none; d=google.com; s=arc-20160816; b=jLzklCE0HCJ+4gy1PLcVGHnIfFvIWUEiG688mVM/B3eukT2eYksFoiG+9VEvElPvjo vnLnkT7nuiOz5HY/K9K2PpSO/1AVRgq2n7VRR8UqJHWsQ+xncABog3ZfU9Njf8W2CFH9 IfL3DdL84pGYXn/+XOW1IHZF7s80vdJsf+ySNMv0J7L1B8dLTyIuG8WZf40p4tUnog3d LmUv2LzGWvCG1HoCnDDATRpmntnQZ/N8+6z6EuIeeMYi81R8KMXiRxYuGPk8VLiU+99l qgrarK03MKQ2Ps7XZ7BQcS+9xwJ3uJOErDXcTTF4s19yfKfdzoaplSTYKdzCnmNvEBFq Afvg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=pSBZ4teiT65KdseN7yIIIb+0e7AZnQifdUrDUKr1cgk=; b=mUhCqMPrzMYZk2L2xiJzj3Tsd3IhxZ+HCzcAHD/1Zku0FIPNq3sDx90xGzzylILMnh 15sqZHC0poPLvHF1FguAJOP8+ZIj34HSFK01F4AFfmYQuTh4EgtsLSljECNCPzhbvVLn iR8rYBIyCdpUG+k0swFxISPj9jqrcrbHN9WIiAUAvGBgKYdWyOlAz5NfMOqqbq+f3/4B 1zP6v86RWBVv40Ykper9sjbgga2JOp2NSIC913WtAuTauEYd8IP/u/qt8kZ5d/PFg2LH s1H6HiIa2t5+TL3isxRYWbzzH9JxnC88EyFuNzCQYhZx3I749x4VZSdDWW9YMLFrjagi GeMA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s15-v6si27023371pgr.269.2018.07.14.15.30.06; Sat, 14 Jul 2018 15:30:22 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731893AbeGNWuA (ORCPT + 99 others); Sat, 14 Jul 2018 18:50:00 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:46395 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731454AbeGNWuA (ORCPT ); Sat, 14 Jul 2018 18:50:00 -0400 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id BC08C8049F; Sun, 15 Jul 2018 00:29:25 +0200 (CEST) Date: Sun, 15 Jul 2018 00:29:25 +0200 From: Pavel Machek To: Jacek Anaszewski Cc: Baolin Wang , Bjorn Andersson , Mark Brown , Linux LED Subsystem , LKML Subject: Re: [PATCH v3 1/2] leds: core: Introduce generic pattern interface Message-ID: <20180714222924.GA2776@amd> References: <1665b877dc2f886a90a00e3ca3b7425372d99b6e.1530248085.git.baolin.wang@linaro.org> <8da1b769-8aa3-9698-467a-2e7b0707fecf@gmail.com> <20180714212033.GA31950@amd> <00fa2693-9308-8d74-0124-04066a76c35a@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Q68bSM7Ycu6FN28Q" Content-Disposition: inline In-Reply-To: <00fa2693-9308-8d74-0124-04066a76c35a@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 --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun 2018-07-15 00:02:57, Jacek Anaszewski wrote: > Hi Pavel, >=20 > On 07/14/2018 11:20 PM, Pavel Machek wrote: > >Hi! > > > >>>It also drew my attention to the issue of desired pattern sysfs > >>>interface semantics on uninitialized pattern. In your implementation > >>>user seems to be unable to determine if the pattern is activated > >>>or not. We should define the semantics for this use case and > >>>describe it in the documentation. Possibly pattern could > >>>return alone new line character then. > > > >Let me take a step back: we have triggers.. like LED blinking. > > > >How is that going to interact with patterns? We probably want the > >patterns to be ignored in that case...? > > > >Which suggest to me that we should treat patterns as a trigger. I > >believe we do something similar with blinking already. > > > >Then it is easy to determine if pattern is active, and pattern > >vs. trigger issue is solved automatically. >=20 > I'm all for it. I proposed this approach during the previous > discussions related to possible pattern interface implementations, > but you seemed not to be so enthusiastic in [0]. >=20 > [0] https://lkml.org/lkml/2017/4/7/350 Hmm. Reading my own email now, I can't decipher it. I believe I meant "changing patterns from kernel in response to events is probably overkill"... or something like that. Sorry about confusion, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --Q68bSM7Ycu6FN28Q Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAltKeUQACgkQMOfwapXb+vIwGwCdGSEWCtTrqnALWtu/u3PaXpkp nyMAniy/PdfB/SjZFi/V93NsCT/Lybcs =l8Lc -----END PGP SIGNATURE----- --Q68bSM7Ycu6FN28Q--