From: Bjorn Helgaas <helgaas@kernel.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Marek Behún" <kabel@kernel.org>,
devicetree@vger.kernel.org, robh+dt@kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH dt + pci 2/2] PCI: Add function for parsing `slot-power-limit-milliwatt` DT property
Date: Wed, 12 Jan 2022 18:00:27 -0600 [thread overview]
Message-ID: <20220113000027.GA294943@bhelgaas> (raw)
In-Reply-To: <20220112222822.7yirl7k57ju5d2ox@pali>
On Wed, Jan 12, 2022 at 11:28:22PM +0100, Pali Rohár wrote:
> On Wednesday 12 January 2022 16:08:15 Bjorn Helgaas wrote:
> > On Sun, Oct 31, 2021 at 04:07:06PM +0100, Marek Behún wrote:
> > > From: Pali Rohár <pali@kernel.org>
> > >
> > > Add function of_pci_get_slot_power_limit(), which parses the
> > > `slot-power-limit-milliwatt` DT property, returning the value in
> > > milliwatts and in format ready for the PCIe Slot Capabilities Register.
> > >
> > > Signed-off-by: Pali Rohár <pali@kernel.org>
> > > Signed-off-by: Marek Behún <kabel@kernel.org>
> >
> > Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> >
> > Do we have a caller of of_pci_get_slot_power_limit() yet? I didn't
> > see one from a quick look
> > (https://lore.kernel.org/linux-pci/?q=b%3Aof_pci_get_slot_power_limit).
> >
> > Let's merge this when we have a user for it.
>
> I have a patch for both pci-mvebu.c and pci-aardvark.c drivers. But
> there are lot of patches for these drivers waiting on mailing list for
> review... Should I sent another patch for pci-mvebu.c which will use
> this of_pci_get_slot_power_limit() function?
If the of_pci_get_slot_power_limit() patches are independent of the
ones waiting for review, they could be added to *this* series.
Bjorn
next prev parent reply other threads:[~2022-01-13 0:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 15:07 [PATCH dt + pci 1/2] dt-bindings: Add 'slot-power-limit-milliwatt' PCIe port property Marek Behún
2021-10-31 15:07 ` [PATCH dt + pci 2/2] PCI: Add function for parsing `slot-power-limit-milliwatt` DT property Marek Behún
2022-01-07 18:04 ` Marek Behún
2022-01-07 21:17 ` Rob Herring
2022-01-12 22:08 ` Bjorn Helgaas
2022-01-12 22:28 ` Pali Rohár
2022-01-13 0:00 ` Bjorn Helgaas [this message]
2021-11-12 15:25 ` [PATCH dt + pci 1/2] dt-bindings: Add 'slot-power-limit-milliwatt' PCIe port property Rob Herring
2021-11-12 15:32 ` Pali Rohár
2021-11-12 16:30 ` Rob Herring
2021-11-12 17:12 ` Pali Rohár
2021-11-12 17:24 ` Marek Behún
2021-11-12 20:56 ` Rob Herring
2021-11-13 11:31 ` Pali Rohár
2021-11-16 21:31 ` Pali Rohár
2022-01-05 14:14 ` Marek Behún
2022-01-05 14:27 ` Rob Herring
2022-01-05 15:14 ` Pali Rohár
2022-01-05 15:26 ` Rob Herring
2022-01-05 15:36 ` Pali Rohár
2022-01-05 17:11 ` Marek Behún
2022-02-18 11:31 ` Pali Rohár
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=20220113000027.GA294943@bhelgaas \
--to=helgaas@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kabel@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pali@kernel.org \
--cc=robh+dt@kernel.org \
/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).