Received: by 10.213.65.68 with SMTP id h4csp815294imn; Fri, 23 Mar 2018 17:33:19 -0700 (PDT) X-Google-Smtp-Source: AG47ELtoyelzC3K7H3b5hmrG5ksIDys6PN+27O31XcazveqaxVZkhW0GKl3EYcFrJOYoO5Db+J3x X-Received: by 2002:a17:902:6c4f:: with SMTP id h15-v6mr16535539pln.33.1521851599552; Fri, 23 Mar 2018 17:33:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521851599; cv=none; d=google.com; s=arc-20160816; b=iGkOsC9LelCWbalmjuWpqLdiMAF2Qy/ZlSUgkezjk5NqqSv0Ey522zY/azwy/nMLaE DKu2OX60v2KQBQyS4yFtGVV+5t8Fzah8JmgSkkemZPWK3o50iIEGGAN93hHdHmUGfCWy vn/fd3kR6V1BuGBO7/yOn6clKYsHxgDU7xonRAgFUaoK8oBFfnoqYsrTruBm34+2n+YS 7g9ylJ9sS1U2ghHMtkpoFgHnCIRRBcCYVmN9x799OLHin09NhzHpzSF7eoRi19HPoqgv gwSzdwZdkQFIIBCGFi9+zsfBxsUYFjYXY7UgZPlvfxvTvyhPVNcDTtXNxQDiXGApwWyQ 3g5A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=o/2foLG2TjBIPZdtqmDeZTWptA3iu89Uk2NzJTLkL08=; b=pmwmvH7DUaCt7PHgoFZi4qc8Q+ZSekDy5jTBfGMXS3D8uQFWDQvsthF8HDUprRBYah Hg12YRQ/VokVNtxGlrnVFimRBY/8Rh9Eb7M+6kVo0ttwWzn+ruRPpgrA1RqU2LIwFjW7 hmRY0XH95tP/N9BAeXv+tZw/0IvVugBswUmpUgk1XRnv59eIrv94T+qRBzCRJrR+eNjA SOJUXP37XP4kITtiZNroD2tQxSzvTsefBPN8STJPUMDLtuRF3sBIqNgqa9UcwVZOLQpy 6ivN64cF3tuLRAxqhmx7HPjSaVrWCCnOYBHi1Yat/gTMqfKdmBlUAeClVDy/zY/bxdGP WIEg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=FSCMqIF5; 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; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f16-v6si9228429pli.731.2018.03.23.17.33.05; Fri, 23 Mar 2018 17:33:19 -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=@ti.com header.s=ti-com-17Q1 header.b=FSCMqIF5; 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; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752231AbeCXAcD (ORCPT + 99 others); Fri, 23 Mar 2018 20:32:03 -0400 Received: from lelnx194.ext.ti.com ([198.47.27.80]:62933 "EHLO lelnx194.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751490AbeCXAb6 (ORCPT ); Fri, 23 Mar 2018 20:31:58 -0400 Received: from dflxv15.itg.ti.com ([128.247.5.124]) by lelnx194.ext.ti.com (8.15.1/8.15.1) with ESMTP id w2O0UVrb003768; Fri, 23 Mar 2018 19:30:31 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ti.com; s=ti-com-17Q1; t=1521851431; bh=lIv3TM8wst52K/ocglD4MvqN1FgM9n2q+YV/iqTkPc4=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=FSCMqIF5OVCiAwL4fabdKZFLzHPUdGF01SRK/aHlQ4Cvtfjy04jHqLUZphten1mkp 474TzRrkoFFt09mB3XEPQfJ6ZeFMBQ7vKS1shepBhbRnHGfNGP6Tuif14oBnWKwunb 8SbDy1YLnAvYtqGkue7vXSqfOgCBHUpBZonYGHA4= Received: from DFLE109.ent.ti.com (dfle109.ent.ti.com [10.64.6.30]) by dflxv15.itg.ti.com (8.14.3/8.13.8) with ESMTP id w2O0UVvJ019830; Fri, 23 Mar 2018 19:30:31 -0500 Received: from DFLE104.ent.ti.com (10.64.6.25) by DFLE109.ent.ti.com (10.64.6.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.35; Fri, 23 Mar 2018 19:30:31 -0500 Received: from dlep32.itg.ti.com (157.170.170.100) by DFLE104.ent.ti.com (10.64.6.25) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.1261.35 via Frontend Transport; Fri, 23 Mar 2018 19:30:31 -0500 Received: from [128.247.58.153] (ileax41-snat.itg.ti.com [10.172.224.153]) by dlep32.itg.ti.com (8.14.3/8.13.8) with ESMTP id w2O0UVNR021240; Fri, 23 Mar 2018 19:30:31 -0500 Subject: Re: [PATCH v4 0/8] ARM: davinci: complete the conversion to using the reset framework To: Bartosz Golaszewski , Stephen Boyd , Bjorn Andersson , Ohad Ben-Cohen CC: David Lechner , Kevin Hilman , Mark Rutland , Michael Turquette , Philipp Zabel , Rob Herring , Russell King , Sekhar Nori , devicetree , , Linux Kernel Mailing List , Bartosz Golaszewski , , Linux ARM References: <20180323130455.11470-1-brgl@bgdev.pl> <152182378792.178046.3747112581117251857@swboyd.mtv.corp.google.com> <152182490783.178046.1191965992600877708@swboyd.mtv.corp.google.com> From: Suman Anna Message-ID: Date: Fri, 23 Mar 2018 19:30:31 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Bart, On 03/23/2018 12:16 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 take a closer look and test on Mon. A quick glance of the remoteproc changes seem to be fine. I will let Bjorn comment on the patch flow. The only reason I had to use the clock in the driver was for the reset before, and hopefully this will allow me to actually switch to using pm_runtime API like I do with the rest of the TI remoteproc drivers (Keystone remoteproc driver also uses PSC for clock and reset but then it goes through different set of drivers). So, I see a mix of driver and dts patches in the series, are all the dts patches coming through Sekhar? regards Suman > > Thanks, > Bart > -- > To unsubscribe from this list: send the line "unsubscribe linux-remoteproc" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >