Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4436749ybi; Mon, 3 Jun 2019 10:49:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqywqH+uNXmW1aNbazyIMw9YAIbKJpITHS6wh2JTEVtRrrlBmp4C/L57phwT3M1p79UBR+mk X-Received: by 2002:a63:1f11:: with SMTP id f17mr24563972pgf.311.1559584186801; Mon, 03 Jun 2019 10:49:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559584186; cv=none; d=google.com; s=arc-20160816; b=0cw71pa3CVxVrSJTDm6bxCnnyLIriIwxMGTbr6N+xM8xOf55CHb7w31ItE0oCoqSL1 GhYV+gQmeKrP2R6ZThHBVkmb/GD09H2nU/O54UIHgNOUuIqI1rvgL1tKqkXrRRIicPMh /NDuWjg+F/O0EIE1JVoIfNv+WuFj34Xy6Y61tAcc/lzX4+Ot3T5hBfxmW1oKdw6GeCLM DgV0/HzlB3GMevirZ47Z2i27z2vKfV0wxoAothQcpTg6X6Ndk74wN7VBx7J2Q6RX5OGI gMHdTOxqy3hbjCrkoZIz77ImCXrwSsXs7zWNEfH79TvQKZx2xnp8ek0lCJq9U6uwuSRx mb0Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=BhMqWjtF0uEZOLI2iM56ESRiaXGol3y/jPJWzpUeGnM=; b=U/Je/njVBeJjyGf59WcQdchtb7BKFouGWGQSvGAj5ooEzPy25Vs9QgQfdRJsKb1lie JkBQE2x3bTDgyhWSMPfl9fPSgsTJeoNj3po30fdzzucTXmNvBx63ow4Fz2n5eL8uhYDu zUsveUPBo/T4xrj1G9ziWsPFxrgkfODKi+BiFf1Ep8H3S/x6x3WsNPg9Z8aggH2hQ9x8 3sELgdu/XJSpxn0mSz8iQ4hJovIEqD9Bvv45nKodpS+1LRIR1gm3z2VqJ+HefGIy6OlD TyXL8mJCvLpOc5fD7yydUDssAoBZhdZaTmkKXDPre09ryh/qKgmMMIyQrDDVspS0K3YO E16A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=N70Pgheg; 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=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n11si19411433pjp.51.2019.06.03.10.49.30; Mon, 03 Jun 2019 10:49:46 -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=@kernel.org header.s=default header.b=N70Pgheg; 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=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729347AbfFCQij (ORCPT + 99 others); Mon, 3 Jun 2019 12:38:39 -0400 Received: from mail.kernel.org ([198.145.29.99]:42272 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727308AbfFCQij (ORCPT ); Mon, 3 Jun 2019 12:38:39 -0400 Received: from mail-wm1-f44.google.com (mail-wm1-f44.google.com [209.85.128.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id C1BDD27290; Mon, 3 Jun 2019 16:38:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559579918; bh=do4LaCsAOPTd/xXZSnOPF8r9lTDiUPMdRTL2m5faea4=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=N70PghegSq3Sp1SpJr7jbTVhVknam2TQYZJLQdRm/w1+/4RPG1PxDgq1Ptja8yWvF O1Ek+RuJtu16YFsjFU//VyeEJQuMr6cbSPNwAg+o7/wAr9/lKPeAlxbfho7HgfcxhT Jsr+Sz0rNPsWOBm0Bz3ZtMK9Rr9pNLnl1Sp5D3RQ= Received: by mail-wm1-f44.google.com with SMTP id c6so8865091wml.0; Mon, 03 Jun 2019 09:38:37 -0700 (PDT) X-Gm-Message-State: APjAAAWIkHekPIgTOVk5h3xpAdE0+XFEhWZ3I6ZPgN4P2byVda6Ku/oJ zAtDX9MrAVpHJN8SQHEfaa0SmvbbyAiauFCdw1I= X-Received: by 2002:a1c:c545:: with SMTP id v66mr3207828wmf.51.1559579916334; Mon, 03 Jun 2019 09:38:36 -0700 (PDT) MIME-Version: 1.0 References: <20190520080421.12575-1-wens@kernel.org> <20190520090327.iejd3q7c3iwomzlz@flea> In-Reply-To: <20190520090327.iejd3q7c3iwomzlz@flea> From: Chen-Yu Tsai Date: Tue, 4 Jun 2019 00:38:22 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 00/25] clk: sunxi-ng: clk parent rewrite part 1 To: Stephen Boyd Cc: Maxime Ripard , Chen-Yu Tsai , Michael Turquette , linux-arm-kernel , linux-clk , linux-kernel Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stephen, On Mon, May 20, 2019 at 5:03 PM Maxime Ripard wrote: > > On Mon, May 20, 2019 at 04:03:56PM +0800, Chen-Yu Tsai wrote: > > From: Chen-Yu Tsai > > > > Hi everyone, > > > > This is series is the first part of a large series (I haven't done the > > rest) of patches to rewrite the clk parent relationship handling within > > the sunxi-ng clk driver. This is based on Stephen's recent work allowing > > clk drivers to specify clk parents using struct clk_hw * or parsing DT > > phandles in the clk node. > > > > This series can be split into a few major parts: > > > > 1) The first patch is a small fix for clk debugfs representation. This > > was done before commit 1a079560b145 ("clk: Cache core in > > clk_fetch_parent_index() without names") was posted, so it might or > > might not be needed. Found this when checking my work using > > clk_possible_parents. > > > > 2) A bunch of CLK_HW_INIT_* helper macros are added. These cover the > > situations I encountered, or assume I will encounter, such as single > > internal (struct clk_hw *) parent, single DT (struct clk_parent_data > > .fw_name), multiple internal parents, and multiple mixed (internal + > > DT) parents. A special variant for just an internal single parent is > > added, CLK_HW_INIT_HWS, which lets the driver share the singular > > list, instead of having the compiler create a compound literal every > > time. It might even make sense to only keep this variant. > > > > 3) A bunch of CLK_FIXED_FACTOR_* helper macros are added. The rationale > > is the same as the single parent CLK_HW_INIT_* helpers. > > > > 4) Bulk conversion of CLK_FIXED_FACTOR to use local parent references, > > either struct clk_hw * or DT .fw_name types, whichever the hardware > > requires. > > > > 5) The beginning of SUNXI_CCU_GATE conversion to local parent > > references. This part is not done. They are included as justification > > and examples for the shared list of clk parents case. > > That series is pretty neat. As far as sunxi is concerned, you can add my > Acked-by: Maxime Ripard > > > I realize this is going to be many patches every time I convert a clock > > type. Going forward would the people involved prefer I send out > > individual patches like this series, or squash them all together? > > For bisection, I guess it would be good to keep the approach you've > had in this series. If this is really too much, I guess we can always > change oru mind later on. Any thoughts on this series and how to proceed? Thanks ChenYu