From: Dongjiu Geng <gengdongjiu@huawei.com>
To: <mturquette@baylibre.com>, <sboyd@kernel.org>,
<robh+dt@kernel.org>, <vkoul@kernel.org>,
<dan.j.williams@intel.com>, <p.zabel@pengutronix.de>,
<devicetree@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <dmaengine@vger.kernel.org>
Subject: Re: [PATCH v5 0/4] Enable Hi3559A SOC clock and HiSilicon Hiedma Controller
Date: Sat, 28 Nov 2020 12:07:51 +0800 [thread overview]
Message-ID: <bac15a2e-b9db-b7b0-6004-ad76fa8c5be5@huawei.com> (raw)
In-Reply-To: <20201119200129.28532-1-gengdongjiu@huawei.com>
ping, sorry for the noise.
On 2020/11/20 4:01, Dongjiu Geng wrote:
> v4->v5:
> 1. change the patch author mail name
>
> v3->v4:
> 1. fix the 'make dt_binding_check' issues.
> 2. Combine the 'Enable HiSilicon Hiedma Controller' series patches to this series.
> 3. fix the 'make dt_binding_check' issues in 'Enable HiSilicon Hiedma Controller' patchset
>
>
> v2->v3:
> 1. change dt-bindings documents from txt to yaml format.
> 2. Add SHUB clock to access the devices of m7
>
> Dongjiu Geng (4):
> dt-bindings: Document the hi3559a clock bindings
> clk: hisilicon: Add clock driver for hi3559A SoC
> dt: bindings: dma: Add DT bindings for HiSilicon Hiedma Controller
> dmaengine: dma: Add Hiedma Controller v310 Device Driver
>
> .../clock/hisilicon,hi3559av100-clock.yaml | 66 +
> .../bindings/dma/hisilicon,hiedmacv310.yaml | 103 ++
> drivers/clk/hisilicon/Kconfig | 7 +
> drivers/clk/hisilicon/Makefile | 1 +
> drivers/clk/hisilicon/clk-hi3559a.c | 865 ++++++++++
> drivers/dma/Kconfig | 14 +
> drivers/dma/Makefile | 1 +
> drivers/dma/hiedmacv310.c | 1441 +++++++++++++++++
> drivers/dma/hiedmacv310.h | 136 ++
> include/dt-bindings/clock/hi3559av100-clock.h | 165 ++
> 10 files changed, 2799 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/hisilicon,hi3559av100-clock.yaml
> create mode 100644 Documentation/devicetree/bindings/dma/hisilicon,hiedmacv310.yaml
> create mode 100644 drivers/clk/hisilicon/clk-hi3559a.c
> create mode 100644 drivers/dma/hiedmacv310.c
> create mode 100644 drivers/dma/hiedmacv310.h
> create mode 100644 include/dt-bindings/clock/hi3559av100-clock.h
>
prev parent reply other threads:[~2020-11-28 4:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 20:01 [PATCH v5 0/4] Enable Hi3559A SOC clock and HiSilicon Hiedma Controller Dongjiu Geng
2020-11-19 20:01 ` [PATCH v5 1/4] dt-bindings: Document the hi3559a clock bindings Dongjiu Geng
2020-11-30 22:07 ` Rob Herring
2020-12-07 12:13 ` Dongjiu Geng
2020-11-19 20:01 ` [PATCH v5 2/4] clk: hisilicon: Add clock driver for hi3559A SoC Dongjiu Geng
2020-11-19 20:01 ` [PATCH v5 3/4] dt: bindings: dma: Add DT bindings for HiSilicon Hiedma Controller Dongjiu Geng
2020-11-30 22:11 ` Rob Herring
2020-11-19 20:01 ` [PATCH v5 4/4] dmaengine: dma: Add Hiedma Controller v310 Device Driver Dongjiu Geng
2020-11-28 4:07 ` Dongjiu Geng [this message]
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=bac15a2e-b9db-b7b0-6004-ad76fa8c5be5@huawei.com \
--to=gengdongjiu@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=vkoul@kernel.org \
/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).