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 7F425C7EE2F for ; Mon, 12 Jun 2023 17:36:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236993AbjFLRgp (ORCPT ); Mon, 12 Jun 2023 13:36:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44058 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236860AbjFLRgW (ORCPT ); Mon, 12 Jun 2023 13:36:22 -0400 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C69A51BC5; Mon, 12 Jun 2023 10:35:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1686591319; x=1718127319; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=WukTNRen46NQ+J1/agJdZz6fX5veY5abkQR/wVmN5ec=; b=PZ8E0pbqivhM1J/K+H5Q613i5seEZ2hQJamG+Rapoz2mssybPr+7QW+z KhXYlbJCbqD7mRRmn/acaeyiRvmph+s4sMON7+5LLfPqyMsySxQzF7eVH bA9jGSWFJuo7grJB9SY+u/0bcC/L/uLUSQ1pHXUZC8oANBfq/kDu8o/dL /jHJvYibar+PHofD+i2cNF9q6afn5n3j7BcBORYVU8O41+3lMKaBBo63f 3cJtZeX9YfvV0RuSEEH1HibBL/KkXrfPcDdisN/01hazkTK6h/dV/3IyT u4XJDACYGovr3nyS2MZWVvk0HTClxfCmST9k3utkBE4HgU12o7jSgk3ra g==; X-IronPort-AV: E=McAfee;i="6600,9927,10739"; a="338476749" X-IronPort-AV: E=Sophos;i="6.00,236,1681196400"; d="scan'208";a="338476749" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Jun 2023 10:34:44 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10739"; a="744400263" X-IronPort-AV: E=Sophos;i="6.00,236,1681196400"; d="scan'208";a="744400263" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga001.jf.intel.com with ESMTP; 12 Jun 2023 10:34:41 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1q8lR9-003GYj-2h; Mon, 12 Jun 2023 20:34:39 +0300 Date: Mon, 12 Jun 2023 20:34:39 +0300 From: Andy Shevchenko To: Linus Walleij Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org, Geert Uytterhoeven , Bartosz Golaszewski , Alexander Stein Subject: Re: [rfc, rft, PATCH v1 1/1] gpio: aggregator: Introduce delay support for individual output pins Message-ID: References: <20230608162130.55015-1-andriy.shevchenko@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit 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 Fri, Jun 09, 2023 at 09:50:37AM +0200, Linus Walleij wrote: > On Thu, Jun 8, 2023 at 6:22 PM Andy Shevchenko > wrote: > > > The aggregator mode can also handle properties of the platform, that > > do not belong to the GPIO controller itself. One of such a property > > is signal delay line. Intdoduce support of it. > (...) > > I don't like the idea of gpio-delay or similar. We have already GPIO > > aggregator that incorporates the GPIO proxy / forwarder functionality. > > You are right. This is the right solution going forward IMO. Thank you for the support. Take into consideration 1 kinda neutral and 2 for votes, I'll going to split and improve the patch (series). -- With Best Regards, Andy Shevchenko