Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1029976imm; Wed, 18 Jul 2018 15:18:22 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfWzyDJLrqQL3ozIL6FA8tck3HroNQTzWJBoc3Rv4d4I0mQtjDOy/trB74bvbHLOQP1+x4v X-Received: by 2002:a17:902:3e3:: with SMTP id d90-v6mr7594498pld.12.1531952302697; Wed, 18 Jul 2018 15:18:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531952302; cv=none; d=google.com; s=arc-20160816; b=xke10QcCbmFPFJaeyBJD8Hzbm+qqXVg1SE5CAy0jB/A7o0TiFqP+VYJF3A7l5MYu87 775wqkpjVL/5GSHcehMI4RmzGfm1csVCTPKXIQoO+l6MiK6glUo4V3UFWTsYPH4Mxy8X refJc39wezu+JtdyOoX60okxrXhA/3ycQe7gd/Ol5Gm5PTMUbvkDPsP5A3BUrSwiYF9i //DEHN8dxwwI4K+90J2jHUoSi3Z2Ruj9DiTYU0YcT6qkSfZFkAQIfQyxJ8dDTKYZxQ56 SEaJnQDntZkeYWZDkjjZI/81NSLFQYK9N04bvluictsQHm0bZ3Aim85Zyxjy8ttBBNxS 14cg== 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=BJ0S7FCJrpN+eivySX8kw2v+n+7HhRY3QbImnSECIOg=; b=smwwfCgVssgQtvOgk/PNfH/SEFFyNRnh+gUNfLcQJE2QDmoybqFbgkciZsTFymOWNV EQrf4uz2i/oj5PSFmT4IZxI/8y3GrJpbxFSDQY0l2bAHlx/euEgLAdJPYh1gIcj5xWVU lXMweJLdQWbynLSm++EjfQETbzV/zSrBgZJAJhhJTS5QX85afQ/tuDUcDfha4Hv9sBiv sMOat1A2Jc3rx/dOnaJg1MqelmbzngEGm/D/lqGuMa2prZo+c64PoJ9i0iN49tSkGsAi RhB/pF7vY8mROmTyF/I00mCbvvi4vp11U3VJK8LIcKjZ11buwpd9wDXAHYIYeTAV1XGc YYJw== 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 v2-v6si4066873pgt.228.2018.07.18.15.18.07; Wed, 18 Jul 2018 15:18: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 S1730053AbeGRW5W (ORCPT + 99 others); Wed, 18 Jul 2018 18:57:22 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:35173 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729692AbeGRW5W (ORCPT ); Wed, 18 Jul 2018 18:57:22 -0400 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id 1CCF780498; Thu, 19 Jul 2018 00:17:23 +0200 (CEST) Date: Thu, 19 Jul 2018 00:17:17 +0200 From: Pavel Machek To: Jacek Anaszewski Cc: David Lechner , Baolin Wang , Bjorn Andersson , Mark Brown , Linux LED Subsystem , LKML Subject: Re: [PATCH v3 1/2] leds: core: Introduce generic pattern interface Message-ID: <20180718221717.GA5451@amd> References: <20180714212033.GA31950@amd> <00fa2693-9308-8d74-0124-04066a76c35a@gmail.com> <20180714222924.GA2776@amd> <20180714223907.GB2776@amd> <1138f834-e805-6076-bb5b-aa1fdc1f2606@gmail.com> <2c3a8911-150a-9b25-2a66-a9432047f96b@lechnology.com> <68996338-a902-2b57-0bb9-df274a496b06@gmail.com> <20180718075637.GA10279@amd> <913151e4-c19f-9a22-697c-52a9fb48cb32@gmail.com> <0e0cd8f7-dc73-6733-65f2-9a14506b0f0e@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline In-Reply-To: <0e0cd8f7-dc73-6733-65f2-9a14506b0f0e@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 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > >Please keep in mind that this is ABI documentation for the pattern file > >to be exposed by LED core, and not by the pattern trigger, that, as we > >agreed, will be implemented later. In this case, I'd go for >=20 > Gosh, I got completely distracted by the recent discussion about > pattern synchronization. >=20 > So, to recap, we need to decide if we are taking Baolin's solution > or we're opting for implementing pattern trigger. >=20 > If we choose the latter, then we will also need some software > pattern engine in the trigger, to be applied as a software pattern > fallback for the devices without hardware pattern support. > It will certainly delay the contribution process, provided that Baolin > would find time for this work at all. I'd recommend the latter. Yes, software pattern as a fallback would be nice, but I have that code already... let me get it back to running state, and figure out where to add interface for "hardware acceleration". I'd like to have same interface to userland, whether pattern can be done by hardware or by software. Best regards, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --YZ5djTAD1cGYuMQK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAltPvG0ACgkQMOfwapXb+vLXtACfTKHNaRLxjr+WDpk/1nmcemfr p4AAoI0XSXo2xJH9nrjOkmt2Vmgs9ACb =kDS4 -----END PGP SIGNATURE----- --YZ5djTAD1cGYuMQK--