From: pisa@cmp.felk.cvut.cz
To: devicetree@vger.kernel.org, mkl@pengutronix.de,
linux-can@vger.kernel.org
Cc: wg@grandegger.com, davem@davemloft.net, robh+dt@kernel.org,
mark.rutland@arm.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, martin.jerabek01@gmail.com,
ondrej.ille@gmail.com, Pavel Pisa <pisa@cmp.felk.cvut.cz>
Subject: [PATCH v2 0/2] dt-bindings: net: can: binding for CTU CAN FD open-source IP core.
Date: Wed, 27 Feb 2019 18:26:27 +0100 [thread overview]
Message-ID: <cover.1551287365.git.pisa@cmp.felk.cvut.cz> (raw)
From: Pavel Pisa <pisa@cmp.felk.cvut.cz>
The patch update, added separate patch to add Czech Technical University
to the vendors list. Change ctu_can_fd_0 instance string to lowercase
(originally uppercase because build from official abbreviations).
Clarify that clock-names are not used for now but can be used in future.
Pavel Pisa (2):
dt-bindings: vendor-prefix: add prefix for Czech Technical University
in Prague.
dt-bindings: net: can: binding for CTU CAN FD open-source IP core.
The corresponding sources for testing program from user-space
and for Linux kernel driver for platform and PCIe IP core
integrations are available there
https://gitlab.fel.cvut.cz/canbus/ctucanfd_ip_core/tree/master/driver/
.../devicetree/bindings/net/can/ctu,ctucanfd.txt | 108 +++++++++++++++++++++
.../devicetree/bindings/vendor-prefixes.txt | 1 +
2 files changed, 109 insertions(+)
create mode 100644 Documentation/devicetree/bindings/net/can/ctu,ctucanfd.txt
--
2.11.0
next reply other threads:[~2019-02-27 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 17:26 pisa [this message]
2019-02-27 17:26 ` [PATCH v2 1/2] dt-bindings: vendor-prefix: add prefix for Czech Technical University in Prague pisa
2019-03-12 15:51 ` Rob Herring
2019-02-27 17:26 ` [PATCH v2 2/2] dt-bindings: net: can: binding for CTU CAN FD open-source IP core pisa
2019-02-28 10:13 ` Michal Vokáč
2019-03-12 15:54 ` Rob Herring
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=cover.1551287365.git.pisa@cmp.felk.cvut.cz \
--to=pisa@cmp.felk.cvut.cz \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.jerabek01@gmail.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=ondrej.ille@gmail.com \
--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).