[PATCH v3 0/3] mailbox: hisilicon: add Hi6220 mailbox driver

From: Leo Yan
Date: Tue Sep 15 2015 - 10:38:23 EST


Hi6220 mailbox supports up to 32 channels. Each channel is unidirectional
with a maximum message size of 8 words. I/O is performed using register
access (there is no DMA) and the cell raises an interrupt when messages
are received.

This patch series is to implement Hi6220 mailbox driver. It registers
two channels into framework for communication with MCU, one is tx channel
and another is rx channel. Now mailbox driver is used to send message to
MCU to control dynamic voltage and frequency scaling for CPU, GPU and DDR.

Changes from v2:
* Get rid of unused memory regions from memory node in DT, and don't use
reserved-memory node according to Mark and Leif's suggestion; Haojian also
has updated UEFI for efi memory info

Changes from v1:
* Correct lock usage for SMP scenario

Changes from RFC:
* According to Jassi's review, totally remove the abstract common driver
layer and only commit driver dedicated for Hi6220
* According to Paul Bolle's review, fix typo issue for Kconfig and remove
unnecessary dependency with OF and fix minor for mailbox driver
* Refine a little for dts nodes


Leo Yan (3):
dt-bindings: mailbox: Document Hi6220 mailbox driver
mailbox: Hi6220: add mailbox driver
arm64: dts: add Hi6220 mailbox node

.../bindings/mailbox/hisilicon,hi6220-mailbox.txt | 57 +++
arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 16 +-
arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 8 +
drivers/mailbox/Kconfig | 8 +
drivers/mailbox/Makefile | 2 +
drivers/mailbox/hi6220-mailbox.c | 519 +++++++++++++++++++++
6 files changed, 606 insertions(+), 4 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mailbox/hisilicon,hi6220-mailbox.txt
create mode 100644 drivers/mailbox/hi6220-mailbox.c

--
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/