All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aswath Govindraju <a-govindraju@ti.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Nishanth Menon <nm@ti.com>,
	Aswath Govindraju <a-govindraju@ti.com>,
	Wolfgang Grandegger <wg@grandegger.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	<linux-can@vger.kernel.org>, <linux-phy@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH RFC 0/2] CAN TRANSCEIVER: Add support for setting mux
Date: Thu, 11 Nov 2021 22:13:10 +0530	[thread overview]
Message-ID: <20211111164313.649-1-a-govindraju@ti.com> (raw)

On some boards, for routing CAN signals from controller to transceiver,
muxes might need to be set. Therefore, add support for setting the mux by
reading the mux-controls property from the device tree node.

Aswath Govindraju (2):
  dt-bindings: phy: ti,tcan104x-can: Document mux-controls property
  phy: phy-can-transceiver: Add support for setting mux

 .../bindings/phy/ti,tcan104x-can.yaml         |  6 ++++++
 drivers/phy/phy-can-transceiver.c             | 21 +++++++++++++++++++
 2 files changed, 27 insertions(+)

-- 
2.17.1


WARNING: multiple messages have this Message-ID (diff)
From: Aswath Govindraju <a-govindraju@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Nishanth Menon <nm@ti.com>,
	Aswath Govindraju <a-govindraju@ti.com>,
	Wolfgang Grandegger <wg@grandegger.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	<linux-can@vger.kernel.org>, <linux-phy@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH RFC 0/2] CAN TRANSCEIVER: Add support for setting mux
Date: Thu, 11 Nov 2021 22:13:10 +0530	[thread overview]
Message-ID: <20211111164313.649-1-a-govindraju@ti.com> (raw)

On some boards, for routing CAN signals from controller to transceiver,
muxes might need to be set. Therefore, add support for setting the mux by
reading the mux-controls property from the device tree node.

Aswath Govindraju (2):
  dt-bindings: phy: ti,tcan104x-can: Document mux-controls property
  phy: phy-can-transceiver: Add support for setting mux

 .../bindings/phy/ti,tcan104x-can.yaml         |  6 ++++++
 drivers/phy/phy-can-transceiver.c             | 21 +++++++++++++++++++
 2 files changed, 27 insertions(+)

-- 
2.17.1


-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

             reply	other threads:[~2021-11-11 16:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 16:43 Aswath Govindraju [this message]
2021-11-11 16:43 ` [PATCH RFC 0/2] CAN TRANSCEIVER: Add support for setting mux Aswath Govindraju
2021-11-11 16:43 ` [PATCH RFC 1/2] dt-bindings: phy: ti,tcan104x-can: Document mux-controls property Aswath Govindraju
2021-11-11 16:43   ` [PATCH RFC 1/2] dt-bindings: phy: ti, tcan104x-can: " Aswath Govindraju
2021-11-11 16:43 ` [PATCH RFC 2/2] phy: phy-can-transceiver: Add support for setting mux Aswath Govindraju
2021-11-11 16:43   ` Aswath Govindraju
2021-11-12  8:40   ` Marc Kleine-Budde
2021-11-12  8:40     ` Marc Kleine-Budde
2021-11-12 13:48     ` Aswath Govindraju
2021-11-12 13:48       ` Aswath Govindraju
2021-11-12 19:15       ` Peter Rosin
2021-11-12 19:15         ` Peter Rosin
2021-11-15  6:31         ` Aswath Govindraju
2021-11-15  6:31           ` Aswath Govindraju
2021-11-17 21:24           ` Peter Rosin
2021-11-17 21:24             ` Peter Rosin
2021-11-18 11:12             ` Aswath Govindraju
2021-11-18 11:12               ` Aswath Govindraju
2021-11-18 12:44               ` Peter Rosin
2021-11-18 12:44                 ` Peter Rosin
2021-11-19  7:42                 ` Aswath Govindraju
2021-11-19  7:42                   ` Aswath Govindraju
2021-11-22 13:04 ` [PATCH RFC 0/2] CAN TRANSCEIVER: " Aswath Govindraju
2021-11-22 13:04   ` 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 \
    --in-reply-to=20211111164313.649-1-a-govindraju@ti.com \
    --to=a-govindraju@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=mkl@pengutronix.de \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.com \
    --cc=vkoul@kernel.org \
    --cc=wg@grandegger.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.