From: Greg KH <gregkh@linuxfoundation.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
kw@linux.com, arnd@arndb.de, lpieralisi@kernel.org,
shuah@kernel.org, kishon@kernel.org, aman1.gupta@samsung.com,
p.rajanbabu@samsung.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, bhelgaas@google.com,
linux-arm-msm@vger.kernel.org, robh@kernel.org,
linux-kselftest@vger.kernel.org, stable+noautosel@kernel.org
Subject: Re: [PATCH v2 1/4] PCI: qcom-ep: Mark BAR0/BAR2 as 64bit BARs and BAR1/BAR3 as RESERVED
Date: Sat, 30 Nov 2024 17:17:58 +0100 [thread overview]
Message-ID: <2024113005-oboe-widow-d61e@gregkh> (raw)
In-Reply-To: <20241129195537.GA2770926@bhelgaas>
On Fri, Nov 29, 2024 at 01:55:37PM -0600, Bjorn Helgaas wrote:
> On Fri, Nov 29, 2024 at 02:54:12PM +0530, Manivannan Sadhasivam wrote:
> > On all Qcom endpoint SoCs, BAR0/BAR2 are 64bit BARs by default and software
> > cannot change the type. So mark the those BARs as 64bit BARs and also mark
> > the successive BAR1/BAR3 as RESERVED BARs so that the EPF drivers cannot
> > use them.
>
> "Default" implies an initial setting that can be changed, but you say
> "by default" and also "software cannot change the type." Can they be
> anything *other* than 64-bit BARs?
>
> If they're hardwired to be 64-bit BARs, I would just say that.
>
> > Cc: stable+noautosel@kernel.org # depends on patch introducing only_64bit flag
>
> If stable maintainers need to act on this, do they need to search for
> the patch introducing only_64bit flag? That seems onerous; is there a
> SHA1 that would make it easier?
>
> > Fixes: f55fee56a631 ("PCI: qcom-ep: Add Qualcomm PCIe Endpoint controller driver")
Yes, having a sha1 that has that "feature addition" would be great,
surely that isn't 6.13-rc1, is it?
thanks,
greg k-h
next prev parent reply other threads:[~2024-11-30 16:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 9:24 [PATCH v2 0/4] Migrate PCI Endpoint Subsystem tests to Kselftest Manivannan Sadhasivam
2024-11-29 9:24 ` [PATCH v2 1/4] PCI: qcom-ep: Mark BAR0/BAR2 as 64bit BARs and BAR1/BAR3 as RESERVED Manivannan Sadhasivam
2024-11-29 14:38 ` Dmitry Baryshkov
2024-11-29 19:55 ` Bjorn Helgaas
2024-11-30 16:17 ` Greg KH [this message]
2024-12-02 12:58 ` Manivannan Sadhasivam
2024-12-02 17:40 ` Bjorn Helgaas
2024-11-29 9:24 ` [PATCH v2 2/4] misc: pci_endpoint_test: Fix the return value of IOCTL Manivannan Sadhasivam
2024-11-29 10:51 ` Damien Le Moal
2024-11-29 16:30 ` Manivannan Sadhasivam
2024-12-11 7:47 ` Manivannan Sadhasivam
2024-11-29 9:24 ` [PATCH v2 3/4] selftests: Move PCI Endpoint tests from tools/pci to Kselftests Manivannan Sadhasivam
2024-11-29 9:24 ` [PATCH v2 4/4] selftests: pci_endpoint: Migrate to Kselftest framework Manivannan Sadhasivam
2024-11-29 13:51 ` Niklas Cassel
2024-11-29 16:35 ` Manivannan Sadhasivam
2024-11-29 16:42 ` Niklas Cassel
2024-11-29 16:52 ` Manivannan Sadhasivam
2024-11-29 17:13 ` Niklas Cassel
2024-11-29 18:25 ` Manivannan Sadhasivam
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=2024113005-oboe-widow-d61e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aman1.gupta@samsung.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=p.rajanbabu@samsung.com \
--cc=robh@kernel.org \
--cc=shuah@kernel.org \
--cc=stable+noautosel@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