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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 7574CC41514 for ; Thu, 22 Aug 2019 16:24:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4C8CB233FD for ; Thu, 22 Aug 2019 16:24:12 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lixom-net.20150623.gappssmtp.com header.i=@lixom-net.20150623.gappssmtp.com header.b="wnk14vUU" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389866AbfHVQYL (ORCPT ); Thu, 22 Aug 2019 12:24:11 -0400 Received: from mail-io1-f68.google.com ([209.85.166.68]:41176 "EHLO mail-io1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728371AbfHVQYK (ORCPT ); Thu, 22 Aug 2019 12:24:10 -0400 Received: by mail-io1-f68.google.com with SMTP id j5so13011488ioj.8 for ; Thu, 22 Aug 2019 09:24:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lixom-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5jA9zwn1UxjBuCxNstI14/1pfzFprdw/Ed8oKUD0YIk=; b=wnk14vUUq6zpP5CzYxIVacuXxytmkig+eZ/o2O8a9Wid0GHC4JbykIBqwDLLux1mAZ 2n70jUXa8jEv0BnA2gtWJHfOibK6cxxKsdnjcHfBoPCbXR1PRgp4nqaXCLPtinun87Eb 8Eeds3rTPI+f/r4ORNbQmnGN2qNtZLfoAm5C54V2AciQERaf+dUo6JfPP+Q2yTy7p9mr YrkPLYFkvlkI128m5q/nrW4J9aZnu5PFtVJE/3X0GkF7LfPUs0KnKbC+ZoOqUeU8npbE 4Z1KAzE4lbVQEMW0GvbFodhHRJkgYty7ucFet4lsx8NXbLXQ/T8KqMzNxazxQ+RRSLcv GkYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5jA9zwn1UxjBuCxNstI14/1pfzFprdw/Ed8oKUD0YIk=; b=sSw1nboEu4JgTtE7Ak6kvpIVhezv9NwmMEtLvXWSq94Po05Ow7UPl5wzuGkb2BLi46 1Pjzyp+AT92l2E6ZhP7T7e9jRqcv73TtX3E6txFizZf9mU17hTMvQKPBMRML9M4D0yNx WbChdWklIoGjp6L/ia8hYslD4VzJJPyj/tk41pTOeEUw/9ZwKsvMRocrWLFJEEenQk9d bsvJ7SX0yzKVY8o0TDWtffg0iUlIeXWutTJ6qm5PGzjuECItOnfy27+29EmHjaSpGR1O 51b8CyjL/fhmqQ5WaSgEWcSVvDHWNvRqR6vaDYtPWouUJ8aMEl6MjUeArzVg/1b2TVuG IxPw== X-Gm-Message-State: APjAAAXeBZO8hL3ts/vVRusTW9CQAZrVlKJzQYvmpH/JpyYC2GTF+UPk 9+NsI51GoH5n4jAYZPWXl/0mwb+G5xUvvftiGwMvXQ== X-Google-Smtp-Source: APXvYqzCwIozfnYJNCN4i+QfSef2+thQeEphqEkwMXZMvYLndmnllz8/vu0rhkQbN9YkrG2PKeJ5ts2DohP9qnbTM5E= X-Received: by 2002:a5e:8a46:: with SMTP id o6mr646257iom.36.1566491050001; Thu, 22 Aug 2019 09:24:10 -0700 (PDT) MIME-Version: 1.0 References: <20190822092643.593488-1-lkundrak@v3.sk> <244fdc87-0fe5-be79-d9cd-2395d0ac3f57@kernel.org> In-Reply-To: <244fdc87-0fe5-be79-d9cd-2395d0ac3f57@kernel.org> From: Olof Johansson Date: Thu, 22 Aug 2019 09:23:59 -0700 Message-ID: Subject: Re: [PATCH v2 00/20] Initial support for Marvell MMP3 SoC To: Marc Zyngier Cc: Lubomir Rintel , Rob Herring , Mark Rutland , Thomas Gleixner , Jason Cooper , Kishon Vijay Abraham I , Russell King , Michael Turquette , Stephen Boyd , DTML , Linux Kernel Mailing List , Linux ARM Mailing List , linux-clk 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 On Thu, Aug 22, 2019 at 3:32 AM 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. DT changes, unless there's lack of backwards compatibility, are best merged through the platform trees. Especially for new platforms like these where there's likely going to be nearby changes (and thus conflicts). I.e. driver changes I'm all for bringing through driver trees (including binding patches), but please leave dts/dtsi changes to the platform. -Olof