Received: by 10.223.185.116 with SMTP id b49csp3911886wrg; Tue, 6 Mar 2018 07:02:17 -0800 (PST) X-Google-Smtp-Source: AG47ELvHEN2BdwN/d18JhRmNcQxZ6HoPGbYJdq2RoEut2R0rS6/fHzmPSCiIDkuHvmBdC/0AeNEP X-Received: by 10.101.81.204 with SMTP id i12mr15300994pgq.206.1520348537547; Tue, 06 Mar 2018 07:02:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520348537; cv=none; d=google.com; s=arc-20160816; b=jyMVBCTA5ctliNBYN48i45xTtL/jEzF/xiOPcSyzPlLoJo/yzP+7l0SUg9QHy3d1bx IVZUgistBYoWI3m76V/Z4TL3yn/Lh2Tqc75segGhgegwttlbghzzq9ao3t3loHw8IydA TbdIBBufU3eG2R2pSZu5qDc/U//Y2T+k/oU1AIlOpg+zuNvEdi6Kl50UxoJ7QmETPRx/ 1BM7JduX4nhxWH+WtIQdwbtYL7un4aaeWybBntM2zUaXpCgioHY9Y34nvSNjbQgPUC0N +WqjZWH6ddGmyXufjVPHlfp2G0x67lgWVahGNInf/swvYoTMyXK6vjZcG5IGT298FRG6 5F4g== 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:mime-version :organization:references:in-reply-to:date:cc:to:from:subject :message-id:arc-authentication-results; bh=azdZlB6MmlcVt9AW45Aya0V/GPXIhlpdJcu4lnnz/sM=; b=rCMDPcaUUtEK2sq4Ms3htp1nxoWsbNwvJ5wCySzLSs4+1pjDYI9R4riR1F5XFlOLrD ZO6MeLnkBh/dmbCPHQlgq+qpD/7+zy8SsjviwwULb1QMItVa23oHzR9gp04MksVo+1gi EO3n3Xxy0MMnrH5rdjI0Iw94BIRM3H4oivd+6rkp34T/E5hhyYas7BguZz/roFvMbFgw Y0J9Aaf7x+srBt/HQJeiTPMgZ/SpODY2S3renrzL29umvDh3oi7qgeOeSc39nX78097z OP8UJaqi80xJg9wmhkMywohylqWYkSKPXCUca/rTyaV4F1Z1no/LcVo5GagBCtfXLNL3 A+lw== 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 u5-v6si11225805plz.165.2018.03.06.07.02.00; Tue, 06 Mar 2018 07:02:17 -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; 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 S932963AbeCFO7d (ORCPT + 99 others); Tue, 6 Mar 2018 09:59:33 -0500 Received: from mga09.intel.com ([134.134.136.24]:21499 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932589AbeCFO7b (ORCPT ); Tue, 6 Mar 2018 09:59:31 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Mar 2018 06:59:31 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,431,1515484800"; d="scan'208";a="209287884" Received: from smile.fi.intel.com (HELO smile) ([10.237.72.86]) by fmsmga006.fm.intel.com with ESMTP; 06 Mar 2018 06:59:29 -0800 Message-ID: <1520348368.10722.440.camel@linux.intel.com> Subject: Re: [PATCH] pinctrl: intel: Implement intel_gpio_get_direction callback From: Andy Shevchenko To: Javier Arteaga , Mika Westerberg Cc: Heikki Krogerus , Linus Walleij , linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org Date: Tue, 06 Mar 2018 16:59:28 +0200 In-Reply-To: <1520348165.10722.438.camel@linux.intel.com> References: <20180306134213.16898-1-javier@emutex.com> <3585081b-70af-5c31-08c0-84e96b6055bc@emutex.com> <1520348165.10722.438.camel@linux.intel.com> Organization: Intel Finland Oy Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.5-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2018-03-06 at 16:56 +0200, Andy Shevchenko wrote: > On Tue, 2018-03-06 at 14:31 +0000, Javier Arteaga wrote: > > > +static int intel_gpio_get_direction(struct gpio_chip *chip, > > > unsigned int offset) > > > +{ > > > + if (padcfg0 & PADCFG0_PMODE_MASK) > > > + return -EINVAL; > > Actually we might return direction of GPIO function while pin is in > some > other mode, though it would probably make not much sense in practice. One more though, this is a call back for GPIO function anyway, so, above condition should never happen. I think it's safe to remove it completely. > > > + > > > + return !!(padcfg0 & PADCFG0_GPIOTXDIS); > > > +} -- Andy Shevchenko Intel Finland Oy