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 X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E6DB8C3A59B for ; Fri, 30 Aug 2019 14:26:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BAE4B23407 for ; Fri, 30 Aug 2019 14:26:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1567175214; bh=yWzcaCkt9XVIzrbWWo/4tDyL/qMekNCK4plXFdMAR6o=; h=Subject:To:Cc:References:From:Date:In-Reply-To:List-ID:From; b=RcQQBnHP42NXNjPT0dmc4JlXbOMaYqQHbxmHtBc0ksSL4bwnLTcQRltO0sgjnL7Ct Nsgh1dfYvCWBL07hOD12kJPCWWprFjidBpOP7KUK5zLCHJ3V9kbpivnHvAZgg0fhjf HabDu0Bww6CaAtT7mgSTA7mdZkPo+NK79SPAdib8= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728026AbfH3O0y (ORCPT ); Fri, 30 Aug 2019 10:26:54 -0400 Received: from foss.arm.com ([217.140.110.172]:33052 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727751AbfH3O0y (ORCPT ); Fri, 30 Aug 2019 10:26:54 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 7556D344; Fri, 30 Aug 2019 07:26:53 -0700 (PDT) Received: from [10.1.197.61] (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 868E83F703; Fri, 30 Aug 2019 07:26:51 -0700 (PDT) Subject: Re: [PATCH v2 00/20] Initial support for Marvell MMP3 SoC To: Lubomir Rintel , Olof Johansson Cc: Rob Herring , Mark Rutland , Thomas Gleixner , Jason Cooper , Kishon Vijay Abraham I , Russell King , Michael Turquette , Stephen Boyd , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org References: <20190822092643.593488-1-lkundrak@v3.sk> <244fdc87-0fe5-be79-d9cd-2395d0ac3f57@kernel.org> <424d2881edcaf7cedbfa5cbbf2e73aaff5355df3.camel@v3.sk> <08a0e65e-4a80-f611-e36e-8e3f70fa8113@kernel.org> <481e832401c148baf222639f10f494b90dcd23c9.camel@v3.sk> From: Marc Zyngier Organization: Approximate Message-ID: Date: Fri, 30 Aug 2019 15:26:50 +0100 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <481e832401c148baf222639f10f494b90dcd23c9.camel@v3.sk> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-clk-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org On 26/08/2019 12:59, Lubomir Rintel wrote: > On Fri, 2019-08-23 at 10:42 +0100, Marc Zyngier wrote: >> On 23/08/2019 08:21, Lubomir Rintel wrote: >>> On Thu, 2019-08-22 at 11:31 +0100, Marc Zyngier wrote: >>>> On 22/08/2019 10:26, Lubomir Rintel wrote: >>>>> Hi, >>>>> >>>>> this is a second spin of a patch set that adds support for the Marvell >>>>> MMP3 processor. MMP3 is used in OLPC XO-4 laptops, Panasonic Toughpad >>>>> FZ-A1 tablet and Dell Wyse 3020 Tx0D thin clients. >>>>> >>>>> Compared to v1, there's a handful of fixes in response to reviews. Patch >>>>> 02/20 is new. Details in individual patches. >>>>> >>>>> Apart from the adjustments in mach-mmp/, the patch makes necessary >>>>> changes to the irqchip driver and adds an USB2 PHY driver. The latter >>>>> has a dependency on the mach-mmp/ changes, so it can't be submitted >>>>> separately. >>>>> >>>>> The patch set has been tested to work on Wyse Tx0D and not ruin MMP2 >>>>> support on XO-1.75. >>>> >>>> How do you want this series to be merged? I'm happy to take the irqchip >>>> related patches as well as the corresponding DT change (once reviewed) >>>> through my tree. >>> >>> I was hoping for the Arm SoC tree, because there are some dependencies >>> (MMP3 USB PHY depends on MMP3 SoC). >>> >>> That said, the irqchip patches are rather independent and the only >>> downside of them going in via a different tree will be that the other >>> tree that will lack them won't boot on MMP3 (things will compile >>> though). I don't know if that's okay. What's typically done in cases >>> like these? >> >> I usually take the irqchip patches that can be built standalone (without >> dependency on header files, for example). If you want them to go via >> another tree, stick my >> >> Acked-by: Marc Zyngier >> >> on patches #6 through #9. > > Actually, please go ahead and pick the irqchip patches into your tree. > > The rest of the patch set may need a couple more spins, and it will be > nice if it gets shorter. Applied to irqchip-next. M. -- Jazz is not dead, it just smells funny...