Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp5357219pxb; Sun, 6 Feb 2022 23:24:45 -0800 (PST) X-Google-Smtp-Source: ABdhPJyxl3fK8PAGDSzG6QCgTIYCkVzolVjswFi+2SCfkeET4PFWWq2TOdDwlgAD+5JVWzWrRDL2 X-Received: by 2002:a17:907:7ba0:: with SMTP id ne32mr9096905ejc.540.1644218685183; Sun, 06 Feb 2022 23:24:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644218685; cv=none; d=google.com; s=arc-20160816; b=pHw47J3zBD+2NSyvBjAj7zV8BVbVYKlduQnEA7rc/jHlx3Q5+dplDRThZ7ELPCtFjo 1e8fUDgvv9UOEysrzBrXSb8MwFl3d1pYzsQ6o0ILMT35NDoYk4mYbiUlKvYOQss32U6+ gAW+m16izQ+hxyPW4ujRML9XnOc5CDxUUC1/OFLDJ8mJY17wQXimMiFu+cSgqaMUbKL3 FPCviuq1qqw7qgTpcIhqx8Ti6pxjXjRxxxKGWUOw08lgKcx0OsCdAAwdzd4nQsgka/44 1jVXXKVc3WiRplP9KQBp9Ww3dL4hArJcHEt3XKdyQOevORzq+T0pRerHSg57gpmRi7rI JzRA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:user-agent:date:to:cc:from:subject :references:in-reply-to:content-transfer-encoding:mime-version :dkim-signature; bh=aIvClW/a5UB3hYudC+FS6qKEAip0bPSsL77pzYjT72M=; b=DdMl1x41tTwmDNheUd2/XMf5g0Xx591g/DgdfmDTPtWF1roiIfLVdYPSPQzXZRJry0 bnlPtRKgs+zKTCkvH4MgUqoYqmiVoVt0/Avrp9vbOJOjXxceLHlzLzDtIl6e5h6J04Nc dJwmhVbMBVVKPZITS16fTlOy+whCmnnLYd0gB4ia6+7MAaYvE2FGnGpAy2oR4ZP+5UWz faAIb+56oPQxx/k6jALUpqtaOKlc+HIL1xRQneHO7xJxXT701/FgJcbFlH35x8c7djcy YZbozLoi9i8hucTk7+rC63nqc6lA2O6/r+D4lJ9gcyyxtRLWRmCAhlsaS3TgZVZTAKTb cC3Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=uG+rJszu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id cw22si7853907ejc.925.2022.02.06.23.24.20; Sun, 06 Feb 2022 23:24:45 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=uG+rJszu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1378923AbiBECzu (ORCPT + 99 others); Fri, 4 Feb 2022 21:55:50 -0500 Received: from dfw.source.kernel.org ([139.178.84.217]:51762 "EHLO dfw.source.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229807AbiBECzt (ORCPT ); Fri, 4 Feb 2022 21:55:49 -0500 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 59F8160C55; Sat, 5 Feb 2022 02:55:49 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id AA1BBC004E1; Sat, 5 Feb 2022 02:55:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1644029748; bh=BQUS4mKdVMdQIuKV+9qmm5n95QdGCKeA5gbAJQNI5a4=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=uG+rJszuNbiwN9nUKvB9AHrWF0wucl97LlmgSUSQEEq5PyV981G+OfIz3c3Atba61 djk0cQoGfBOaqu2Yn4R7sqUuHXAHGzcXFGMDgVTN1mV74Swe/unZspxgfOEhkrbMrb pSHzBpWHyqt1h8rPjVnyZoCLrplCSwyz9Nf8QIRSGgyRGmO1nBnsDcqthzRd/x5i9r kq1UijJ1KPzqINzfjJR2egFHt8gjXUrRnI+G3AHRiu+pqYK5czmRDhj9ygQa9BbLVt Bwz93TBtA7IthgukYw1IRXJAt5oEd1gtLimfGDo1ehJX2fZSxzSosVHqHuiCHBKbfG KGW9zrHXn0okg== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: References: <20220110114930.1406665-1-sergio.paracuellos@gmail.com> Subject: Re: [PATCH v8 0/4] clk: ralink: make system controller a reset provider From: Stephen Boyd Cc: , John Crispin , linux-staging@lists.linux.dev, NeilBrown , Philipp Zabel , linux-kernel To: Greg KH , Sergio Paracuellos Date: Fri, 04 Feb 2022 18:55:46 -0800 User-Agent: alot/0.10 Message-Id: <20220205025548.AA1BBC004E1@smtp.kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Sergio Paracuellos (2022-01-26 04:45:31) > On Wed, Jan 26, 2022 at 1:14 PM Greg KH wrot= e: > > > > On Wed, Jan 26, 2022 at 01:08:52PM +0100, Sergio Paracuellos wrote: > > > On Wed, Jan 26, 2022 at 1:06 PM Greg KH = wrote: > > > > > > > > On Mon, Jan 10, 2022 at 12:49:26PM +0100, Sergio Paracuellos wrote: > > > > > Hi all, > > > > > > > > > > This patch series add minimal change to provide mt7621 resets pro= perly > > > > > defining them in the 'mediatek,mt7621-sysc' node which is the sys= tem > > > > > controller of the SoC and is already providing clocks to the rest= of > > > > > the world. > > > > > > > > > > There is shared architecture code for all ralink platforms in 're= set.c' > > > > > file located in 'arch/mips/ralink' but the correct thing to do to= align > > > > > hardware with software seems to define and add related reset code= to the > > > > > already mainlined clock driver. > > > > > > > > > > After this changes, we can get rid of the useless reset controlle= r node > > > > > in the device tree and use system controller node instead where t= he property > > > > > '#reset-cells' has been added. Binding documentation for this nod= eq has > > > > > been updated with the new property accordly. > > > > > > > > > > This series also provide a bindings include header where all rela= ted > > > > > reset bits for the MT7621 SoC are defined. > > > > > > > > > > Also, please take a look to this review [0] to understand better = motivation > > > > > for this series. > > > > > > > > > > Regarding the way of merging this: > > > > > - I'd like patches 1 and 4 which are related going through stagi= ng tree. > > > > > > > > Patches 1 and 4 now in the staging tree, thanks. > > > > > > Stephen wanted all to go through the CLK tree since PATCH 3 and 1 were > > > also a dependency... Can we get all of them through the same tree, > > > then? I am ok with both CLK or staging trees. > > > > That's fine with me if they all go through the CLK tree, but there will > > be a merge issue that I already fixed up in my tree. If you want me to > > drop them, just let me know. >=20 > Stephen, what do you prefer? Is it better all going through staging-tree = then? >=20 Sure take them through staging tree. Acked-by: Stephen Boyd