From: Leo Yan <leo.yan@linaro.org>
To: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
Tyler Baker <tyler.baker@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Sudeep Holla <sudeep.holla@arm.com>,
Bintian Wang <bintian.wang@huawei.com>,
Chen Feng <puck.chen@hisilicon.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Wei Xu <xuwei5@hisilicon.com>
Subject: Re: [PATCH v7 RESEND 0/4] mailbox: hisilicon: add Hi6220 mailbox driver
Date: Mon, 15 Feb 2016 21:54:26 +0800 [thread overview]
Message-ID: <20160215135426.GA10532@leoy-linaro> (raw)
In-Reply-To: <1455544226-10094-1-git-send-email-leo.yan@linaro.org>
On Mon, Feb 15, 2016 at 09:50:22PM +0800, Leo Yan wrote:
> 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 v6:
> * Fix to use lowercase for hexadecimal value in DT binding document
Hi Jassi,
Per your request, I have rebased patches over mailbox-for-next.
Hi Wei,
Could you help merge patch 3/4 for Hi6220's DTS?
Thanks,
Leo Yan
>
> Changes from v5:
> * Refine to use mailbox three specifiers for client driver, so add xlate
> callback function in mailbox driver to support these specifiers
> * Refine document for property "hi6220,mbox-tx-noirq"
>
> Changes from v4:
> * According to Jassi's suggestion, using DT binding to register channels
> * Change to use operating-points-v2 to register operating points
>
> Changes from v3:
> * The patch series for enabling idle state for Hi6220 has reserved memory
> regions, so this series will not include it anymore
> * Refined mailbox driver according to Jassi's suggestion;
> Removed kfifo from mailbox driver;
> Removed spinlock for ipc registers accessing, due every channel has its
> own dedicated bit in ipc register and readl/writel will introduce memory
> barrier, so don't need spinlock to protect ipc registers accessing
> * After mailbox driver is ready, can use patch 4 to enable CPU's OPPs and
> stub clock driver; finally can enable CPUFreq driver for CPU frequency
> scaling
>
> 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 (4):
> dt-bindings: mailbox: Document Hi6220 mailbox driver
> mailbox: Hi6220: add mailbox driver
> arm64: dts: add mailbox node for Hi6220
> arm64: dts: add Hi6220's stub clock node
>
> .../bindings/mailbox/hisilicon,hi6220-mailbox.txt | 74 ++++
> arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 64 ++++
> drivers/mailbox/Kconfig | 8 +
> drivers/mailbox/Makefile | 2 +
> drivers/mailbox/hi6220-mailbox.c | 395 +++++++++++++++++++++
> 5 files changed, 543 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mailbox/hisilicon,hi6220-mailbox.txt
> create mode 100644 drivers/mailbox/hi6220-mailbox.c
>
> --
> 1.9.1
>
next prev parent reply other threads:[~2016-02-15 13:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 13:50 [PATCH v7 RESEND 0/4] mailbox: hisilicon: add Hi6220 mailbox driver Leo Yan
2016-02-15 13:50 ` [PATCH v7 RESEND 1/4] dt-bindings: mailbox: Document " Leo Yan
2016-02-15 13:50 ` [PATCH v7 RESEND 2/4] mailbox: Hi6220: add " Leo Yan
2016-02-15 13:50 ` [PATCH v7 RESEND 3/4] arm64: dts: add mailbox node for Hi6220 Leo Yan
2016-02-15 13:50 ` [PATCH v7 RESEND 4/4] arm64: dts: add Hi6220's stub clock node Leo Yan
2016-02-15 13:54 ` Leo Yan [this message]
[not found] ` <1455544226-10094-1-git-send-email-leo.yan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-02-26 11:40 ` [PATCH v7 RESEND 0/4] mailbox: hisilicon: add Hi6220 mailbox driver Jassi Brar
[not found] ` <CABb+yY0_OzKmftb0HQKyfuE+2jgOfoRLHp-ok=Ux36sK8na6Ag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-27 7:53 ` Wei Xu
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=20160215135426.GA10532@leoy-linaro \
--to=leo.yan@linaro.org \
--cc=arnd@arndb.de \
--cc=bintian.wang@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=puck.chen@hisilicon.com \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tyler.baker@linaro.org \
--cc=will.deacon@arm.com \
--cc=xuwei5@hisilicon.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).