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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 96601C433F5 for ; Tue, 16 Nov 2021 17:41:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 73BCF61BD4 for ; Tue, 16 Nov 2021 17:41:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238937AbhKPRod (ORCPT ); Tue, 16 Nov 2021 12:44:33 -0500 Received: from mail.kernel.org ([198.145.29.99]:45076 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238906AbhKPRod (ORCPT ); Tue, 16 Nov 2021 12:44:33 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 2661061BE6; Tue, 16 Nov 2021 17:41:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1637084496; bh=SUZXJmH/OIl6JJgyk34glFwLEwzwnUjrD36f2aUaAJw=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=WSw0FZmjm28lW2YpaJPPVxQecnmroHqZ8c2cmVouFMWnEATQk1WPCO0d5XisP94fk /6l+o1NIt4fZoY/i15bf/vJjwSoIF11MQezXxIgTTkMqMLBIkqL22t1EsXjHpjeZbl Rl3Br3cN/aZffB+NQVo5IRINh9w0rO3HrXvUJjZ/RdJKShkjvJx7vK8b/aDZIjknU+ S655gaKDzq4j8Yklf6MT2lH+83xVn1uvzuGswHuwMixyMYgC8DpoHbiXX9hlANpWE2 mzcaP/wGUeCMMJzRAeUAoNVSH6EbZu3Rz4H6OSeV0QJSfjx58yN5Gnt0PuPDVx1drM u9sFxoA5ND60Q== Received: by mail-ed1-f50.google.com with SMTP id z5so31467259edd.3; Tue, 16 Nov 2021 09:41:36 -0800 (PST) X-Gm-Message-State: AOAM5337FW1u0714jDMYMkeiZQ3S+SL3CFw8lskG1f9T89/N2XoR14iw W6V0ePuriCIyxa/sTARymZg0UP0BvPWqqAldAw== X-Google-Smtp-Source: ABdhPJyPdHpMtvWV4K8vxUNIGAXaUuvPJGm5qvH4fNjo7NkpHLg/mCNjx6oT6P4Sz3PJuwDjEdAC6OPH8Q9nmGs08dU= X-Received: by 2002:a17:907:a411:: with SMTP id sg17mr12160289ejc.84.1637084494387; Tue, 16 Nov 2021 09:41:34 -0800 (PST) MIME-Version: 1.0 References: <20211110221456.11977-1-jim2101024@gmail.com> <20211110221456.11977-6-jim2101024@gmail.com> In-Reply-To: From: Rob Herring Date: Tue, 16 Nov 2021 11:41:22 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v8 5/8] PCI/portdrv: add mechanism to turn on subdev regulators To: Jim Quinlan , =?UTF-8?Q?Pali_Roh=C3=A1r?= Cc: Jim Quinlan , PCI , Bjorn Helgaas , Nicolas Saenz Julienne , Mark Brown , "maintainer:BROADCOM BCM7XXX ARM ARCHITECTURE" , Sean V Kelley , Jonathan Cameron , Qiuxu Zhuo , Keith Busch , open list Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org +Pali On Mon, Nov 15, 2021 at 2:44 PM Jim Quinlan wrote: > > On Thu, Nov 11, 2021 at 5:57 PM Rob Herring wrote: > > > > On Wed, Nov 10, 2021 at 4:15 PM Jim Quinlan wrote: > > > > > > Adds a mechanism inside the root port device to identify standard PCIe > > > regulators in the DT, allocate them, and turn them on before the rest of > > > the bus is scanned during pci_host_probe(). A root complex driver can > > > leverage this mechanism by setting the pci_ops methods add_bus and > > > remove_bus to pci_subdev_regulators_{add,remove}_bus. > > > > > > The allocated structure that contains the regulators is stored in > > > dev.driver_data. > > > > > > The unabridged reason for doing this is as follows. We would like the > > > Broadcom STB PCIe root complex driver (and others) to be able to turn > > > off/on regulators[1] that provide power to endpoint[2] devices. Typically, > > > the drivers of these endpoint devices are stock Linux drivers that are not > > > aware that these regulator(s) exist and must be turned on for the driver to > > > be probed. The simple solution of course is to turn these regulators on at > > > boot and keep them on. However, this solution does not satisfy at least > > > three of our usage modes: > > > > > > 1. For example, one customer uses multiple PCIe controllers, but wants the > > > ability to, by script invoking and unbind, turn any or all of them by and > > > their subdevices off to save power, e.g. when in battery mode. > > > > > > 2. Another example is when a watchdog script discovers that an endpoint > > > device is in an unresponsive state and would like to unbind, power toggle, > > > and re-bind just the PCIe endpoint and controller. > > > > > > 3. Of course we also want power turned off during suspend mode. However, > > > some endpoint devices may be able to "wake" during suspend and we need to > > > recognise this case and veto the nominal act of turning off its regulator. > > > Such is the case with Wake-on-LAN and Wake-on-WLAN support where PCIe > > > end-point device needs to be kept powered on in order to receive network > > > packets and wake-up the system. > > > > > > In all of these cases it is advantageous for the PCIe controller to govern > > > the turning off/on the regulators needed by the endpoint device. The first > > > two cases can be done by simply unbinding and binding the PCIe controller, > > > if the controller has control of these regulators. > > > > > > [1] These regulators typically govern the actual power supply to the > > > endpoint chip. Sometimes they may be a the official PCIe socket > > > power -- such as 3.3v or aux-3.3v. Sometimes they are truly > > > the regulator(s) that supply power to the EP chip. > > > > > > [2] The 99% configuration of our boards is a single endpoint device > > > attached to the PCIe controller. I use the term endpoint but it could > > > possible mean a switch as well. > > > > > > Signed-off-by: Jim Quinlan > > > --- > > > drivers/pci/bus.c | 72 ++++++++++++++++++++++++++++++++++ > > > drivers/pci/pci.h | 8 ++++ > > > drivers/pci/pcie/portdrv_pci.c | 32 +++++++++++++++ > > > 3 files changed, 112 insertions(+) > > > > > > diff --git a/drivers/pci/bus.c b/drivers/pci/bus.c > > > index 3cef835b375f..c39fdf36b0ad 100644 > > > --- a/drivers/pci/bus.c > > > +++ b/drivers/pci/bus.c > > > @@ -419,3 +419,75 @@ void pci_bus_put(struct pci_bus *bus) > > > if (bus) > > > put_device(&bus->dev); > > > } > > > + > > > +static void *alloc_subdev_regulators(struct device *dev) > > > +{ > > > + static const char * const supplies[] = { > > > + "vpcie3v3", > > > + "vpcie3v3aux", > > > + "vpcie12v", > > > + }; > > > + const size_t size = sizeof(struct subdev_regulators) > > > + + sizeof(struct regulator_bulk_data) * ARRAY_SIZE(supplies); > > > + struct subdev_regulators *sr; > > > + int i; > > > + > > > + sr = devm_kzalloc(dev, size, GFP_KERNEL); > > > + > > > + if (sr) { > > > + sr->num_supplies = ARRAY_SIZE(supplies); > > > + for (i = 0; i < ARRAY_SIZE(supplies); i++) > > > + sr->supplies[i].supply = supplies[i]; > > > + } > > > + > > > + return sr; > > > +} > > > + > > > + > > > +int pci_subdev_regulators_add_bus(struct pci_bus *bus) > > > +{ > > > + struct device *dev = &bus->dev; > > > + struct subdev_regulators *sr; > > > + int ret; > > > + > > > + if (!pcie_is_port_dev(bus->self)) > > > + return 0; > > > + > > > + if (WARN_ON(bus->dev.driver_data)) > > > + dev_err(dev, "multiple clients using dev.driver_data\n"); > > > + > > > + sr = alloc_subdev_regulators(&bus->dev); > > > + if (!sr) > > > + return -ENOMEM; > > > + > > > + bus->dev.driver_data = sr; > > > + ret = regulator_bulk_get(dev, sr->num_supplies, sr->supplies); > > > + if (ret) > > > + return ret; > > > + > > > + ret = regulator_bulk_enable(sr->num_supplies, sr->supplies); > > > + if (ret) { > > > + dev_err(dev, "failed to enable regulators for downstream device\n"); > > > + return ret; > > > + } > > > + > > > + return 0; > > > +} > > > +EXPORT_SYMBOL_GPL(pci_subdev_regulators_add_bus); > > > > Can't these just go in the portdrv probe and remove functions now? > > > > Rob > > Not really. The idea is that only when a host controller driver does this > > static struct pci_ops my_pcie_ops = { > .add_bus = pci_subdev_regulators_add_bus , /* see note below */ > .remove_bus = pci_subdev_regulators_remove_bus, > ... > } > > does it explicitly want this feature. Without doing this, every PCI > port in the world will execute a devm_kzalloc() and > devm_regulator_bulk_get() to (likely) grab nothing, and then there > will be three superfluous lines in the boot log: You can opt-in based on there being a DT node. > pci_bus 0001:01: 0001:01 supply vpcie12v not found, using dummy regulator > pci_bus 0001:01: 0001:01 supply vpcie3v3 not found, using dummy regulator > pci_bus 0001:01: 0001:01 supply vpcie3v3aux not found, using dummy regulator This would be annoying, but not really a reason for how to design this. > Secondly, our HW needs to know when the alloc/get/enable of > regulators is done so that the PCIe link can then be attempted. This > is pretty much the cornerstone of this patchset. To do this the brcm > RC driver's call to pci_subdev_regulators_add_bus() is wrapped by > brcm_pcie_add_bus() so that we can do this: > > static struct pci_ops my_pcie_ops = { > .add_bus = brcm_pcie_add_bus , /* calls pci_subdev_regulators_add_bus() */ > .remove_bus = pci_subdev_regulators_remove_bus, Do add_bus/remove_bus get called during resume/suspend? If not, how do you handle the link during resume? Maybe there needs to be explicit hooks for link handling. Pali has been looking into this some. Rob