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 DBD1FC433FE for ; Wed, 16 Nov 2022 13:38:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238497AbiKPNiu (ORCPT ); Wed, 16 Nov 2022 08:38:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52674 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238294AbiKPNik (ORCPT ); Wed, 16 Nov 2022 08:38:40 -0500 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 64DAAF038 for ; Wed, 16 Nov 2022 05:38:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1668605919; x=1700141919; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=xJDAFKBccGBEfHFK8kKpsPqsX9HjlC02ZGEv1dPTP4c=; b=fYzgRK/G33r+hgbdoEd1hIaW9aF/LsN6o6liKu/mThWytD/PqicCXu3b luFH4Ru0CqNYtCssndPXoj7oBbH/S8gW+FTom7ZxqGWcTrhrfjrLzCz1S QwlLz6rWlHgUtfJ/uyO7llwXZYtZXC+csjbLVUJXME5poj45icLX4bqVS cdL5aaAPmfMQ+tNJyczBNvqsl3vqwIdpzZtcVImXDsBUDKJYBMdbUJtk7 FgV//Bf+QlkQLiMVcxY5wtYh5ybykuox9D9PCqCsU1peD5uusckyQAlsn wwwyM24ZK9FSb8Zt2edBUnXCVBVyx+UnnMKQcbagKbA7qPQqcUfQN6QP5 g==; X-IronPort-AV: E=McAfee;i="6500,9779,10532"; a="292933471" X-IronPort-AV: E=Sophos;i="5.96,167,1665471600"; d="scan'208";a="292933471" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Nov 2022 05:38:39 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10532"; a="670502918" X-IronPort-AV: E=Sophos;i="5.96,167,1665471600"; d="scan'208";a="670502918" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga008.jf.intel.com with ESMTP; 16 Nov 2022 05:38:37 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1ovIcd-00D93w-2H; Wed, 16 Nov 2022 15:38:35 +0200 Date: Wed, 16 Nov 2022 15:38:35 +0200 From: Andy Shevchenko To: Niyas Sait Cc: linux-gpio@vger.kernel.org, mika.westerberg@linux.intel.com, rafael@kernel.org, linus.walleij@linaro.org Subject: Re: [PATCH RFC v2 0/3] pinctrl: add ACPI support to pin controller Message-ID: References: <20221115175415.650690-1-niyas.sait@linaro.org> <3766343a-ce40-10aa-99dc-2ea94bc1ffbd@linaro.org> <05f3c105-12f8-1fd5-0e6c-1ab7e24a01df@linaro.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-gpio@vger.kernel.org On Wed, Nov 16, 2022 at 03:27:30PM +0200, Andy Shevchenko wrote: > On Wed, Nov 16, 2022 at 10:40:19AM +0000, Niyas Sait wrote: > > On 16/11/2022 09:56, Andy Shevchenko wrote: > > > The GPIO to pin mapping is done by GPIO ranges. This can be made up in the > > > driver or, IIRC, in DT (so in ACPI) by already registered properties). > > > > > > Not sure, why you don't use them. > > > > OK. I might have missed it. > > > > In DT, gpio-ranges property is used to describe the mapping, I could not > > find equivalent property in GPIO ACPI properties - > > https://www.kernel.org/doc/html/latest/firmware-guide/acpi/gpio-properties.html > > It's the same. You just need to check the code of GPIO library to make sure > that it uses fwnode / device property APIs, so it will be parsed in ACPI case > as well. Ah, and it's always welcome to have Documentation updates to make it up-to-date. -- With Best Regards, Andy Shevchenko