From: Bjorn Helgaas <helgaas@kernel.org>
To: Meng Li <Meng.Li@windriver.com>
Cc: geert+renesas@glider.be, magnus.damm@gmail.com,
robh+dt@kernel.org, marek.vasut+renesas@gmail.com,
yoshihiro.shimoda.uh@renesas.com, lorenzo.pieralisi@arm.com,
kw@linux.com, bhelgaas@google.com, lgirdwood@gmail.com,
broonie@kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] pci: pcie-rcar: add regulators support
Date: Tue, 19 Oct 2021 08:30:07 -0500 [thread overview]
Message-ID: <20211019133007.GA2331336@bhelgaas> (raw)
In-Reply-To: <20211019095858.21316-1-Meng.Li@windriver.com>
On Tue, Oct 19, 2021 at 05:58:58PM +0800, Meng Li wrote:
> From: Andrey Gusakov <andrey.gusakov@cogentembedded.com>
>
> Add PCIe regulators for KingFisher board.
Please pay attention to the existing code and history. Your current
subject line is:
pci: pcie-rcar: add regulators support
which looks nothing like the history:
$ git log --oneline drivers/pci/controller/pcie-rcar-host.c
861e133ba268 ("PCI: rcar-host: Remove unneeded includes")
a115b1bd3af0 ("PCI: rcar: Add L1 link state fix into data abort hook")
d21faba11693 ("PCI: Bulk conversion to generic_handle_domain_irq()")
83ed8d4fa656 ("PCI: rcar: Convert to MSI domains")
93cd1bb4862d ("PCI: rcar: Don't allocate extra memory for the MSI capture address")
c4e0fec2f7ee ("PCI: rcar: Always allocate MSI addresses in 32bit space")
6e8e137abeab ("PCI: rcar: Drop unused members from struct rcar_pcie_host")
b64aa11eb2dd ("PCI: Set bridge map_irq and swizzle_irq to default functions")
669cbc708122 ("PCI: Move DT resource setup into devm_pci_alloc_host_bridge()")
b411b2e1adb9 ("PCI: rcar: Use struct pci_host_bridge.windows list directly")
61f11f8250e2 ("PCI: rcar: Use devm_pci_alloc_host_bridge()")
4f5c883d7815 ("PCI: Move setting pci_host_bridge.busnr out of host drivers")
6176a5f32751 ("PCI: rcar: Use pci_is_root_bus() to check if bus is root bus")
6a589900d050 ("PCI: Set default bridge parent device")
a68e06e729b1 ("PCI: rcar: Fix runtime PM imbalance on error")
56d292348470 ("PCI: rcar: Use pci_host_probe() to register host")
78a0d7f2f5a3 ("PCI: rcar: Move shareable code to a common file")
a18f4b6ea50b ("PCI: rcar: Rename pcie-rcar.c to pcie-rcar-host.c")
You could use something like:
PCI: rcar-host: Add regulator support for KingFisher
> + host->pcie3v3 = devm_regulator_get_optional(dev, "pcie3v3");
> + if (IS_ERR(host->pcie3v3)) {
+1 to Geert's comments. Sprinkling IS_ERR() everywhere is kind of
ugly. host->pcie3v3 should be NULL if not present.
Bjorn
prev parent reply other threads:[~2021-10-19 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 9:58 [PATCH] pci: pcie-rcar: add regulators support Meng Li
2021-10-19 10:19 ` Geert Uytterhoeven
2021-10-19 10:59 ` Li, Meng
2021-10-19 12:36 ` Mark Brown
2021-10-19 13:30 ` Bjorn Helgaas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211019133007.GA2331336@bhelgaas \
--to=helgaas@kernel.org \
--cc=Meng.Li@windriver.com \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=kw@linux.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=magnus.damm@gmail.com \
--cc=marek.vasut+renesas@gmail.com \
--cc=robh+dt@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).