public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: "Krishna chaitanya chundru" <quic_krichai@quicinc.com>,
	linux-pci@vger.kernel.org, linux-pm@vger.kernel.org,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Kevin Xie" <kevin.xie@starfivetech.com>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	"Rob Herring" <robh@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Mayank Rana <quic_mrana@quicinc.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH v7 2/2] PCI: Enable runtime pm of the host bridge
Date: Mon, 11 Nov 2024 17:46:29 +0100	[thread overview]
Message-ID: <4de3c1d4-2488-40bf-8089-9e2246dbf28c@web.de> (raw)
In-Reply-To: <20241111-runtime_pm-v7-2-9c164eefcd87@quicinc.com>

…
> PM framework expectes parent runtime pm enabled before enabling runtime

               expects?                PM?


> pm of the child. …

  PM?


> drivers, before calling pci_host_probe() as pm frameworks expects if the

                                              PM framework?


> parent device supports runtime pm then it needs to enabled before child

                                 PM?


> runtime pm.

          PM?


Can any tags (like “Fixes” and “Cc”) become helpful for the proposed change?

Regards,
Markus

  reply	other threads:[~2024-11-11 16:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-11  8:41 [PATCH v7 0/2] PCI: Enable runtime pm of the host bridge Krishna chaitanya chundru
2024-11-11  8:41 ` [PATCH v7 1/2] PCI: starfive: Enable PCIe controller's runtime PM before probing " Krishna chaitanya chundru
2024-11-11  8:41 ` [PATCH v7 2/2] PCI: Enable runtime pm of the " Krishna chaitanya chundru
2024-11-11 16:46   ` Markus Elfring [this message]
2024-11-13  5:24     ` Krishna Chaitanya Chundru
2025-01-07 13:19   ` Johan Hovold
2025-01-07 14:10     ` Krishna Chaitanya Chundru
2025-01-07 14:27       ` Johan Hovold
2025-01-13 16:25         ` Manivannan Sadhasivam
2025-01-14 21:16           ` Bjorn Helgaas
2025-01-19 15:29             ` Manivannan Sadhasivam
2025-01-20 10:29               ` Johan Hovold
2025-01-20 15:28                 ` Manivannan Sadhasivam
2025-01-21 13:18                   ` Johan Hovold
2025-01-21 13:34                     ` Johan Hovold
2025-01-24  5:15                     ` Manivannan Sadhasivam
2025-01-27 14:31           ` Ulf Hansson
2025-01-27 19:57             ` Rafael J. Wysocki
2025-01-28 11:47               ` Rafael J. Wysocki
2025-01-28 15:58                 ` Manivannan Sadhasivam
2025-01-28 16:07                   ` Rafael J. Wysocki
2024-11-12 23:44 ` [PATCH v7 0/2] " Bjorn Helgaas

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=4de3c1d4-2488-40bf-8089-9e2246dbf28c@web.de \
    --to=markus.elfring@web.de \
    --cc=bhelgaas@google.com \
    --cc=kevin.xie@starfivetech.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=quic_krichai@quicinc.com \
    --cc=quic_mrana@quicinc.com \
    --cc=rafael@kernel.org \
    --cc=robh@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