From: Tobias Waldekranz <tobias@waldekranz.com>
To: Paolo Abeni <pabeni@redhat.com>, Andrew Lunn <andrew@lunn.ch>
Cc: davem@davemloft.net, kuba@kernel.org, f.fainelli@gmail.com,
olteanv@gmail.com, netdev@vger.kernel.org, linux@armlinux.org.uk,
chris.packham@alliedtelesis.co.nz
Subject: Re: [PATCH net 2/4] net: dsa: mv88e6xxx: Give chips more time to activate their PPUs
Date: Tue, 10 Dec 2024 15:07:34 +0100 [thread overview]
Message-ID: <87cyhz8wd5.fsf@waldekranz.com> (raw)
In-Reply-To: <a9c93b21-71e4-431d-9ab2-e73d47d12dd8@redhat.com>
On tis, dec 10, 2024 at 13:10, Paolo Abeni <pabeni@redhat.com> wrote:
> On 12/6/24 14:39, Tobias Waldekranz wrote:
>> On fre, dec 06, 2024 at 14:18, Andrew Lunn <andrew@lunn.ch> wrote:
>>> On Fri, Dec 06, 2024 at 02:07:34PM +0100, Tobias Waldekranz wrote:
>>>> +
>>>> + if (err) {
>>>> + dev_err(chip->dev, "PPU did not come online: %d\n", err);
>>>> + return err;
>>>> + }
>>>> +
>>>> + if (i)
>>>> + dev_warn(chip->dev,
>>>> + "PPU was slow to come online, retried %d times\n", i);
>>>
>>> dev_dbg()? Does the user care if it took longer than one loop
>>> iteration?
>>
>> My resoning was: While it does seem fine that the device takes this long
>> to initialize, if it turns out that this is an indication of some bigger
>> issue, it might be good to have it recorded in the log.
>
> What about dev_info()? Warn in the log message tend to be interpreted in
> pretty drastic ways.
Sure, that seems fair. I'll lower it in v2.
next prev parent reply other threads:[~2024-12-10 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 13:07 [PATCH net 0/4] net: dsa: mv88e6xxx: Amethyst (6393X) fixes Tobias Waldekranz
2024-12-06 13:07 ` [PATCH net 1/4] net: dsa: mv88e6xxx: Improve I/O related error logging Tobias Waldekranz
2024-12-06 13:07 ` [PATCH net 2/4] net: dsa: mv88e6xxx: Give chips more time to activate their PPUs Tobias Waldekranz
2024-12-06 13:18 ` Andrew Lunn
2024-12-06 13:39 ` Tobias Waldekranz
2024-12-07 15:38 ` Andrew Lunn
2024-12-08 21:23 ` Tobias Waldekranz
2024-12-15 23:12 ` Tobias Waldekranz
2024-12-16 9:22 ` Andrew Lunn
2024-12-10 12:10 ` Paolo Abeni
2024-12-10 14:07 ` Tobias Waldekranz [this message]
2024-12-06 13:07 ` [PATCH net 3/4] net: dsa: mv88e6xxx: Never force link on in-band managed MACs Tobias Waldekranz
2024-12-06 13:07 ` [PATCH net 4/4] net: dsa: mv88e6xxx: Limit rsvd2cpu policy to user ports on 6393X Tobias Waldekranz
2024-12-08 20:23 ` [PATCH net 0/4] net: dsa: mv88e6xxx: Amethyst (6393X) fixes Chris Packham
2024-12-08 21:32 ` Tobias Waldekranz
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=87cyhz8wd5.fsf@waldekranz.com \
--to=tobias@waldekranz.com \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).