Received: by 10.213.65.68 with SMTP id h4csp539252imn; Fri, 23 Mar 2018 09:56:59 -0700 (PDT) X-Google-Smtp-Source: AG47ELu+XeCucfY7pvqowdrnZbMekBvKRBiMU640vM+njhWg3eOdwOJc5xLz4+ECXIwHZzcaIR3h X-Received: by 10.98.182.26 with SMTP id j26mr4749456pff.223.1521824219309; Fri, 23 Mar 2018 09:56:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521824219; cv=none; d=google.com; s=arc-20160816; b=ilMeiE/q0UK9q4XYA+xKdpRKyGyMN2C/xbfqEXIiK44dgAA9nt6bWUyM/551F0He1W fgkrLNLdzC88npGOfW+12c0AEsIOpwjUplgyAXmguDf+Wi+KizN2QoYHiusaWLw6L8E0 f782X7y9SOIxZSquYHL2CIhKm1KilrwUpdENDLWKq7SGsl7kQQMyx9n2Ezr1iUqvqFTD C2RIjXwWMW2Yth3ZGopQkTV956mJhZh08guL/eLteT1dWwnr5Et6uUfoND267NyUH7uz NeK2FvNmiZChFeL0EOfEvUtSXC2LqY/moS+KHAW+bGqFLkCrd8whbf+FnLKx7+wUVW4F J8QA== 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=7jSx/yAVlsAs1fH29jqe/kRnaAcErdjjsUcHGPGOdpk=; b=VN/gNid7LouM1cYqhWSGOUdg9xKLWpLE6gLWrC58pIlL8JSdmpwwwcXYB8va/uHbxB oHKkNr1tRwhZrl7gnoMhJoHgNl2lzIlYcUPBjvSIDhKU+ulGd0GcENh/+zUyyyysvCib MRKFaVve6O6Qvl61IyImjBE07TzKNqnsVl2isaePlUHOzobclSLgNqsz03JgWYI8FwFX tGIFJkv8/t5cMNbX3ksbLblbYnEfzS55CnQAyJdl5j5aHjD9O3g+3xZOssaMrR3C5B4w GFMSs6YX7fJllyS1dv79Lr44X/g0VspPQF7DLo2p+6YWE1sHUv4Mt/NnM6aVkYLR2HgW zu1g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@bgdev-pl.20150623.gappssmtp.com header.s=20150623 header.b=jwRIglFD; 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 b34-v6si8977494plc.53.2018.03.23.09.56.44; Fri, 23 Mar 2018 09:56:59 -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=jwRIglFD; 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 S1752306AbeCWQzy (ORCPT + 99 others); Fri, 23 Mar 2018 12:55:54 -0400 Received: from mail-oi0-f54.google.com ([209.85.218.54]:40004 "EHLO mail-oi0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752227AbeCWQzs (ORCPT ); Fri, 23 Mar 2018 12:55:48 -0400 Received: by mail-oi0-f54.google.com with SMTP id 1-v6so5153984oix.7 for ; Fri, 23 Mar 2018 09:55:48 -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=7jSx/yAVlsAs1fH29jqe/kRnaAcErdjjsUcHGPGOdpk=; b=jwRIglFDTUnOXrnyglMOjNrrS/KFi7RnP86NhbAPAjGLIz/PV2Vpe179RLXO3Jl93A WPa18fB7pXCW7ZHnzWoD8SQkqmZuQJGGfEfgS7x/v06IW4FBiNvE4Vj/Vrl71/Ww1c7T JL3tUB+PFiw8670h6vFCDQZpJoF3/ndX8K2RVfHf8mUV/kwVvRb3KTWQ75eW6IG5spxq xJm71XcVJYbQ1s9L+okA170/aUNmZDHTVStHRST79eliQy9AjW9CH9x/h3Qlth4ju30O wLvnLEVkoX7jaG/8mFMsjtiMofo2KLB9Q6kLXH3JYJd9TZAij21PP/b/vdQ9Bvp0Px8s Y15Q== 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=7jSx/yAVlsAs1fH29jqe/kRnaAcErdjjsUcHGPGOdpk=; b=frGVoVvk+NmrR+MxeadnaJwjej0DkHOt7e95uP8Zx9vG1BhzOXtHM7yw57UE+MMSnW 4yMIaJdwJmygpOoWWO08USxZVcA8u8yEEwJ/JuhGxCX9eAVH71Z5PSjlQXTzyl+gHtQG Qt6EI6HZJG+KmOOwM6hhxCrQ7JflVLOF/tQ/T5H8rFtFhR5l3NCjv97a5qVzTCfcZOcH FtYBvlM3cLdCSrQeoET8AWtpAxLKvFgSBTlTYFarVIVWTr63LHZcjmaGan0lMZ83XAsd lJUpasX6wSz+7Ubzf5aDh2OM3pneg8TsKk3J6uogDzySmdalUn8ByroOkcMHrNVQJUMu GI2w== X-Gm-Message-State: AElRT7GZ81DAw6pe79WdPgVAwSvtLZOvVj7PB4Z5TST0ZEFrO4Py5prY IxeFOUeLzQGsczdlYMrMeE0lz6tueIg5W1woxgQciA== X-Received: by 10.202.223.68 with SMTP id w65mr7254958oig.155.1521824147965; Fri, 23 Mar 2018 09:55:47 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:1426:0:0:0:0:0 with HTTP; Fri, 23 Mar 2018 09:55:47 -0700 (PDT) In-Reply-To: <152182378792.178046.3747112581117251857@swboyd.mtv.corp.google.com> References: <20180323130455.11470-1-brgl@bgdev.pl> <152182378792.178046.3747112581117251857@swboyd.mtv.corp.google.com> From: Bartosz Golaszewski Date: Fri, 23 Mar 2018 17:55:47 +0100 Message-ID: Subject: Re: [PATCH v4 0/8] ARM: davinci: complete the conversion to using the reset framework To: Stephen Boyd Cc: Bjorn Andersson , David Lechner , Kevin Hilman , Mark Rutland , Michael Turquette , Ohad Ben-Cohen , Philipp Zabel , Rob Herring , Russell King , Sekhar Nori , 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-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? Best regards, Bartosz Golaszewski