From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Huacai Chen <chenhuacai@kernel.org>,
bhelgaas@google.com, kw@linux.com, lpieralisi@kernel.org
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] pci: loongson: Workaround MIPS firmware MRRS settings
Date: Thu, 7 Sep 2023 00:11:59 +0800 [thread overview]
Message-ID: <8c598a6f-98fc-c769-cbcb-90820a4a4872@flygoat.com> (raw)
In-Reply-To: <c2bdde51-4dcc-59ac-5f54-bcf43152fc92@flygoat.com>
在 2023/8/31 18:04, Jiaxun Yang 写道:
>
>
> 在 2023/8/31 17:42, Huacai Chen 写道:
>> On Thu, Aug 31, 2023 at 4:58 PM Jiaxun Yang <jiaxun.yang@flygoat.com>
>> wrote:
>>>
>>>
>>> 在 2023/8/31 14:22, Huacai Chen 写道:
>>>
>>> [...]
>>>> But it is worth to try, and you can walk the children to set mrrs when
>>>> the quirk runs on bridges, I think.
>>> No, this will break hotplug, I had managed to get hotplug work on
>>> 2K1000.
>>> Also we have no guarantee on order of discovering devices.
>>>>> but the old quirk should run on every single device.
>>>> Your current patch has a drawback that both quirks will run for MIPS,
>>>> and their order is random (though it may cause nothing, but not
>>>> elegant).
>>> Actually loongson_mrrs_quirk is declared by DECLARE_PCI_FIXUP_EARLY but
>>> loongson_old_mrrs_quirk is declared by DECLARE_PCI_FIXUP_ENABLE,
>>> which means loongson_old_mrrs_quirk always runs after
>>> loongson_mrrs_quirk as
>>> expected.
>> Then I think it is better to put this quirk in arch/mips/loongson64/,
>> just as pci_fixup_radeon().
Huacai, if you are happy with changes in this patch, do you mind to give
out a
conditional R-b tag?
Since this regression is in tree for a while, I really don't want to see
it lapse into
next release.
>
> Hmm, spiting two quirks with similar functionality into two places
> doesn't sound
> like a good idea.
>
> PCI folks, what do you think?
Bjorn, Lorenzo and Krzysztof, do you mind to give some input on this fix?
Thanks
- Jiaxun
>
> Thanks.
> - Jiaxun
>
> [...]
next prev parent reply other threads:[~2023-09-06 16:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 6:10 Jiaxun Yang
2023-08-06 2:20 ` Jiaxun Yang
2023-08-06 14:30 ` Huacai Chen
2023-08-08 7:38 ` Jiaxun Yang
2023-08-29 12:26 ` Linux regression tracking (Thorsten Leemhuis)
2023-08-31 5:31 ` Jiaxun Yang
2023-08-31 6:22 ` Huacai Chen
2023-08-31 8:58 ` Jiaxun Yang
2023-08-31 9:42 ` Huacai Chen
2023-08-31 10:04 ` Jiaxun Yang
2023-09-06 16:11 ` Jiaxun Yang [this message]
2023-09-07 1:18 ` Manivannan Sadhasivam
2023-09-07 3:13 ` Jiaxun Yang
2023-09-07 5:08 ` Manivannan Sadhasivam
2023-09-20 12:33 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-20 11:04 ` Thorsten Leemhuis
2023-10-22 13:36 ` Jiaxun Yang
2023-10-22 13:38 ` Jiaxun Yang
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=8c598a6f-98fc-c769-cbcb-90820a4a4872@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=bhelgaas@google.com \
--cc=chenhuacai@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--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
all inboxes | Powered by JetHome®