From: bintian.wang@huawei.com (Bintian)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 5/6] arm64: dts: Add dts files for Hisilicon Hi6220 SoC
Date: Tue, 9 Jun 2015 10:30:47 +0800 [thread overview]
Message-ID: <55764FD7.2000805@huawei.com> (raw)
In-Reply-To: <557643EB.8000106@huawei.com>
Hello Arnd, Hello Olof, Hello Kevin,
I checked the git log of Linux 4.1-rc7 from Linus, he says Linux 4.1
will have an rc8, so we may have time to review the following two pull
requests from Wei Xu?
[GIT PULL v2]Hisilicon 64-bit SoC changes for 4.2
[GIT PULL]Hisilicon 64-bit soc hi6220 DT changes for 4.2
Thanks for your time.
BR,
Bintian
On 2015/6/9 9:39, Bintian wrote:
> Hello Shawn,
>
> On 2015/6/9 8:55, Shawn Guo wrote:
>> A minor random comment below.
>>
>> On Sat, May 30, 2015 at 09:51:00AM +0800, Bintian Wang wrote:
>>> + ao_ctrl: ao_ctrl {
>>> + compatible = "hisilicon,hi6220-aoctrl", "syscon";
>>> + reg = <0x0 0xf7800000 0x0 0x2000>;
>>> + #clock-cells = <1>;
>>> + };
>>> +
>>> + sys_ctrl: sys_ctrl {
>>> + compatible = "hisilicon,hi6220-sysctrl", "syscon";
>>> + reg = <0x0 0xf7030000 0x0 0x2000>;
>>> + #clock-cells = <1>;
>>> + };
>>> +
>>> + media_ctrl: media_ctrl {
>>> + compatible = "hisilicon,hi6220-mediactrl", "syscon";
>>> + reg = <0x0 0xf4410000 0x0 0x1000>;
>>> + #clock-cells = <1>;
>>> + };
>>> +
>>> + pm_ctrl: pm_ctrl {
>>
>> An unit-address should be coded in the node name, when it has a 'reg'
>> property.
> Thanks for your suggestion, Rob also gives me the same suggestion :)
>
> In fact, I added the reg to node name in the "[GIT PULL]Hisilicon 64-bit
> soc hi6220 DT changes for 4.2", but it seems the pull is too late for
> kernel 4.2, I will prepare it for 4.3.
>
> Thanks,
>
> Bintian
>
>>
>> Shawn
>>
>>> + compatible = "hisilicon,hi6220-pmctrl", "syscon";
>>> + reg = <0x0 0xf7032000 0x0 0x1000>;
>>> + #clock-cells = <1>;
>>> + };
>>
>> .
>>
>
>
> .
>
next prev parent reply other threads:[~2015-06-09 2:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 1:50 [PATCH v9 0/6] arm64,hi6220: Enable Hisilicon Hi6220 SoC Bintian Wang
2015-05-30 1:50 ` [PATCH v9 1/6] arm64: Enable Hisilicon ARMv8 SoC family in Kconfig and defconfig Bintian Wang
2015-06-02 9:03 ` Will Deacon
2015-05-30 1:50 ` [PATCH v9 2/6] arm64: hi6220: Document devicetree bindings for Hisilicon hi6220 SoC Bintian Wang
2015-06-04 4:36 ` Rob Herring
2015-06-04 7:23 ` Bintian
2015-05-30 1:50 ` [PATCH v9 3/6] clk: hi6220: Document devicetree bindings for hi6220 clock Bintian Wang
2015-05-30 1:50 ` [PATCH v9 4/6] Documentation: DT: PL011: hi6220: add compatible string for Hisilicon designed UART Bintian Wang
2015-06-02 8:59 ` Linus Walleij
2015-06-02 9:13 ` Marc Zyngier
2015-06-02 9:43 ` Russell King - ARM Linux
2015-06-08 13:32 ` Linus Walleij
2015-06-02 10:55 ` Bintian
2015-06-02 11:24 ` Russell King - ARM Linux
2015-06-02 11:46 ` Bintian
2015-05-30 1:51 ` [PATCH v9 5/6] arm64: dts: Add dts files for Hisilicon Hi6220 SoC Bintian Wang
2015-06-03 3:10 ` Bintian
2015-06-09 0:55 ` Shawn Guo
2015-06-09 1:39 ` Bintian
2015-06-09 2:30 ` Bintian [this message]
2015-05-30 1:51 ` [PATCH v9 6/6] dt-bindings: Add header file of hi6220 clock driver Bintian Wang
2015-06-02 0:14 ` [PATCH v9 0/6] arm64,hi6220: Enable Hisilicon Hi6220 SoC Kevin Hilman
2015-06-02 3:57 ` Bintian
2015-06-02 9:05 ` Will Deacon
2015-06-02 10:49 ` Bintian
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=55764FD7.2000805@huawei.com \
--to=bintian.wang@huawei.com \
--cc=linux-arm-kernel@lists.infradead.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).