From: Hans Zhang <18255117159@163.com>
To: Frank Li <Frank.li@nxp.com>
Cc: jingoohan1@gmail.com, manivannan.sadhasivam@linaro.org,
lpieralisi@kernel.org, kw@linux.com, robh@kernel.org,
bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, rockswang7@gmail.com
Subject: Re: [PATCH] PCI: dwc: Add the sysfs property to provide the LTSSM status of the PCIe link
Date: Fri, 24 Jan 2025 21:12:49 +0800 [thread overview]
Message-ID: <54428aa3-2178-45d0-83d3-0b6254347bb5@163.com> (raw)
In-Reply-To: <Z5JrXsDDM2IManp+@lizhi-Precision-Tower-5810>
On 2025/1/24 00:16, Frank Li wrote:
>> +static char *dw_ltssm_sts_string(enum dw_pcie_ltssm ltssm)
>> +{
>> + char *str;
>> +
>> + switch (ltssm) {
>> +#define DW_PCIE_LTSSM_NAME(n) case n: str = #n; break
>> + DW_PCIE_LTSSM_NAME(DW_PCIE_LTSSM_DETECT_QUIET);
>> + DW_PCIE_LTSSM_NAME(DW_PCIE_LTSSM_DETECT_ACT);
>> + DW_PCIE_LTSSM_NAME(DW_PCIE_LTSSM_POLL_ACTIVE);
>> + DW_PCIE_LTSSM_NAME(DW_PCIE_LTSSM_POLL_COMPLIANCE);
>> + ...
>> + default:
>> + str = "DW_PCIE_LTSSM_UNKNOWN";
>> + break;
>
> I prefer
> const char * str[] =
> {
> "detect_quitet",
> "detect_act",
> ...
> }
>
> return str[ltssm];
>
> Or
> #define DW_PCIE_LTSSM_NAME(n) case n: return #n;
> ...
> default:
> return "DW_PCIE_LTSSM_UNKNOWN";
Hi Frank,
I considered the two methods you mentioned before I submitted this patch.
The first, I think, will increase the memory overhead.
+static const char * const dw_pcie_ltssm_str[] = {
+ [DW_PCIE_LTSSM_DETECT_QUIET] = "DETECT_QUIET",
+ [DW_PCIE_LTSSM_DETECT_ACT] = "DETECT_ACT",
+ [DW_PCIE_LTSSM_POLL_ACTIVE] = "POLL_ACTIVE",
+ [DW_PCIE_LTSSM_POLL_COMPLIANCE] = "POLL_COMPLIANCE",
...
The second, ./scripts/checkpatch.pl checks will have a warning
WARNING: Macros with flow control statements should be avoided
#121: FILE: drivers/pci/controller/dwc/pcie-designware.h:329:
+#define DW_PCIE_LTSSM_NAME(n) case n: return #n
>> +static ssize_t ltssm_status_show(struct device *dev,
>> + struct device_attribute *attr, char *buf)
>> +{
>> + struct pci_dev *pdev = to_pci_dev(dev);
>> + struct pci_host_bridge *bridge = pci_find_host_bridge(pdev->bus);
>> + struct dw_pcie_rp *pp = bridge->sysdata;
>> + struct dw_pcie *pci = to_dw_pcie_from_pp(pp);
>> +
>> + return sysfs_emit(buf, "%s\n",
>> + dw_ltssm_sts_string(dw_pcie_get_ltssm(pci)));
>
> Suggest dump raw value also
>
> val = dw_pcie_get_ltssm(pci);
> return sysfs_emit(buf, "%s (0x%02x)\n",
> dw_ltssm_sts_string(val), val);
Thanks, i think it's a good idea.
Best regards
Hans
next prev parent reply other threads:[~2025-01-24 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 7:13 [PATCH] PCI: dwc: Add the sysfs property to provide the LTSSM status of the PCIe link Hans Zhang
2025-01-23 16:16 ` Frank Li
2025-01-24 13:12 ` Hans Zhang [this message]
2025-01-24 16:01 ` Frank Li
2025-01-26 14:30 ` Hans Zhang
2025-01-23 16:49 ` Bjorn Helgaas
2025-01-26 14:06 ` Hans Zhang
2025-01-24 13:29 ` 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=54428aa3-2178-45d0-83d3-0b6254347bb5@163.com \
--to=18255117159@163.com \
--cc=Frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.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=robh@kernel.org \
--cc=rockswang7@gmail.com \
/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