From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752644AbcGLIZs (ORCPT ); Tue, 12 Jul 2016 04:25:48 -0400 Received: from mout.kundenserver.de ([212.227.17.10]:49950 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750949AbcGLIZq convert rfc822-to-8bit (ORCPT ); Tue, 12 Jul 2016 04:25:46 -0400 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Wan Zongshun , Daniel Lezcano , devicetree@vger.kernel.org, jason@lakedaemon.net, Wan Zongshun , linux-kernel@vger.kernel.org, Russell King , p.zabel@pengutronix.de, Thomas Gleixner , linux-clk@vger.kernel.org Subject: Re: [PATCH v2 03/10] Clocksource: add nuc970 clocksource driver Date: Tue, 12 Jul 2016 10:28:35 +0200 Message-ID: <26830152.1oBSpuVOM0@wuerfel> User-Agent: KMail/5.1.3 (Linux/4.4.0-22-generic; KDE/5.18.0; x86_64; ; ) In-Reply-To: <57849D2B.60305@iommu.org> References: <1468135649-19980-1-git-send-email-vw@iommu.org> <3277576.eNgdG7zPqq@wuerfel> <57849D2B.60305@iommu.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="UTF-8" X-Provags-ID: V03:K0:KdZLF3r03ZcwooX4E90cfQFdE2DnMf4Y3DQh15HODw4AoOh04bo uRh4pZDB/AGURLC7Gzv2DfSp4D8fZrXAmJ7pyhC78voQC5cP8NJ2dNgx2ssKx/5Bh7HCsnz R9gvLU/a8vMaD0Tu/TSIIuAQoqQ6nOGvX/cRzaOSOKEb1S9aOC2uzKr4az5DoZqAd5jb+pS pGkLMj3HMU7s8mCByuFCw== X-UI-Out-Filterresults: notjunk:1;V01:K0:YAF9gNphB/s=:xBBacKO6xAMgaIjmQxjvHe vV4PShNbVBPjOhR8u0jckmS4wYwoXceJ7MMj3J7Ir8NcxTqs9YMHMn/ViWSvkVzS3adOAe4xQ ccff9x4NY0lPEdBiaYUBve3WIoYYYtArFHSKNuHj6Z4pB5H0lLEJ6AZKdTbSsoZnYs6u5OLky CcPZcV34Jj7FpsHRs44r0bj8hvDbrSZsQOdcu/M0axTlVjmEOosFHsVzhgYLpmaRsI3BdhU8U UWq3hBfQ8HH4Xho3O1q62pDydDdl0vmD7AiCLefJZ1VlDivAUW4f7tWcsbiG78oQpX68delEa xIoveC2pV/bagiZY0jkLJVjlnXnOLmw34u+OCnG/pMC4eO70tzb4h4+sEMscljlllQbDWJE8n 0ulcfw4xRMUlSFLCW7gJ/utRrouG0Jf/8H6Tx3CdyvXraUCXyaGWMaLdf8+xplljSbCoEeEFn IEH/pJ6xdAkmUtTerrPm7vW558FexarMcycxXs/Iwx/LTuLyZn0QSSATXRKiMIvq9rI/pPxA7 GwLia9ySZuQJB6xj4C54IYknHnK2vT6VTLziMCPqpfBKaLGAUUIfSPOTAqKMzyLJ0TfWj/isf qYkFNrIIalCjfBXvTtocZzZID9l8/rd3N8qJ1CepHKJTeinhTBjdapGyuBxAgM9ohfLNI6FVg j+KaRg/qVYvFIPRVfvxI1CW+XYy5tpDrQkYwYxAyrZ7mS+5lsf5O/ayGZEmWHJciCRxM96UkO MBkZMua2rnE9vcEC Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday, July 12, 2016 3:32:59 PM CEST Wan Zongshun wrote: > > On 2016年07月11日 23:36, Arnd Bergmann wrote: > > On Sunday, July 10, 2016 3:27:23 PM CEST Wan Zongshun wrote: > >> > >> +config NUC900_TIMER > >> + bool "Clocksource timer for nuc900 platform" if COMPILE_TEST > >> + depends on ARM > >> + select CLKSRC_OF if OF > >> + select CLKSRC_MMIO > >> + help > >> + Enables the clocksource for the NUC900 platform. > >> > > > > I have put this patch into my randconfig build system and found that > > it lacks a dependency: > > > > > > > > diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig > > index e18ef32776a3..59b9251eef37 100644 > > --- a/drivers/clocksource/Kconfig > > +++ b/drivers/clocksource/Kconfig > > @@ -523,7 +523,7 @@ config CLKSRC_ST_LPC > > > > config NUC900_TIMER > > bool "Clocksource timer for nuc900 platform" if COMPILE_TEST > > - depends on ARM > > + depends on ARM && GENERIC_CLOCKEVENTS > > select CLKSRC_OF if OF > > select CLKSRC_MMIO > > help > > > > So this patch, I still need submit or you have merged it? Ideally the driver should get submitted through the clocksource maintainer tree. I have not applied it to any git tree that I plan to send anywhere. > > > > Also the init function has changed its return type in linux-next: > > > >> +static void __init nuc970_timer_of_init(struct device_node *node) > > > > This now needs to return an error code or we get: > > > > ../include/linux/of.h:1004:20: error: comparison of distinct pointer types lacks a cast [-Werror] > > .data = (fn == (fn_type)NULL) ? fn : fn } > > > > Daniel Lezcano seems to have implemented a migration strategy, but I > > can't see what you are supposed to do here, since the > > CLOCKSOURCE_OF_DECLARE_RET macro is no longer part of linux-next. > > Wait for Daniel's comments? or what should I do now? Yes, let's see what he says. I guess from the timing, this will probably have to wait for linux-4.9 anyway, and then we have no problem because the API change will make it into 4.8. Arnd