Received: by 2002:a05:6a10:c7d3:0:0:0:0 with SMTP id h19csp686364pxy; Sat, 14 Aug 2021 20:36:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwjpKpc83dibj5zBDmHowARJdufOtyVbU1UX822cZUVqOtCMXuglkSc3MdGSGKaqFrzDUul X-Received: by 2002:a5d:8450:: with SMTP id w16mr7288960ior.141.1628998577228; Sat, 14 Aug 2021 20:36:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628998577; cv=none; d=google.com; s=arc-20160816; b=MkAQpI32W6MQyxK0Wsyio0mzW13jPxTRNMD0NgzhDu3DYmdyNjPlIe7Rz4JdUON9Rk /LyD2qLjA5x//HozBigutsWh/U9rYPe/1v8ulXw4LGPhG6DjIip5lt75s4RnTaC0qBcT YUMSgTcv8x0P4Rt3t2buLYq0gJkDipXwvyIXqlw1PTo6OjCE+EB/MeIrySUv2Q5jzw8m gPadgbzGwcCmzPBR6nLkoeGwblbZwk057rfZgAjE9eVdHXLK7PJCsKZWBESzEj/GEMQL gxGz1+04GCszpbtV5CHn3G7hfukR7zB2P0Qk+ZYB2ccxb9zcIQzr+lOp14w5LXbBh3jM YY6g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=24BtdqoalyX+qO1ZvKAIDhjStHJbzcfxAS7OM8FxEMs=; b=oHxzhzu2DbDjG0p21Sq90Osh0Mfmx9ZS6CgFGf7FO1D/jsm8OS/RIPFyixnp2OaWze D7XDbv8Er8zynWT8kL2dPfAa6M2+dH8R6x9jnNrIsIoqER3WdJVFIhTEMyC9tpmj7/hD WRYtiz4wAMS7liZmmW1GBZpcGaKwuU4viB9RyEScKvzeyPfaeZiUc/L3Bh8BwN8P9Sdi upWc5FfG2hbiQtExJPNnRgKnEq/SCeXBc++sjLH2tQkpSPD/SYe//JxE8x6G9QXba/pv wVZR3wQzrl47T3x5RZL0GkveR2zo0WIc1xEufzKaLKl9vF8a0zSxOEiUMyVgers+FZMQ l1tw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b1si6969444ilj.117.2021.08.14.20.36.05; Sat, 14 Aug 2021 20:36:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236043AbhHODe0 (ORCPT + 99 others); Sat, 14 Aug 2021 23:34:26 -0400 Received: from smtp11.smtpout.orange.fr ([80.12.242.133]:42069 "EHLO smtp.smtpout.orange.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235606AbhHODeX (ORCPT ); Sat, 14 Aug 2021 23:34:23 -0400 Received: from tomoyo.flets-east.jp ([114.149.34.46]) by mwinf5d21 with ME id hfZ7250050zjR6y03fZrxo; Sun, 15 Aug 2021 05:33:53 +0200 X-ME-Helo: tomoyo.flets-east.jp X-ME-Auth: bWFpbGhvbC52aW5jZW50QHdhbmFkb28uZnI= X-ME-Date: Sun, 15 Aug 2021 05:33:53 +0200 X-ME-IP: 114.149.34.46 From: Vincent Mailhol To: Marc Kleine-Budde , linux-can@vger.kernel.org Cc: =?UTF-8?q?Stefan=20M=C3=A4tje?= , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Vincent Mailhol Subject: [PATCH v5 3/7] can: bittiming: change unit of TDC parameters to clock periods Date: Sun, 15 Aug 2021 12:32:44 +0900 Message-Id: <20210815033248.98111-4-mailhol.vincent@wanadoo.fr> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210815033248.98111-1-mailhol.vincent@wanadoo.fr> References: <20210815033248.98111-1-mailhol.vincent@wanadoo.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org In the current implementation, all Transmission Delay Compensation (TDC) parameters are expressed in time quantum. However, ISO 11898-1 actually specifies that these should be expressed in *minimum* time quantum. Furthermore, the minimum time quantum is specified to be "one node clock period long" (c.f. paragraph 11.3.1.1 "Bit time"). For sake of simplicity, we prefer to use the "clock period" term instead of "minimum time quantum" because we believe that it is more broadly understood. This patch fixes that discrepancy by updating the documentation and the formula for TDCO calculation. N.B. In can_calc_tdco(), the sample point (in time quantum) was calculated using a division, thus introducing a risk of rounding and truncation errors. On top of changing the unit to clock period, we also modified the formula to use only additions. Suggested-by: Stefan Mätje Signed-off-by: Vincent Mailhol --- drivers/net/can/dev/bittiming.c | 9 +++++---- include/linux/can/bittiming.h | 28 +++++++++++++++++----------- 2 files changed, 22 insertions(+), 15 deletions(-) diff --git a/drivers/net/can/dev/bittiming.c b/drivers/net/can/dev/bittiming.c index 7dbda411915a..582463bc15f7 100644 --- a/drivers/net/can/dev/bittiming.c +++ b/drivers/net/can/dev/bittiming.c @@ -193,12 +193,13 @@ void can_calc_tdco(struct net_device *dev) * one or two. */ if (dbt->brp == 1 || dbt->brp == 2) { - /* Reuse "normal" sample point and convert it to time quanta */ - u32 sample_point_in_tq = can_bit_time(dbt) * dbt->sample_point / 1000; + /* Sample point in clock periods */ + u32 sample_point_in_tc = (CAN_SYNC_SEG + dbt->prop_seg + + dbt->phase_seg1) * dbt->brp; - if (sample_point_in_tq < tdc_const->tdco_min) + if (sample_point_in_tc < tdc_const->tdco_min) return; - tdc->tdco = min(sample_point_in_tq, tdc_const->tdco_max); + tdc->tdco = min(sample_point_in_tc, tdc_const->tdco_max); priv->ctrlmode |= CAN_CTRLMODE_TDC_AUTO; } } diff --git a/include/linux/can/bittiming.h b/include/linux/can/bittiming.h index 9e20260611cc..aebbe65dab7e 100644 --- a/include/linux/can/bittiming.h +++ b/include/linux/can/bittiming.h @@ -31,8 +31,8 @@ * * To solve this issue, ISO 11898-1 introduces in section 11.3.3 * "Transmitter delay compensation" a SSP (Secondary Sample Point) - * equal to the distance, in time quanta, from the start of the bit - * time on the TX pin to the actual measurement on the RX pin. + * equal to the distance from the start of the bit time on the TX pin + * to the actual measurement on the RX pin. * * This structure contains the parameters to calculate that SSP. * @@ -44,8 +44,13 @@ * |<------- TDCO ------->| * |<----------- Secondary Sample Point ---------->| * + * To increase precision, contrary to the other bittiming parameters + * which are measured in time quanta, the TDC parameters are measured + * in clock periods (also referred as "minimum time quantum" in ISO + * 11898-1). + * * @tdcv: Transmitter Delay Compensation Value. The time needed for - * the signal to propagate, i.e. the distance, in time quanta, + * the signal to propagate, i.e. the distance, in clock periods, * from the start of the bit on the TX pin to when it is received * on the RX pin. @tdcv depends on the controller modes: * @@ -62,17 +67,18 @@ * TDC is disabled and all the values of this structure should be * ignored. * - * @tdco: Transmitter Delay Compensation Offset. Offset value, in time - * quanta, defining the distance between the start of the bit - * reception on the RX pin of the transceiver and the SSP + * @tdco: Transmitter Delay Compensation Offset. Offset value, in + * clock periods, defining the distance between the start of the + * bit reception on the RX pin of the transceiver and the SSP * position such that SSP = @tdcv + @tdco. * * @tdcf: Transmitter Delay Compensation Filter window. Defines the - * minimum value for the SSP position in time quanta. If the SSP - * position is less than @tdcf, then no delay compensations occur - * and the normal sampling point is used instead. The feature is - * enabled if and only if @tdcv is set to zero (automatic mode) - * and @tdcf is configured to a value greater than @tdco. + * minimum value for the SSP position in clock periods. If the + * SSP position is less than @tdcf, then no delay compensations + * occur and the normal sampling point is used instead. The + * feature is enabled if and only if @tdcv is set to zero + * (automatic mode) and @tdcf is configured to a value greater + * than @tdco. */ struct can_tdc { u32 tdcv; -- 2.31.1