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 B89D4C77B7E for ; Thu, 1 Jun 2023 15:59:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233638AbjFAP72 (ORCPT ); Thu, 1 Jun 2023 11:59:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57364 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233663AbjFAP71 (ORCPT ); Thu, 1 Jun 2023 11:59:27 -0400 Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BC09E19B; Thu, 1 Jun 2023 08:59:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1685635162; x=1717171162; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=vQCl0k1HS2FOiiCRWugQq4VpCXw0LJEwXLGRbREcVuE=; b=CU/wMJ84xIuHwS031mA+OVLQy8wnlBUsCvxSQYVFkPldNHlM70Ub7WMF OyhZ5TAPajRSzmAKVpxuVfYqyvqI6TpZnisqvGbvazATnE2kvI5H+ZnnX r71Bt0laC2jeBtQFHsYUgA1Ufd9+He7aZMycOeZXgBjGeqUyesLKTNcFI VVJxX+GKj7mI+lBDdZp7DjNbfWoWUQeGLTHkt9W/FD/IJuo+xLoYCcYNO IQajxRyBkAqxS3XRvlnXCfOp/AI7FyI35fExRD1+88X6aySk52aGac52O X3fgQxud51UK3BCJRQDQ04r1sVurtYFNs8R2yeFa7sxO1yZ5JWyFVny7f A==; X-IronPort-AV: E=McAfee;i="6600,9927,10728"; a="358895107" X-IronPort-AV: E=Sophos;i="6.00,210,1681196400"; d="scan'208";a="358895107" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Jun 2023 08:59:22 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10728"; a="710549976" X-IronPort-AV: E=Sophos;i="6.00,210,1681196400"; d="scan'208";a="710549976" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga007.fm.intel.com with ESMTP; 01 Jun 2023 08:59:20 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1q4khq-000SGs-2E; Thu, 01 Jun 2023 18:59:18 +0300 Date: Thu, 1 Jun 2023 18:59:18 +0300 From: Andy Shevchenko To: Wolfram Sang , linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org Cc: Linus Walleij , Bartosz Golaszewski Subject: Re: [PATCH v8 1/1] gpio: add sloppy logic analyzer using polling Message-ID: References: <20220329091126.4730-1-wsa+renesas@sang-engineering.com> <20220329091126.4730-2-wsa+renesas@sang-engineering.com> 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 Thu, Jun 01, 2023 at 06:58:15PM +0300, Andy Shevchenko wrote: > On Wed, May 25, 2022 at 05:07:39PM +0200, Wolfram Sang wrote: > > On Wed, Mar 30, 2022 at 05:51:10PM +0300, Andy Shevchenko wrote: > > > On Tue, Mar 29, 2022 at 11:11:26AM +0200, Wolfram Sang wrote: > > > > This is a sloppy logic analyzer using GPIOs. It comes with a script to > > > > isolate a CPU for polling. While this is definitely not a production > > > > level analyzer, it can be a helpful first view when remote debugging. > > > > Read the documentation for details. > > > > > > Good enough I think, > > > Reviewed-by: Andy Shevchenko > > > > Thanks, Andy! > > > > To GPIO maintainers: can we apply the "new-driver-rule" and still have > > it in 5.19? There can't be any regression and it has all comments > > addressed. Also, I am talking about this project at Kernel Recipes late > > next week and it would be great to say that it is finally merged :) > > Year passed. Any news here? Ah, GPIO maintainers probably missed this since no Cc. -- With Best Regards, Andy Shevchenko