Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 667E7C433FE for ; Mon, 10 Jan 2022 10:59:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244342AbiAJK7i (ORCPT ); Mon, 10 Jan 2022 05:59:38 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41888 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244347AbiAJK7f (ORCPT ); Mon, 10 Jan 2022 05:59:35 -0500 Received: from mail-ua1-x92f.google.com (mail-ua1-x92f.google.com [IPv6:2607:f8b0:4864:20::92f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EF389C06173F; Mon, 10 Jan 2022 02:59:34 -0800 (PST) Received: by mail-ua1-x92f.google.com with SMTP id h11so703100uar.5; Mon, 10 Jan 2022 02:59:34 -0800 (PST) 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=Pyr2Zb4j02PsgvvNoNyOvWlod9U9+4JSnC74+5rak8Q=; b=YyQ506hwqXXe8clqnSFa983M9zu/XTmA4qYrFQNJpM+4qoeJFvFIvdzPLl4VJVyctv QqAXW2hrYyksTQGMFAXkpU91IH/VLZihHw79TpCMMAMgMJco1v9puEJXk7+lhemAKas1 V+NeVQ0iZyy7rRoR/Zu8CKDxjLP64FPfc8jbDNYsSqLD9XsXEEPtkOjoSyuGM9fkiS6u Cy0LEZSSUmzaABRV0HfjrGMB30xYKwUSiksibyHJ29eQpavDM7+do/jySLVE5MIjOkDf FowiZnoXk6zgwYHZvit5AxB0G83ZXFa3rmK5VmxrpfBGz+QK5Ol9Q7XUHMcfIl4kHSgH jKIw== 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=Pyr2Zb4j02PsgvvNoNyOvWlod9U9+4JSnC74+5rak8Q=; b=1wlWjF0H7I9wTaE9qgc0JuNvTAC9bGumZCibpWEwPRmsmJ0/rMt7PHoupSVVME/HHf /h8FRcMsJR1gCyRpEF657aFsC+if9ujL71bTffGD/89V7I91jfANptHUxuQCZD55ieep O87TE0U/WC5B8lJJKdFUhskU6h0F0vkumbro/JFb5xP7YWKsTm2QdbaiWMxibOje4nqw DaAj6AwgBIScdN5RlHYCMngfRVKYontS3uO+lrkc8DCc2JUrOdAfPcI+4TiPlJ9RG7PH 5j1F+KhyQFL2EXhkS0wce9YMsW37uOreJOi6SHtGMJRoH+KZKpr1vbbFW0tuXA9WKKTg RcDg== X-Gm-Message-State: AOAM530sGryHtKbI0yUHMA92b+oNKqfsG6K0L6pK+w3sXOoRt/dCetlg T1xUQ/9BWxq7nWQSZU1yZoEy/F9iJqfo19R521U= X-Google-Smtp-Source: ABdhPJzNC5Xto+6tTHLSaWjQV0UE4a2ufJIsEM38VWdwK4FT0ZrmU5mE9sbtMvpdllGygej3DVycShZmNO0+zFIeetc= X-Received: by 2002:a05:6102:dc9:: with SMTP id e9mr24288454vst.17.1641812374133; Mon, 10 Jan 2022 02:59:34 -0800 (PST) MIME-Version: 1.0 References: <20220110083910.1351020-1-sergio.paracuellos@gmail.com> <20220110083910.1351020-4-sergio.paracuellos@gmail.com> <5368e89c391e1329ed2be6496655f1bb50acfd19.camel@pengutronix.de> <12b7e367e8323f6da7bb548dbbae0d342608e52b.camel@pengutronix.de> In-Reply-To: <12b7e367e8323f6da7bb548dbbae0d342608e52b.camel@pengutronix.de> From: Sergio Paracuellos Date: Mon, 10 Jan 2022 11:59:22 +0100 Message-ID: Subject: Re: [PATCH v6 3/4] clk: ralink: make system controller node a reset provider To: Philipp Zabel Cc: "open list:COMMON CLK FRAMEWORK" , John Crispin , linux-staging@lists.linux.dev, Greg KH , NeilBrown , linux-kernel , Stephen Boyd Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 10, 2022 at 11:23 AM Philipp Zabel wrote: > > On Mon, 2022-01-10 at 10:39 +0100, Sergio Paracuellos wrote: > [...] > > > Is this known to work for all possible users, without delay between > > > assert and deassert? > > > > It seems it is. This is based on the original reset implementation for > > ralink. See: > > > > https://elixir.bootlin.com/linux/v5.16/source/arch/mips/ralink/reset.c#L55 > > > > > Are there any users of the reset_control_reset() API at all? This API > > > was added for self-clearing reset bits, so if there are no users that > > > need to pretend this is a reset pulse at the hardware level (there may > > > be), I'd prefer if this was just left out. > > > > I am not following you here. What do you mean? > > Looking at drivers/staging/mt7621-dts/mt7621.dtsi, it appears the > current reset users are: > mediatek,mt7621-i2c > ralink,mt7621-spi > ralink,rt3883-gdma > mediatek,mt7621-hsdma > mediatek,mt7621-eth > mediatek,mt7621 > mediatek,mt7621-pci > > Many of the corresponding drivers use device_reset(), which is a > shorthand for requesting a reset control and calling > reset_control_reset() on it. That will call mt7621_reset_device, so it > is indeed used. > Ok, pretty clear now, thanks for clarification :). > regards > Philipp Best regards, Sergio Paracuellos