From: Franklin S Cooper Jr <fcooper@ti.com>
To: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<netdev@vger.kernel.org>, <linux-can@vger.kernel.org>,
<wg@grandegger.com>, <mkl@pengutronix.de>, <robh+dt@kernel.org>,
<quentin.schulz@free-electrons.com>,
<dev.kurt@vandijck-laurijssen.be>, <andrew@lunn.ch>,
<sergei.shtylyov@cogentembedded.com>, <socketcan@hartkopp.net>
Cc: Franklin S Cooper Jr <fcooper@ti.com>
Subject: [PATCH v5 4/4] can: m_can: Add call to of_can_transceiver
Date: Fri, 18 Aug 2017 15:21:37 -0500 [thread overview]
Message-ID: <20170818202137.29816-5-fcooper@ti.com> (raw)
In-Reply-To: <20170818202137.29816-1-fcooper@ti.com>
Add call to new generic functions that provides support via a binding
to limit the arbitration rate and/or data rate imposed by the physical
transceiver connected to the MCAN peripheral.
Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
---
drivers/net/can/m_can/m_can.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/can/m_can/m_can.c b/drivers/net/can/m_can/m_can.c
index f4947a7..f72116e 100644
--- a/drivers/net/can/m_can/m_can.c
+++ b/drivers/net/can/m_can/m_can.c
@@ -1649,6 +1649,8 @@ static int m_can_plat_probe(struct platform_device *pdev)
devm_can_led_init(dev);
+ of_can_transceiver(dev);
+
dev_info(&pdev->dev, "%s device registered (irq=%d, version=%d)\n",
KBUILD_MODNAME, dev->irq, priv->version);
--
2.9.4.dirty
prev parent reply other threads:[~2017-08-18 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 20:21 [PATCH v5 0/4] can: Support transceiver based bit rate limit Franklin S Cooper Jr
2017-08-18 20:21 ` [PATCH v5 1/4] can: dev: Add support for limiting configured bitrate Franklin S Cooper Jr
[not found] ` <20170818202137.29816-1-fcooper-l0cyMroinI0@public.gmane.org>
2017-08-18 20:21 ` [PATCH v5 2/4] dt-bindings: can: can-transceiver: Document new binding Franklin S Cooper Jr
2017-08-18 20:21 ` [PATCH v5 3/4] dt-bindings: can: m_can: Document new can transceiver binding Franklin S Cooper Jr
2017-08-18 20:21 ` Franklin S Cooper Jr [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=20170818202137.29816-5-fcooper@ti.com \
--to=fcooper@ti.com \
--cc=andrew@lunn.ch \
--cc=dev.kurt@vandijck-laurijssen.be \
--cc=devicetree@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=quentin.schulz@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=socketcan@hartkopp.net \
--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