Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp9099468rwd; Wed, 21 Jun 2023 03:04:00 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ57ZGnFTsUYUAnm6ESLYamk20epnbv1kuMgVoD7Vd9ue+5gwgmoUuTHlUNYa2EcqvelVjoW X-Received: by 2002:a05:6a21:3388:b0:121:3e28:19ee with SMTP id yy8-20020a056a21338800b001213e2819eemr14000873pzb.10.1687341839490; Wed, 21 Jun 2023 03:03:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687341839; cv=none; d=google.com; s=arc-20160816; b=Q30X+uyAjaxHt4Vj/6coc19b9GCkIeMMBe/Z4hBQHZTZRqYAubbWjquBhAeUWj+xYc zUaEiHoC/BA7bj4xdIeg8OK2+N6xMuXTsU8PaWl/toLRXqnf48XtELw9GzL7xZFbnhKB /5/3mQYVsiVjMm4iShM89dFnZo034FdKcHgEGc/aqVw3Ry9VeLiPaehMT0dpxwPaDbOT 8CEb0T7LC2iH92se5q8xEhE0NqJfi7zY5zzuDBvDg24PVQXtZYqdp31jq8q4CRKMppyK LAaWnGjLiSzDgdfxB+JTp7tzzailNkLODYNAaq/6an4bIfkBqSraJ48WUnk7JEvJj7HZ l4/Q== 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 :message-id:date:subject:cc:to:from:dkim-signature; bh=FnoYzlqcpbqIFDX/QCzP0DM0XYhA9I/O0wRSd0b2d80=; b=VGGVyxF/tjLrE0Ua8aD8cemzutzdRWlYKhyt6mTHxV65sj6PPIRwzGXddMmwSjOp0P yHxNmK1NYhoKamyHSQGhmTNetgl1YgOyTftwUdk3zwa9OSGBWg6Iwko21H1IHFOXz0rD v9ndMs6GkHULqmKQDdru2q0/o3YP9YvLNkw/yK8zrBT/KeOQGQG1ugUvydMnjSuehphc NgzAnzhBZRpIEHUfoOtLXp3L9q1Jx8oFJD2CDNUhi/ZQbkawurieyR/e9W6UwV1dH8gc lxgsPa3wmWY8sqjjYy2BYY5ogEhl1JLSV9zgUw3BJkn5WXMfAmTh2tCDPY50/IjgiPdG HDlg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20221208.gappssmtp.com header.s=20221208 header.b=OKCgz0Va; 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 v16-20020a63d550000000b005404f8dd0easi3481753pgi.292.2023.06.21.03.03.20; Wed, 21 Jun 2023 03:03:59 -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=@baylibre-com.20221208.gappssmtp.com header.s=20221208 header.b=OKCgz0Va; 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 S231622AbjFUJcZ (ORCPT + 99 others); Wed, 21 Jun 2023 05:32:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35084 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231332AbjFUJbP (ORCPT ); Wed, 21 Jun 2023 05:31:15 -0400 Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AED26198D for ; Wed, 21 Jun 2023 02:31:09 -0700 (PDT) Received: by mail-wr1-x431.google.com with SMTP id ffacd0b85a97d-311153ec442so4550953f8f.1 for ; Wed, 21 Jun 2023 02:31:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20221208.gappssmtp.com; s=20221208; t=1687339868; x=1689931868; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=FnoYzlqcpbqIFDX/QCzP0DM0XYhA9I/O0wRSd0b2d80=; b=OKCgz0VaMI1Fv6yd2XldHp/3Alw1/cS1VYDm4ECvg32UV+E10/b7GlASd5Luv4QTDe gl7+Y2+pMX7ebU1ik0S+/Bfjt+amyNuaVDzBp9q1dQm8nFS470hJzdR7tZXyr6Q4x5fN yy4l8FtsayAy/qYIK/O4ngS4Z8pBog+1eRV8Um2eyVNWrMK0IbXKS858U0IWVV4eTRw9 sr7aBZXPzwDkEI7pzvxZQqaGXD45sobVdOJ+U7xJMGNTAwX13i+wjEefT/9ctkCN8KjB 7ZStrac+Cl8yc2N9adH9Rcz9ni7eoCebFDY12q/U9V52Id688qhVzmdepEW+oLWS+tbE n0OQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687339868; x=1689931868; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=FnoYzlqcpbqIFDX/QCzP0DM0XYhA9I/O0wRSd0b2d80=; b=XJXINnCXgw5o/up9zYtSIpAxdMCfwvynFUIi92dbN+MA5j9ahSiinpwqym8L6prIw/ VUZ90nEUt+jHn9SAzGXavK/oGH8L99APK02Kd7/30LP3MT/8vKG4GiV3Cw2W5wKASFwH ZIk47OMcvNVls4Cy391nS2DQjrgwVTyPXY1n8p5XbZKmr9tmZ49AMw9X0XvBEIXLOFp+ IzFlow+gCLU7fe+0gQTT/fenptcbHS8fQAxV/tJsyLYb3NJ3uBCRXx37n26u9ycRehbF z0OtxcfzFf7loQoDXJPuwNkKTRSgrR6uDrInb13WzBrHjwTMMVjbOaZL84AuhCutWJF5 0A5g== X-Gm-Message-State: AC+VfDzJvGCdlLnp9jB8iG7NVULt3uOQ3alv+9CZAfAysQh9jRVZegWv Ujq0qVfdhJvojwJTLqTeVU0DAQ== X-Received: by 2002:a5d:4203:0:b0:311:1107:9aba with SMTP id n3-20020a5d4203000000b0031111079abamr13408111wrq.19.1687339868152; Wed, 21 Jun 2023 02:31:08 -0700 (PDT) Received: from blmsp.fritz.box ([2001:4091:a247:82fa:b762:4f68:e1ed:5041]) by smtp.gmail.com with ESMTPSA id t10-20020a5d49ca000000b002fe96f0b3acsm3977344wrs.63.2023.06.21.02.31.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 21 Jun 2023 02:31:07 -0700 (PDT) From: Markus Schneider-Pargmann To: Wolfgang Grandegger , Marc Kleine-Budde , Rob Herring , Krzysztof Kozlowski Cc: "David S . Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Conor Dooley , Chandrasekar Ramakrishnan , Michal Kubiak , Vivek Yadav , linux-can@vger.kernel.org, netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Simon Horman , Markus Schneider-Pargmann Subject: [PATCH v2 0/6] can: tcan4x5x: Introduce tcan4552/4553 Date: Wed, 21 Jun 2023 11:30:57 +0200 Message-Id: <20230621093103.3134655-1-msp@baylibre.com> X-Mailer: git-send-email 2.40.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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, 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 Hi everyone, This series introduces two new chips tcan-4552 and tcan-4553. The generic driver works in general but needs a few small changes. These are caused by the removal of wake and state pins. In v2 I updated the bindings to use tcan4x5x always as a fallback. The driver now uses the first more specific binding if available. If the given binding does not match the chip that is present, a warning is printed and the correct driver data is loaded instead. Based on v6.4-rc1. Best, Markus Changes in v2: - Update the binding documentation to specify tcan4552 and tcan4553 with the tcan4x5x as fallback - Update the driver to use auto detection as well. If compatible differs from the ID2 register, use the ID2 register and print a warning. - Small style changes Previous versions: v1 - https://lore.kernel.org/lkml/20230314151201.2317134-1-msp@baylibre.com Markus Schneider-Pargmann (6): dt-bindings: can: tcan4x5x: Add tcan4552 and tcan4553 variants can: tcan4x5x: Remove reserved register 0x814 from writable table can: tcan4x5x: Check size of mram configuration can: tcan4x5x: Rename ID registers to match datasheet can: tcan4x5x: Add support for tcan4552/4553 can: tcan4x5x: Add error messages in probe .../devicetree/bindings/net/can/tcan4x5x.txt | 11 +- drivers/net/can/m_can/m_can.c | 16 ++ drivers/net/can/m_can/m_can.h | 1 + drivers/net/can/m_can/tcan4x5x-core.c | 161 ++++++++++++++---- drivers/net/can/m_can/tcan4x5x-regmap.c | 1 - 5 files changed, 155 insertions(+), 35 deletions(-) base-commit: ac9a78681b921877518763ba0e89202254349d1b -- 2.40.1