linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Krzysztof Wilczyński" <kw@linux.com>
To: Robin McCorkell <robin@mccorkell.me.uk>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] PCI: Limit REBAR quirk to just Sapphire RX 5600 XT Pulse
Date: Wed, 27 Oct 2021 11:47:14 +0200	[thread overview]
Message-ID: <YXkgIjURbhdWo4YX@rocinante> (raw)
In-Reply-To: <20211026214513.25986-1-robin@mccorkell.me.uk>

[+CC adding Bjorn as the PCI sub-system maintainer]

Hi Robin,

Thank you for sending the patch over!

> A particular RX 5600 device requires a hack in the rebar logic, but the
> current branch is too general and catches other devices too, breaking
> them. This patch changes the branch to be more selective on the
> particular revision.
> 
> This patch fixes intermittent freezes on other RX 5600 devices where the
> hack is unnecessary. Credit to all contributors in the linked issue on
> the AMD bug tracker.
> 
> See also: https://gitlab.freedesktop.org/drm/amd/-/issues/1707
[...]

The commit message could be improved a little bit so that it's more in
preferred imperative tone describing what precisely is broken and how it
fixes the problem for Sapphire RX 5600 XT and other ATI cards.  Also,
consistent capitalisation of "REBAR" between the subject and the commit
message would be a plus.

There is also no need to add "this patch" - we also know that this is this
very patch, especially since this isn't a series that comprises of multiple
other patches.

Also, sine this is a v2, it would be nice to include a small changelog,
even if the change is trivial, with helps as people don't have to go and
read other e-mail threads to find out what was changed and why.

> Reported-by: Simon May <@Socob on gitlab.freedesktop.com>
> Tested-by: Kain Centeno <@kaincenteno on gitlab.freedesktop.com>
> Tested-by: Tobias Jakobi <@tobiasjakobi on gitlab.freedesktop.com>
> Suggested-by: lijo lazar <@lijo on gitlab.freedesktop.com>

The above would be "gitlab.freedesktop.org", I believe.  Having said that,
I am not sure if we can accept username handles to some remote Git hosting
platform in lieu of proper, so to speak, e-mail addresses.

[...]
>  	/* Sapphire RX 5600 XT Pulse has an invalid cap dword for BAR 0 */
>  	if (pdev->vendor == PCI_VENDOR_ID_ATI && pdev->device == 0x731f &&
> -	    bar == 0 && cap == 0x7000)
> +	    pdev->revision == 0xC1 && bar == 0 && cap == 0x7000)

A small nitpick: lowercase hexadecimal values to match how it's been used
in other places.

	Krzysztof

  reply	other threads:[~2021-10-27  9:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 20:46 [PATCH] Limit AMD Radeon rebar hack to a single revision Robin McCorkell
2021-10-26 21:28 ` Bjorn Helgaas
2021-10-26 21:44   ` [PATCH v2] PCI: Limit REBAR quirk to just Sapphire RX 5600 XT Pulse Robin McCorkell
2021-10-27  9:47     ` Krzysztof Wilczyński [this message]
2021-11-01 21:55     ` Bjorn Helgaas
2021-11-02 12:27       ` Christian König
2021-10-26 21:49   ` [PATCH] Limit AMD Radeon rebar hack to a single revision Robin McCorkell
2021-10-27  6:38     ` Christian König

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=YXkgIjURbhdWo4YX@rocinante \
    --to=kw@linux.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=robin@mccorkell.me.uk \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).