clk: hisilicon: ARCH_HIP04 and ARCH_HIX5HD2?
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.
Paul Bolle
Quoted 10 lines · Paul Bolle
0) Commit
d3e6573c48f4("clk: hip04: add clock driver") was included in v3.15. That clock driver is built only ifCONFIG_ARCH_HIP04is set.And commit
5efaf09021a5("clk: hisi: addclk-hix5hd2.c") was included in v3.16-rc1. And that driver is built only ifCONFIG_ARCH_HIX5HD2is set.1) Neither the symbol
ARCH_HIP04nor the symbolARCH_HIX5HD2is part of v3.16-rc1. These symbols are also not part of next-20140619. I assume that both are pending somewhere. Is that correct?
Quoted 7 lines
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.
Paul Bolle
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.
Regards
Haojian
Quoted 19 lines · Haojian Zhuang
Quoted 6 lines · Paul Bolle
0) Commit
d3e6573c48f4("clk: hip04: add clock driver") was included in v3.15. That clock driver is built only ifCONFIG_ARCH_HIP04is set.And commit
5efaf09021a5("clk: hisi: addclk-hix5hd2.c") was included in v3.16-rc1. And that driver is built only ifCONFIG_ARCH_HIX5HD2is set.Quoted 7 lines
1) Neither the symbol
ARCH_HIP04nor the symbolARCH_HIX5HD2is 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.
Quoted 5 lines
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
Quoted 26 lines · Paul Bolle
Quoted 19 lines · Haojian Zhuang
Quoted 6 lines · Paul Bolle
0) Commit
d3e6573c48f4("clk: hip04: add clock driver") was included in v3.15. That clock driver is built only ifCONFIG_ARCH_HIP04is set.And commit
5efaf09021a5("clk: hisi: addclk-hix5hd2.c") was included in v3.16-rc1. And that driver is built only ifCONFIG_ARCH_HIX5HD2is set.Quoted 7 lines
1) Neither the symbol
ARCH_HIP04nor the symbolARCH_HIX5HD2is 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.
Quoted 5 lines
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.
Quoted 8 lines
ARCH_HIX5HD2landed in v3.17-rc1, so it left my list of minor worries.I assume the code to add
ARCH_HIP04is 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