From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755502AbaIDXHM (ORCPT ); Thu, 4 Sep 2014 19:07:12 -0400 Received: from cpsmtpb-ews09.kpnxchange.com ([213.75.39.14]:62609 "EHLO cpsmtpb-ews09.kpnxchange.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751133AbaIDXHK (ORCPT ); Thu, 4 Sep 2014 19:07:10 -0400 Message-ID: <1409872027.5546.132.camel@x220> Subject: Re: clk: hisilicon: ARCH_HIP04 and ARCH_HIX5HD2? From: Paul Bolle To: Haojian Zhuang Cc: Mike Turquette , Zhangfei Gao , Haifeng Yan , "linux-kernel@vger.kernel.org" Date: Fri, 05 Sep 2014 01:07:08 +0200 In-Reply-To: References: <1403167807.23136.31.camel@x220> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-3.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 Sep 2014 23:07:08.0757 (UTC) FILETIME=[F3C5B850:01CFC894] X-RcptDomain: vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2014-06-19 at 17:00 +0800, Haojian Zhuang wrote: > On 19 June 2014 16:50, Paul Bolle 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