[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMRc=MckdQ1f5jwd8LaFRz3XER-wvRTstRJHxQ9LLasYQHpMBg@mail.gmail.com>
Date: Fri, 25 Oct 2024 10:06:39 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>, Bjorn Helgaas <bhelgaas@...gle.com>,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>, Johan Hovold <johan+linaro@...nel.org>,
Abel Vesa <abel.vesa@...aro.org>, Stephan Gerhold <stephan.gerhold@...aro.org>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Bjorn Andersson <bjorn.andersson@....qualcomm.com>
Subject: Re: [PATCH 4/5] PCI/pwrctl: Move pwrctl device creation to its own
helper function
On Fri, Oct 25, 2024 at 10:05 AM Manivannan Sadhasivam
<manivannan.sadhasivam@...aro.org> wrote:
>
> >
> > Would it be possible to move this into drivers/pwrctl/ and provide a
> > header stub for when PCI_PWRCTL is disabled in Kconfig?
> >
>
> Unfortunately, no. Because the pwrctl drivers are modular and PCI core is
> built-in. So if we use the pwrctl APIs in PCI core, then it will require pwrctl
> to always be built-in, which we do not want.
>
Got it.
Bartosz
Powered by blists - more mailing lists