Received: by 10.192.165.148 with SMTP id m20csp5017623imm; Tue, 1 May 2018 07:47:05 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqX7pmcoEzUmj+hohCVRPsB6V2sRi5boRH5b+pDKOBSu2tu0Gkyplh35bnYBzdYjxhQxeh/ X-Received: by 2002:a65:50cc:: with SMTP id s12-v6mr13506326pgp.313.1525186025675; Tue, 01 May 2018 07:47:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525186025; cv=none; d=google.com; s=arc-20160816; b=EhR7thIsL8c154arbBC8Brd1YTLBooaJjWe1CQdugBFq8DdbllsqChAVJ5iSTmG4Md cR0buLB1ID+DFIgnl6lwqS5ZwRwyt0tB/s8M1G6DV2zK2GrszmfBhOHowHMe5qDOlxoc zE6hzk072+pT+qceM+TL7LiYOyDyFfYz6WW8WDTaaAEywrne7MUP+FxDv5Ahkfz7AHcZ NJY05rO+Ybaivl1TMWx5kqQrgeFg2MfqRikv2NtGWMj+sKATEE0jTiiOZkh3MCnuWcxA mHN5LdoBX8ybzk3biCovEtNVyKAUWAfGhu2KmcfAmPKw8Cr6GpNwUBMpRkq7C/10dXpT cknQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=GxKw5qa/GAstWbIZhojvWfap2mtprnfD8yV+TlYy15U=; b=eLJcrW4nCHaBJM10YjHanbQS69SB+eAnij2H0Kt8SWNXyMAT2XDTChftNoZ/NNHk3+ RGKyrRIQzSdSHyDqTcAwMKjpXw1zHLi7vFmmKzgOnH+yGTJ6Ocebp9IrlQ4yGwQcBftU cC3bMtpb3xCDWu3EqeUZzSIYhVEr9r6POid3gLIWuRVjc3mH8OI5uvcAMo+cskvT/If5 Vnu4eMR1rv5z3fZkSOwGqmo34lzjKZ+VRTTk7CXaKnkvqshG/sIBsCBSk4cNSLHJEB1H ej2/bx73s3MoIG4Amfs8BEMU7Z/U2mdqALhCatfdAZIu1eXREb6VlbJXS2d6qym/MmnU skMA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=DRnRZvcA; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v7-v6si7892886pgr.443.2018.05.01.07.46.51; Tue, 01 May 2018 07:47:05 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=DRnRZvcA; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755865AbeEAOqb (ORCPT + 99 others); Tue, 1 May 2018 10:46:31 -0400 Received: from fllnx209.ext.ti.com ([198.47.19.16]:13782 "EHLO fllnx209.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754738AbeEAOq3 (ORCPT ); Tue, 1 May 2018 10:46:29 -0400 Received: from dlelxv90.itg.ti.com ([172.17.2.17]) by fllnx209.ext.ti.com (8.15.1/8.15.1) with ESMTP id w41EjOGP006854; Tue, 1 May 2018 09:45:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ti.com; s=ti-com-17Q1; t=1525185924; bh=eeh5a6/m2gRwy7aCOKmKaOrzgi6KpVRky3c39aoj8kQ=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=DRnRZvcAe51UISR4AjrPtp/HYzAcIlXiyjBC94ZNAmqii7Fq2QjTkDDp298yYgcn6 BWSAYmKICoV7PH3tNghgH5Da0p7WxXRG1qkF9VWbK7LLl2GA0VCsaSGeEmoWc5RS+J U78YiGIVHjneOmUE875cgaPMpXypU/fNRODuEkQ4= Received: from DLEE101.ent.ti.com (dlee101.ent.ti.com [157.170.170.31]) by dlelxv90.itg.ti.com (8.14.3/8.13.8) with ESMTP id w41EjO6D025874; Tue, 1 May 2018 09:45:24 -0500 Received: from DLEE101.ent.ti.com (157.170.170.31) by DLEE101.ent.ti.com (157.170.170.31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Tue, 1 May 2018 09:45:23 -0500 Received: from dflp33.itg.ti.com (10.64.6.16) by DLEE101.ent.ti.com (157.170.170.31) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.1466.3 via Frontend Transport; Tue, 1 May 2018 09:45:23 -0500 Received: from [172.24.190.172] (ileax41-snat.itg.ti.com [10.172.224.153]) by dflp33.itg.ti.com (8.14.3/8.13.8) with ESMTP id w41EjJTD026092; Tue, 1 May 2018 09:45:20 -0500 Subject: =?UTF-8?Q?Re:_[PATCH_v9_00/27]_ARM:_davinci:_convert_to_common_cloc?= =?UTF-8?Q?k_framework=e2=80=8b?= To: David Lechner , , , CC: Michael Turquette , Stephen Boyd , Rob Herring , Mark Rutland , Kevin Hilman , Bartosz Golaszewski , Adam Ford , References: <20180427001745.4116-1-david@lechnology.com> From: Sekhar Nori Message-ID: <1ea1b841-24da-e74a-50a8-98b0793e61a5@ti.com> Date: Tue, 1 May 2018 20:15:19 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180427001745.4116-1-david@lechnology.com> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday 27 April 2018 05:47 AM, David Lechner wrote: > This series converts mach-davinci to use the common clock framework. > > The series works like this, the first 3 patches fix some issues with the clock > drivers that have already been accepted into the mainline kernel. > > Then, starting with "ARM: davinci: pass clock as parameter to > davinci_timer_init()", we get the mach code ready for the switch by adding the > code needed for the new clock drivers and adding #ifndef CONFIG_COMMON_CLK > around the legacy clocks so that we can switch easily between the old and the > new. > > "ARM: davinci: switch to common clock framework" actually flips the switch > to start using the new clock drivers. Then the next 8 patches remove all > of the old clock code. > > The final four patches add device tree clock support to the one SoC that > supports it. > > This series has been tested on TI OMAP-L138 LCDK (both device tree and legacy > board file). I have reviewed this series and looks good to me except some comments I gave and some issues you have identified yourself in patches 25 and 26. I think this is a good compromise to achieve platform device based clocks as far as possible with current kernel framework. I know Bartosz is working on solving the problem generically and I guess once thats agreed upon, DaVinci can convert too. But I think this series has been in the works for far too long and should be merged (the remoteproc dependencies that Bartosz pointed out should be resolved too). You can wait for clock maintainers opinion though before spinning another version. I have not tested this series yet, will do so soon. Thanks, Sekhar PS: I started giving a Reviewed-by: for the mach-davinci patches before realizing the futility of doing so and stopped mid-way. They will have my sign-off anyway once I test and merge them.