Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp2618390pxb; Sun, 17 Oct 2021 20:40:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJznMEimElJ0rOEERF4WEGc2M8yS8EMlaPrEnbmgYZy7vmOUdZxGCMAf1EJ5ly05u8Rw+8se X-Received: by 2002:a17:902:d353:b0:13f:a15d:3d71 with SMTP id l19-20020a170902d35300b0013fa15d3d71mr11920869plk.77.1634528432373; Sun, 17 Oct 2021 20:40:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634528432; cv=none; d=google.com; s=arc-20160816; b=c6Y+kG4k9AP1LfepqU3hisyz2dYpnIn3jpA9T7iMZlNs9TVb3eMTejWuORdmCX4I04 6FX3gepCNLCZ5SM8GbQhfSkSY6gw6WpEouh9ry9Oiuv6ySoY+Ei72A8fAnFUmmKufGSz H6Xdvw3orKRQDvsYwY1tQCmGb+c/eTVP+h3LpSPRzbNeLNEJcik4qPaz4ZxvYYcC7y/Q OouEGs3jiVRxAUy+mEFdh94egHmivcTekC70wIBeYiTdoqVT5NLU6spmm4vNtCPOoVMd QkuQR6vhGZ5gE2/E/900O/NVP78btWrKsNKN+0rCfOXSGKvGVlEtdkroM5B8xPB75h/H lB8A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=zNAUH8TjDFzaFJVIqct55AXw+xWzukjzRr3h7rQ5J3g=; b=ReqiGSxYYwqAeZu5wsN5UpLm4lkkGc9IQpjU5nSNeaXa6ZkC8++eodmE2T43qKB7Ys yYszyRfZMsxI10VH+MVDp56Llc0XQPxD/nFgtAKNPXVBN+fPb5HjxK1faXRIOZyVsIPc t5IOgLpxANY2fmdD/5KqvZqIKZ9WOAKkTPl5LCRfHKK7HwN4cPlwQVcJvmxOJfMw89qM SBrhbkKmElz/M3e6i9gLmOov2NVElE3SkN146XOjKMlcrypIjVk4amWIk2cdvhX1JZGz 4BnX7AG+ITv9+MS1EedanJoD25OXiEJAX6jvsHHyfOQSUDaBO5K8BMY/DWWoSy3zTwsd /aHQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=jJnBGNwZ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f126si2301690pfg.59.2021.10.17.20.40.18; Sun, 17 Oct 2021 20:40:32 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=jJnBGNwZ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S245001AbhJQGxr (ORCPT + 98 others); Sun, 17 Oct 2021 02:53:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51096 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232431AbhJQGxq (ORCPT ); Sun, 17 Oct 2021 02:53:46 -0400 Received: from mail-vk1-xa2a.google.com (mail-vk1-xa2a.google.com [IPv6:2607:f8b0:4864:20::a2a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EC12EC061765; Sat, 16 Oct 2021 23:51:36 -0700 (PDT) Received: by mail-vk1-xa2a.google.com with SMTP id 34so7125793vkl.13; Sat, 16 Oct 2021 23:51:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zNAUH8TjDFzaFJVIqct55AXw+xWzukjzRr3h7rQ5J3g=; b=jJnBGNwZTUy94l7GdW/7dM0ak1B4tPtJ3KhbRlQWbODnhUIthJ12JuiiwR4fKmuJtO 9LSrUXAmgtlcTCB7za3Rsi2OLP1C15ibRn3HKP9pDc3QT5Ujzy3Ijt2qvBNFobY8NAF8 RPULzytg0lGnBxU88Q7L/z8VwEAQ6hLlpG3npFUhgmC9SgCtNCmifibrxRemZnsrHMHG lgnpgnO7VizudOxTfl83luUQu4YeqNl9uINzRNw195NY+Ywd7ajrGsrMCsU0PucP+nrQ zbuxQRL/VBUd0kqghB1nTWEq2DI7EidGIdaoY09/XTnUcr/OfDUwWzoi0oNP+6jbAdcP ktuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zNAUH8TjDFzaFJVIqct55AXw+xWzukjzRr3h7rQ5J3g=; b=InEbvgm+roHe39skgBaAg4prwZNu3NSM8jvvPrRVywPfCrULd3twy4Ve2M/CvqywWY SN+9n9tD5vw+Y/SlZpFihRtqDHEwZISRYNGyLwdfTknHqDQA8XC8wJ0Z1lGphx6vP3TV E3wyZGZYul2/jKBl0yEXbFzn7i/2MA8h8ui5RwTVHlu4iHpN+zi4KDoVi6QkFEceClSo bT9CRV11A8l1AX+eJzxm2COP+Y7FGQQHxTORh1VLcdwPPZmdD2GdWqQrsUY6Xh2bOeVF c3YN/VhBZHJ1JqxYX+GlWAM0Ig2y/WpXZKgsTahhgRLaN36y1BEdM7J51eLP+xYT3Pw2 iO7A== X-Gm-Message-State: AOAM531GsORYcuTwfnXFI3OZx9F90DlRc7jEj2MPmm58H4N0wM6GtEDZ k3+E+xEatjEf1uPrYVwVlQ8bk8kBxUGKkNyeaVg= X-Received: by 2002:a05:6122:d06:: with SMTP id az6mr444750vkb.17.1634453495343; Sat, 16 Oct 2021 23:51:35 -0700 (PDT) MIME-Version: 1.0 References: <20211006112306.4691-1-sergio.paracuellos@gmail.com> In-Reply-To: <20211006112306.4691-1-sergio.paracuellos@gmail.com> From: Sergio Paracuellos Date: Sun, 17 Oct 2021 08:51:24 +0200 Message-ID: Subject: Re: [PATCH v2 0/4] clk: ralink: make system controller a reset provider To: Stephen Boyd Cc: "open list:COMMON CLK FRAMEWORK" , Greg KH , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Rob Herring , linux-staging@lists.linux.dev, NeilBrown , linux-kernel , John Crispin Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stephen, On Wed, Oct 6, 2021 at 1:23 PM Sergio Paracuellos wrote: > > Hi all, > > This patch series add minimal change to provide mt7621 resets properly > defining them in the 'mediatek,mt7621-sysc' node which is the system > 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 'reset.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 controller node > in the device tree and use system controller node instead where the property > '#reset-cells' has been added. Binding documentation for this nodeq has > been updated with the new property accordly. > > This series also provide a bindings include header where all related > reset bits for the MT7621 SoC are defined. > > Also, please take a look to this review [0] to understand better motivation > for this series. > > Thanks in advance for your feedback. > > Changes in v2: > - Address review comments of Dan Carpenter [1]: > + Avoid 'inline' in function definition. > + Return proper error codes (-EINVAL) instead of '-1'. > + Make use of 'devm_kzalloc' instead of 'kzalloc'. Can you please take a look into this series? I'd like them to be added in the next merge window and if something needs to be changed I'd like to have a bit of time to do it :)). Regarding how to merge this I guess all of the patches should apply cleanly in any tree but since there are already changes in mt7621-dts maybe patches 1 and 4 which are related can go through the staging tree (if Greg is ok with this) and the bindings doc change and driver changes (patches 2 and 3) can go through your tree. Thanks in advance for your time. Best regards, Sergio Paracuellos > > Best regards, > Sergio Paracuellos > > [0]: https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20210926145931.14603-3-sergio.paracuellos@gmail.com/ > [1]: https://lkml.org/lkml/2021/10/6/204 > > Sergio Paracuellos (4): > dt-bindings: reset: add dt binding header for Mediatek MT7621 resets > dt-bindings: clock: mediatek,mt7621-sysc: add '#reset-cells' property > clk: ralink: make system controller node a reset provider > staging: mt7621-dts: align resets with binding documentation > > .../bindings/clock/mediatek,mt7621-sysc.yaml | 12 +++ > drivers/clk/ralink/clk-mt7621.c | 79 +++++++++++++++++++ > drivers/staging/mt7621-dts/mt7621.dtsi | 27 +++---- > include/dt-bindings/reset/mt7621-reset.h | 37 +++++++++ > 4 files changed, 140 insertions(+), 15 deletions(-) > create mode 100644 include/dt-bindings/reset/mt7621-reset.h > > -- > 2.33.0 >