Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp5683624rwb; Mon, 5 Dec 2022 02:38:04 -0800 (PST) X-Google-Smtp-Source: AA0mqf7pRKnbi3XHV2bG0TwgJGUrt8j/E5penDTmcJhi/+aGCy9vr/dXz3XF3e9/9lsFivoq05+p X-Received: by 2002:a17:90a:fcf:b0:219:861b:b108 with SMTP id 73-20020a17090a0fcf00b00219861bb108mr17451648pjz.121.1670236683988; Mon, 05 Dec 2022 02:38:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670236683; cv=none; d=google.com; s=arc-20160816; b=rvQOUd2mUIotArIkE/GPafO6baKPTEjUjnE16InSA9gVXjilhUDzSCrjGWC2708wnt pFEw6rb/BLom4gUgDlTvtfEGlOvq+fXRkKf6fdwFcyLu/E2YrL3w4Glta73W4Y7RuZ56 VZGfd8amHPWMKDPnQbDRYcGb1bwMkckO3joRjUjDvws2jCVAGgkN1e7yhAwb8NXioCAr DQ36nl3MiVwkOg9mHiUt9zvYsYwcFg/yEwJ6u8slRb6Wa8XjGmkXaRjoRu9h7xt3FYUW LUQvwEG7cxXZBB9xIwwWVMNh8OAFI2+nxFBIk7hx1up/96O/RGGcZUR/WqDONsgPaLgq g33A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=+mqkHAvBv1y5qS2y58nAD/iFpsVKp/726AYMa4PGL3o=; b=ijtkj5r9wzocuxnStA7eOJ2R67ntiEHKMQUhtxMLr4/Gf1MJRqQqa1FuYNAw1viKmH b6HpiYZzMuJ47sVANsfWiljBUGB8NtwDyLA1h0GZy5LbDORBgxI5AsOBokU7iuuIsxLm YWtFr6Wr0ryChiM6nbT8a825IT4CVRHHSRAlTNlYPiTdz9bCyDz/aUhCkj72/z6nUKiX dg5ezUtpCa1D9B5Ts0aRoygPiehatezfn/i6DTYiYpDrZjwK4YGPlXiXESds6u8UMin5 XyMXPYhCUO5Jy2bo/QaGX7PPM4I2uewdRkFK0US3KrfcvGHzjnckaZ7eGAiQJPG+AaSz 22Sw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=wjJlMPQF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x4-20020a63db44000000b00476e764bb0esi14771819pgi.392.2022.12.05.02.37.53; Mon, 05 Dec 2022 02:38:03 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=wjJlMPQF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229785AbiLEJKy (ORCPT + 82 others); Mon, 5 Dec 2022 04:10:54 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56668 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229949AbiLEJKS (ORCPT ); Mon, 5 Dec 2022 04:10:18 -0500 Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C1B4BDE8C for ; Mon, 5 Dec 2022 01:09:35 -0800 (PST) Received: by mail-ed1-x52f.google.com with SMTP id s5so14768503edc.12 for ; Mon, 05 Dec 2022 01:09:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=+mqkHAvBv1y5qS2y58nAD/iFpsVKp/726AYMa4PGL3o=; b=wjJlMPQFvu5r3taMHZ7MUIsm8Y8OlsIkDMO05PgJsPs10HD6/mSS6m0uS1B3uXHyuJ Zx8f3AQsRj27lhL7oAgx0ggwJvcJx5JItoPWXovLhk9mlAhoXzJNy3iokvxTjChNDLNa wk2TyEe/S2g+Ww12WtM9km3V/aJo1QEghKMBZkghK7EY/VOpVhfVqq3Netjy9wlLKKs8 5a+QXKJmClAT1PPbHbqkX+T9B2zAsZZwbkpEhfd7MlAWEyy6i5DXMhpzPncwYBc6uZwO wiFjYkpDOqD/VLUuEWdJ6aQ4Q9GJMA94PecIzJRhQ61BFNT2r5B7YPzz+IEdax2XbDkh vJCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=+mqkHAvBv1y5qS2y58nAD/iFpsVKp/726AYMa4PGL3o=; b=uxUNFv+yLqZzwnKUK5iH78C2zPRBcQvKL84mpo0pVfC/0N64s4mgmYyazO1ZSDlcrz VFglD6yincIUKKCyNDwG99wGmRBuIhsXzEUVlyc9E5GMkJFDYfj7t2XDjG2/ap9dADJx Eet/uAmllTvbgDZNS+BdMJxC+GtMHfzeIf7ZcrVgIfEx0Ra7ozJwYvEfbDaqqrCdpCMQ ZzkAySJ/4ChLNCC29o/NEMUnbGlcsFQSKeyz3ajAYLEdd4Ca04tFPT7T2abr4t4hVYXR aQD0OSogjKCWQEwMSIDLWjQoxNWvOLQHH5OKZwTe25xLTQ1cIYKD4Uud0gUoIz8B70/4 G3Vw== X-Gm-Message-State: ANoB5pkoesJ7n9owHjNzCzEecl/hQyuVsl5lt3UFYLmWoQSvRqXQCGWP 3wIlib2WPXtCWM6MKaF99nifgg== X-Received: by 2002:a05:6402:290:b0:46b:81d2:e3d0 with SMTP id l16-20020a056402029000b0046b81d2e3d0mr23709060edv.314.1670231373853; Mon, 05 Dec 2022 01:09:33 -0800 (PST) Received: from blmsp ([185.238.219.11]) by smtp.gmail.com with ESMTPSA id b17-20020a1709063cb100b007b4bc423b41sm5917994ejh.190.2022.12.05.01.09.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 05 Dec 2022 01:09:33 -0800 (PST) Date: Mon, 5 Dec 2022 10:09:32 +0100 From: Markus Schneider-Pargmann To: Marc Kleine-Budde Cc: Chandrasekar Ramakrishnan , Wolfgang Grandegger , linux-can@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 00/15] can: m_can: Optimizations for tcan and peripheral chips Message-ID: <20221205090932.zdoqxifsf6aty4k6@blmsp> References: <20221116205308.2996556-1-msp@baylibre.com> <20221202140306.n3iy74ru5f6bxmco@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20221202140306.n3iy74ru5f6bxmco@pengutronix.de> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Good Morning Marc, On Fri, Dec 02, 2022 at 03:03:06PM +0100, Marc Kleine-Budde wrote: > On 16.11.2022 21:52:53, Markus Schneider-Pargmann wrote: > > Hi, > > > > this series is aimed at optimizing the driver code for tcan chips and > > more generally for peripheral m_can chips. > > > > I did different things to improve the performance: > > - Reduce the number of SPI transfers. > > - Reduce the number of interrupts. > > - Enable use of FIFOs. > > > > I am working with a tcan4550 in loopback mode attached to a beaglebone > > black. I am currently working on optimizing the receive path as well > > which will be submitted in another series once it is done. > > The patches I've not commented on look fine. If you re-spin the series > only containing those, I'll include them in my next pull request, which > I'll send out soonish. Ok, thank you, I will send a subset of the patches today. > > regards, > Marc > > > Best, > > Markus > > > > Markus Schneider-Pargmann (15): > > can: m_can: Eliminate double read of TXFQS in tx_handler > > can: m_can: Wakeup net queue once tx was issued > > can: m_can: Cache tx putidx and transmits in flight > > can: m_can: Use transmit event FIFO watermark level interrupt > > can: m_can: Disable unused interrupts > > can: m_can: Avoid reading irqstatus twice > > can: m_can: Read register PSR only on error > > can: m_can: Count TXE FIFO getidx in the driver > > can: m_can: Count read getindex in the driver > > can: m_can: Batch acknowledge rx fifo > > can: m_can: Batch acknowledge transmit events > > can: tcan4x5x: Remove invalid write in clear_interrupts > > can: tcan4x5x: Fix use of register error status mask > > can: tcan4x5x: Fix register range of first block > > can: tcan4x5x: Specify separate read/write ranges > > > > drivers/net/can/m_can/m_can.c | 140 +++++++++++++++--------- > > drivers/net/can/m_can/m_can.h | 5 + > > drivers/net/can/m_can/tcan4x5x-core.c | 19 ++-- > > drivers/net/can/m_can/tcan4x5x-regmap.c | 45 ++++++-- > > 4 files changed, 141 insertions(+), 68 deletions(-) > > > > > > base-commit: 094226ad94f471a9f19e8f8e7140a09c2625abaa > > prerequisite-patch-id: e9df6751d43bb0d1e3b8938d7e93bc1cfa22cef2 > > prerequisite-patch-id: dad9ec37af766bcafe54cb156f896267a0f47fe1 > > prerequisite-patch-id: f4e6f1a213a31df2741a5fa3baa87aa45ef6707a > > BTW: I don't have access to these prerequisite-patch-id. I think I messed up here. I have three patches, SPI fixes and devicetree snippet that this series is based on. I guess I shouldn't have used --base then or rebase on something without these patches first. Thanks, Markus