From: Dongjiu Geng <gengdongjiu@huawei.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: <mturquette@baylibre.com>, <sboyd@kernel.org>,
<robh+dt@kernel.org>, <dan.j.williams@intel.com>,
<p.zabel@pengutronix.de>, <linux-clk@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<dmaengine@vger.kernel.org>
Subject: Re: [PATCH v7 0/4] Enable Hi3559A SOC clock and HiSilicon Hiedma Controller
Date: Tue, 12 Jan 2021 19:22:45 +0800 [thread overview]
Message-ID: <cd34cdfd-eee5-b217-a151-9ff7290c112f@huawei.com> (raw)
In-Reply-To: <20210112104010.GN2771@vkoul-mobl>
On 2021/1/12 18:40, Vinod Koul wrote:
> On 15-12-20, 11:09, Dongjiu Geng wrote:
>> v6->v7:
>> 1. rename hisi,misc-control to hisi,misc-control to hisilicon,misc-control
>>
>> v5->v6:
>> 1. Drop #size-cells and #address-cell in the hisilicon,hi3559av100-clock.yaml
>> 2. Add discription for #reset-cells in the hisilicon,hi3559av100-clock.yaml
>> 3. Remove #clock-cells in hisilicon,hiedmacv310.yaml
>> 4. Merge property misc_ctrl_base and misc_regmap together for hiedmacv310 driver
>>
>> 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
>
> Is there a reason to have dma and clk drivers in a single series..? I am
> sure I have skipping few versions thinking this is clock driver series..
>
> Unless there is a dependency please split up.. If there is a dependency
> please specify that
Thank you very much for your pointing out. I will split up.
>
>
>>
>> .../clock/hisilicon,hi3559av100-clock.yaml | 59 +
>> .../bindings/dma/hisilicon,hiedmacv310.yaml | 94 ++
>> 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 | 1442 +++++++++++++++++
>> drivers/dma/hiedmacv310.h | 136 ++
>> include/dt-bindings/clock/hi3559av100-clock.h | 165 ++
>> 10 files changed, 2784 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
>>
>> --
>> 2.17.1
>
prev parent reply other threads:[~2021-01-12 11:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 11:09 [PATCH v7 0/4] Enable Hi3559A SOC clock and HiSilicon Hiedma Controller Dongjiu Geng
2020-12-15 11:09 ` [PATCH v7 1/4] dt-bindings: Document the hi3559a clock bindings Dongjiu Geng
2020-12-21 18:54 ` Rob Herring
2021-01-07 4:11 ` Dongjiu Geng
2020-12-15 11:09 ` [PATCH v7 2/4] clk: hisilicon: Add clock driver for hi3559A SoC Dongjiu Geng
2021-01-12 19:48 ` Stephen Boyd
2020-12-15 11:09 ` [PATCH v7 3/4] dt: bindings: dma: Add DT bindings for HiSilicon Hiedma Controller Dongjiu Geng
2020-12-21 18:55 ` Rob Herring
2020-12-15 11:09 ` [PATCH v7 4/4] dmaengine: dma: Add Hiedma Controller v310 Device Driver Dongjiu Geng
2021-01-12 12:06 ` Vinod Koul
2021-01-12 10:40 ` [PATCH v7 0/4] Enable Hi3559A SOC clock and HiSilicon Hiedma Controller Vinod Koul
2021-01-12 11:22 ` 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=cd34cdfd-eee5-b217-a151-9ff7290c112f@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).