Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1168191AbdDXJn6 (ORCPT ); Mon, 24 Apr 2017 05:43:58 -0400 Received: from mail-wr0-f176.google.com ([209.85.128.176]:33255 "EHLO mail-wr0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1168177AbdDXJnn (ORCPT ); Mon, 24 Apr 2017 05:43:43 -0400 Date: Mon, 24 Apr 2017 11:43:38 +0200 From: Daniel Lezcano To: Lee Jones Cc: sboyd@codeaurora.org, mturquette@baylibre.com, xuwei5@hisilicon.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org Subject: Re: [PATCH V2] clk: hi6220: Add the hi655x's pmic clock Message-ID: <20170424094338.GC2137@mai> References: <1491683412-12237-1-git-send-email-daniel.lezcano@linaro.org> <20170424093154.ffo7zsr66a2yjy74@dell> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170424093154.ffo7zsr66a2yjy74@dell> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1669 Lines: 61 On Mon, Apr 24, 2017 at 10:31:54AM +0100, Lee Jones wrote: > On Sat, 08 Apr 2017, Daniel Lezcano wrote: > > > The hi655x multi function device is a PMIC providing regulators. > > > > The PMIC also provides a clock for the WiFi and the Bluetooth, let's implement > > this clock in order to add it in the hi655x MFD and allow proper wireless > > initialization. > > > > Signed-off-by: Daniel Lezcano > > --- > > > > Changelog: > > > > V2: > > - Added COMPILE_TEST option, compiled on x86 > > - Removed useless parenthesis > > - Used of_clk_hw_simple_get() instead of deref dance > > - Do bailout if the clock-names is not specified > > - Rollback on error > > - Folded mfd line change and binding > > - Added #clock-cells binding documentation > > - Added #clock-cells in the DT > > > > V1: initial post > > --- > > ?? > > > --- > > I'm unsure if this as been mentioned before, but bundling; > driver & architecture changes and documentation into a single patch is > very seldom a good idea. In this case, you should split this into at > least 3, perhaps 4 patches. > > > .../devicetree/bindings/mfd/hisilicon,hi655x.txt | 6 + > > Patch 1 > > > arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 1 + > > Patch 2 > > > drivers/clk/Kconfig | 8 ++ > > drivers/clk/Makefile | 1 + > > drivers/clk/clk-hi655x.c | 140 +++++++++++++++++++++ > > Patch 3 > > > drivers/mfd/hi655x-pmic.c | 3 +- > > Patch 4 > > [...] Yep. Will do that next time. Thanks. -- Daniel