From: Oleksij Rempel <o.rempel@pengutronix.de>
To: mkl@pengutronix.de, Wolfgang Grandegger <wg@grandegger.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Rob Herring <robh+dt@kernel.org>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
kernel@pengutronix.de, linux-can@vger.kernel.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Joakim Zhang <qiangqing.zhang@nxp.com>
Subject: [PATCH v3 0/2] convert flexcan to the yaml
Date: Thu, 22 Oct 2020 09:52:16 +0200 [thread overview]
Message-ID: <20201022075218.11880-1-o.rempel@pengutronix.de> (raw)
changes v3:
- can-controller.yaml: add "additionalProperties: true"
- fsl,flexcan.yaml: remove maxItems and not needed type definition
changes v2:
- add can-controller.yaml for common patterns
- use phandle-array instead of uint32-array
- Drop the outer 'items' in fsl,stop-mode
- use can@ instead of flexcan@
Oleksij Rempel (2):
dt-bindings: can: add can-controller.yaml
dt-bindings: can: flexcan: convert fsl,*flexcan bindings to yaml
.../bindings/net/can/can-controller.yaml | 18 +++
.../bindings/net/can/fsl,flexcan.yaml | 135 ++++++++++++++++++
.../bindings/net/can/fsl-flexcan.txt | 57 --------
3 files changed, 153 insertions(+), 57 deletions(-)
create mode 100644 Documentation/devicetree/bindings/net/can/can-controller.yaml
create mode 100644 Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml
delete mode 100644 Documentation/devicetree/bindings/net/can/fsl-flexcan.txt
--
2.28.0
next reply other threads:[~2020-10-22 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 7:52 Oleksij Rempel [this message]
2020-10-22 7:52 ` [PATCH v3 1/2] dt-bindings: can: add can-controller.yaml Oleksij Rempel
2020-10-30 15:34 ` Rob Herring
2020-10-22 7:52 ` [PATCH v3 2/2] dt-bindings: can: flexcan: convert fsl,*flexcan bindings to yaml Oleksij Rempel
2020-10-30 15:35 ` Rob Herring
2020-11-10 15:43 ` Rob Herring
2020-11-11 13:23 ` Marc Kleine-Budde
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=20201022075218.11880-1-o.rempel@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=qiangqing.zhang@nxp.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).