[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241105003214.GA1614659@rocinante>
Date: Tue, 5 Nov 2024 09:32:14 +0900
From: Krzysztof WilczyĆski <kw@...ux.com>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: manivannan.sadhasivam@...aro.org, Bjorn Helgaas <bhelgaas@...gle.com>,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
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>,
stable+noautosel@...nel.org
Subject: Re: [PATCH 0/5] PCI/pwrctl: Ensure that the pwrctl drivers are
probed before PCI client drivers
Hello,
> > > This series reworks the PCI/pwrctl integration to ensure that the pwrctl drivers
> > > are always probed before the PCI client drivers. This series addresses a race
> > > condition when both pwrctl and pwrctl/pwrseq drivers probe parallely (even when
> > > the later one probes last). One such issue was reported for the Qcom X13s
> > > platform with WLAN module and fixed with 'commit a9aaf1ff88a8 ("power:
> > > sequencing: request the WLAN enable GPIO as-is")'.
> > >
> > > Though the issue was fixed with a hack in the pwrseq driver, it was clear that
> > > the issue is applicable to all pwrctl drivers. Hence, this series tries to
> > > address the issue in the PCI/pwrctl integration.
> >
> > Applied to bwctrl, thank you!
>
> Should be pci/pwrctl. bwctrl (bandwidth control) and pwrctl (power
> control) are quite different despite the confusingly similar names.
Correct. I moved patches to the correct branch. Sorry about that!
Krzysztof
Powered by blists - more mailing lists