Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp871905imm; Sat, 14 Jul 2018 15:05:19 -0700 (PDT) X-Google-Smtp-Source: AAOMgpeEYucIuppAJkv5ku0KfvdNeXy1rlAfX1sNt/dteqWEFmXaIGDwgr8hf0ijAEw/o4OsnUh/ X-Received: by 2002:a62:d8c:: with SMTP id 12-v6mr12496917pfn.202.1531605919393; Sat, 14 Jul 2018 15:05:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531605919; cv=none; d=google.com; s=arc-20160816; b=xHa0PAvob69ZeRvIqQL/plPezOg5vC1U7ZnkBP1HUxh77NJX978kM1Zx9rfHoemYyF NdXWD6ZWbfm1GbaXxgKYRzfeY6mGdXn0EwM/1CIT+BpTSwip/d1pA/2g0BXOACGTc8tk CipcGq9Bqj2tW7HjeQvvdoemgSeFr5Tr3HAImxKfR2zgXQoIVtpBb5UEX9NJrzH9TjCU WpbKUiKax9eR/MEu4DqmVWbrqm7jdfJ+9ztF38ToaulC+kw953OCdsgRc19ir/dyQ7uE cs9GQWoksoES70Bowy4j6JQN5RQFg2i6FpqkdC9R8m2bCWBhMHoHFnQEjF5v8xxonLkZ Kf/Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=K7ig861cIsEqOm33FlzLYu3y3dREU2igERhoL9/mHZY=; b=DMaHNY6ChnFWEuarz7R4t3rzxwfUxplxBK7kvRSvoj2yYcHm+azS3uWrdx8jKmG4wO 9a7VhsY2iJhMYyVKNX0OP5pG7OO8o1NUDRK9sQfJ3kTrQICkBR0h90ihgdl42G41u67Z iD7ZPLn2V0MvvrHFhEb9P3Jh7pzP1hCzjqDYWwT4Xh+5JQ/k3cRkLZesjKfWfLGoaDSP m5lTY2Q6He9FlXzWPTe5qyE1ok+MKPQwaw6QcN6tj3m7DKaBX23LS+H5eQVX1OhHisqh xq0080NMRhgbtulW4yYqGS4nNfhORXCN8IB02D+9xaIHph+pRngvtyvTdedZFmVsdBCz fhPQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=QrpUYVvy; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x18-v6si3367102pll.193.2018.07.14.15.04.31; Sat, 14 Jul 2018 15:05:19 -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; dkim=pass header.i=@gmail.com header.s=20161025 header.b=QrpUYVvy; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731583AbeGNWXa (ORCPT + 99 others); Sat, 14 Jul 2018 18:23:30 -0400 Received: from mail-wr1-f67.google.com ([209.85.221.67]:40087 "EHLO mail-wr1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727580AbeGNWXa (ORCPT ); Sat, 14 Jul 2018 18:23:30 -0400 Received: by mail-wr1-f67.google.com with SMTP id t6-v6so28281017wrn.7; Sat, 14 Jul 2018 15:03:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=K7ig861cIsEqOm33FlzLYu3y3dREU2igERhoL9/mHZY=; b=QrpUYVvyRkFBtFhaYAJw9v2HqGNSv8zh2IKp5gH0B74JdAKmsZiAAZ9WU6jT1z4Vlo cZeCFSSbe3u1qXvfuRXyJlWVWwc/3b/DdNxILdGFE3/Cpgdkoc2xFYnR5aXo9EfWHB/M T9EJj4mOtwrBdbsh0mGdquACQJz4vzz4GO7rTofyKHFom1WrZwWur++pclZE3HYAXJaJ 7RKgqYIOhFlLw1LQek8ktFUWjd2qV6Qb7idMyG2UFiHj602B2KGet/7qqg+arzDYVRVI kzv0p5LJol8SvaQnXnWveU16QFSQAbw/+uSE9scy9OrwtTbn2ZAWYRNdWIZeLGB1s/0d g5XA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=K7ig861cIsEqOm33FlzLYu3y3dREU2igERhoL9/mHZY=; b=p2CQwDgm+7+450Tg5uPeTi5G/1GfKUyTIJGFNtOhFhWddZu4H2/FOmVuHDLZu8OT0f 7hqIvnJCP4g5v+XGRrNzZsINMwvKWDqZZZ+iGxTGrrYg1kY97Dqj83VNxs5vPpAMAshy /zBrrFVFZvWpC6PcE4c0UQ9wOWE2XC321yyqzikjlvT8nALG4rvO6gqXfs71Oz6Zw9gl daTfVbJ9yFXg1W/BqZopw/komVMo5AcOT1+kKSyNrT5b3u4fGYG7+ktq7tV3VkApWpTp kniPbid1SkdPjlFuTOil53atafiFxFfj6YTQ/+mPIHJ12e1T2D9gNf+g3OG1NLhoS/r7 j7iA== X-Gm-Message-State: AOUpUlF0Jpradg1jz1m3MpCa9Cbe3qKGwVMnTET4zPK0eaHTl28ZCVLL z9jIWN/xI2ddnuc0wzXK2H/XqgTD X-Received: by 2002:a5d:4452:: with SMTP id x18-v6mr8864537wrr.227.1531605780334; Sat, 14 Jul 2018 15:03:00 -0700 (PDT) Received: from [192.168.1.18] (cji197.neoplus.adsl.tpnet.pl. [83.31.58.197]) by smtp.gmail.com with ESMTPSA id f190-v6sm23065767wmd.0.2018.07.14.15.02.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 14 Jul 2018 15:02:59 -0700 (PDT) Subject: Re: [PATCH v3 1/2] leds: core: Introduce generic pattern interface To: Pavel Machek , Baolin Wang Cc: Bjorn Andersson , Mark Brown , Linux LED Subsystem , LKML References: <1665b877dc2f886a90a00e3ca3b7425372d99b6e.1530248085.git.baolin.wang@linaro.org> <8da1b769-8aa3-9698-467a-2e7b0707fecf@gmail.com> <20180714212033.GA31950@amd> From: Jacek Anaszewski Message-ID: <00fa2693-9308-8d74-0124-04066a76c35a@gmail.com> Date: Sun, 15 Jul 2018 00:02:57 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180714212033.GA31950@amd> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Pavel, 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. 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]. [0] https://lkml.org/lkml/2017/4/7/350 -- Best regards, Jacek Anaszewski