From: 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>, 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: Re: [PATCH 0/2] CAN: Add support for setting mux Date: Tue, 14 Dec 2021 20:01:50 +0530 [thread overview] Message-ID: <7c3a0ac9-308c-2ef1-b8ae-6aa4e1a10d73@ti.com> (raw) In-Reply-To: <20211202131002.12217-1-a-govindraju@ti.com> Hi All, On 02/12/21 6:40 pm, 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 > > The following series of patches are dependent on, > - https://lkml.org/lkml/2021/12/2/423 > Thank you for the comments. I have posted a respin(v2) for this series after making the fixes. Thanks, Aswath > 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 | 13 +++++++++++ > drivers/phy/Kconfig | 1 + > drivers/phy/phy-can-transceiver.c | 22 +++++++++++++++++++ > 3 files changed, 36 insertions(+) > -- linux-phy mailing list linux-phy@lists.infradead.org https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: Aswath Govindraju <a-govindraju@ti.com> To: unlisted-recipients:; (no To-header on input) Cc: Wolfgang Grandegger <wg@grandegger.com>, Marc Kleine-Budde <mkl@pengutronix.de>, Kishon Vijay Abraham I <kishon@ti.com>, 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: Re: [PATCH 0/2] CAN: Add support for setting mux Date: Tue, 14 Dec 2021 20:01:50 +0530 [thread overview] Message-ID: <7c3a0ac9-308c-2ef1-b8ae-6aa4e1a10d73@ti.com> (raw) In-Reply-To: <20211202131002.12217-1-a-govindraju@ti.com> Hi All, On 02/12/21 6:40 pm, 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 > > The following series of patches are dependent on, > - https://lkml.org/lkml/2021/12/2/423 > Thank you for the comments. I have posted a respin(v2) for this series after making the fixes. Thanks, Aswath > 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 | 13 +++++++++++ > drivers/phy/Kconfig | 1 + > drivers/phy/phy-can-transceiver.c | 22 +++++++++++++++++++ > 3 files changed, 36 insertions(+) >
next prev parent reply other threads:[~2021-12-14 14:32 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-02 13:10 [PATCH 0/2] CAN: Add support for setting mux Aswath Govindraju 2021-12-02 13:10 ` Aswath Govindraju 2021-12-02 13:10 ` [PATCH 1/2] dt-bindings: phy: ti,tcan104x-can: Document mux-states property Aswath Govindraju 2021-12-02 13:10 ` [PATCH 1/2] dt-bindings: phy: ti, tcan104x-can: " Aswath Govindraju 2021-12-13 20:19 ` [PATCH 1/2] dt-bindings: phy: ti,tcan104x-can: " Rob Herring 2021-12-13 20:19 ` Rob Herring 2021-12-14 3:46 ` Aswath Govindraju 2021-12-14 3:46 ` Aswath Govindraju 2021-12-02 13:10 ` [PATCH 2/2] phy: phy-can-transceiver: Add support for setting mux Aswath Govindraju 2021-12-02 13:10 ` Aswath Govindraju 2021-12-14 7:32 ` Vinod Koul 2021-12-14 7:32 ` Vinod Koul 2021-12-14 14:31 ` Aswath Govindraju [this message] 2021-12-14 14:31 ` [PATCH 0/2] CAN: " 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=7c3a0ac9-308c-2ef1-b8ae-6aa4e1a10d73@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=robh+dt@kernel.org \ --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: linkBe 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.