From patchwork Thu Apr 27 20:45:36 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Dario Binacchi X-Patchwork-Id: 88385 Return-Path: Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:b0ea:0:b0:3b6:4342:cba0 with SMTP id b10csp521852vqo; Thu, 27 Apr 2023 13:48:54 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ494gd/mEPquDcPgLKJ1Eh/gNIB/kSYlbFp/lQZYFEwt8qvTyJPUSfo+xwOJ2Z4sXnBMoIk X-Received: by 2002:a17:902:ce92:b0:1a6:81fc:b585 with SMTP id f18-20020a170902ce9200b001a681fcb585mr3508639plg.41.1682628534322; Thu, 27 Apr 2023 13:48:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1682628534; cv=none; d=google.com; s=arc-20160816; b=V8UEGwIZiq9E71SV5ZPPkBcYd9TOvbCSATck4njMs1SPjtjvrIYB/wB/L7F746yntv 2CR56I9lDtBC5E4FkufOYY0BwSwJJlTNN6wtZDFXQa3ROtLjd4Bh1b/9zIh+Y8co8usv 4u0sS9WhlNZ2D3Q9vqt9wuHoWQkoVnT4Uz9Xyq76N2PNi27fAYdIIZoSQ2nu99YeQ0Pl jpqEx08P3fK3mMBlfEyNHkXrmGsspveFrDZl/iZ3oe3Chgby5LiMGo3ASfC+4fO+aF3X sJ4jMV66/kcFJftyliymSMiuCc1QIXgwayoadQNAbwvpFatKn5tDHtbC8XzPL0dWO8sa rtzg== 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 :dkim-signature; bh=Hf8K+LPV3HpQoodPsHclIndfavzTHfh5H+b7Pu9+qX0=; b=Ju6at0Hz4r7qwAVUTwhZ0aavdLaDeK0eSOOlLhX6i7JMIOzgn4Ot5lV5NYJrnWbIbW H/kzlCfnGQN+fILgfUfqW9DdsJG5yc1SmmKFYLvmieqOFUk2Mq/Edj9pg4xwoB6OhqGH +L9sMYgaMrW5epm6kFN9PhnUr0F1nbkuT36bYqmS6z9pbSzX3ezSV7JHlX5/SaE76PF/ TRtSe00cHbqbAomIYv5nrfTNg3dFtIY+QWTcyTrnqnsxTUj3hg+ooa55T4XdCYs2O30/ c0bHyvHmC+QyD72vmfPDamxFCQLZ34/8v6Vk71AHjW2IHUmPz8I+JVqvTeT+z7Zno/23 JUJA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@amarulasolutions.com header.s=google header.b=lYQb9N0D; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=amarulasolutions.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id la5-20020a170902fa0500b001a93e74c8b8si16442222plb.481.2023.04.27.13.48.39; Thu, 27 Apr 2023 13:48:54 -0700 (PDT) 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=@amarulasolutions.com header.s=google header.b=lYQb9N0D; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=amarulasolutions.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344316AbjD0Upz (ORCPT + 99 others); Thu, 27 Apr 2023 16:45:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41400 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344295AbjD0Upt (ORCPT ); Thu, 27 Apr 2023 16:45:49 -0400 Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0338E3C07 for ; Thu, 27 Apr 2023 13:45:47 -0700 (PDT) Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-959a3e2dd27so1077479166b.3 for ; Thu, 27 Apr 2023 13:45:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amarulasolutions.com; s=google; t=1682628346; x=1685220346; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=Hf8K+LPV3HpQoodPsHclIndfavzTHfh5H+b7Pu9+qX0=; b=lYQb9N0DXJFaYlcVpdVJTsWypegS4pxbOgWG4uYPWRv0tlbBFBKpgdjjuIJ7l89OKn MjxoNkkecvtACZfe3IMOjhngU6dFPvHM6Jb0dKqxdqG2fY33lE5vlStJ4DhOLLou9+Oc EFPe8U5O53BQC+dflc06JM2/KRewWS9Fgm8wY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682628346; x=1685220346; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Hf8K+LPV3HpQoodPsHclIndfavzTHfh5H+b7Pu9+qX0=; b=SNIQD5LzVPq0t4bj8Z6XjFfopm//xoA212uQ9j7WAvOeJyyu3SpHFLGa2TpGpYujI2 2RdMEIQ5Ss8JGWz+dkFHEXusdC8J5PPawGUrkAFSXRaSQTjQ2JWrVlI1DtFsmjV7M3bu FU4Zw8rfMpsS3OfeCgyMhfeTcbSUFRu6mfn1cUG6rM94BD4zIamyPI6gv8ThKv3LHsQY xiV8SN3AdHI8CuBSvx9CVihYKE4jkLIqWYarQmRd92Whp48a8hu1BFSq0udiB++kK4jT 9AdmML+aUUNQnbliB6oWcU0/6yK6h64U1i6slw3kQ5WeSgX+jpS/f7yWI9q/D9YXNjm+ sPWw== X-Gm-Message-State: AC+VfDyG/cDYpL996hgqmZTEIJV3FudT4ru0LOuZNDpAJRQW19KkDr/c sbsNj6rY41/x/MF3IpZBFDjyviUpgEHCdlBtjugPLg== X-Received: by 2002:a17:906:9b86:b0:957:758e:df57 with SMTP id dd6-20020a1709069b8600b00957758edf57mr3360655ejc.65.1682628346138; Thu, 27 Apr 2023 13:45:46 -0700 (PDT) Received: from dario-ThinkPad-T14s-Gen-2i.homenet.telecomitalia.it (host-87-5-99-194.retail.telecomitalia.it. [87.5.99.194]) by smtp.gmail.com with ESMTPSA id s12-20020a170906bc4c00b00947ed087a2csm10171360ejv.154.2023.04.27.13.45.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 27 Apr 2023 13:45:45 -0700 (PDT) From: Dario Binacchi To: linux-kernel@vger.kernel.org Cc: michael@amarulasolutions.com, Amarula patchwork , Dario Binacchi , Alexandre Torgue , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Krzysztof Kozlowski , Marc Kleine-Budde , Maxime Coquelin , Paolo Abeni , Rob Herring , Wolfgang Grandegger , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-can@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, netdev@vger.kernel.org Subject: [PATCH v2 1/5] dt-bindings: net: can: add "st,can-secondary" property Date: Thu, 27 Apr 2023 22:45:36 +0200 Message-Id: <20230427204540.3126234-2-dario.binacchi@amarulasolutions.com> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20230427204540.3126234-1-dario.binacchi@amarulasolutions.com> References: <20230427204540.3126234-1-dario.binacchi@amarulasolutions.com> MIME-Version: 1.0 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable 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 X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1764363898136103279?= X-GMAIL-MSGID: =?utf-8?q?1764363898136103279?= On the stm32f7 Socs the can peripheral can be in single or dual configuration. In the dual configuration, in turn, it can be in primary or secondary mode. The addition of the 'st,can-secondary' property allows you to specify this mode in the dual configuration. CAN peripheral nodes in single configuration contain neither "st,can-primary" nor "st,can-secondary". Signed-off-by: Dario Binacchi Reviewed-by: Rob Herring --- (no changes since v1) .../bindings/net/can/st,stm32-bxcan.yaml | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/Documentation/devicetree/bindings/net/can/st,stm32-bxcan.yaml b/Documentation/devicetree/bindings/net/can/st,stm32-bxcan.yaml index 769fa5c27b76..de1d4298893b 100644 --- a/Documentation/devicetree/bindings/net/can/st,stm32-bxcan.yaml +++ b/Documentation/devicetree/bindings/net/can/st,stm32-bxcan.yaml @@ -21,11 +21,22 @@ properties: st,can-primary: description: - Primary and secondary mode of the bxCAN peripheral is only relevant - if the chip has two CAN peripherals. In that case they share some - of the required logic. + Primary mode of the bxCAN peripheral is only relevant if the chip has + two CAN peripherals in dual CAN configuration. In that case they share + some of the required logic. + Not to be used if the peripheral is in single CAN configuration. To avoid misunderstandings, it should be noted that ST documentation - uses the terms master/slave instead of primary/secondary. + uses the terms master instead of primary. + type: boolean + + st,can-secondary: + description: + Secondary mode of the bxCAN peripheral is only relevant if the chip + has two CAN peripherals in dual CAN configuration. In that case they + share some of the required logic. + Not to be used if the peripheral is in single CAN configuration. + To avoid misunderstandings, it should be noted that ST documentation + uses the terms slave instead of secondary. type: boolean reg: