From: Benjamin Gaignard <benjamin.gaignard@st.com>
To: <wg@grandegger.com>, <mkl@pengutronix.de>, <davem@davemloft.net>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>,
<sriram.dash@samsung.com>
Cc: <linux-can@vger.kernel.org>, <netdev@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: [PATCH v3 0/2] Convert bosch,m_can to json-schema
Date: Fri, 7 Feb 2020 10:51:11 +0100 [thread overview]
Message-ID: <20200207095113.14489-1-benjamin.gaignard@st.com> (raw)
The goal of this series is to convert bosch,m_can bindings to json-schema.
First convert can-transceiver to yaml and then use it for bosch,m_can.yaml.
version 3:
- only declare max-bitrate property in can-transceiver.yaml
- move can-transceive node into bosch,m_can.yaml bindings
Benjamin Gaignard (2):
dt-bindinsg: net: can: Convert can-transceiver to json-schema
dt-bindings: net: can: Convert M_CAN to json-schema
.../devicetree/bindings/net/can/bosch,m_can.yaml | 147 +++++++++++++++++++++
.../bindings/net/can/can-transceiver.txt | 24 ----
.../bindings/net/can/can-transceiver.yaml | 18 +++
.../devicetree/bindings/net/can/m_can.txt | 75 -----------
4 files changed, 165 insertions(+), 99 deletions(-)
create mode 100644 Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
delete mode 100644 Documentation/devicetree/bindings/net/can/can-transceiver.txt
create mode 100644 Documentation/devicetree/bindings/net/can/can-transceiver.yaml
delete mode 100644 Documentation/devicetree/bindings/net/can/m_can.txt
--
2.15.0
next reply other threads:[~2020-02-07 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 9:51 Benjamin Gaignard [this message]
2020-02-07 9:51 ` [PATCH v3 1/2] dt-bindinsg: net: can: Convert can-transceiver to json-schema Benjamin Gaignard
2020-02-07 9:51 ` [PATCH v3 2/2] dt-bindings: net: can: Convert M_CAN " Benjamin Gaignard
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=20200207095113.14489-1-benjamin.gaignard@st.com \
--to=benjamin.gaignard@st.com \
--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=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sriram.dash@samsung.com \
--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).