Received: by 10.213.65.68 with SMTP id h4csp454783imn; Tue, 27 Mar 2018 02:32:18 -0700 (PDT) X-Google-Smtp-Source: AG47ELsrJE0diOPWhnYiPtqwBCYHMBwcQXGWS4LRQmeC3PIRWg+51sS3bjS8PO198V+qYRCnzu2G X-Received: by 10.98.5.71 with SMTP id 68mr35618917pff.241.1522143138374; Tue, 27 Mar 2018 02:32:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522143138; cv=none; d=google.com; s=arc-20160816; b=aPcm4ErX3J2YKXAZqDSwwrhh0n2jySlHPjUxHRBaxDf6wSQrtllNNLn+hX0nhaxnRh TtM7l1LtHabb5CZIzbcohu9srCjjLyC0w/TI+Osl64Ok/nczxwrzG8gghLBxI/kX9nof 5a5X7++KldzXHdMKHyOP9jdti71hYaI0wxcuz1xBQLOq+8GvrCqnCs17FsLSCQ4tHdAH 35vVmcvJDGomEilJIcXx+mQp3+bvtwHzbJUHmco0XWNhxz83ubXU2d58sa/xrk6UK+3X REuX/I2UlBah2Kf4vncu4oSk6lqwIsBnaat/PMIr0QkA0liOQ6WDtY+ujEOPWcoM1pa5 Fe+A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=cy3xJF0tJuVv4XraK9aYSGBkmzGcClQiQGBLmXWFRNU=; b=A10Vew66yK9agThuFDE3YDcv66SbTbv4fIbWlPNC5ElL75m12IYHgwSOgl2UZod/By XdPafKPVGhzLsBHwVt4az6l9Bk3XFYL0dTujkYaInrMVrOObdYasmSn2xiHifiovHMpW b4FTha06PLXdObRURAqVTBQdXZtRtZQ5QFHlFbKC6zyZf2Mifg0cyoJ2BR2dtwTAQt4s T7CxXiwRX8NGcdno91pPwFIjcxXdgBlJkQrLwzvovYfFfh7VVFNoXQd9hqc1WPILeiaO dxpOGNT3acssxs2dWEHKPPcK+pdW4QVHjBbMxg7zSV+0BCTqPW3Tswzetd9L2xGrnJxP Iwwg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@bgdev-pl.20150623.gappssmtp.com header.s=20150623 header.b=Lg1Si/u3; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m77si717509pfk.56.2018.03.27.02.32.03; Tue, 27 Mar 2018 02:32:18 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@bgdev-pl.20150623.gappssmtp.com header.s=20150623 header.b=Lg1Si/u3; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752016AbeC0J35 (ORCPT + 99 others); Tue, 27 Mar 2018 05:29:57 -0400 Received: from mail-oi0-f65.google.com ([209.85.218.65]:43059 "EHLO mail-oi0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750918AbeC0J3y (ORCPT ); Tue, 27 Mar 2018 05:29:54 -0400 Received: by mail-oi0-f65.google.com with SMTP id u84-v6so9357345oie.10 for ; Tue, 27 Mar 2018 02:29:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bgdev-pl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cy3xJF0tJuVv4XraK9aYSGBkmzGcClQiQGBLmXWFRNU=; b=Lg1Si/u3hL2bf2+xt6ZiPjpTKMHsFrlGM7nBqoQGd/eCHaspg3S8gpq/cjbRZPBTbm iXNcgYxVLm6QoUdbQKGkWnZUD1kzT1b4zCnmYsgZUmhe3MHGJdDF2U3ZjIkV6fZy9bYO XbA3Yfy4YZm+97+A/AYrdDfFTQIvWHduXPdHSm+1cleCg6qyiUvRYtQdLcFOUEMG+Gkm HTrKnr5S4qDFWuprTnJfZcTgBrpcyUEG4CJjrUb9JbYCKe0RZ8RIsRU4OdvzCqnBBcnY Jrr5/LxHMy1HN6JfDD8QnUp4m+ZXpM4QtyjlstzY9iiMFZ/wKOHyCTpJr5PD02gGTUIQ 3KCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=cy3xJF0tJuVv4XraK9aYSGBkmzGcClQiQGBLmXWFRNU=; b=hn+7Ng4jF4Gn6KoqSGbP4cDUCyFrsKzWp6tFrzGUEby7ISefmxJ/5luKxVvw/JTCvd WyQ6uhNLp/0tK9VRIL8jX9NRPK3OlKambJJAeKaEL3KmHq5RT+Z0kPdU2AKbL9iNzwbK aoKfroLOCQJcIoOwDMJie9/39DMLaU3v5AyJoHZfq5sC2Et9bDpAfnJyrW50gNxjhvLt liovBIKH6OjSmx4rY16WfTuDcItlUhKBKcJIiluEfL55d/SB6DRPbVPal82fe7WUb5qk zFfHLr3g2y8XoKR207HtZVJDuyAVIrZO4M8UvrUTCKOcmLKc/RoL2JMAy64D3xnKgFuK ootg== X-Gm-Message-State: AElRT7FmJ55WLBz93zt+qDPWP8wlUJ4IhWIaAo/xoO1J46sNxVMORhnk wQX4MS9kH6HDZM0yetEfoJg9hBXvcNfbIrjtEx7csQ== X-Received: by 10.202.190.70 with SMTP id o67mr22240274oif.103.1522142994001; Tue, 27 Mar 2018 02:29:54 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:578c:0:0:0:0:0 with HTTP; Tue, 27 Mar 2018 02:29:53 -0700 (PDT) In-Reply-To: <6c55e081-57ba-6c39-8494-cda5022aa927@ti.com> References: <20180323130455.11470-1-brgl@bgdev.pl> <152182378792.178046.3747112581117251857@swboyd.mtv.corp.google.com> <152182490783.178046.1191965992600877708@swboyd.mtv.corp.google.com> <6c55e081-57ba-6c39-8494-cda5022aa927@ti.com> From: Bartosz Golaszewski Date: Tue, 27 Mar 2018 11:29:53 +0200 Message-ID: Subject: Re: [PATCH v4 0/8] ARM: davinci: complete the conversion to using the reset framework To: Sekhar Nori Cc: Stephen Boyd , Bjorn Andersson , Ohad Ben-Cohen , David Lechner , Kevin Hilman , Mark Rutland , Michael Turquette , Philipp Zabel , Rob Herring , Russell King , devicetree , linux-remoteproc@vger.kernel.org, Linux Kernel Mailing List , Bartosz Golaszewski , linux-clk@vger.kernel.org, Linux ARM 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 2018-03-27 8:09 GMT+02:00 Sekhar Nori : > Hi Bart, > > On Friday 23 March 2018 10:46 PM, Bartosz Golaszewski wrote: >> 2018-03-23 18:08 GMT+01:00 Stephen Boyd : >>> Quoting Bartosz Golaszewski (2018-03-23 09:55:47) >>>> 2018-03-23 17:49 GMT+01:00 Stephen Boyd : >>>>> Quoting Bartosz Golaszewski (2018-03-23 06:04:47) >>>>>> From: Bartosz Golaszewski >>>>>> >>>>>> This series converts the only user of the handcoded, mach-specific reset >>>>>> routines in the davinci platform to using the reset framework. >>>>>> >>>>>> Patch 1 modifies the way lookup entries are registered with the reset >>>>>> framework. >>>>>> >>>>>> Patches 2-4 add necessary lookups/DT-properties. >>>>>> >>>>>> Patches 5-7 convert the davinci-rproc driver to the reset framework. >>>>>> >>>>>> Patch 8 removes now dead code. >>>>>> >>>>>> Philipp: it turned out that it's indeed better to use the reset >>>>>> controller's device name for the entry lookup. >>>>>> >>>>>> Tested both in DT and legacy modes by booting the examples from >>>>>> ti-ipc-rtos recipe in meta-ti. >>>>>> >>>>>> This series applies on top of David Lechner's common-clk-v9 branch[1] >>>>>> with Philipp Zabel's reset/next branch[2] pulled in. >>>>>> >>>>>> It can be found in my github tree as well[3]. >>>>>> >>>>> >>>>> What's the merge strategy for the rest of the patches? I should apply >>>>> the clk ones after the next -rc1? >>>> >>>> Or maybe Philipp can provide us with an immutable branch with the reset patches? >>>> >>>> The you could apply the driver patches and let Sekhar take all the >>>> platform code? >>>> >>> >>> Ok that could work too. >> >> Ohad, Bjorn can you ack the remoteproc patches? Are you OK with >> Stephen taking them through the clock tree? Otherwise it would get >> complicated since they depend on the first clk patch and the last clk >> patch depends on them. > > I will not be queuing the DTS patches for v4.17. They depend on clock > framework DTS patches which itself I plan to queue for v4.18. Given > this, I think the best bet is: > > Ohad/Bjorn queue remoteproc patches already acked by Suman and having no > dependencies. That is, 5/8 and 6/8. > > If Philipp can provide an immutable branch with reset changes, it will > be great and Stephen can queue 4/8. If not, its best to resend that > patch to Stephen once v4.17-rc1 is out. > > The remaining patches need to wait till v4.18 (or even v4.19 if > dependencies don't pan out well). > > Thanks, > Sekhar Very good, thanks. I've just sent out a v3 with three non-reset remoteproc patches that can already be applied by Suman. Thanks, Bartosz