From: yegorslists@googlemail.com
To: linux-can@vger.kernel.org
Cc: linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, tony@atomide.com, mkl@pengutronix.de,
andrej.skvortzov@gmail.com,
Yegor Yefremov <yegorslists@googlemail.com>
Subject: [PATCH v5 0/3] Adding DT support for TI HECC module
Date: Fri, 17 Feb 2017 16:52:30 +0100 [thread overview]
Message-ID: <1487346753-19286-1-git-send-email-yegorslists@googlemail.com> (raw)
From: Yegor Yefremov <yegorslists@googlemail.com>
This is an attempt to revive DT support for TI HECC that was started in 2015 [1].
Changes v4 -> v5:
- remove unneeded manual deallocations as we now use devm_ routines
(suggested by Marc Kleine-Budde)
Changes v3 -> v4:
- implement tranciever handling via regulator API (suggested by Marc Kleine-Budde)
- convert the driver to DT only driver, i.e. remove legacy platform struct and header
(suggested by Marc Kleine-Budde)
Changes v2 -> v3:
- rename compatible property to "ti,am3517-hecc" (though there is a stipped
device named 3505, EMAC driver already uses am3517-emac name, so keep this
property consistent)
- use reg-names to specify different HECC I/O mapping (suggested by Tony Lindgren)
- provide fallback offsets and sizes for board files
- convert optional property ti,int_line to ti,use-hecc1int and add proper
description
Changes v1 -> v2:
- change compatible to "ti,am3505
- remove CONFIG_OF
- don't set int_line to 0 explicitly
[1] http://comments.gmane.org/gmane.linux.can/8616
Yegor Yefremov (3):
ARM: dts: AM35x: Add hecc node
can: ti_hecc: Add TI HECC DT binding documentation
can: ti_hecc: Add DT support for TI HECC module
.../devicetree/bindings/net/can/ti_hecc.txt | 33 ++++
arch/arm/boot/dts/am3517.dtsi | 12 ++
drivers/net/can/ti_hecc.c | 170 +++++++++++----------
include/linux/can/platform/ti_hecc.h | 44 ------
4 files changed, 133 insertions(+), 126 deletions(-)
create mode 100644 Documentation/devicetree/bindings/net/can/ti_hecc.txt
delete mode 100644 include/linux/can/platform/ti_hecc.h
--
2.1.4
next reply other threads:[~2017-02-17 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 15:52 yegorslists [this message]
[not found] ` <1487346753-19286-1-git-send-email-yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-02-17 15:52 ` [PATCH v5 1/3] ARM: dts: AM35x: Add hecc node yegorslists-gM/Ye1E23mwN+BqQ9rBEUg
2017-03-06 16:23 ` Tony Lindgren
2017-02-17 16:04 ` [PATCH v5 0/3] Adding DT support for TI HECC module Marc Kleine-Budde
2017-02-17 15:52 ` [PATCH v5 2/3] can: ti_hecc: Add TI HECC DT binding documentation yegorslists
[not found] ` <1487346753-19286-3-git-send-email-yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-02-27 16:44 ` Rob Herring
2017-02-28 8:04 ` Marc Kleine-Budde
2017-02-17 15:52 ` [PATCH v5 3/3] can: ti_hecc: Add DT support for TI HECC module yegorslists
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=1487346753-19286-1-git-send-email-yegorslists@googlemail.com \
--to=yegorslists@googlemail.com \
--cc=andrej.skvortzov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=robh@kernel.org \
--cc=tony@atomide.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).