Received: by 10.213.65.68 with SMTP id h4csp1087969imn; Wed, 21 Mar 2018 02:13:17 -0700 (PDT) X-Google-Smtp-Source: AG47ELsDGzQsUrbN7ZEutsg2inVGa10dAAEwjFLZxdrTDrfdg8Iuy3ilUDMx3EJ31WmFXDvWAWpM X-Received: by 10.101.77.144 with SMTP id p16mr14426832pgq.327.1521623597559; Wed, 21 Mar 2018 02:13:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521623597; cv=none; d=google.com; s=arc-20160816; b=Sp53ifzX5T0BmAO/mx9LXKzLmvCy7jbUFmvlPB75HQZQG3eBy+kI6MliYjESNrxXP9 IcBz73V0iAx4wFQpPn2Hy0EZIA/4odfA+i8j1DnY6vtWktzet+PBF8O95i47psVO+Oml 0pzntjVmhBV7SNnIkYaaktR7+0m9AGVh6/qGLaIG0uWMrRjiCKDnlaFa0IsgeFy6HG8i tnLCJwyEyfs6hijnMuaJ3M94M/Hw5jrg0jLovwDRUsTya+VMuZufpJSXKHXQJBNGrbqP Ra1Buza2Ld4JeExtLTAdZy0jYk3XyF7RWeHdhVpg7QTqbbnuS1wqC0oxLsqn4HXksUHR YB9Q== 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=EprtO/BQHnRIfDoIQYkRxJeAa1+VmDVnbnrilj19Z/o=; b=wRdRhX/VBo8w/l0Y0aDhWMsl278adIAJ7Qed3pO8BiJ9djR/U7xKw+v1inhV9tXT94 xPW9Hj7mAwOF3vYjq5QwaKSbEXupQe3vSvNs0bz4ODkYVXAmZugEyMCH6me4a3njKW2n piYxeJWydVgZ0wELMxYxw82SKSLPkX/I1jXCGM/uvtUQsifuePKMr9BGsEP7FTwMDrL+ jnr1iNSir/wQ9x+K21qYvJnSJnh9E/vztHmhAdbE6XcAcfxnoGWmyM5tth8TH5BNbA1y faXsexlaxXA3ouVEfLBna1gXovp7KYlLAf5sLKXG6/k9CwytRRetAG4q4ArBeXCsnzOO 8Fxg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=MWNYw9km; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c12si55631pfe.133.2018.03.21.02.13.03; Wed, 21 Mar 2018 02:13:17 -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=@gmail.com header.s=20161025 header.b=MWNYw9km; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751890AbeCUJLW (ORCPT + 99 others); Wed, 21 Mar 2018 05:11:22 -0400 Received: from mail-wm0-f42.google.com ([74.125.82.42]:50298 "EHLO mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751459AbeCUJLR (ORCPT ); Wed, 21 Mar 2018 05:11:17 -0400 Received: by mail-wm0-f42.google.com with SMTP id f19so8305589wmc.0; Wed, 21 Mar 2018 02:11:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=EprtO/BQHnRIfDoIQYkRxJeAa1+VmDVnbnrilj19Z/o=; b=MWNYw9kmLe2RjPUbQcp8T3RRi8VX34bMDJDJSUI/B8t+bgnWZq6yhawW7oF0eJrCdE mmUjn0A1QrrWm+Lpmt1z++0wrzKNY5R9cIXiZsxEPNwr4+ByUwPUzObP1sC/0PDZ/4Mj vuqoTI38EUI0tTDuSZ8pJArri1yPssdP4yu4pd5JEbx6sK+P/IjGUMd/iJ60XPKWjtTF d0INVqhjk/e6rBsHzF6tTwL41QtlciRU4wvhSG/4Y99fGNzCV7+hHdVrK4K/IpU/7+2R MNo6b+af3jG40llJqK4hJvoAGC0P8QKJlBdEvbBbDVjoKqiqft1/E2cFJSz2TcNOR679 I/kQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=EprtO/BQHnRIfDoIQYkRxJeAa1+VmDVnbnrilj19Z/o=; b=sEtwtMnto7e6T8NP5pUaTMSf0c1+esAmD2d+TUPruuH0Ps63HwxBvSZbV6s3ST1CY8 EPGquVi4GkEoT90gG/i0+/GcWfDmsBRT8QBDivgCs1nkCfAMB3mLEM1EKKv+EbDGCpaV GIsXr/8UQqJtgJBabr8ymOmwyXk+tI3JAj0V3mf7nh6PK/fGmJTrU/DVJsS94GW0+09F VY3SBQjMUoUiwHjORpIKcRqgrim6VG83MATkzupHjeHeuIOM1HiS/MeFlxwclEhukm3O jB23A3iSlcJEeH55EtrtGz1kBN2JOVLdhEIoAGg0dgLFar63OHVQR22dvyHvBgM78svg Jw0w== X-Gm-Message-State: AElRT7Hua/yciVJCoNepgXktO3FskVXl2rSFSoZUMjvVxPZSuIzZ9iXz 4rU8SduiKIOvrbQ63Js/dVI= X-Received: by 10.28.232.89 with SMTP id f86mr2162767wmh.72.1521623476147; Wed, 21 Mar 2018 02:11:16 -0700 (PDT) Received: from ziggy.stardust ([47.61.192.62]) by smtp.gmail.com with ESMTPSA id r126sm4725187wmb.10.2018.03.21.02.11.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Mar 2018 02:11:15 -0700 (PDT) Subject: Re: [PATCH v2 0/5] update Mediatek MT2712 clock and scpsys support To: Stephen Boyd , Stephen Boyd , Weiyi Lu , Arnd Bergmann Cc: Mike Turquette , Rob Herring , James Liao , Fan Chen , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-clk@vger.kernel.org, srv_heupstream@mediatek.com References: <20180312070342.4335-1-weiyi.lu@mediatek.com> <1521526068.13313.8.camel@mtksdaap41> <152153061465.254778.3061562183948751301@swboyd.mtv.corp.google.com> From: Matthias Brugger Message-ID: <6c29df1f-f619-5e11-4160-b58e154f6592@gmail.com> Date: Wed, 21 Mar 2018 10:11:09 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <152153061465.254778.3061562183948751301@swboyd.mtv.corp.google.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/20/2018 08:23 AM, Stephen Boyd wrote: > Quoting Weiyi Lu (2018-03-19 23:07:48) >> On Mon, 2018-03-12 at 15:03 +0800, Weiyi Lu wrote: >>> This series is based on v4.16-rc1 and composed of scpsys control (PATCH 1-2) and clock control (PATCH 3-5). >>> Basically, all changes are for the ECO design change of MT2712. >>> >>> changes since v1: >>> - Avoid renumbering clocks. Append new clocks at the bottom of each own subsystem. >>> >> Hi Matthias & Stephen, >> >> Sorry to bother. Just saw patch 1/2 are already pushed to v4.16-next-soc >> and patch 3/5 are applied onto clk-next. What about the patch 4(arm64: >> dts: add clock device nodes of MT2712). Does there any problem remain or >> it cause some problems? Many thanks. > > Patch 4 can go via arm-soc? I'm not planning to apply that patch. > I can take it through my branch, no problem. But I think it is too late for this cycle. CCing Arnd to confirm. Regards, Matthias