From: Vinod Koul <vkoul@kernel.org>
To: Aswath Govindraju <a-govindraju@ti.com>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Kishon Vijay Abraham I <kishon@ti.com>,
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: Re: [PATCH v3 0/2] CAN: Add support for setting mux
Date: Thu, 23 Dec 2021 16:58:24 +0530 [thread overview]
Message-ID: <YcRdWJtREHFWXBKM@matsya> (raw)
In-Reply-To: <20211216041012.16892-1-a-govindraju@ti.com>
On 16-12-21, 09:40, Aswath Govindraju wrote:
> The following series of patches add support for setting
> muxes to route signals from CAN controller to transceiver
> by reading the property mux-states from the device tree
> node
These look okay to me
>
> The following series of patches are dependent on,
> - https://lkml.org/lkml/2021/12/2/423
Pls post when these are merged..
>
> Changes since v2:
> - Fixed the bindings removing the description about
> the arguments in mux-states property
>
> Changes since v1:
> - Fixed the description for mux-states property in bindings
> file
> - appended declaration of variable ret in the end
>
> Aswath Govindraju (2):
> dt-bindings: phy: ti,tcan104x-can: Document mux-states property
> phy: phy-can-transceiver: Add support for setting mux
>
> .../bindings/phy/ti,tcan104x-can.yaml | 7 ++++++
> drivers/phy/Kconfig | 1 +
> drivers/phy/phy-can-transceiver.c | 24 ++++++++++++++++++-
> 3 files changed, 31 insertions(+), 1 deletion(-)
>
> --
> 2.17.1
--
~Vinod
prev parent reply other threads:[~2021-12-23 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 4:10 [PATCH v3 0/2] CAN: Add support for setting mux Aswath Govindraju
2021-12-16 4:10 ` [PATCH v3 1/2] dt-bindings: phy: ti,tcan104x-can: Document mux-states property Aswath Govindraju
2021-12-16 20:33 ` Rob Herring
2022-03-08 16:39 ` [PATCH v3 1/2] dt-bindings: phy: ti, tcan104x-can: " Rob Herring
2021-12-16 4:10 ` [PATCH v3 2/2] phy: phy-can-transceiver: Add support for setting mux Aswath Govindraju
2021-12-23 11:28 ` Vinod Koul [this message]
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=YcRdWJtREHFWXBKM@matsya \
--to=vkoul@kernel.org \
--cc=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=robh+dt@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 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).