From: Faiz Abbas <faiz_abbas@ti.com>
To: David Laight <David.Laight@ACULAB.COM>,
"'Joe Perches'" <joe@perches.com>,
"kishon@ti.com" <kishon@ti.com>
Cc: "bhelgaas@google.com" <bhelgaas@google.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI: dwc: dra7xx: Print link state to console for debug
Date: Thu, 19 Oct 2017 18:53:04 +0530 [thread overview]
Message-ID: <f7f37f47-2df0-be9d-76c0-188207b57adf@ti.com> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6DD00997A7@AcuExch.aculab.com>
Hi,
On Tuesday 17 October 2017 08:15 PM, David Laight wrote:
> From: Joe Perches
>> Sent: 17 October 2017 07:35
>> On Tue, 2017-10-17 at 11:13 +0530, Faiz Abbas wrote:
>>> Enable support for printing the LTSSM link state for debugging PCI
>>> when link is down.
>> []
>>> diff --git a/drivers/pci/dwc/pci-dra7xx.c b/drivers/pci/dwc/pci-dra7xx.c
>>> index 34427a6..7b150b0 100644
>>> --- a/drivers/pci/dwc/pci-dra7xx.c
>>> +++ b/drivers/pci/dwc/pci-dra7xx.c
>>> @@ -98,6 +98,18 @@ struct dra7xx_pcie_of_data {
>>>
>>> #define to_dra7xx_pcie(x) dev_get_drvdata((x)->dev)
>>>
>>> +static char state[][20] = {
>>> + "DETECT_QUIET", "DETECT_ACT", "POLL_ACTIVE", "POLL_COMPLIANCE",
>>> + "POLL_CONFIG", "PRE_DETECT_QUIET", "DETECT_WAIT", "CFG_LINKWD_START",
>>> + "CFG_LINKWD_ACEPT", "CFG_LANENUM_WAIT", "CFG_LANENUM_ACEPT",
>>> + "CFG_COMPLETE", "CFG_IDLE", "RCVRY_LOCK", "RCVRY_SPEED",
>>> + "RCVRY_RCVRCFG", "RCVRY_IDLE", "L0", "L0S", "L123_SEND_EIDLE",
>>> + "L1_IDLE", "L2_IDLE", "L2_WAKE", "DISABLED_ENTRY", "DISABLED_IDLE",
>>> + "DISABLED", "LPBK_ENTRY", "LPBK_ACTIVE", "LPBK_EXIT",
>>> + "LPBK_EXIT_TIMEOUT", "HOT_RESET_ENTRY", "HOT_RESET", "RCVRY_EQ0",
>>> + "RCVRY_EQ1", "RCVRY_EQ2", "RCVRY_EQ3"
>>
>> what's wrong with using the far more typical
>>
>> static const char *link_state[] = {
>> "DETECT_QUIET",
>> ...
>
> Or 4 aligned columns.
4 aligned columns are difficult as the strings are of different sizes.
> Better still used named initialisers:
> [xxx_DETECT_QUIET] = "DETECT_QUIET",
> you really don't want an 'off-by-one' in that list.
Sounds good. Let me see how I can implement this.
Thanks,
Faiz
next prev parent reply other threads:[~2017-10-19 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 5:43 Faiz Abbas
2017-10-17 6:35 ` Joe Perches
2017-10-17 14:45 ` David Laight
2017-10-19 13:23 ` Faiz Abbas [this message]
2017-10-18 6:16 ` Faiz Abbas
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=f7f37f47-2df0-be9d-76c0-188207b57adf@ti.com \
--to=faiz_abbas@ti.com \
--cc=David.Laight@ACULAB.COM \
--cc=bhelgaas@google.com \
--cc=joe@perches.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pci@vger.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
all inboxes | Powered by JetHome®