Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp848506imm; Sat, 14 Jul 2018 14:22:00 -0700 (PDT) X-Google-Smtp-Source: AAOMgpd4/727tpWZR1s/9C9Y5JxA58wPjSOWMB4X1a7djpni6GBD+3tP6zlHUjPDBltrr60ns+0J X-Received: by 2002:a62:5486:: with SMTP id i128-v6mr12192018pfb.166.1531603320147; Sat, 14 Jul 2018 14:22:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531603320; cv=none; d=google.com; s=arc-20160816; b=xHeDMCP0kjhyq1ea79ofmqgxj9iCJXShXeGT5SLCQ5fcr4/z52idR1g7vpQ/KzhMMf FLSNhQQ9IcMtWZGjybJlNYXpPq+dNC1G3lR8iIjkAqrb5V4bMvMiabZqLwD2WYEU/MYb b2ZZK422Np69D/4Ry1VlD9jpY/OtCMphnd+tBMruJv40S6BzUesA6pYEmK+y5TwfzbUQ xWzAXYQnyEh7RAr17Wx4nvaRKGXpIxwrsid29uh8cJnuHjmCls7bTPbWL6uYZBSCrtjZ xpoChcwivq2K6Eyv2J+22r6x92Y3nubzSCUnXd+PHBztCy5wQoOmzR/mOle2KoSDp/MZ buKQ== 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=0sOcX8WU96wUp8sQ1o6noQjSVmI8AdFLGcw1R0isnW8=; b=XeUVYMCxovE8PXWmY2Lwj+khX76k3VLu87h9ZlqGJHBun1KPUIe4724uqMNOoB6L4w 2g2AYScB9E+/XDV6GTBsiaXrXgHnu/PPVJcBpjr1gvMFuPV6d+vcrTQKv/SsHW5V6H5w o7SPM7GffajvL92bwx25yiymPCazZ5RHLcCvQkPSMYW/7rBfdTWeXZRIlq6JVsQYF3Nm vSKZ0gHRfF0KNBaZh74SecMlhJoPatSlC4GmXT6Q/Mz9sZKvY+u6vxIgletFIApfBI0f ktU3M0/j7X9tKVhj8iSkDUXNKJFANsqTr1/KE8+VmBGE/2jJ3XVJ0Z/chnrqh3KF2N8z qykA== 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 y8-v6si14521311pfk.75.2018.07.14.14.21.31; Sat, 14 Jul 2018 14:22:00 -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 S1731526AbeGNVk5 (ORCPT + 99 others); Sat, 14 Jul 2018 17:40:57 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:45126 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731213AbeGNVk5 (ORCPT ); Sat, 14 Jul 2018 17:40:57 -0400 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id 3A4C180551; Sat, 14 Jul 2018 23:20:34 +0200 (CEST) Date: Sat, 14 Jul 2018 23:20:33 +0200 From: Pavel Machek To: Baolin Wang Cc: Jacek Anaszewski , Bjorn Andersson , Mark Brown , Linux LED Subsystem , LKML Subject: Re: [PATCH v3 1/2] leds: core: Introduce generic pattern interface Message-ID: <20180714212033.GA31950@amd> References: <1665b877dc2f886a90a00e3ca3b7425372d99b6e.1530248085.git.baolin.wang@linaro.org> <8da1b769-8aa3-9698-467a-2e7b0707fecf@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: 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 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. Best regards, Pavel =09 --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --17pEHd4RhPHOinZp Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAltKaSEACgkQMOfwapXb+vKJGwCdEF3ulFFXbcvA4gYX9fRI9HwR u4sAoJO/HWV9eFgalZ/ymHT3IN5s5VSR =f5Gu -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp--