lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 22 Oct 2021 15:24:50 -0400 From: Jim Quinlan <james.quinlan@...adcom.com> To: Mark Brown <broonie@...nel.org>, Rob Herring <robh@...nel.org> Cc: Jim Quinlan <jim2101024@...il.com>, "open list:PCI NATIVE HOST BRIDGE AND ENDPOINT DRIVERS" <linux-pci@...r.kernel.org>, Nicolas Saenz Julienne <nsaenz@...nel.org>, "maintainer:BROADCOM BCM7XXX ARM ARCHITECTURE" <bcm-kernel-feedback-list@...adcom.com>, Florian Fainelli <f.fainelli@...il.com>, Bjorn Helgaas <bhelgaas@...gle.com>, Rob Herring <robh+dt@...nel.org>, Saenz Julienne <nsaenzjulienne@...e.de>, "moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE" <linux-arm-kernel@...ts.infradead.org>, "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE" <linux-rpi-kernel@...ts.infradead.org>, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" <devicetree@...r.kernel.org>, open list <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v5 1/6] dt-bindings: PCI: Add bindings for Brcmstb EP voltage regulators On Fri, Oct 22, 2021 at 10:49 AM Mark Brown <broonie@...nel.org> wrote: > > On Fri, Oct 22, 2021 at 10:06:54AM -0400, Jim Quinlan wrote: > > > The use of a regulator property in the pcie EP subnode such as > > "vpcie12v-supply" depends on a pending pullreq to the pci-bus.yaml > > file at > > > > https://github.com/devicetree-org/dt-schema/pull/54 > > This contains updates to add the generic PCIe supply rails, not the > brcm-ep-a and brcm-ep-b supplies (which as I said on the other patch > look like they ought to be renamed). That's fine since they're > obviously not generic PCIe things but this means that those bindings > need to be added to the device specific bindings here. Currently > there's only an update to the examples. Just to be clear, and assuming that the brcm-ep-[ab] supply names are green-lighted by you and Rob, are you saying I have to update the github site or our YAML file? If the latter, it seems odd to be describing an EP-device property in the YAML for an RC driver since the github site already describes the EP-device. Jim
Powered by blists - more mailing lists