Received: by 10.223.176.5 with SMTP id f5csp1082392wra; Sat, 3 Feb 2018 17:57:07 -0800 (PST) X-Google-Smtp-Source: AH8x2253NIh4Z8//qzZ3naXZQfFhSzjEp7tSvtS3AUw4hN9tZOfcCEH29HZhyLwrMIdDrtRNaQ24 X-Received: by 10.98.41.68 with SMTP id p65mr1698240pfp.86.1517709427197; Sat, 03 Feb 2018 17:57:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517709427; cv=none; d=google.com; s=arc-20160816; b=ybEqr5SPGPChrunqyW6uLq+qRKnQRw8UJoSq+kYN1s0CeZB+cbcc2I1HzZDdM7Rwx9 y/ftv59Ev7qp9D/nn9uOny1g11VZOy77JFnAs1h48uJQOfzuk69scvLwsj9u7G0H+wLu mpgz8LWQ/rKnAfBD24TxP+Yur6QM6u5uR+gUvVe79vv6YquSE9XX45FhSh2XjtpztyN+ revye4H/W0JcYCdB3LihzTSPZRlc1J/XNDiVxVfytW/JrvHNmwyco5M0LYvmhjEirsAY 3me0e2aVR7eHvsh1iBe7umy4tJd8o5U6i0rwj0DDbofcDAdok2sspPzT7zTXLr2Bwii2 ogCA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :content-id:spamdiagnosticmetadata:spamdiagnosticoutput :content-language:accept-language:in-reply-to:references:message-id :date:thread-index:thread-topic:subject:cc:to:from:dkim-signature :arc-authentication-results; bh=yv9nv45yLR9E3uztAmRJI4pMcLjvH+IcpX+EyzB1dJs=; b=cU2lOHFz7L2j60UeicmdXlz0qX5FwxrljQC7wAT8rDv7TWss/iHqOuAbHSh7hqu8lW MURO7FDNr2P3+eoSveZm+UPIUpUHGEhZ/oCCT92RbNOxrmnnYF1Y6Oagsd9LEXccebKG VXgkP9kK3YCYcPhOD7idzxD82v7ilMoUjLeAa/dr/kTP0zIjniJspMEQvJbX84Czlo2/ +1bRKrYCb9tEMvsjicGLYGGpdypSWoFm9uxBcRYyWF2yZraGAdiMJ0CP57m3iP+HDcCd SLMbHbIjZ+j9hTtSGcJV8vLswJ8KJLDEOQ0Gxv2BDd4NPX8qEfhR8LOpNVvgzIfndJFO Jhdw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@microsoft.com header.s=selector1 header.b=XxKw9+V4; 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=REJECT sp=REJECT dis=NONE) header.from=microsoft.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f80si2691646pfk.88.2018.02.03.17.56.52; Sat, 03 Feb 2018 17:57:07 -0800 (PST) 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=@microsoft.com header.s=selector1 header.b=XxKw9+V4; 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=REJECT sp=REJECT dis=NONE) header.from=microsoft.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752592AbeBDAan (ORCPT + 99 others); Sat, 3 Feb 2018 19:30:43 -0500 Received: from mail-bn3nam01on0106.outbound.protection.outlook.com ([104.47.33.106]:23504 "EHLO NAM01-BN3-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752193AbeBDAai (ORCPT ); Sat, 3 Feb 2018 19:30:38 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=yv9nv45yLR9E3uztAmRJI4pMcLjvH+IcpX+EyzB1dJs=; b=XxKw9+V4lcGG6k8mOM8XJut0m1xx6Tzrzj5F+2TLofNVAG2yFHuOoajzCZ96VW+VhZ53HOQLN1B8LVn9qOAouLZB8GHVBuFW4pYc0Wt7dvT0pM8xLLyXYjO6bD44tpu2oATf7PiNyaofI/bdIt47RciWU/VaqeVqtXVoaGXs/5s= Received: from DM5PR2101MB1032.namprd21.prod.outlook.com (52.132.128.13) by DM5PR2101MB0901.namprd21.prod.outlook.com (52.132.132.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.506.3; Sun, 4 Feb 2018 00:30:36 +0000 Received: from DM5PR2101MB1032.namprd21.prod.outlook.com ([fe80::3056:4338:5f9d:bfad]) by DM5PR2101MB1032.namprd21.prod.outlook.com ([fe80::3056:4338:5f9d:bfad%6]) with mapi id 15.20.0506.000; Sun, 4 Feb 2018 00:30:36 +0000 From: Sasha Levin To: Pavel Machek CC: "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , Matthieu CASTET , "linux-leds@vger.kernel.org" , Jacek Anaszewski Subject: Re: [PATCH AUTOSEL for 4.14 065/110] led: core: Fix brightness setting when setting delay_off=0 Thread-Topic: [PATCH AUTOSEL for 4.14 065/110] led: core: Fix brightness setting when setting delay_off=0 Thread-Index: AQHTnRjyue81aK36CEu9eh05vWJz5aOTItkAgABBrIA= Date: Sun, 4 Feb 2018 00:30:36 +0000 Message-ID: <20180204003029.2lkcmh6wvzpnlrls@sasha-lappy> References: <20180203180015.29073-1-alexander.levin@microsoft.com> <20180203180015.29073-65-alexander.levin@microsoft.com> <20180203203525.GA5860@amd> In-Reply-To: <20180203203525.GA5860@amd> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [52.168.54.252] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1;DM5PR2101MB0901;7:h1RFVhaYqKf2wq6H9IJMOPJ6cOidtXJJGrBxQ7tMBm0xCkC0HdI56ALWjg69R/SVcx326LEguZxzFTZlGENT8VpyxTzza1aVTA5MmmypWFiyUBDLYOZNDHacfDkCfP87xZLL/3T9ti/haO8UWC1k9vWJ5iSHSIVz02CK8b8fyXPdJK212riBCQF81nwUupxa0vgZkFCXVpzb0MozOcaYwEGLjbFhJIE8xEDMtJj2bSWEtC8Xf0RDuXzADWflpiJw x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-ht: Tenant x-ms-office365-filtering-correlation-id: 5053a7d5-9fcd-4ca8-5fae-08d56b66826d x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(7020095)(4652020)(48565401081)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7193020);SRVR:DM5PR2101MB0901; x-ms-traffictypediagnostic: DM5PR2101MB0901: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(61425038)(6040501)(2401047)(5005006)(8121501046)(3231101)(2400082)(944501161)(10201501046)(3002001)(93006095)(93001095)(6055026)(61426038)(61427038)(6041288)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123560045)(20161123558120)(20161123564045)(6072148)(201708071742011);SRVR:DM5PR2101MB0901;BCL:0;PCL:0;RULEID:;SRVR:DM5PR2101MB0901; x-forefront-prvs: 05739BA1B5 x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(7916004)(366004)(396003)(346002)(39380400002)(376002)(39860400002)(377424004)(189003)(199004)(22452003)(6116002)(1076002)(2906002)(106356001)(66066001)(5660300001)(8936002)(81166006)(2950100002)(6916009)(2900100001)(81156014)(4326008)(25786009)(68736007)(86362001)(9686003)(53936002)(575784001)(6346003)(72206003)(6512007)(478600001)(186003)(76176011)(59450400001)(3846002)(33896004)(10290500003)(6246003)(26005)(102836004)(86612001)(14454004)(39060400002)(6506007)(5250100002)(6436002)(99286004)(3280700002)(3660700001)(97736004)(229853002)(8676002)(7736002)(305945005)(105586002)(316002)(54906003)(6486002)(33716001)(10090500001)(21314002)(217873001);DIR:OUT;SFP:1102;SCL:1;SRVR:DM5PR2101MB0901;H:DM5PR2101MB1032.namprd21.prod.outlook.com;FPR:;SPF:None;PTR:InfoNoRecords;MX:1;A:1;LANG:en; received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts) authentication-results: spf=none (sender IP is ) smtp.mailfrom=Alexander.Levin@microsoft.com; x-microsoft-antispam-message-info: MhW8Da2EokN/LLgLvrLqAE0gcIYkRwW/xDQzqTgoHW/i7DmA9GuXT5mYOa144SDuT7dfoOIDu9r0Swaeg1s9xQ== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-Network-Message-Id: 5053a7d5-9fcd-4ca8-5fae-08d56b66826d X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Feb 2018 00:30:36.0724 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR2101MB0901 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Feb 03, 2018 at 09:35:26PM +0100, Pavel Machek wrote: >On Sat 2018-02-03 18:00:59, Sasha Levin wrote: >> From: Matthieu CASTET >> >> [ Upstream commit 2b83ff96f51d0b039c4561b9f95c824d7bddb85c ] >> >> With the current code, the following sequence won't work : >> echo timer > trigger >> >> echo 0 > delay_off >> * at this point we call >> ** led_delay_off_store >> ** led_blink_set >> *** stop timer >> ** led_blink_setup >> ** led_set_software_blink >> *** if !delay_on, led off >> *** if !delay_off, set led_set_brightness_nosleep <--- LED_BLINK_SW is s= et but timer is stop >> *** otherwise start timer/set LED_BLINK_SW flag >> >> echo xxx > brightness >> * led_set_brightness >> ** if LED_BLINK_SW >> *** if brightness=3D0, led off >> *** else apply brightness if next timer <--- timer is stop, and will nev= er apply new setting >> ** otherwise set led_set_brightness_nosleep >> >> To fix that, when we delete the timer, we should clear LED_BLINK_SW. > >Can you run the tests on the affected stable kernels? I have feeling >that the problem described might not be present there. Hm, I don't seem to have HW to test that out. Maybe someone else does? --=20 Thanks, Sasha=