Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp5072036ybi; Tue, 28 May 2019 07:08:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqzbVZamLecOhox+t45UAtUhhMrXhgSt8zUzmiisEYhz4tKUFB2TRo3fbUk4KR+dbsm20Oh1 X-Received: by 2002:a63:4621:: with SMTP id t33mr132401502pga.246.1559052481161; Tue, 28 May 2019 07:08:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559052481; cv=none; d=google.com; s=arc-20160816; b=RXX1CqVvAlBqShQdcdc9z2YASqTplrhzwTnLmDZfcVuMJzjPhcnsEIS1ebpAvcGORH SSxSdrcJ+NAdbxeuOxjftD7/XwK/oHN88vq3mRjRyxeSg+2Asjt1aQLJ6ndb9pAEetqE 49Nhebb0+Qu3GwOtF6Qmst+NEub0o+0BGd1JPDf+qceZ/fNFUHxYMTstSeY838nX7svP h54BPlfHpyRJtX0yyq4mYA3NeXtHVgS6xQtKSL8vqpOrs7YELXIrYVCc9Lb+h2W7zvc1 De2stSSEH/OVbLtE9/7VXIG12UA1Zlw6KFplKYAJCmduzV5mlf4MG667CktA8Qn7iXze 0LPA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:references:cc:to:from:subject:dkim-signature; bh=P5KVIiZh3Nun0m+9PqwCu28xvWWa75LyAqbjIU0ZS74=; b=OLtRwMLckYDSEehdoLlSO+rP6AWK4T/sLB4ycY6JIm/X/ZgxTptNy2Kc7YZd5zAljk RxM5yj3NKFy0vtCqkrTkiTHRQji3MTPnhNsfrCvPLubyl5jl+n4FpIq2q24mPxVRfZsE /H83G8apcG9hLfjmogVDBEocj83uIPWvotOA9XnafCUDInZMmPSavfjsIOY9OxgXqwIJ 2LFG8sjw6YQmxgzPNtWtTFfqTg7V7HGaVi5rnpDZXKeUauUOSKmgpbDZlZoSqWhdwz8A ryaK59SAnZ0QkkjHF/3k5W52lfUnK3XKdBhPfAfS3oVXdoh2FebvYhNJw2soSyGzphAt VRng== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=QIfoVyy8; 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=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m9si21889529plt.182.2019.05.28.07.07.45; Tue, 28 May 2019 07:08:01 -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=@ti.com header.s=ti-com-17Q1 header.b=QIfoVyy8; 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=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726788AbfE1Le4 (ORCPT + 99 others); Tue, 28 May 2019 07:34:56 -0400 Received: from fllv0016.ext.ti.com ([198.47.19.142]:45862 "EHLO fllv0016.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726305AbfE1Lez (ORCPT ); Tue, 28 May 2019 07:34:55 -0400 Received: from lelv0265.itg.ti.com ([10.180.67.224]) by fllv0016.ext.ti.com (8.15.2/8.15.2) with ESMTP id x4SBYoRP099127; Tue, 28 May 2019 06:34:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1559043290; bh=P5KVIiZh3Nun0m+9PqwCu28xvWWa75LyAqbjIU0ZS74=; h=Subject:From:To:CC:References:Date:In-Reply-To; b=QIfoVyy88eGvEv3Y6yfq8GFY/mwrZ/ioUsL0RpdqGiACEPymZ0gcg1WAQyMxEEEWD K8lOu2uDCJ3pbRerxtYkxDloAXJy1fGBij0MCCzQHO1DtHi3R1kOaTvGiQYKLuaVf0 LRw+juTFQbFsXU0i3N1WLHZiMrtf/mSwuyVmaUJM= Received: from DFLE103.ent.ti.com (dfle103.ent.ti.com [10.64.6.24]) by lelv0265.itg.ti.com (8.15.2/8.15.2) with ESMTPS id x4SBYnGN124533 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 28 May 2019 06:34:50 -0500 Received: from DFLE111.ent.ti.com (10.64.6.32) by DFLE103.ent.ti.com (10.64.6.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Tue, 28 May 2019 06:34:49 -0500 Received: from fllv0040.itg.ti.com (10.64.41.20) by DFLE111.ent.ti.com (10.64.6.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5 via Frontend Transport; Tue, 28 May 2019 06:34:49 -0500 Received: from [10.250.65.13] (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0040.itg.ti.com (8.15.2/8.15.2) with ESMTP id x4SBYmh8069662; Tue, 28 May 2019 06:34:48 -0500 Subject: Re: [PATCH v3 1/9] leds: multicolor: Add sysfs interface definition From: Dan Murphy To: Pavel Machek CC: , , , , References: <20190523190820.29375-1-dmurphy@ti.com> <20190523190820.29375-2-dmurphy@ti.com> <20190527103355.GA5287@amd> <522728b0-147b-3708-fea1-88a895491e05@ti.com> Message-ID: <34dbfab0-0dd4-cf9a-ed86-a74363981077@ti.com> Date: Tue, 28 May 2019 06:34:47 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <522728b0-147b-3708-fea1-88a895491e05@ti.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Pavel On 5/27/19 7:45 PM, Dan Murphy wrote: > Pavel > > On 5/27/19 5:33 AM, Pavel Machek wrote: >> On Thu 2019-05-23 14:08:12, Dan Murphy wrote: >>> Add a documentation of LED Multicolor LED class specific >>> sysfs attributes. >>> >>> Signed-off-by: Dan Murphy >>> --- >>> ? .../ABI/testing/sysfs-class-led-multicolor??? | 57 >>> +++++++++++++++++++ >>> ? 1 file changed, 57 insertions(+) >>> ? create mode 100644 >>> Documentation/ABI/testing/sysfs-class-led-multicolor >>> >>> diff --git a/Documentation/ABI/testing/sysfs-class-led-multicolor >>> b/Documentation/ABI/testing/sysfs-class-led-multicolor >>> new file mode 100644 >>> index 000000000000..2f102ede258b >>> --- /dev/null >>> +++ b/Documentation/ABI/testing/sysfs-class-led-multicolor >>> @@ -0,0 +1,57 @@ >>> +What:??????? /sys/class/leds//colors/sync_enable >>> +Date:??????? April 2019 >> I believe I suggested more reasonable interface. Why not use that? >> > > Can you please provide the reference to your interface? > I think I found the suggestion [0].? Assuming that was the suggestion it violates the kernel 1 value/file and there was agreement that this interface had value. In testing the interface, it made sense to be able to setup a color after writing each color brightness file and then syncing the color LEDs with the new brightness levels.? It also provides flexibility to be able to set a single LED color without writing sync.? The decision to do either or should really be a user space decision.?? If I have referenced the wrong thread please let me know which thread you are referring to. [0] https://lore.kernel.org/patchwork/patch/1057044/ Dan