Received: by 2002:a05:6a10:17d3:0:0:0:0 with SMTP id hz19csp244087pxb; Fri, 16 Apr 2021 04:44:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxBSrm3NzOzZllX9MJ+lHa93c6ZJ7Ig+4XvkFW0QI/lOZ+V8E9BUOmgzEHmF2kerulqyG3S X-Received: by 2002:a17:90a:1190:: with SMTP id e16mr9260022pja.110.1618573444538; Fri, 16 Apr 2021 04:44:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618573444; cv=none; d=google.com; s=arc-20160816; b=or5wQ+CTxFHu0EoIGgaymdaHBfg6DKTHmzqvQmEIuw0/EmHbz1h+AplGl7YNdFhCwj 1WAj6qZgBdhLkNS7GKLmq8U5jy6e1qye3yhayt3rnCUKP3KZ4Y5XXcp5YwVR4xebn/tL NUD6P0yauLRkguFpMYjbNKIzDJq6nV9dqeVjCS1KESUBTxJ8kVKs+uXrAITFwyYErCf7 /+sJLi7C0Wc40ZE4DKr2dUqNKG+xoD2h76/6/+AY73pcSQr7eabWI0Je87BiYDcEccbz iRj+DL1wXWBuOIWjSbIblrLBc+B+KZaaedw32V7XTvAsnJNVV2sNFLBGM3RQbKsBhrfR 3jyg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:to:mime-version:message-id:date:subject:cc:from :dkim-signature; bh=YzBU+cLhccqcsDURJtSYpEEhzleC4dnairSrugdNE1A=; b=y4iIpzgoeQEW7tWCqtZhJA8Orhu/ybjnIRAXIghdyIWdp5UIvAbrJWgpAI+WLqPCD/ Ow5DuhcpEgikUeCouZHEAfif/MODigYv36D67824M984SU0zGC+sXU5pCCBcFRxKA53f cuplVbUC6k+OXRiXwHKdGz8sYHgMrZKu9Mlk6EYUzPGbfqseznm+XeFVOayGDAWXixcx HtQpF6nY8nx0qNpSSI3jO0vjpjDjCxrI9j59+7jhKyntRzI3IazTo5CKqb3jzkDqEAD5 JacuT14k2pKU1YRt3g3wJwKlgwbrSWL/oWJ7ppf64lNpcGp42D5DrTuCdZO5Sm+frSHT VN2A== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@ti.com header.s=ti-com-17Q1 header.b=Byweb9b+; 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; dmarc=fail (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 90si6534144plc.183.2021.04.16.04.43.52; Fri, 16 Apr 2021 04:44:04 -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; dkim=fail header.i=@ti.com header.s=ti-com-17Q1 header.b=Byweb9b+; 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; dmarc=fail (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242151AbhDPLbo (ORCPT + 99 others); Fri, 16 Apr 2021 07:31:44 -0400 Received: from fllv0015.ext.ti.com ([198.47.19.141]:46844 "EHLO fllv0015.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239255AbhDPLbl (ORCPT ); Fri, 16 Apr 2021 07:31:41 -0400 Received: from lelv0265.itg.ti.com ([10.180.67.224]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id 13GBV3jZ106510; Fri, 16 Apr 2021 06:31:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1618572663; bh=YzBU+cLhccqcsDURJtSYpEEhzleC4dnairSrugdNE1A=; h=From:To:CC:Subject:Date; b=Byweb9b+UMrEf5ZDslCCazJwDg0Vg7230dkxIilNF0VoU7p+ppY7EZtSBNiuVUuhJ aNvuwpQpzyRkpxiwv0UyivgX5DSPfUTpNpEYMrg8BrSp1Ww47gjR+7RgAtTd+nYcEB 8tqOJyLVwFmb98BUIv4QoRWBFbrPCNYdP335QoSQ= Received: from DFLE109.ent.ti.com (dfle109.ent.ti.com [10.64.6.30]) by lelv0265.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 13GBV281122015 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 16 Apr 2021 06:31:03 -0500 Received: from DFLE101.ent.ti.com (10.64.6.22) by DFLE109.ent.ti.com (10.64.6.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Fri, 16 Apr 2021 06:31:02 -0500 Received: from fllv0040.itg.ti.com (10.64.41.20) by DFLE101.ent.ti.com (10.64.6.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2 via Frontend Transport; Fri, 16 Apr 2021 06:31:02 -0500 Received: from gsaswath-HP-ProBook-640-G5.dal.design.ti.com (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0040.itg.ti.com (8.15.2/8.15.2) with ESMTP id 13GBUwIu073816; Fri, 16 Apr 2021 06:30:59 -0500 From: Aswath Govindraju CC: , , , , Kishon Vijay Abraham I , Vinod Koul , Rob Herring , Marc Kleine-Budde , Wolfgang Grandegger , Lokesh Vutla , Vignesh Raghavendra , Grygorii Strashko , Aswath Govindraju Subject: [PATCH v5 0/3] CAN TRANSCEIVER: Add support for CAN transceivers Date: Fri, 16 Apr 2021 17:00:55 +0530 Message-ID: <20210416113058.23815-1-a-govindraju@ti.com> X-Mailer: git-send-email 2.17.1 MIME-Version: 1.0 Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 To: unlisted-recipients:; (no To-header on input) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The following series of patches add support for CAN transceivers. TCAN1042 has a standby signal that needs to be pulled high for sending/receiving messages[1]. TCAN1043 has a enable signal along with standby signal that needs to be pulled up for sending/receiving messages[2], and other combinations of the two lines can be used to put the transceiver in different states to reduce power consumption. On boards like the AM654-idk and J721e-evm these signals are controlled using gpios. Patch 1 rewords the comment that restricts max_link_rate attribute to have units of Mbps. Patch 2 models the transceiver as a phy device tree node with properties for max bit rate supported, gpio properties for indicating gpio pin numbers to which standby and enable signals are connected. Patch 2 adds a generic driver to support CAN transceivers. changes since v4: - In patch 3 made the correction from mcan to CAN, in Kconfig help changes since v3: - dropped patch 2(in v3) - changed the node name property in patch 3(in v3) - picked up Rob Herring's reviewed-by for patch 3(in v3) changes since v2: - dropped 5 and 6 patches and to be sent via linux-can-next - added static keyword for can_transceiver_phy_probe() - changed enable gpio example to active high in patch 3 - Rearranged the file names in alphabetical order in Makefile and MAINTAINERS file changes since v1: - Added patch 1 (in v2) that rewords the comment that restrict max_link_rate attribute to have units of Mbps. - Added patch 2 (in v2) that adds an API for devm_of_phy_optional_get_by_index - Patch 1 (in v1) - updated MAINTAINERS file - Patch 2 (in v1) - replaced m_can with CAN to make the driver independent of CAN driver - Added prefix CAN_TRANSCEIVER for EN_PRESENT and STB_PRESENT - Added new line before return statements in power_on() and power_off - Added error handling patch for devm_kzalloc() - used the max_link_rate attribute directly instead of dividing it by 1000000 - removed the spaces before GPIOD_OUT_LOW in devm_gpiod_get() - Corrected requested value for standby-gpios to GPIOD_OUT_HIGH - Updated MAINTAINERS file - Patch 3 (in v1) - replaced minItems with maxItems - Removed phy-names property as there is only one phy - Patch 4 (in v1) - replaced dev_warn with dev_info when no transceiver is found - Added struct phy * field in m_can_classdev struct - moved phy_power_on and phy_power_off to m_can_open and m_can_close respectively - Moved the check for max_bit_rate to generice transceiver driver [1] - https://www.ti.com/lit/ds/symlink/tcan1042h.pdf [2] - https://www.ti.com/lit/ds/symlink/tcan1043-q1.pdf Aswath Govindraju (3): phy: core: Reword the comment specifying the units of max_link_rate to be Mbps dt-bindings: phy: Add binding for TI TCAN104x CAN transceivers phy: phy-can-transceiver: Add support for generic CAN transceiver driver .../bindings/phy/ti,tcan104x-can.yaml | 56 +++++++ MAINTAINERS | 2 + drivers/phy/Kconfig | 9 ++ drivers/phy/Makefile | 1 + drivers/phy/phy-can-transceiver.c | 146 ++++++++++++++++++ include/linux/phy/phy.h | 2 +- 6 files changed, 215 insertions(+), 1 deletion(-) create mode 100644 Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml create mode 100644 drivers/phy/phy-can-transceiver.c -- 2.17.1