From: Vinod Koul <vkoul@kernel.org>
To: Aswath Govindraju <a-govindraju@ti.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-can@vger.kernel.org
Subject: Re: [PATCH v5] phy: phy-can-transceiver: Add support for setting mux
Date: Mon, 11 Apr 2022 20:14:23 +0530 [thread overview]
Message-ID: <YlQ+x555++i4Vmlx@matsya> (raw)
In-Reply-To: <20220408111316.21189-1-a-govindraju@ti.com>
On 08-04-22, 16:43, Aswath Govindraju wrote:
> 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-states property from the device tree node.
Applied, thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Aswath Govindraju <a-govindraju@ti.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-can@vger.kernel.org
Subject: Re: [PATCH v5] phy: phy-can-transceiver: Add support for setting mux
Date: Mon, 11 Apr 2022 20:14:23 +0530 [thread overview]
Message-ID: <YlQ+x555++i4Vmlx@matsya> (raw)
In-Reply-To: <20220408111316.21189-1-a-govindraju@ti.com>
On 08-04-22, 16:43, Aswath Govindraju wrote:
> 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-states property from the device tree node.
Applied, thanks
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2022-04-11 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 11:13 [PATCH v5] phy: phy-can-transceiver: Add support for setting mux Aswath Govindraju
2022-04-08 11:13 ` Aswath Govindraju
2022-04-11 14:44 ` Vinod Koul [this message]
2022-04-11 14:44 ` Vinod Koul
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=YlQ+x555++i4Vmlx@matsya \
--to=vkoul@kernel.org \
--cc=a-govindraju@ti.com \
--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=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.