From: khilman@kernel•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v8 6/7] clk: hi6220: Clock driver support for Hisilicon hi6220 SoC
Date: Thu, 28 May 2015 10:32:05 -0700 [thread overview]
Message-ID: <7h4mmwip62.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5566CF13.8060806@huawei.com> (Bintian's message of "Thu, 28 May 2015 16:17:23 +0800")
Bintian <bintian.wang@huawei•com> writes:
> Hello Mike,
>
> On 2015/5/28 13:26, Michael Turquette wrote:
>> Quoting Bintian Wang (2015-05-23 21:11:11)
>>> Add clock drivers for hi6220 SoC, this driver controls the SoC
>>> registers to supply different clocks to different IPs in the SoC.
>>>
>>> We add one divider clock for hi6220 because the divider in hi6220
>>> also has a mask bit but it doesnot obey the rule defined by flag
>>> "CLK_DIVIDER_HIWORD_MASK", we can not get index of the mask bit by
>>> left shift fixed bits (e.g. 16 bits), so we add this divider clock
>>> to handle it.
>>>
>>> Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro•org>
>>> Signed-off-by: Bintian Wang <bintian.wang@huawei•com>
>>> Acked-by: Haojian Zhuang <haojian.zhuang@linaro•org>
>>> Reviewed-by: Zhangfei Gao <zhangfei.gao@linaro•org>
>>> Tested-by: Will Deacon <will.deacon@arm•com>
>>> Tested-by: Tyler Baker <tyler.baker@linaro•org>
>>
>> Hi Bintian,
>>
>> Thanks for making the changes requested by Stephen. I've taken his patch
>> to add assigned-clock-rate/parent support for AMBA interconnects and
>> applied it to 4.1-rc1, and then I've applied your v8 patches #4-6 on top
>> of that. You can find it at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next-hi6220
> Thank you very much!
>
> I think you also need to pick patch "[PATCH v5 3/6] clk: hi6220:
> Document devicetree bindings for hi6220 clock", which described the
> dt binding of clk, and it is also acked by Stephen(v4 is the same to
> v5).
>
>> I have merged this into clk-next so it can get some cycles in
>> linux-next.
>>
>> Stephen,
>>
>> Can you send your patch out to Russell properly? It needs his ack (or
>> for him to take it outright) in order to unblock the hi6220 clock driver
>> from being merged.
> It doesn't block hi6220 clock driver now, because the UART1 is not
> enabled in hi6220 dts now.
Now that the clk changes are queued up, can you (re)post the remaining
hikey patches with a changelog stating the dependency on the clk-next
branch. I believe what's left is just the DT and Kconfig/defconfig
changes, correct?
With some acks from the DT maintainers, these should be ready to be
merged through arm-soc.
Thanks,
Kevin
next prev parent reply other threads:[~2015-05-28 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 4:11 [PATCH v8 4/7] clk: hisilicon: Remove __init for marking function prototypes Bintian Wang
2015-05-24 4:11 ` [PATCH v8 5/7] dt-bindings: Add header file of hi6220 clock driver Bintian Wang
2015-05-24 4:11 ` [PATCH v8 6/7] clk: hi6220: Clock driver support for Hisilicon hi6220 SoC Bintian Wang
2015-05-28 5:26 ` Michael Turquette
2015-05-28 8:17 ` Bintian
2015-05-28 17:32 ` Kevin Hilman [this message]
2015-05-29 0:58 ` Bintian
2015-05-29 1:07 ` Michael Turquette
2015-05-29 2:34 ` Bintian
2015-05-28 16:50 ` [PATCH v8 4/7] clk: hisilicon: Remove __init for marking function prototypes Kevin Hilman
2015-05-29 2:07 ` Bintian
-- strict thread matches above, loose matches on Subject: below --
2015-05-29 2:08 [PATCH v8 0/7] arm64,hi6220: Enable Hisilicon Hi6220 SoC Bintian Wang
2015-05-29 2:08 ` [PATCH v8 6/7] clk: hi6220: Clock driver support for Hisilicon hi6220 SoC Bintian Wang
2015-06-03 22:39 ` Michael Turquette
2015-06-04 0:46 ` 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=7h4mmwip62.fsf@deeprootsystems.com \
--to=khilman@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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