From: Aswath Govindraju <firstname.lastname@example.org> To: unlisted-recipients:; (no To-header on input) Cc: Chandrasekar Ramakrishnan <email@example.com>, Wolfgang Grandegger <firstname.lastname@example.org>, Marc Kleine-Budde <email@example.com>, "David S . Miller" <firstname.lastname@example.org>, Jakub Kicinski <email@example.com>, Rob Herring <firstname.lastname@example.org>, <email@example.com>, <firstname.lastname@example.org>, <email@example.com>, <firstname.lastname@example.org>, Vignesh Raghavendra <email@example.com>, Lokesh Vutla <firstname.lastname@example.org>, Kishon Vijay Abraham I <email@example.com>, Aswath Govindraju <firstname.lastname@example.org> Subject: [PATCH v4 0/2] MCAN: Add support for implementing transceiver as a phy Date: Mon, 10 May 2021 10:55:39 +0530 [thread overview] Message-ID: <email@example.com> (raw) The following series of patches add support for implementing the transceiver as a phy of m_can_platform driver. TCAN1042 has a standby signal that needs to be pulled high for sending/receiving messages. TCAN1043 has a enable signal along with standby signal that needs to be pulled up for sending/receiving messages, 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. These gpios are set in phy driver, and the transceiver can be put in different states using phy API. The phy driver is added in the series . This patch series is dependent on . changes since v3: - Added phy_power_off() in case of an error in m_can_open(). changes since v2: - changed dev_err to dev_err_probe in patch 2 - used mcan_class instead of priv to assign max bit rate - Picked up Rob Herring's acked-by for patch 1 changes since v1: - Used the API devm_phy_get_optional() instead of devm_of_phy_get_optional_by_index()  - https://www.ti.com/lit/ds/symlink/tcan1042h.pdf  - https://www.ti.com/lit/ds/symlink/tcan1043-q1.pdf  - https://lore.kernel.org/patchwork/project/lkml/list/?series=498359  - https://lore.kernel.org/patchwork/patch/1413286/ Faiz Abbas (2): dt-bindings: net: can: Document transceiver implementation as phy can: m_can: Add support for transceiver as phy .../devicetree/bindings/net/can/bosch,m_can.yaml | 3 +++ drivers/net/can/m_can/m_can.c | 11 +++++++++++ drivers/net/can/m_can/m_can.h | 2 ++ drivers/net/can/m_can/m_can_platform.c | 13 +++++++++++++ 4 files changed, 29 insertions(+) -- 2.17.1
next reply other threads:[~2021-05-10 5:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-10 5:25 Aswath Govindraju [this message] 2021-05-10 5:25 ` [PATCH v4 1/2] dt-bindings: net: can: Document transceiver implementation as phy Aswath Govindraju 2021-05-10 5:25 ` [PATCH v4 2/2] can: m_can: Add support for transceiver " Aswath Govindraju 2021-07-24 17:56 ` Marc Kleine-Budde 2021-06-14 12:32 ` [PATCH v4 0/2] MCAN: Add support for implementing transceiver as a phy Aswath Govindraju 2021-06-16 9:17 ` Marc Kleine-Budde 2021-07-19 14:17 ` Aswath Govindraju
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v4 0/2] MCAN: Add support for implementing transceiver as a phy' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).