mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans Zhang <18255117159@163.com>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: robh@kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, Cheng Xin <chengqin1525@126.com>,
	lpieralisi@kernel.org, jingoohan1@gmail.com,
	kwilczynski@kernel.org, bhelgaas@google.com, mani@kernel.org
Subject: Re: [PATCH] PCI: dwc: Add PCIe event counters for groups 5 to 7 in DWC debugfs
Date: Sat, 7 Mar 2026 09:54:56 +0800	[thread overview]
Message-ID: <32b46d99-566e-41a8-b25f-6f0e1bed21e2@163.com> (raw)
In-Reply-To: <a07f2bf8-6c91-e89f-d07b-721e6f10805c@rock-chips.com>



On 3/7/26 00:11, Shawn Lin wrote:
> 在 2026/03/06 星期五 23:07, Hans Zhang 写道:
>> Extend the DesignWare PCIe controller's debugfs statistical counter
>> interface with event definitions from groups 5 through 7 as documented
>> in the DWC PCIe Databook (version 3.30a, section 3.8.2.3, Tables 3-59,
>> 3-60, 3-61). These counters provide visibility into Layer1 non-error
>> events (link state transitions,ASPM, L1 substates), Layer2 DLLP
>> exchanges, and Layer3 TLP transactions.
>>
>> The counters are exposed under the debugfs statistical counter directory,
>> allowing users to monitor link behavior and diagnose PCIe protocol issues
>> more effectively.
>>
>> Co-developed-by: Cheng Xin <chengqin1525@126.com>
>> Signed-off-by: Cheng Xin <chengqin1525@126.com>
>> Signed-off-by: Hans Zhang <18255117159@163.com>
>> ---
>> Thank you, Cheng Xin, for providing the 3.30a version of the DWC PCIe 
>> Data Book.
>> ---
>>   .../controller/dwc/pcie-designware-debugfs.c  | 52 ++++++++++++++++++-
>>   1 file changed, 51 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/pci/controller/dwc/pcie-designware-debugfs.c b/ 
>> drivers/pci/controller/dwc/pcie-designware-debugfs.c
>> index 0d1340c9b364..2efddb21b2b2 100644
>> --- a/drivers/pci/controller/dwc/pcie-designware-debugfs.c
>> +++ b/drivers/pci/controller/dwc/pcie-designware-debugfs.c
>> @@ -131,13 +131,16 @@ static const u32 err_inj_type_mask[] = {
>>    *                   supported in DWC RAS DES
>>    * @name: Name of the error counter
>>    * @group_no: Group number that the event belongs to. The value can 
>> range
>> - *          from 0 to 4
>> + *          from 0 to 7
>>    * @event_no: Event number of the particular event. The value ranges 
>> are:
>>    *        Group 0: 0 - 10
>>    *        Group 1: 5 - 13
>>    *        Group 2: 0 - 7
>>    *        Group 3: 0 - 5
>>    *        Group 4: 0 - 1
>> + *        Group 5: 0 - 13
>> + *        Group 6: 0 - 6
>> + *        Group 7: 0 - 25
>>    */
>>   struct dwc_pcie_event_counter {
>>       const char *name;
>> @@ -181,6 +184,53 @@ static const struct dwc_pcie_event_counter 
>> event_list[] = {
>>       {"completion_timeout", 0x3, 0x5},
>>       {"ebuf_skp_add", 0x4, 0x0},
>>       {"ebuf_skp_del", 0x4, 0x1},
>> +    {"l0_to_recovery_entry", 0x5, 0x0},
>> +    {"l1_to_recovery_entry", 0x5, 0x1},
>> +    {"tx_l0s_entry", 0x5, 0x2},
>> +    {"rx_l0s_entry", 0x5, 0x3},
>> +    {"aspm_l1_reject", 0x5, 0x4},
>> +    {"l1_entry", 0x5, 0x5},
>> +    {"l1_cpm", 0x5, 0x6},
>> +    {"l1.1_entry", 0x5, 0x7},
>> +    {"l1.2_entry", 0x5, 0x8},
>> +    {"l1_short_duration", 0x5, 0x9},
>> +    {"l1.2_abort", 0x5, 0xa},
>> +    {"l2_entry", 0x5, 0xb},
>> +    {"speed_change", 0x5, 0xc},
>> +    {"link_width_change", 0x5, 0xd},
>> +    {"tx_ack_dllp", 0x6, 0x0},
>> +    {"tx_update_fc_dllp", 0x6, 0x1},
>> +    {"rx_ack_dllp", 0x6, 0x2},
>> +    {"rx_update_fc_dllp", 0x6, 0x3},
>> +    {"rx_nullified_tlp", 0x6, 0x4},
>> +    {"tx_nullified_tlp", 0x6, 0x5},
>> +    {"rx_duplicate_tlp", 0x6, 0x6},
>> +    {"tx_memory_write", 0x7, 0x0},
>> +    {"tx_memory_read", 0x7, 0x1},
>> +    {"tx_configuration_write", 0x7, 0x2},
>> +    {"tx_configuration_read", 0x7, 0x3},
>> +    {"tx_io_write", 0x7, 0x4},
>> +    {"tx_io_read", 0x7, 0x5},
>> +    {"tx_completion_without_data", 0x7, 0x6},
>> +    {"tx_completion_w_data", 0x7, 0x7},
>> +    {"tx_message_tlp_pcie_vc_only", 0x7, 0x8},
>> +    {"tx_atomic", 0x7, 0x9},
>> +    {"tx_tlp_with_prefix", 0x7, 0xa},
>> +    {"rx_memory_write", 0x7, 0xb},
>> +    {"rx_memory_read", 0x7, 0xc},
>> +    {"rx_configuration_write", 0x7, 0xd},
>> +    {"rx_configuration_read", 0x7, 0xe},
>> +    {"rx_io_write", 0x7, 0xf},
>> +    {"rx_io_read", 0x7, 0x10},
>> +    {"rx_completion_without_data", 0x7, 0x11},
>> +    {"rx_completion_w_data", 0x7, 0x12},
>> +    {"rx_message_tlp_pcie_vc_only", 0x7, 0x13},
>> +    {"rx_atomic", 0x7, 0x14},
>> +    {"rx_tlp_with_prefix", 0x7, 0x15},
> 
> Hmm, 5.10a/5.60a databooks only list the first 21 events for Group 7,
> It's rather counterintuitive, perhaps it would make sense that debug 
> signals should keep adding more. Other parts look good to me.

Hi Shawn,

Thank you very much for your reply and reminder.

The version information in the commit message is incorrect. It should be 
"6.30a" instead of "3.30a". I will send the next version with corrections.

Best regards,
Hans

> 
>> +    {"tx_ccix_tlp", 0x7, 0x16},
>> +    {"rx_ccix_tlp", 0x7, 0x17},
>> +    {"tx_deferrable_memory_write_tlp", 0x7, 0x18},
>> +    {"rx_deferrable_memory_write_tlp", 0x7, 0x19},
>>   };
>>   static ssize_t lane_detect_read(struct file *file, char __user *buf,
>>


      reply	other threads:[~2026-03-07  1:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 15:07 Hans Zhang
2026-03-06 16:11 ` Shawn Lin
2026-03-07  1:54   ` Hans Zhang [this message]

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=32b46d99-566e-41a8-b25f-6f0e1bed21e2@163.com \
    --to=18255117159@163.com \
    --cc=bhelgaas@google.com \
    --cc=chengqin1525@126.com \
    --cc=jingoohan1@gmail.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=robh@kernel.org \
    --cc=shawn.lin@rock-chips.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

all inboxes | Powered by JetHome®