From: Bjorn Helgaas <helgaas@kernel.org>
To: Manikandan Karunakaran Pillai <mpillai@cadence.com>
Cc: "lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"manivannan.sadhasivam@linaro.org"
<manivannan.sadhasivam@linaro.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"robh@kernel.org" <robh@kernel.org>,
"kw@linux.com" <kw@linux.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pci: cdns : Function to read controller architecture
Date: Fri, 31 Jan 2025 12:38:35 -0600 [thread overview]
Message-ID: <20250131183835.GA688678@bhelgaas> (raw)
In-Reply-To: <CH2PPF4D26F8E1C5FA4D55D4271BA4F6F0DA2E82@CH2PPF4D26F8E1C.namprd07.prod.outlook.com>
Look at previous subject lines for changes to these files and follow
the pattern.
On Fri, Jan 31, 2025 at 11:58:07AM +0000, Manikandan Karunakaran Pillai wrote:
> Add support for getting the architecture for Cadence PCIe controllers
> Store the architecture type in controller structure.
This needs to be part of a series that uses pcie->is_hpa for
something. This patch all by itself isn't useful for anything.
Please post the resulting series with a cover letter and the patches
as responses to it:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/5.Posting.rst?id=v6.13#n333
You can look at previous postings to see the style, e.g.,
https://lore.kernel.org/linux-pci/20250115074301.3514927-1-pandoh@google.com/T/#t
> +static void cdns_pcie_ctlr_set_arch(struct cdns_pcie *pcie)
> +{
> + /* Read register at offset 0xE4 of the config space
> + * The value for architecture is in the lower 4 bits
> + * Legacy-b'0010 and b'1111 for HPA-high performance architecture
> + */
Don't include the hex register offset in the comment. That's what
CDNS_PCIE_CTRL_ARCH is for. It doesn't need the bit values either.
Use the conventional comment style:
/*
* Text ...
*/
> + u32 arch, reg;
> +
> + reg = cdns_pcie_readl(pcie, CDNS_PCIE_CTRL_ARCH);
> + arch = FIELD_GET(CDNS_PCIE_CTRL_ARCH_MASK, reg);
Thanks for using GENMASK() and FIELD_GET().
> + if (arch == CDNS_PCIE_CTRL_HPA) {
> + pcie->is_hpa = true;
> + } else {
> + pcie->is_hpa = false;
> + }
> +}
> +/*
> + * Read completion time out reset value to decode controller architecture
> + */
> +#define CDNS_PCIE_CTRL_ARCH 0xE4
Is this another name for the PCI_EXP_DEVCTL2 in the PCIe Capability?
Or maybe PCI_EXP_DEVCAP2? If so, use those existing #defines and the
related masks (if it's DEVCAP2, you'd probably have to add a new one
for the Completion Timeout Ranges Supported field).
There's something similar in cdns_pcie_retrain(), where
CDNS_PCIE_RP_CAP_OFFSET is apparently the config space offset of the
PCIe Capability.
> +#define CDNS_PCIE_CTRL_ARCH_MASK GENMASK(3, 0)
> +#define CDNS_PCIE_CTRL_HPA 0xF
next prev parent reply other threads:[~2025-01-31 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250131114516.2501350-1-mpillai@cadence.com>
2025-01-31 11:58 ` [PATCH] pci: cdns : Function to read controller architecture Manikandan Karunakaran Pillai
2025-01-31 18:38 ` Bjorn Helgaas [this message]
2025-02-03 14:04 ` Manikandan Karunakaran Pillai
2025-02-03 15:48 ` 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=20250131183835.GA688678@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mpillai@cadence.com \
--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