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 v3 0/4] can: Support transceiver based bit rate limit
Date: Wed, 2 Aug 2017 19:51:46 -0500 [thread overview]
Message-ID: <20170803005150.9286-1-fcooper@ti.com> (raw)
Add a new generic binding that CAN drivers can be used to specify the max
bit rate supported by a transceiver. This is useful since in some instances
since the maximum speeds may be limited by the transceiver used. However,
transceivers may not provide a means to determine this limitation at
runtime. Therefore, create a new binding that mimics "fixed-link" that
allows a user to hardcode the max speeds that can be used.
Also add support for this new binding in the MCAN driver.
Note this is an optional subnode so even if a driver adds support for
parsing fixed-transceiver the user does not have to define it in their
device tree.
Version 3 changes:
Switch from having two "max bitrates" to one universal bitrate.
Version 2 changes:
Rename function
Define proper variable default
Drop unit address
Move check to changelink function
Reword commit message
Reword documentation
Franklin S Cooper Jr (4):
can: dev: Add support for limiting configured bitrate
dt-bindings: can: fixed-transceiver: Add new CAN fixed transceiver
bindings
dt-bindings: can: m_can: Include reference to new fixed transceiver
binding
can: m_can: Add call to of_can_transceiver_fixed
.../bindings/net/can/fixed-transceiver.txt | 24 +++++++++++
.../devicetree/bindings/net/can/m_can.txt | 9 ++++
drivers/net/can/dev.c | 50 ++++++++++++++++++++++
drivers/net/can/m_can/m_can.c | 2 +
include/linux/can/dev.h | 5 +++
5 files changed, 90 insertions(+)
create mode 100644 Documentation/devicetree/bindings/net/can/fixed-transceiver.txt
--
2.9.4.dirty
next reply other threads:[~2017-08-03 0:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 0:51 Franklin S Cooper Jr [this message]
2017-08-03 0:51 ` [PATCH v3 1/4] can: dev: Add support for limiting configured bitrate Franklin S Cooper Jr
2017-08-03 0:51 ` [PATCH v3 2/4] dt-bindings: can: fixed-transceiver: Add new CAN fixed transceiver bindings Franklin S Cooper Jr
2017-08-03 9:18 ` Sergei Shtylyov
2017-08-03 9:48 ` Franklin S Cooper Jr
2017-08-03 12:22 ` Sergei Shtylyov
2017-08-03 15:38 ` Franklin S Cooper Jr
2017-08-10 1:00 ` Franklin S Cooper Jr
2017-08-03 0:51 ` [PATCH v3 3/4] dt-bindings: can: m_can: Include reference to new fixed transceiver binding Franklin S Cooper Jr
2017-08-03 9:20 ` Sergei Shtylyov
2017-08-03 9:54 ` Franklin S Cooper Jr
2017-08-03 0:51 ` [PATCH v3 4/4] can: m_can: Add call to of_can_transceiver_fixed Franklin S Cooper Jr
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=20170803005150.9286-1-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;
as well as URLs for NNTP newsgroup(s).