From: <fixed-term.Oleksij.Rempel@de.bosch.com>
To: <linux-kernel@vger.kernel.org>, <linux-soc@vger.kernel.org>,
<dirk.behme@de.bosch.com>, <mkl@pengutronix.de>
Cc: Oleksij Rempel <linux@rempel-privat.de>
Subject: [RFC 0/3] add Inter Chip Communication framework
Date: Wed, 9 Nov 2016 07:04:18 +0100 [thread overview]
Message-ID: <1478671461-25135-1-git-send-email-fixed-term.Oleksij.Rempel@de.bosch.com> (raw)
From: Oleksij Rempel <linux@rempel-privat.de>
Hallo all,
i'm working on upstreamable version of ICC (Inter Chip Communication)
framework. It is used to provide kernel level abstraction for functionality
located in neighbor SoC or MCU.
The idea is not really different from existing driver/hsi, but currently it
seems to be painful to rework it to fit our needs.
The structure of ICC is fallowing:
- transport level: currently only SSI32 (based on SPI) is provided.
I can imagine that HSI (drivers/hsi) and HTC (ath9k-htc) can be placed
here too.
- icc bus: provides an upstraction level for icc clients
- icc clients. Drivers for: char device, watchdog, rtc, CAN, gpio.
Current patchset I a request for comments, before I'll start to bug you will
patch reviews und PRs.
Please let me know if i'm going to right or wrong direction.
Oleksij Rempel (3):
icc: add add SSI32 transport driver
watchdog: add icc watchdog driver
char: add icc_char device
drivers/Kconfig | 2 +
drivers/Makefile | 1 +
drivers/char/Kconfig | 9 ++
drivers/char/Makefile | 1 +
drivers/char/icc_char.c | 280 +++++++++++++++++++++++++++++++++++
drivers/icc/Kconfig | 13 ++
drivers/icc/Makefile | 5 +
drivers/icc/icc_bus.c | 204 ++++++++++++++++++++++++++
drivers/icc/ssi32/Kconfig | 12 ++
drivers/icc/ssi32/Makefile | 6 +
drivers/icc/ssi32/ssi32_prot.c | 256 ++++++++++++++++++++++++++++++++
drivers/icc/ssi32/ssi32_prot.h | 94 ++++++++++++
drivers/icc/ssi32/ssi32_spi_hif.c | 300 ++++++++++++++++++++++++++++++++++++++
drivers/icc/ssi32/ssi32_spi_hif.h | 40 +++++
drivers/watchdog/Kconfig | 8 +
drivers/watchdog/Makefile | 1 +
drivers/watchdog/icc_wdt.c | 185 +++++++++++++++++++++++
include/linux/icc/icc.h | 88 +++++++++++
include/linux/icc/ssi32.h | 32 ++++
19 files changed, 1537 insertions(+)
create mode 100644 drivers/char/icc_char.c
create mode 100644 drivers/icc/Kconfig
create mode 100644 drivers/icc/Makefile
create mode 100644 drivers/icc/icc_bus.c
create mode 100644 drivers/icc/ssi32/Kconfig
create mode 100644 drivers/icc/ssi32/Makefile
create mode 100644 drivers/icc/ssi32/ssi32_prot.c
create mode 100644 drivers/icc/ssi32/ssi32_prot.h
create mode 100644 drivers/icc/ssi32/ssi32_spi_hif.c
create mode 100644 drivers/icc/ssi32/ssi32_spi_hif.h
create mode 100644 drivers/watchdog/icc_wdt.c
create mode 100644 include/linux/icc/icc.h
create mode 100644 include/linux/icc/ssi32.h
--
1.9.1
next reply other threads:[~2016-11-09 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 6:04 fixed-term.Oleksij.Rempel [this message]
2016-11-09 6:04 ` [RFC 1/3] icc: add add SSI32 transport driver fixed-term.Oleksij.Rempel
2016-11-09 6:04 ` [RFC 2/3] watchdog: add icc watchdog driver fixed-term.Oleksij.Rempel
2016-11-09 6:04 ` [RFC 3/3] char: add icc_char device fixed-term.Oleksij.Rempel
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=1478671461-25135-1-git-send-email-fixed-term.Oleksij.Rempel@de.bosch.com \
--to=fixed-term.oleksij.rempel@de.bosch.com \
--cc=dirk.behme@de.bosch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=mkl@pengutronix.de \
/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).