Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp3509532pxb; Mon, 4 Apr 2022 19:17:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwkbfJ/zFkSjFdfqi4MqpOG0PDEgJiZ2CxPdYG70ZTaQck3QppDg9zR7tiJhNd5k//H/ebn X-Received: by 2002:a63:9dc6:0:b0:398:6e02:c105 with SMTP id i189-20020a639dc6000000b003986e02c105mr953604pgd.495.1649125044128; Mon, 04 Apr 2022 19:17:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649125044; cv=none; d=google.com; s=arc-20160816; b=gbVGwQM1swvhM0dQT7X/Eidp2XUOCTC8RZM03eOXVAMTQNrwjNpcUiew+2ljGcZJvm UaaOqjNnnEMDLQs+O3/Lyjm20Eg3PYy8rKVv9nEEV6KhvaejawS/MWNWJn+XR41U6jDD PIiDIu/2LDj4VxxChmdzaYjGUJrXSHA7TJOQUGlAxt/qoEh72FiL8St9mgbhodsBdTiG ad+q6ugia4FvZrEMNIJ30k92gwa1M6dkVU2gztHIGTrxCepm6tHPZDz785ASBLN3mUFs +nFK9zFNHJcHYN+KCb5wF6gVF1fGb0V/dw6ZM1S2fVJpHXXGvxfy7J3zwxCSuQlObElk RJmw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=Gm8Q9IkyRhAeqdPU+N8JCDzIc1jnZK1MiElDRAVrowg=; b=sajEn1/8zXjvYW1otouoF9OHGnDAAjmpptWg7rkDonFo8e4d0YaDgrH+HSKgfgBjJ5 yFyiZlQRYacto5YCUb0M3w9GCK1tmY6hkkGdVmq7+WVTTHdZbeTog1YN0C7nWr13JneK 77O/5xjxfyKea4suAVpsipZBEho4V6bZ5dbowgQAncCBtao3d4VP2V+zbaOLfb6aSfEH ZFlVYy0RPk16ZQPWRIHPBf6B7FXJUh6hYLVKFJEgNFOEkBWHuf1x6FvE3KS9GWhrnUtP cjBpFsANATjZaY7g6qic4tZmJNZrU6GoZZe3o7mnE7ldSoUZC5UrWaFHBLO/KUxyDqhG /qUA== ARC-Authentication-Results: i=1; mx.google.com; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id q9-20020a170902c9c900b00156a87b3106si3806193pld.565.2022.04.04.19.17.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 04 Apr 2022 19:17:24 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id EC9532908B8; Mon, 4 Apr 2022 17:39:40 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234781AbiDDVwF (ORCPT + 99 others); Mon, 4 Apr 2022 17:52:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49346 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1379592AbiDDRng (ORCPT ); Mon, 4 Apr 2022 13:43:36 -0400 Received: from mail-oi1-f173.google.com (mail-oi1-f173.google.com [209.85.167.173]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 29ADE31DE7; Mon, 4 Apr 2022 10:41:39 -0700 (PDT) Received: by mail-oi1-f173.google.com with SMTP id 12so10784259oix.12; Mon, 04 Apr 2022 10:41:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=Gm8Q9IkyRhAeqdPU+N8JCDzIc1jnZK1MiElDRAVrowg=; b=IUBHRZUR1CP3Z09zzwDN8OLdIU3U07bDFgwfp9DzAfLqHZSjUyvTkYVKDifPWhJDEY HgqG9FLdyQi2fqiXqgbicwQbZMmFUM11LmAPO+n2SXPgHr9O0D6HSBmpoCMoVhyBIZDn 9Sk/WyQ9G4n2IGYP5rlMdVnx/1qlvpb293G/i8NtkNHMXb8KdLkxdaSJo6IUeLf3tmuX W+qOksGIRnDK41UUGBq8Y1YP+Uw1AGiHGySiPenYLMiCZr5mthIBFSUOAKJS7CO2oFe3 enx5ldHm+i9K15O0+x0RXLqcupcO+9KdXHTvYIMcm+F4ueuvTVb3F5ifLAlJJTqOvAe9 RBvQ== X-Gm-Message-State: AOAM531zyOtAi5B5SKJweFoAFCSTnnHGT4vx/JXULeGC/nShkQWZ+4Ns A8ISAZey8ULra68Ig6B0Mw== X-Received: by 2002:a05:6808:b0f:b0:2ec:f51d:ae0b with SMTP id s15-20020a0568080b0f00b002ecf51dae0bmr131491oij.67.1649094098466; Mon, 04 Apr 2022 10:41:38 -0700 (PDT) Received: from robh.at.kernel.org (66-90-144-107.dyn.grandenetworks.net. [66.90.144.107]) by smtp.gmail.com with ESMTPSA id r37-20020a05687108a500b000e20bfd86casm901587oaq.11.2022.04.04.10.41.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 04 Apr 2022 10:41:37 -0700 (PDT) Received: (nullmailer pid 1597042 invoked by uid 1000); Mon, 04 Apr 2022 17:41:37 -0000 Date: Mon, 4 Apr 2022 12:41:37 -0500 From: Rob Herring To: =?iso-8859-1?Q?Cl=E9ment_L=E9ger?= Cc: Philipp Zabel , Frank Rowand , Lars Povlsen , Steen Hegelund , UNGLinuxDriver@microchip.com, Thomas Petazzoni , Alexandre Belloni , Allan Nielsen , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH v2 0/3] add fwnode support to reset subsystem Message-ID: References: <20220324141237.297207-1-clement.leger@bootlin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220324141237.297207-1-clement.leger@bootlin.com> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI, RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 24, 2022 at 03:12:34PM +0100, Cl?ment L?ger wrote: > This series is part of a larger series which aims at adding fwnode > support in multiple subsystems [1]. The goal of this series was to > add support for software node in various subsystem but in a first > time only the fwnode support had gained consensus and will be added > to multiple subsystems. The goal is describing a solution. What is the problem? What's the scenario where you have a reset provider not described by firmware providing resets to devices (consumers) also not described by firmware. > For the moment ACPI node support is excluded from the fwnode support > to avoid creating an unspecified ACPI reset device description. With > these modifications, both driver that uses the fwnode_ API or the of_ > API to register the reset controller will be usable by consumer > whatever the type of node that is used. Good, because controlling reset lines directly isn't how the ACPI device model works AFAIK. > One question raised by this series is that I'm not sure if all reset > drivers should be modified to use the new fwnode support or keep the > existing device-tree support. Maintainer advice on that particular > question will be welcome. That would be pointless churn IMO. Why do we need to convert drivers which the vast majority will never use anything but DT? Rob