Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752717AbdFTA3A (ORCPT ); Mon, 19 Jun 2017 20:29:00 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:35569 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752475AbdFTA26 (ORCPT ); Mon, 19 Jun 2017 20:28:58 -0400 Subject: Re: [PATCH v6 00/11] Broadcom Stingray SOC Initial Support To: Stephen Boyd , Florian Fainelli Cc: Anup Patel , Rob Herring , Mark Rutland , Michael Turquette , Catalin Marinas , Will Deacon , Ray Jui , Scott Branden , Jon Mason , Oza Pawandeep , Srinath Mannam , Pramod Kumar , Sandeep Tripathy , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org, bcm-kernel-feedback-list@broadcom.com References: <1496385275-6899-1-git-send-email-anup.patel@broadcom.com> <4c15213f-4ac6-a0a7-f2b8-cde2b4cee891@gmail.com> <20170606223027.GL20170@codeaurora.org> From: Florian Fainelli Message-ID: <0e321ac9-37ce-6c52-e76a-250183ca299c@gmail.com> Date: Mon, 19 Jun 2017 17:28:45 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170606223027.GL20170@codeaurora.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3377 Lines: 87 On 06/06/2017 03:30 PM, Stephen Boyd wrote: > On 06/05, Florian Fainelli wrote: >> >> >> On 06/05/2017 09:51 AM, Florian Fainelli wrote: >>> On 06/01/2017 11:34 PM, Anup Patel wrote: >>>> This patchset adds initial support of Broadcom Stingray SOC >>>> by reusing existing Broadcom iProc device drivers. >>>> >>>> Most of the patches in this patchset are DT patches except >>>> the Stingray clock tree support which just one patch. >>>> >>>> This patchset is based on Linux-4.12-rc3 and it is also available >>>> at stingray-v6 branch of https://github.com/Broadcom/arm64-linux.git >>>> >>>> Changes since v5: >>>> - Rebased patches for Linux-4.12-rc3 >>>> - Update DT node names to match register offset >>>> >>>> Changes since v4: >>>> - Reduce number of include headers in Stingray clk driver >>>> >>>> Changes since v3: >>>> - Rebased patches for Linux-4.12-rc1 >>>> - Updated PATCH3 to have all clocks except genpll3 to be >>>> registered via platform driver probe >>>> >>>> Changes since v2: >>>> - Remove default bootargs from chosen DT node >>>> - Remove "linux" prefix from stdout DT attribute of chosen DT node >>>> - Remove use of GIC_CPU_MASK_xxx() for PPIs >>>> >>>> Changes since v1: >>>> - Rebased patches for Linux-4.12-rc1 >>>> - Removed unwanted /memreserve/ from bcm958742-base.dtsi >>>> - Use ranges DT property to clear view of memory-layout >>>> - Make bcm-sr.h part of clock DT bindings patch >>>> >>>> Anup Patel (3): >>>> dt-bindings: bcm: Add Broadcom Stingray bindings document >>>> arm64: dts: Initial DTS files for Broadcom Stingray SOC >>>> arm64: dts: Add PL022, PL330 and SP805 DT nodes for Stingray >>>> >>>> Oza Pawandeep (1): >>>> arm64: dts: Add I2C DT nodes for Stingray SoC >>>> >>>> Pramod Kumar (3): >>>> arm64: dts: Add NAND DT nodes for Stingray SOC >>>> arm64: dts: Add pinctrl DT nodes for Stingray SOC >>>> arm64: dts: Add GPIO DT nodes for Stingray SOC >>>> >>>> Sandeep Tripathy (3): >>>> dt-bindings: clk: Extend binding doc for Stingray SOC >>>> clk: bcm: Add clocks for Stingray SOC >>>> arm64: dts: Add clock DT nodes for Stingray SOC >>>> >>>> Srinath Mannam (1): >>>> arm64: dts: Add PWM and SDHCI DT nodes for Stingray SOC >>> >>> Applied patches 1, 4-11 to devicetree-arm64/next, thanks! >> >> Also took patch 2, to make sure everything builds properly, Stephen, let >> me know if you want me to take patch #3 as well. >> > > Usually clk tree takes includes and hosts that in a stable branch > for arm-soc maintainers to take. It seems that now arm-soc > maintainers are asking that dts files use plain numbers and then > switch to defines later after -rc1. > > Should I go apply patch 2 myself so I can apply patch 3 to the > clk tree? Personally, I think this is fine because git doesn't > care about duplicate commits anyway and this is just #defines > we're talking about. Alternatively, you can host patch 2 in a > stable branch on v4.12-rc1 that I can pull into clk tree and then > apply patch 3 on top of and merge up into clk-next. Or you can > send me a PR for this clk driver and I can merge it into clk-next > where patch 2 is the parent of the clk driver change. Yes, please apply patch 2 and 3 in your tree, we should be fine. You would also find patch 2 in a stable branch: https://github.com/Broadcom/stblinux/refs/heads/arm64-stingray-for-4.13 Thanks! -- Florian