Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PCI: Mark Px210 PCI-E Extended Tags as broken #223

Merged
merged 1 commit into from
May 28, 2024
Merged

PCI: Mark Px210 PCI-E Extended Tags as broken #223

merged 1 commit into from
May 28, 2024

Conversation

wangzhimin1179
Copy link
Contributor

针对飞腾x100的pcie设备。关闭 Extended Tag 。

@wangzhimin1179
PCI: Mark Px210 PCI-E Extended Tags as broken
647e86a 
Per PCIe r3.1, sec 2.2.6.2 and 7.8.4, a Requester may not use 8-bit
Tags unless its Extended Tag Field Enable is set, but all
Receivers/Completers must handle 8-bit Tags correctly regardless of
their Extended Tag Field Enable.

Phytium Px210 chipset has some issues with 8-bit Tags enabled when
doing DMA operations, add this quirk to disable Extended Tags for
the entire hierarchy to avoid the problem.

Signed-off-by: Liu Tao <liutao@phytium.com.cn>
Signed-off-by: Chen Baozi <chenbaozi@phytium.com.cn>
Signed-off-by: Wang Yinfeng <wangyinfeng@phytium.com.cn>
Signed-off-by: Wang Zhimin <wangzhimin1179@phytium.com.cn>
Signed-off-by: wangzhimin1179 <wangzhimin1179@phytium.com.cn>
@deepin-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign zeno-sole for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@deepin-ci-robot
Copy link

Hi @wangzhimin1179. Thanks for your PR.

I'm waiting for a deepin-community member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Avenger-285714 Avenger-285714 merged commit 0d8acba into deepin-community:linux-6.6.y May 28, 2024
1 of 2 checks passed
@MingcongBai MingcongBai mentioned this pull request May 28, 2024
Merged
3 tasks
@MingcongBai MingcongBai mentioned this pull request Jun 27, 2024
Closed
@MingcongBai MingcongBai mentioned this pull request Aug 20, 2024
Closed
@MingcongBai MingcongBai mentioned this pull request Nov 12, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@BLumia BLumia Awaiting requested review from BLumia

@justforlxz justforlxz Awaiting requested review from justforlxz

Assignees
No one assigned
Labels
needs-ok-to-test
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@wangzhimin1179 @deepin-ci-robot @Avenger-285714