Re: clk: hisilicon: ARCH_HIP04 and ARCH_HIX5HD2?

[Haojian Zhuang]

On 5 September 2014 07:07, Paul Bolle <pebolle@xxxxxxxxxx> wrote:
> On Thu, 2014-06-19 at 17:00 +0800, Haojian Zhuang wrote:
>> On 19 June 2014 16:50, Paul Bolle <pebolle@xxxxxxxxxx> wrote:
>> > 0) Commit d3e6573c48f4 ("clk: hip04: add clock driver") was included in
>> > v3.15. That clock driver is built only if CONFIG_ARCH_HIP04 is set.
>> >
>> > And commit 5efaf09021a5 ("clk: hisi: add clk-hix5hd2.c") was included in
>> > v3.16-rc1. And that driver is built only if CONFIG_ARCH_HIX5HD2 is set.
>> >
>> > 1) Neither the symbol ARCH_HIP04 nor the symbol ARCH_HIX5HD2 is part of
>> > v3.16-rc1. These symbols are also not part of next-20140619. I assume
>> > that both are pending somewhere. Is that correct?
>> >
>> > 2) It would probably be nice if these drivers got some (automatic) build
>> > coverage until those symbols enter the tree. I don't know how that could
>> > be achieved.
>>
>> Because clock driver is the first component should be merged into
>> kernel tree. Otherwise, SoC couldn't be compiled at all since SoC &
>> clock are in two different git tree.
>>
>> I also hope that SoC patches could be merged as soon as possible. But
>> we also need to follow up the comments on SoC patches from mailing
>> list. I can't not say when those SoC patches could be merged into
>> mainline since I'm not the gate keeper. I could only say that we're
>> making effort on this.
>
> ARCH_HIX5HD2 landed in v3.17-rc1, so it left my list of minor worries.
>
> I assume the code to add ARCH_HIP04 is still being worked on. Is that
> correct?
>
>
> Paul Bolle
>

Sorry for late response since I was in trip. Yes, you're right.
ARCH_HIP04 is still working on.

Best Regards
Haojian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/