Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id BE4DCC05027 for ; Wed, 1 Feb 2023 18:32:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230011AbjBAScY (ORCPT ); Wed, 1 Feb 2023 13:32:24 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36868 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231607AbjBAScV (ORCPT ); Wed, 1 Feb 2023 13:32:21 -0500 Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2F44E2D154; Wed, 1 Feb 2023 10:32:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1675276335; x=1706812335; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=Lc3QJ57ZITulULY9CL129xfA2Shk7EL+Hu31oUiLs6o=; b=KEgzXxW+rLTMblTW9iitpm5iWv+xwsKd9jSjCW68M1bjL/5X4a0RXOh/ +QPJrVGJZNmBMpTW3z3+cmNpYQtbSHS3wlZB//reqLFDBpEoNVddpbeNH IYNuSAiE9jOOWvU24866ZRQ+QNAcBdv1mfK9ePRh7X99ycM4ZgwG8IzNo bEpH6Ab8C7ZvBaJS7X3BKN7/oLRbwhbX9vncJZXzglpxlCNSBFCBDHpI6 y0xSsNpVZdayJsy/1IICw/iVEMQ+/Qxh24Lkiv2p1yitGgLUfDbBPkFre wdAYJWhosYeze7Pnr/Q9yq9clE2/77UuuTNT6q5xLECePYlkI2EvGnl9V w==; X-IronPort-AV: E=McAfee;i="6500,9779,10608"; a="307892311" X-IronPort-AV: E=Sophos;i="5.97,265,1669104000"; d="scan'208";a="307892311" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Feb 2023 10:32:13 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10608"; a="658421522" X-IronPort-AV: E=Sophos;i="5.97,265,1669104000"; d="scan'208";a="658421522" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga007.jf.intel.com with ESMTP; 01 Feb 2023 10:32:08 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1pNHtu-000pXF-1L; Wed, 01 Feb 2023 20:32:06 +0200 Date: Wed, 1 Feb 2023 20:32:06 +0200 From: Andy Shevchenko To: Dmitry Torokhov Cc: Arnd Bergmann , linux-gpio@vger.kernel.org, Arnd Bergmann , Bartosz Golaszewski , Christophe Leroy , Linus Walleij , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 4/7] gpiolib: remove gpio_set_debounce Message-ID: References: <20230127101149.3475929-1-arnd@kernel.org> <20230127101149.3475929-5-arnd@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 31, 2023 at 09:44:31PM -0800, Dmitry Torokhov wrote: > On Fri, Jan 27, 2023 at 11:11:46AM +0100, Arnd Bergmann wrote: ... > > - return !gpio_get_value(ts->gpio_pendown); > > + return !gpiod_get_value(ts->gpio_pendown); > > No, we can not blindly do that without checking annotations on GPIOs. But this is easy to fix, i.e. use raw API, no? > > + ts->gpio_pendown = gpiod_get(&spi->dev, "pendown-gpio", GPIOD_IN); > > Wrong name, you will be looking for "pendown-gpio-gpios". > > Sorry, but I have to NAK this in the current form. Oh, indeed. On top of that the conversion missing the label to be set. -- With Best Regards, Andy Shevchenko