Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp2328188pxu; Mon, 7 Dec 2020 03:55:53 -0800 (PST) X-Google-Smtp-Source: ABdhPJwqQ5eav+8v/0/9pPiWwXrXZkXHByEbhpeKsT4P6bA5NxEUuikT9QZju6zRSJ+mRYUrdEpc X-Received: by 2002:a17:906:3187:: with SMTP id 7mr18667917ejy.225.1607342152909; Mon, 07 Dec 2020 03:55:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1607342152; cv=none; d=google.com; s=arc-20160816; b=QHhaQZ12CY26gvktDe4h7IreDlsnhIJch8bObxBk1Dybgaeshk5SJMCnJDX2ygpw8d ksC2GuW4Z1o1TyRILgaX4L2TsnIePyulg4QC8o2WJc3F5KgS6KBOkDUaQu2WEy37Lryn 7mhtxwZgYXRRkIqRx3cpK+ej4yPOx+0Znxqj3M/L94qGFSoDF5LOQyVxtWVP9npEdQwy UqV+itvcjlUNX6BlC90sRG5urf+UytNdmt4jnKoAlXohhg4CF8LrUQUubzlJuFmV3vWX eoiiRILyyEu2jh0D463jcmK/FFW90C3wsLPVQXXIFDNVEme2mEA/zlSp7guC0s5R/oCL btAw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=Cq2jFqDwIfrHoFOscYqfVgmZg47FDTLhoPP6+XAE2X8=; b=mmMvDunxV5CmLyCxrnhVNRETye9DIaTi9mjYlAIulpJ4nNtBbwABf1VtfFUC5C9kzc x2TDCWc9S63w52FV0kdFiZzjvzJBKY1Ci5X4+Hxzx3wR1fZ+1L3rbqsmbP4cspRQFQiQ sNr9Wgt7pXHYpCwGCXSZvb/u6A/ZalHuquLm1KFzUjHLCboEnUH/hYe0Bo3L/2UxA/HL /FeYxwJfrBgGQ1PF+yCnCGcODNZtFYIsBBitydmLiEMh/6CA+IsJpWrHeeFrunEeuXlL g7/mqdgbJS6eIJSa+ljLU20ojFq+jWbiYcpi0uAWwSiaWHL68LNaz7snSv4y+hJo7huQ 5zlw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a15si5130908ejd.293.2020.12.07.03.55.28; Mon, 07 Dec 2020 03:55:52 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726906AbgLGLwi (ORCPT + 99 others); Mon, 7 Dec 2020 06:52:38 -0500 Received: from mail-wm1-f67.google.com ([209.85.128.67]:54117 "EHLO mail-wm1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726617AbgLGLwi (ORCPT ); Mon, 7 Dec 2020 06:52:38 -0500 Received: by mail-wm1-f67.google.com with SMTP id k10so11222343wmi.3; Mon, 07 Dec 2020 03:52:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=Cq2jFqDwIfrHoFOscYqfVgmZg47FDTLhoPP6+XAE2X8=; b=cLnEBmmTvVorb3orFqYas6JyWceC4RR7/ZlQ839ETQcCGPCYl6a3aJ4tePmJHzNbj+ uH5PKrfaqKTVwsVqejBAbnrl9iLPzAIxpFdec/vR1cHuugitT1yp3q63RiAik72ojjbG GZW2AZTm+7dgCPEeEB0htb7Nidz1yRBjw9wrk9HGgvj/+5KuxJLlYc+e7BILTpG9Qval ecE1iFgtgQa0oSEm0+Hxw9fx3P4P71j3RVy3vohd/u8todu6fPmAL+HLPbBfxtqteNSq BMTwBnH1gJpQrjG8tu3Z4I1qRubQ0cKPKcnqJpKShryJXQy3UR0/1wtGzhEQj/uQ9j72 TY3g== X-Gm-Message-State: AOAM532JhRUhBOyPVaHDQe/kp4LelQxBIqBF/ajEYN8JmPybh44WqO8d kBR5bUz3+CLnLyOVBXTVDgs= X-Received: by 2002:a1c:3c09:: with SMTP id j9mr18047135wma.180.1607341910456; Mon, 07 Dec 2020 03:51:50 -0800 (PST) Received: from kozik-lap (adsl-84-226-167-205.adslplus.ch. [84.226.167.205]) by smtp.googlemail.com with ESMTPSA id y2sm14522546wrn.31.2020.12.07.03.51.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 07 Dec 2020 03:51:49 -0800 (PST) Date: Mon, 7 Dec 2020 12:51:47 +0100 From: Krzysztof Kozlowski To: Bongsu Jeon Cc: linux-nfc@lists.01.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Bongsu Jeon Subject: Re: [PATCH net-next] nfc: s3fwrn5: Change irqflags Message-ID: <20201207115147.GA26206@kozik-lap> References: <20201207113827.2902-1-bongsu.jeon@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20201207113827.2902-1-bongsu.jeon@samsung.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 07, 2020 at 08:38:27PM +0900, Bongsu Jeon wrote: > From: Bongsu Jeon > > change irqflags from IRQF_TRIGGER_HIGH to IRQF_TRIGGER_RISING for stable > Samsung's nfc interrupt handling. 1. Describe in commit title/subject the change. Just a word "change irqflags" is not enough. 2. Describe in commit message what you are trying to fix. Before was not stable? The "for stable interrupt handling" is a little bit vauge. 3. This is contradictory to the bindings and current DTS. I think the driver should not force the specific trigger type because I could imagine some configuration that the actual interrupt to the CPU is routed differently. Instead, how about removing the trigger flags here and fixing the DTS and bindings example? Best regards, Krzysztof > > Signed-off-by: Bongsu Jeon > --- > drivers/nfc/s3fwrn5/i2c.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/nfc/s3fwrn5/i2c.c b/drivers/nfc/s3fwrn5/i2c.c > index e1bdde105f24..016f6b6df849 100644 > --- a/drivers/nfc/s3fwrn5/i2c.c > +++ b/drivers/nfc/s3fwrn5/i2c.c > @@ -213,7 +213,7 @@ static int s3fwrn5_i2c_probe(struct i2c_client *client, > return ret; > > ret = devm_request_threaded_irq(&client->dev, phy->i2c_dev->irq, NULL, > - s3fwrn5_i2c_irq_thread_fn, IRQF_TRIGGER_HIGH | IRQF_ONESHOT, > + s3fwrn5_i2c_irq_thread_fn, IRQF_TRIGGER_RISING | IRQF_ONESHOT, > S3FWRN5_I2C_DRIVER_NAME, phy); > if (ret) > s3fwrn5_remove(phy->common.ndev); > -- > 2.17.1 >