From: Faiz Abbas <faiz_abbas@ti.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: kishon@ti.com, bhelgaas@google.com, linux-omap@vger.kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dwc: dra7xx: Print link state to console for debug
Date: Mon, 23 Oct 2017 15:59:49 +0530 [thread overview]
Message-ID: <3692fbeb-bf8a-6de6-898b-551d899e9e55@ti.com> (raw)
In-Reply-To: <20171020230952.GZ6332@bhelgaas-glaptop.roam.corp.google.com>
Hi Bjorn,
On Saturday 21 October 2017 04:39 AM, Bjorn Helgaas wrote:
> On Thu, Oct 19, 2017 at 06:13:29PM +0530, Faiz Abbas wrote:
>> Enable support for printing the LTSSM link state for debugging PCI
>> when link is down.
>>
>> Signed-off-by: Faiz Abbas <faiz_abbas@ti.com>
>> ---
>> v2:
>> 1. Changed dev_err() to dev_dbg()
>> 2. Changed static char array to static const char * const
>> 3. format changes
>
> I'm not really sure how much debug help we want to carry around in the
> mainline kernel. End users aren't going to use this; it seems like
> more of a lab tool, and in situations like that you usually end up
> carrying around some out-of-tree patches for a while anyway. But I
> can probably be convinced either way.
>
It'll be easier to support customers if they can tell us what the state
of the link is by just changing the log level. We won't have to send a
debug patch to the customer to find that out.
Thanks,
Faiz
next prev parent reply other threads:[~2017-10-23 10:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 12:43 [PATCH v2] dwc: dra7xx: Print link state to console for debug Faiz Abbas
2017-10-19 13:08 ` Faiz Abbas
2017-10-19 13:26 ` David Laight
2017-10-26 7:59 ` Faiz Abbas
2017-10-30 8:48 ` Faiz Abbas
2017-11-06 2:56 ` Faiz Abbas
2017-10-20 23:09 ` Bjorn Helgaas
2017-10-23 10:29 ` Faiz Abbas [this message]
2017-10-23 14:04 ` Bjorn Helgaas
2017-10-24 6:18 ` Kishon Vijay Abraham I
2017-10-24 19:59 ` Bjorn Helgaas
2017-10-25 8:21 ` Faiz Abbas
2017-10-25 13:23 ` 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=3692fbeb-bf8a-6de6-898b-551d899e9e55@ti.com \
--to=faiz_abbas@ti.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--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