On Fri, Nov 12, 2021 at 2:20 PM Bjorn Helgaas <helgaas@xxxxxxxxxx> wrote: > > On Fri, Nov 12, 2021 at 01:25:11PM -0500, Jim Quinlan wrote: > > On Thu, Nov 11, 2021 at 5:17 PM Bjorn Helgaas <helgaas@xxxxxxxxxx> wrote: > > > On Wed, Nov 10, 2021 at 05:14:43PM -0500, Jim Quinlan wrote: > > > > Similar to the regulator bindings found in "rockchip-pcie-host.txt", this > > > > allows optional regulators to be attached and controlled by the PCIe RC > > > > driver. That being said, this driver searches in the DT subnode (the EP > > > > node, eg pci-ep@0,0) for the regulator property. > > > > > > > > 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/63 > > > > > > Can you use a lore URL here? github.com is sort of outside the Linux > > > ecosystem and this link is more likely to remain useful if it's to > > > something in kernel.org. > > Hi Bjorn, > > I'm afraid I don't know how or if this github repo transfers > > information to Linux. RobH, what should I be doing here? > > Does this change get posted to any mailing lists where people can > review it? devicetree-spec is where I direct folks to. It's not in lore, but we could add it I guess. But I take PRs too. There's so few other contributions I'm looking to make it as painless as possible for contributors. I'd be happy for more reviewers other than me, but I don't think where changes are posted is the problem there. :( Someone should review all the crap Python code I write too. Generally the flow is I redirect things submitted to the kernel to dtschema instead. So that review happens first at least. > Or would people have to watch the github devicetree-org > repo if they wanted to do that? I was assuming this pci-bus.yaml > change was something that would eventually end up in the Linux kernel > source tree, but dt-scheme doesn't seem to be based on Linus' tree, so > I don't know if there's a connection. It's more the other way around. The 'rule' is common bindings go in dtschema and device specific bindings in the kernel tree. Reality is some common bindings are in the kernel tree primarily because I want everything in dtschema dual licensed and relicensing is a pain. That's why we have pci.txt and pci-bus.yaml still. Rob
