From mboxrd@z Thu Jan 1 00:00:00 1970 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 9865FCCA479 for ; Mon, 18 Jul 2022 18:25:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235970AbiGRSZx (ORCPT ); Mon, 18 Jul 2022 14:25:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33734 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235969AbiGRSZw (ORCPT ); Mon, 18 Jul 2022 14:25:52 -0400 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 90DD22D1D7; Mon, 18 Jul 2022 11:25:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1658168751; x=1689704751; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=ZrDvrrA11F1AztQy2Nks0U7/bE0KiSaoQtsQja6PhiM=; b=dVYdTtmEVHq75hzPDuYagPMXRPyx6LNdkSvhmHdM6VtxpT8eJ+K7oTvv MjoPyNnkpa80riLxUS69F5kKyAtMi3dOwPYSnsjU+ccrOFx00ccxYeOdg 1tXKdEf9SW244GnrUz9cv2xo0XRQGuA5Xwz+Hsg3Z7NfyfAsZW9/V+q9s fPn4som5uh/Yr3hJ4GXOixnx5uU0lSDBa1ZyJvdq5ASD57LrIx/YQWIZy En8zK2UgpjsfbM8CirzWWBuQtmYuetMXZvDrV7Wlu9IJDrqbIV1OcdZ02 muBNFZo2MLrn5QlFl92/3W93T82iGRclG0c0XkOuYFB7G5EzN7jgzCqe3 w==; X-IronPort-AV: E=McAfee;i="6400,9594,10412"; a="311976686" X-IronPort-AV: E=Sophos;i="5.92,281,1650956400"; d="scan'208";a="311976686" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Jul 2022 11:25:43 -0700 X-IronPort-AV: E=Sophos;i="5.92,281,1650956400"; d="scan'208";a="547601715" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Jul 2022 11:25:40 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1oDVR3-001OO1-1n; Mon, 18 Jul 2022 21:25:37 +0300 Date: Mon, 18 Jul 2022 21:25:37 +0300 From: Andy Shevchenko To: Nuno =?iso-8859-1?Q?S=E1?= Cc: linux-acpi@vger.kernel.org, devicetree@vger.kernel.org, linux-gpio@vger.kernel.org, Krzysztof Kozlowski , Bartosz Golaszewski , Frank Rowand , Mika Westerberg , Rob Herring , Linus Walleij Subject: Re: [PATCH 3/4] gpiolib: acpi: support bias pull disable Message-ID: References: <20220713131421.1527179-1-nuno.sa@analog.com> <20220713131421.1527179-4-nuno.sa@analog.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220713131421.1527179-4-nuno.sa@analog.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org On Wed, Jul 13, 2022 at 03:14:20PM +0200, Nuno Sá wrote: > On top of looking at PULL_UP and PULL_DOWN flags, also look at > PULL_DISABLE and set the appropriate GPIO flag. The GPIO core will then > pass down this to controllers that support it. In case this patch will be in v2, Acked-by: Andy Shevchenko P.S. I will be on vacation till mid-August. -- With Best Regards, Andy Shevchenko