From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756074AbcDLG4m (ORCPT ); Tue, 12 Apr 2016 02:56:42 -0400 Received: from szxga03-in.huawei.com ([119.145.14.66]:48202 "EHLO szxga03-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755914AbcDLG4i (ORCPT ); Tue, 12 Apr 2016 02:56:38 -0400 Reply-To: Subject: Re: [PATCH v7 3/3] gpio: dwapb: add gpio-signaled acpi event support References: <1459926480-32966-1-git-send-email-qiujiang@huawei.com> <1459926480-32966-4-git-send-email-qiujiang@huawei.com> <20160408083830.GT1727@lahna.fi.intel.com> <570B9BEA.8060608@huawei.com> <20160412064657.GF1714@lahna.fi.intel.com> To: Mika Westerberg CC: Linus Walleij , Alexandre Courbot , Andy Shevchenko , Alan Tull , Jamie Iles , , "linux-kernel@vger.kernel.org" , "linux-gpio@vger.kernel.org" , ACPI Devel Maling List , Linuxarm From: Jiang Qiu Message-ID: <570C9BF8.7070400@huawei.com> Date: Tue, 12 Apr 2016 14:55:52 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <20160412064657.GF1714@lahna.fi.intel.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.74.160.152] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0204.570C9C07.00AB,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2013-05-26 15:14:31, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: daa1da567891fdd0a9d93d74ae9d639d Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 在 2016/4/12 14:46, Mika Westerberg 写道: > On Mon, Apr 11, 2016 at 08:43:22PM +0800, Jiang Qiu wrote: >>> Currently it just complains if something goes wrong. The GPIO driver >>> itself can still work just fine (including interrupts). >>> >>> I'm fine to change it to return an error code. >> Agree, if add a error code for acpi_gpiochip_request_interrupts(), it looks more pretty. >> >> However, this function is common for other part, maybe cause any other effects if I >> do this change, did you think so? > I'm thinking what the callers are going to do with the error code. > Basically it means that we were not able to attach and configure ACPI > event GPIOs. It does not prevent GPIO drivers from functioning so they > probably just print out some warning message and continue probing, and > we already warn in acpi_gpiochip_request_interrupts() if something fails. > > Unless Linus W insists, let's just keep it as is for now :) Fine to me, thanks:). > . >