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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 8EB80C004C0 for ; Thu, 19 Oct 2023 21:28:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:Date:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=VoK6AKqlEGP9h0CDa5ZA5HEMSzOxm2YRSlj9x+o6TzU=; b=LdGfMhPucif8XP 41fUsZQsQmcGmowNbvPo2mD6GBKBhJyG0K69sZoHKwDCNcAJpxptOJsL0zz63nhWQEvrIZFur1SAo mSCP4Eq8n0yRhP1UKARqjJwyFbGFPTVfe8u9oTP1kBokS7FH0TYPHdVjTLiJRWwp/XBbt8AxrIB7T cAeh0Qzwmzaz+fURdCV2yqlPmolwdJxYUixsjQu8dUd38Mtr9s/HrDRIDU+5z0GCCtWt8uL+6r48A kwlWHfgQs3OGPwVnrXKwbLBI6ZDjYSpkyH3IOD4ZmLPZB/eaVMVRkO07iJhDQMoD0Wvw575gSyyiB GRB8JigYSQjg1weOjkmA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qtaYp-000kJR-2a; Thu, 19 Oct 2023 21:28:07 +0000 Received: from fgw22-7.mail.saunalahti.fi ([62.142.5.83]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qtaYm-000kIm-2T for linux-arm-kernel@lists.infradead.org; Thu, 19 Oct 2023 21:28:06 +0000 Received: from localhost (88-113-24-34.elisa-laajakaista.fi [88.113.24.34]) by fgw22.mail.saunalahti.fi (Halon) with ESMTP id 5fac9ca2-6ec6-11ee-a9de-005056bdf889; Fri, 20 Oct 2023 00:27:58 +0300 (EEST) From: andy.shevchenko@gmail.com Date: Fri, 20 Oct 2023 00:27:58 +0300 To: AKASHI Takahiro Cc: sudeep.holla@arm.com, cristian.marussi@arm.com, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, linus.walleij@linaro.org, Oleksii_Moisieiev@epam.com, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org Subject: Re: [RFC v2 0/5] gpio: add pinctrl based generic gpio driver Message-ID: References: <20231005025843.508689-1-takahiro.akashi@linaro.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20231005025843.508689-1-takahiro.akashi@linaro.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231019_142804_985283_55519022 X-CRM114-Status: GOOD ( 22.91 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Thu, Oct 05, 2023 at 11:58:38AM +0900, AKASHI Takahiro kirjoitti: > This is a revised version of my previous RFC[1]. Although I modified > the commits to make them look SCMI-independent, they are still posted > as RFC because I have never tested them on real hardware. > > (background) > I'm currently working on implementing SCMI pinctrl/gpio drivers > on U-Boot[2]. Although the pinctrl driver for the kernel[3] was submitted > by EPAM, it doesn't contain the gpio driver and I believe that we should > discuss a couple of points on the kernel side to finalize my design for > U-Boot. > > So this RFC is intended for reviews, especially to raise some issues. > > 1) how to obtain a value on an input pin > All the existing gpio drivers are set to obtain a value on an input > pin by accessing the hardware directly. In SCMI case, however, this is > just impossible in its nature and must be supported via a protocol > using "Input-value" configuration type. (See the spec[4], table-23.) > > The current pinconf framework is missing the feature (the pinconf > parameter and a helper function). See patch#1, #2 and #3. > > Please note that there is an issue around the pin configuration in > EPAM's current pinctrl driver as I commented[5]. > > 2) DT bindings > I would like to propose a generic binding for pinctrl based gpio driver. > This allows a "consumer" driver to handle gpio pins like as other > normal gpio controllers support. (patch#5) > > 3) generic GPIO driver > Based on (2), I tried to prototype a generic driver in patch#4. > Thanks to a set of existing pinctrl_gpio helper functions, except (1), > It seems that the driver can be implemented not relying on pin controller > specific code, at least for SCMI pinctrl. > > I will appreciate any comments. Any comment here: I'm listed as a designated reviewer of GPIO patches, why am I not Cc'ed on this? I definitely have some comments against the code (no DT, though). Please, use (up-to-date) MAINTAINERS in your v3. -- With Best Regards, Andy Shevchenko _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel