From: "Christian König" <christian.koenig@amd.com>
To: "Michel Dänzer" <michel@daenzer.net>,
"Alex Deucher" <alexdeucher@gmail.com>,
"Paul Menzel" <pmenzel+amd-gfx@molgen.mpg.de>
Cc: "David Airlie" <airlied@linux.ie>,
LKML <linux-kernel@vger.kernel.org>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
"Chang Zhu" <Changfeng.Zhu@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: Warning: check cp_fw_version and update it to realize GRBM requires 1-cycle delay in cp firmware
Date: Mon, 6 Jan 2020 15:07:57 +0100 [thread overview]
Message-ID: <9e4d867b-cd30-eb2d-406b-d6a462bdb04c@amd.com> (raw)
In-Reply-To: <3553af46-c9c5-cd33-e7f9-bf7a1a5f49a7@daenzer.net>
Am 06.01.20 um 12:29 schrieb Michel Dänzer:
> On 2019-12-26 5:53 p.m., Alex Deucher wrote:
>> On Thu, Dec 26, 2019 at 5:11 AM Paul Menzel
>>>> [ 13.446975] [drm] Warning: check cp_fw_version and update it to realize GRBM requires 1-cycle delay in cp firmware
>>> Chang, it looks like you added that warning in commit 11c6108934.
>>>
>>>> drm/amdgpu: add warning for GRBM 1-cycle delay issue in gfx9
>>>>
>>>> It needs to add warning to update firmware in gfx9
>>>> in case that firmware is too old to have function to
>>>> realize dummy read in cp firmware.
>>> Unfortunately, it looks like you did not even check how the warning is
>>> formatted (needless spaces), so I guess this was totally untested. Also,
>>> what is that warning about, and what is the user supposed to do? I am
>>> unable to find `cp_fw_version` in the source code at all.
>>>
>> The code looks fine. Not sure why it's rendering funny in your log.
>> DRM_WARN_ONCE("Warning: check cp_fw_version and update
>> it to realize \
>> GRBM requires 1-cycle delay in cp firmware\n");
> Looks like the leading spaces after the backslash are included in the
> string. Something like this should be better:
>
> DRM_WARN_ONCE("Warning: check cp_fw_version and update "
> "GRBM requires 1-cycle delay in cp firmware\n");
Warning and error messages in the kernel should be on a single line if
possible to allow for searching the kernel code for the string of the
message.
I suggest to just shorten the message. Especially it is irrelevant why
the CP firmware is to old, that is debugging info at best. Additional to
that the "Warning:" is superfluous.
Something like DRM_WARN_ONCE("CP firmware version to old, please
update!") should perfectly do it.
Regards,
Christian.
>
> (or maybe the intention was to put the second sentence on a new line?)
prev parent reply other threads:[~2020-01-06 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 10:03 Paul Menzel
2019-12-26 16:53 ` Alex Deucher
2020-01-06 11:29 ` Michel Dänzer
2020-01-06 14:07 ` Christian König [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=9e4d867b-cd30-eb2d-406b-d6a462bdb04c@amd.com \
--to=christian.koenig@amd.com \
--cc=Changfeng.Zhu@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
--cc=pmenzel+amd-gfx@molgen.mpg.de \
/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®