From mboxrd@z Thu Jan 1 00:00:00 1970 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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 82E38C43334 for ; Mon, 13 Jun 2022 19:17:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=YCK8GKsWEyke2Od18AbpOPblYgfL584oOCcBwo++SR8=; b=U6X3mRkMEViQmx fgm/e9/eGZwM/PbEY/NnfEDfL47UxsrpLjhAtu57Cw2gqaZdga2A1TIoEX5zcJ3bj4ZVHa5HUALXP pkwSE7OgkI7ixnprZcz0ejsPIU/q43ZP2WG9EK58kSpDdHAlVkwZbFxZUcsSSKdPv+9IsToOKYB4n idmaHROc1SRhcuesSvL9ADXutu0Y4MkAz0IFdvpN/2WRcFcd74OuDCYrHLcYUwArZ2RnraX4HDhTf eaSZwu/ZjRMkOluYhFuXFn2Fl6+Z1Vp8BHbAwY73yoIDZlecnuJkXGaNlfLDZDV6EYyPNAr0DqFmN NR/isfhHOdTxttcOFFXQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1o0pXa-005I0A-MN; Mon, 13 Jun 2022 19:15:58 +0000 Received: from mail-io1-f44.google.com ([209.85.166.44]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1o0pXW-005Hzf-Oc for linux-arm-kernel@lists.infradead.org; Mon, 13 Jun 2022 19:15:56 +0000 Received: by mail-io1-f44.google.com with SMTP id e80so7131879iof.3 for ; Mon, 13 Jun 2022 12:15:53 -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:in-reply-to; bh=GEjnnN//JiCiI3GuISH4q5FQJvUbVSJXakhhE2GaPqM=; b=gRGWnoIKswKnuCV5lUvtQpAGJKe4EAnwFQ1MnnH10EiRh7ck2m/6/+7IpThlJ8/mev hT8GF3wQbCB7GxABSfJmUU58kicExTvrAiuWrlJdarXLzkVIiBgaPaNdmooJ8zx7xpAm WDOVwgSIZg8iLRSzBVXJFkCJpZER9BV9GZT1EwgOQw9jwWQysCefZQ3hprXrWCS+08hc 4mCGA2ghPww5voLITXRIjb/VzkgtkfTlFK92Raqxu5EqnJPI/+qDRWeL+j93hbhTavSy HHzLDf7ZwDoWInLeN/mFpFvVfyjSFqhZDaQIyui71Aoz+QZkKTTKL8HvVHrK55VH1cYX OPzQ== X-Gm-Message-State: AOAM532TkN84jx2lMMNsnffEMuINUGCIPOM2GvJMWRhwR4zolUEEqcIK UNt0jEVrEyMITh7IC8tDzg== X-Google-Smtp-Source: ABdhPJyN8sGx8YDVJ+QgIaLBk8J2Ux3lzoOGfBNp9bkBBkXjzA5iwt1QoG43IxfbO+ZX/BdUykJ0NA== X-Received: by 2002:a02:6619:0:b0:32e:25b7:d9ed with SMTP id k25-20020a026619000000b0032e25b7d9edmr771680jac.30.1655147752566; Mon, 13 Jun 2022 12:15:52 -0700 (PDT) Received: from robh.at.kernel.org ([64.188.179.251]) by smtp.gmail.com with ESMTPSA id d29-20020a023f1d000000b0032e5205f4e7sm678930jaa.4.2022.06.13.12.15.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 13 Jun 2022 12:15:52 -0700 (PDT) Received: (nullmailer pid 4108636 invoked by uid 1000); Mon, 13 Jun 2022 19:15:49 -0000 Date: Mon, 13 Jun 2022 13:15:49 -0600 From: Rob Herring To: Max Krummenacher Cc: max.krummenacher@toradex.com, Ulf Hansson , linux-pm@vger.kernel.org, Francesco Dolcini , Mark Brown , "Rafael J . Wysocki" , Kevin Hilman , Andrejs Cainikovs , Biju Das , Bjorn Andersson , Catalin Marinas , Dmitry Baryshkov , Fabio Estevam , Geert Uytterhoeven , Krzysztof Kozlowski , Marcel Ziswiler , NXP Linux Team , Pengutronix Kernel Team , Sascha Hauer , Shawn Guo , Vinod Koul , Will Deacon , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v1 0/5] power: domain: Add driver for a PM domain provider which controls Message-ID: <20220613191549.GA4092455-robh@kernel.org> References: <20220609150851.23084-1-max.oss.09@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220609150851.23084-1-max.oss.09@gmail.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220613_121554_842279_E3C06F40 X-CRM114-Status: GOOD ( 24.83 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Jun 09, 2022 at 05:08:46PM +0200, Max Krummenacher wrote: > From: Max Krummenacher > > its power enable by using a regulator. > > The currently implemented PM domain providers are all specific to > a particular system on chip. Yes, power domains tend to be specific to an SoC... 'power-domains' is supposed to be power islands in a chip. Linux 'PM domains' can be anything... > This series adds a PM domain provider driver which enables/disables > a regulator to control its power state. Additionally, marked with RFC, > it adds two commits which actually make use of the new driver to > instantiate a power domain provider and have a number of power > domain consumers use the power domain. > > The perceived use case is to control a common power domain used by > several devices for which not all device drivers nessesarily have > a means to control a regulator. Why wouldn't they have means? > It also handles the suspend / resume use case for such devices, > the generic power domain framework will disable the domain once the > last device has been suspend and will enable it again before resuming > the first device. > The generic power domain code handles a power domain consumer > generically outside of the driver's code. (assuming the 'power-domains' > property references exactly one power domain). That's Linux implementation details. > This allows to use the "regulator-pm-pd" driver with an arbitrary > device just by adding the 'power-domains' property to the devices > device tree node. However the device's dt-bindings schema likely does > not allow the property 'power-domains'. > One way to solve this would be to allow 'power-domains' globally > similarly how 'status' and other common properties are allowed as > implicit properties. No. For 'power-domains' bindings have to define how many there are and what each one is. Rob _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel