Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp1171513pxb; Sat, 30 Oct 2021 07:24:29 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwZGeP3owBSWJk7Co0kGmOg3LDAe0zK5nUxl7CwRX923WE1xkGkB7eccl8KHeXgVv1QrQca X-Received: by 2002:a05:6638:3052:: with SMTP id u18mr13263960jak.148.1635603869641; Sat, 30 Oct 2021 07:24:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635603869; cv=none; d=google.com; s=arc-20160816; b=olUlzOttN/HJkyPecUXHaL6+8xo5NjGw8eKHTzHBQIg310pfB192OplTiCKYkN9ANE nJZRqRE8UhU82uqLgSLvBFxRW6z8gypb440zd94JxAOzGeHgmXsLHdRYqTydVWXvjglV J2kYQ5O6bspfspHch2QRM5VlovOQpUDSLghW55hmNQ+U/gugnnPGYsitst7nmf3hRiNv srZAGiV9QbSn67KeyrBhdcGjLh6/je3c9GgT7GLs9w5WxwqTAeKEh3WcEMKZT2AChAUq VpSBYDAAIP09c1TJTUnwJbXtCfnSa8B3RMCds3PrB+sgH3YAI8nrQCGYuBt/jxm91faC xYUQ== 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=2X5YJfC5EItlH9jFztQTg0PcOzeEO1fDAz5we8++GiY=; b=eMYaXjIOSpB3Rf6+gAR/g6nC3FRTU7Npwd489MQqWJFW9jS+cCG3NxwoX3nigcNcQ9 Q+xQGQK07QTo9qDsqKL/VIIrjAlzC/z41MMQ3llrTYqM7Il2J2CIxV++N7LrTSQyE0bm OE4qpJN6LxyHDjf35G2B5YvXrG0hudWMfwb4MMzIYQAerBeRdJGHhvUhxlK7VCqmwAXF Q/JYNnN7jrDrkuVfLYtz+etu7Aex1MM1Q0+azBaJb8i8CbshOgN4x4CVI3oR2UdMPkCg USUi5VS4tXta4sA9ttAZQDq+XTrNVpnRMlmls3tdi/tyvJuMt0zzVhYSUcRKbTW7LsfE mPDQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=DTCl4uKh; 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 i12si13991249ilu.37.2021.10.30.07.24.18; Sat, 30 Oct 2021 07:24:29 -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=DTCl4uKh; 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 S230153AbhJ3OZ5 (ORCPT + 99 others); Sat, 30 Oct 2021 10:25:57 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49898 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229585AbhJ3OZy (ORCPT ); Sat, 30 Oct 2021 10:25:54 -0400 Received: from mail-ua1-x933.google.com (mail-ua1-x933.google.com [IPv6:2607:f8b0:4864:20::933]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 70B56C061570; Sat, 30 Oct 2021 07:23:24 -0700 (PDT) Received: by mail-ua1-x933.google.com with SMTP id i6so9349732uae.6; Sat, 30 Oct 2021 07:23:24 -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=2X5YJfC5EItlH9jFztQTg0PcOzeEO1fDAz5we8++GiY=; b=DTCl4uKh0judLjcX5ts/CnqE0z1+pHIvmxbPrm9qjNWUPUaIpb5juM6IqQpP2tTA3n FDwrPf6WiGmNKHWR1g9aFsqtGiWoylNL4xjCjOab1kJsXmSCl5R9hKG6BYL6vBX8FfCt 5HEmn7XEFkhI/nVdX5vpO/8EO/kIRwg6lUMRyuv0rQpEXL2PQczEFo5IPILiUjpwgI1O FxFHOF83Kyg5g2fqu442ApFy/CRd0Jvu9V14J1PAu4P/98c12CJzE7AwLFfy00X0GCwP 5r1y3eHR/Hgi1+PECLHcwyMYmM8P4DikrCu+P8gwSqRNHMcF6gTtnNDgRJ6EnfUcnMCh yQVg== 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=2X5YJfC5EItlH9jFztQTg0PcOzeEO1fDAz5we8++GiY=; b=R5NL2q6CPvfVSSrjarSEMw4VEVMw/AH8RV+2mytNlvtdRcvaXmZar+9BkoxN9c4HaO icGPEw6zrFh7qIiqI7t+sHuRt7A4Fu5slLbIJ5oKrWJMrNpYXaTmA61KOyk76aqV+Gs8 1hbpW6oGvI/X8EtMrj8gUzPQGUe2DAQZ0uj0ks5XxPO4PkorVNwcLHxyYD4rrwESpXPy 9pRpdJVI5z+U1+mR0tfoxJ+x1O8Y8OxujMpwgpJYLxZk7WV/5ZAEXbdwLymEGHbSc/ib GXSFA0YIOlDhtFn3IP9Kfh6ISqHYbhL6WWayt+YOqP6m1efBve/YyRlsK9TqH0LsADFM LegA== X-Gm-Message-State: AOAM530UfBJHOcInh4sE7pguG9rXY82aBcPCXj1oR62cPjj9KevEb5Yc jKvgsvzutzz8wZ4Mes3cP5yXSqe4elDmZiZS6qk= X-Received: by 2002:a67:ec57:: with SMTP id z23mr19405997vso.55.1635603803625; Sat, 30 Oct 2021 07:23:23 -0700 (PDT) MIME-Version: 1.0 References: <20211006112306.4691-1-sergio.paracuellos@gmail.com> In-Reply-To: From: Sergio Paracuellos Date: Sat, 30 Oct 2021 16:23:12 +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 Sun, Oct 17, 2021 at 8:51 AM Sergio Paracuellos wrote: > > 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. I have just sent v3 since PATCH 4 did not apply cleanly anymore in both clock tree and staging tree. Best regards, Sergio Paracuellos > > 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 > >