From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 722F5C19F2C for ; Thu, 28 Jul 2022 08:14:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235041AbiG1IOr (ORCPT ); Thu, 28 Jul 2022 04:14:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59724 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233818AbiG1IOp (ORCPT ); Thu, 28 Jul 2022 04:14:45 -0400 Received: from mail-sh.amlogic.com (mail-sh.amlogic.com [58.32.228.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D781761D77; Thu, 28 Jul 2022 01:14:43 -0700 (PDT) Received: from [10.18.29.47] (10.18.29.47) by mail-sh.amlogic.com (10.18.11.5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.14; Thu, 28 Jul 2022 16:14:41 +0800 Message-ID: Date: Thu, 28 Jul 2022 16:14:41 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: [PATCH V2 0/3] Add S4 SoC clock controller driver Content-Language: en-US From: Yu Tu To: Jerome Brunet , , , , , , Rob Herring , Neil Armstrong , Kevin Hilman , Michael Turquette , Stephen Boyd , Krzysztof Kozlowski , Martin Blumenstingl References: <20220728054202.6981-1-yu.tu@amlogic.com> <1j8rodhfn9.fsf@starbuckisacylon.baylibre.com> <032b3c3f-f899-bf53-ecbb-35191d39392b@amlogic.com> In-Reply-To: <032b3c3f-f899-bf53-ecbb-35191d39392b@amlogic.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.18.29.47] X-ClientProxiedBy: mail-sh.amlogic.com (10.18.11.5) To mail-sh.amlogic.com (10.18.11.5) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi JB, We suspect that you are not looking carefully. You only see two base addresses for controllers, so you think you should use two clock controllers. But you're missing their direct connection. On 2022/7/28 16:06, Yu Tu wrote: > Hi JB， > > On 2022/7/28 15:08, Jerome Brunet wrote: >> [ EXTERNAL EMAIL ] >> >> >> On Thu 28 Jul 2022 at 13:41, Yu Tu wrote: >> >>> 1. Add clock controller driver for S4 SOC. >>> >>> Yu Tu (3): >>>    dt-bindings: clk: meson: add S4 SoC clock controller bindings >>>    arm64: dts: meson: add S4 Soc clock controller in DT >>>    clk: meson: s4: add s4 SoC clock controller driver >>> >>> V1 -> V2: Change format as discussed in the email. >>> >>> Link:https://lore.kernel.org/linux-amlogic/20220708062757.3662-1-yu.tu@amlogic.com/ >>> >>> >>>   .../bindings/clock/amlogic,gxbb-clkc.txt      |    1 + >>>   MAINTAINERS                                   |    1 + >>>   arch/arm64/boot/dts/amlogic/meson-s4.dtsi     |   11 + >>>   drivers/clk/meson/Kconfig                     |   15 + >>>   drivers/clk/meson/Makefile                    |    1 + >>>   drivers/clk/meson/s4.c                        | 4732 +++++++++++++++++ >>>   drivers/clk/meson/s4.h                        |  296 ++ >>>   include/dt-bindings/clock/s4-clkc.h           |  146 + >>>   8 files changed, 5203 insertions(+) >>>   create mode 100644 drivers/clk/meson/s4.c >>>   create mode 100644 drivers/clk/meson/s4.h >>>   create mode 100644 include/dt-bindings/clock/s4-clkc.h >>> >>> >>> base-commit: b293bc9286ee21824e93f0fcfed3b78fdfee01e6 >> >> Please don't post until you have addressed *ALL* the comments from the >> previous version. > The last email asked you to adopt A1 method, but you did not reply? > >> >> At first glance, I can see that this is still a single driver for >> what is obviously 2 controllers with 2 register spaces. Simple comments >> like the "<< 2" in the register declaration have not been addressed >> either. > I understand that this should be a controller, just two address > descriptions. One is the various PLL registers and one is the clock for > the peripherals. And PLL is to provide a clock source for various > peripheral clocks. So a clock controller is reasonable. I think you got > it wrong. > > Ok, if you insist on using two clock controllers,, please provide your > the reason and example code? > >> >> Seeing that, I have not reviewed this version further. >> I won't until all the comments from v1 are either addressed or answer >> >> Regards >> Jerome >> >> .