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 59210C77B6F for ; Fri, 7 Apr 2023 19:00:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229957AbjDGTAM (ORCPT ); Fri, 7 Apr 2023 15:00:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53772 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229848AbjDGS7l (ORCPT ); Fri, 7 Apr 2023 14:59:41 -0400 Received: from fgw23-7.mail.saunalahti.fi (fgw23-7.mail.saunalahti.fi [62.142.5.84]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F3465C650 for ; Fri, 7 Apr 2023 11:58:10 -0700 (PDT) Received: from localhost (88-113-24-128.elisa-laajakaista.fi [88.113.24.128]) by fgw23.mail.saunalahti.fi (Halon) with ESMTP id 0d580af0-d576-11ed-b972-005056bdfda7; Fri, 07 Apr 2023 21:57:33 +0300 (EEST) From: andy.shevchenko@gmail.com Date: Fri, 7 Apr 2023 21:57:32 +0300 To: Alexander Stein Cc: Linus Walleij , Bartosz Golaszewski , Rob Herring , Krzysztof Kozlowski , linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, Marek Vasut , Laurent Pinchart Subject: Re: [PATCH v1 0/3] gpio: Add gpio-delay support Message-ID: References: <20230406093344.917259-1-alexander.stein@ew.tq-group.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230406093344.917259-1-alexander.stein@ew.tq-group.com> Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Thu, Apr 06, 2023 at 11:33:41AM +0200, Alexander Stein kirjoitti: > Hello everyone, > > thanks for the feedback I've received. This is the first non-RFC series for > adressing a platform specific ramp-up/ramp-down delay on GPIO outputs. > > Changes compared to RFC v2 are mentioned in each patch. Reading the (poor?) documentation does not clarify the use case. Looking at them I think that this is can be implemented as debounce. Also I have no clue why it's so important that we _need_ to have a driver for this. We have plenty of consumer drivers that implement delays on ramping up or down or whatever if they need. Which part(s) did I got wrong? P.S. Are we going to have a _driver_ per each subtle feature like this? -- With Best Regards, Andy Shevchenko