Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp2917739ybl; Mon, 19 Aug 2019 09:18:14 -0700 (PDT) X-Google-Smtp-Source: APXvYqwLYvX3FnJpL0ifWLIljXrLoB5ionqtZSIbRJ1HFST+Kj/XowNy5kh9w+b9fk2l5PcdRBFZ X-Received: by 2002:a17:902:7441:: with SMTP id e1mr23218871plt.37.1566231494214; Mon, 19 Aug 2019 09:18:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566231494; cv=none; d=google.com; s=arc-20160816; b=ihXDaSvT0110j4YCdEyy/z0CwqpR1kHyn7U/2aMZsYovj+5RJ0tcwVh7Q4bMfBH7E9 NpDTtP8G1cReUv18WA7eNQPJNgHHAHVqwV+j9sXHWBz6wm6aUh9WoHcwDutzc61MAXlQ o1c1rkBEsy7CiMumnfqvCvN0LNKHd4d4Wpt2nBF44VmivlVxtDXA1EQEenASK4dxGBo8 41o+92mLCyniPmQ+QoTg9RtxlC6MthLii8GqSWd/yRqyfhfFcTC/AoNsyTqQIPhTHjbr RqlMvtEs1Xuh/BzVstMtI2oIGzS3fpzH7sANx4k8PFKIASyEsNitg3uIIQIR5r+VjDHX Z5Vw== 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:reply-to; bh=nCCrj6RvVz1BVsp2AxHA5np6rFqq04zMJ69ByBhoj80=; b=PGBWw9KKO66nXj3HFj6vRXYnvW/vJ+OmFxkPYu48qZKbfIuctwL5fVZjb5Hv7FVL2Y fze+ykPJvYCbDlQ+eo2aNaTmdsaC8JlcAO9x01pAFCH2W+rigj75Tm9ASlbAL+oPMIr8 BgyefKjoExn8feE4PSsL2fBBFUCwRReqXU1LlVEc+293j435fKJuKNSX3/KmGdH+SSXy 087i1CifkeKUKzsSnOOX3VfX1Ts0xcLHRS7sNLhuUm4x4k4Mj8zwcAf3ljHdHNZlwH7Q IKX4P3agJ64qiXBPO4h39hFrLxz9Cnpu2vi+EIKhaCYcyUT2V+n0f2L5oJJWB1JYDR2n VuWQ== 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 v6si10182364plg.111.2019.08.19.09.17.58; Mon, 19 Aug 2019 09:18:14 -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 S1727353AbfHSQQ5 (ORCPT + 99 others); Mon, 19 Aug 2019 12:16:57 -0400 Received: from mail-ed1-f66.google.com ([209.85.208.66]:41143 "EHLO mail-ed1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726168AbfHSQQ5 (ORCPT ); Mon, 19 Aug 2019 12:16:57 -0400 Received: by mail-ed1-f66.google.com with SMTP id w5so2195770edl.8; Mon, 19 Aug 2019 09:16:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:reply-to:subject:to:cc:references:from :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=nCCrj6RvVz1BVsp2AxHA5np6rFqq04zMJ69ByBhoj80=; b=MnY1xkLLt/6admbaiYa8aFLh6XUEsmjicep+cOnIPyvydqNWkKO6FVVOXkqPM/wMne 9But3Kg0FlKPenLZRUK27jOztNf4lJVQm+vB/g1G4L/ayfGpaB4JO7b+YIoFnIF3cCT6 cvGnGKtttNwQRUPa36gb8AON1Z7rCHVVV/cto5OunrtMbVvyMjj6PeoQPbtCPt6cADvG EcaxJuljxgFKcLBlqSCrrT37rY1q53x5THhRh2gCe28qUeXKpvTjOppzsbeLtD+1g8pt x0vKS5YNA6nUsJojfyn+EsiYg42SXoX16tEYVxcdAuvOev8JLTTh7fra3elEfWfJkLlr wxRw== X-Gm-Message-State: APjAAAV4JoWSbSGCFIZEtJk66MxRi/AVnwJ1zKk64Sbhr02IIFp6OoMI kAhbaiEXs22vJA+ANHKvAuyTipBC X-Received: by 2002:a17:907:2101:: with SMTP id qn1mr22259516ejb.3.1566231415418; Mon, 19 Aug 2019 09:16:55 -0700 (PDT) Received: from [10.10.2.174] (bran.ispras.ru. [83.149.199.196]) by smtp.gmail.com with ESMTPSA id t12sm2891678edw.40.2019.08.19.09.16.54 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 19 Aug 2019 09:16:54 -0700 (PDT) Reply-To: efremov@linux.com Subject: Re: [PATCH v3 1/4] PCI: pciehp: Add pciehp_set_indicators() to jointly set LED indicators To: sathyanarayanan kuppuswamy Cc: Bjorn Helgaas , Lukas Wunner , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org References: <20190819160643.27998-1-efremov@linux.com> <20190819160643.27998-2-efremov@linux.com> From: Denis Efremov Message-ID: <9cbb34b0-d6be-fbba-9992-9b6939018e5d@linux.com> Date: Mon, 19 Aug 2019 19:16:53 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <20190819160643.27998-2-efremov@linux.com> Content-Type: text/plain; charset=utf-8 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, On 8/19/19 7:06 PM, Denis Efremov wrote: > + switch (pwr) { > + case PCI_EXP_SLTCTL_PWR_IND_ON: > + case PCI_EXP_SLTCTL_PWR_IND_BLINK: > + case PCI_EXP_SLTCTL_PWR_IND_OFF: > + cmd |= pwr; > + mask |= PCI_EXP_SLTCTL_PIC; > + } > + On 8/12/19 11:25 AM, sathyanarayanan kuppuswamy wrote: > Do we need to switch case here ? if (pwr > 0) {} should work right ? I saved the switch here from v2. I think switch makes the inputs check more precise and filters-out all non-valid values. Maybe this check is too strict? We could use mask here ON|OFF|BLINK for the check, but I don't know how hardware will handle a case, for example, pwr == ON|BLINK. Thanks, Denis