From: Kurt Kanzenbach <kurt@linutronix.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Richard Cochran <richardcochran@gmail.com>,
Kamil Alkhouri <kamil.alkhouri@hs-offenburg.de>,
ilias.apalodimas@linaro.org
Subject: Re: [RFC PATCH 6/9] net: dsa: hellcreek: Add debugging mechanisms
Date: Fri, 19 Jun 2020 10:36:45 +0200 [thread overview]
Message-ID: <875zbnqwo2.fsf@kurt> (raw)
In-Reply-To: <20200618173458.GH240559@lunn.ch>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
Hi Andrew,
On Thu Jun 18 2020, Andrew Lunn wrote:
> On Thu, Jun 18, 2020 at 08:40:26AM +0200, Kurt Kanzenbach wrote:
>> The switch has registers which are useful for debugging issues:
>
> debugfs is not particularly likes. Please try to find other means
> where possible. Memory usage fits nicely into devlink. See mv88e6xxx
> which exports the ATU fill for example.
OK, I'll have a look at devlink and the mv88e6xxx driver to see if that
could be utilized.
> Are trace registers counters?
No. The trace registers provide bits for error conditions and if packets
have been dropped e.g. because of full queues or FCS errors, and so on.
>
>> +static int hellcreek_debugfs_init(struct hellcreek *hellcreek)
>> +{
>> + struct dentry *file;
>> +
>> + hellcreek->debug_dir = debugfs_create_dir(dev_name(hellcreek->dev),
>> + NULL);
>> + if (!hellcreek->debug_dir)
>> + return -ENOMEM;
>
> Just a general comment. You should not check the return value from any
> debugfs call, since it is totally optional. It will also do the right
> thing if the previous call has failed. There are numerous emails from
> GregKH about this.
OK.
Thanks,
Kurt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-06-19 8:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 6:40 [RFC PATCH 0/9] Hirschmann Hellcreek DSA driver Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 1/9] net: dsa: Add tag handling for Hirschmann Hellcreek switches Kurt Kanzenbach
2020-06-18 13:42 ` Andrew Lunn
2020-06-18 6:40 ` [RFC PATCH 2/9] net: dsa: Add DSA driver " Kurt Kanzenbach
2020-06-18 15:22 ` Andrew Lunn
2020-06-19 8:12 ` Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 3/9] net: dsa: hellcreek: Add PTP clock support Kurt Kanzenbach
2020-06-18 15:46 ` Jakub Kicinski
2020-06-19 8:13 ` Kurt Kanzenbach
2020-06-18 17:23 ` Andrew Lunn
2020-06-19 8:26 ` Kurt Kanzenbach
2020-06-19 13:40 ` Andrew Lunn
2020-06-22 11:52 ` Kurt Kanzenbach
2020-06-24 13:03 ` Richard Cochran
2020-06-25 7:08 ` Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 4/9] net: dsa: hellcreek: Add support for hardware timestamping Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 5/9] net: dsa: hellcreek: Add TAPRIO offloading support Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 6/9] net: dsa: hellcreek: Add debugging mechanisms Kurt Kanzenbach
2020-06-18 17:34 ` Andrew Lunn
2020-06-19 8:36 ` Kurt Kanzenbach [this message]
2020-06-19 13:42 ` Andrew Lunn
2020-06-22 12:32 ` Kurt Kanzenbach
2020-06-22 13:55 ` Andrew Lunn
2020-06-23 6:07 ` Kurt Kanzenbach
2020-06-22 14:14 ` Vladimir Oltean
2020-06-23 6:04 ` Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 7/9] net: dsa: hellcreek: Add PTP status LEDs Kurt Kanzenbach
2020-06-18 17:46 ` Andrew Lunn
2020-06-19 8:45 ` Kurt Kanzenbach
2020-06-19 13:52 ` Andrew Lunn
2020-06-18 6:40 ` [RFC PATCH 8/9] dt-bindings: Add vendor prefix for Hirschmann Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 9/9] dt-bindings: net: dsa: Add documentation for Hellcreek switches Kurt Kanzenbach
2020-06-18 13:47 ` Andrew Lunn
2020-06-19 8:47 ` Kurt Kanzenbach
2020-06-19 13:56 ` Andrew Lunn
2020-06-22 12:02 ` Kurt Kanzenbach
2020-06-22 13:49 ` Andrew Lunn
2020-06-23 6:09 ` Kurt Kanzenbach
2020-06-18 17:40 ` Florian Fainelli
2020-06-19 8:48 ` Kurt Kanzenbach
2020-06-22 12:05 ` Kurt Kanzenbach
2020-06-26 17:11 ` Florian Fainelli
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=875zbnqwo2.fsf@kurt \
--to=kurt@linutronix.de \
--cc=andrew@lunn.ch \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=kamil.alkhouri@hs-offenburg.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=vivien.didelot@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.