From: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
To: Jingoo Han <jingoohan1@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Shawn Lin <shawn.lin@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org,
Niklas Cassel <cassel@kernel.org>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: dw-rockchip: Disable BAR 0 and BAR 1 for RC mode
Date: Wed, 14 Jan 2026 13:07:33 +0530 [thread overview]
Message-ID: <176837625328.207176.2407040245231111635.b4-ty@kernel.org> (raw)
In-Reply-To: <1766570461-138256-1-git-send-email-shawn.lin@rock-chips.com>
On Wed, 24 Dec 2025 18:01:01 +0800, Shawn Lin wrote:
> To slitence the useless bar allocation error log of RC when
> scanning bus, as RC doesn't need BARs at all.
>
> pci 0000:00:00.0: [1d87:3588] type 01 class 0x060400 PCIe Root Port
> pci 0000:00:00.0: BAR 0 [mem 0x00000000-0x3fffffff]
> pci 0000:00:00.0: BAR 1 [mem 0x00000000-0x3fffffff]
> pci 0000:00:00.0: ROM [mem 0x00000000-0x0000ffff pref]
> ...
> pci 0000:00:00.0: BAR 0 [mem 0x900000000-0x93fffffff]: assigned
> pci 0000:00:00.0: BAR 1 [mem size 0x40000000]: can't assign; no space
> pci 0000:00:00.0: BAR 1 [mem size 0x40000000]: failed to assign
> pci 0000:00:00.0: ROM [mem 0xf0200000-0xf020ffff pref]: assigned
> pci 0000:00:00.0: BAR 0 [mem 0x900000000-0x93fffffff]: releasing
> pci 0000:00:00.0: ROM [mem 0xf0200000-0xf020ffff pref]: releasing
> pci 0000:00:00.0: BAR 0 [mem 0x900000000-0x93fffffff]: assigned
> pci 0000:00:00.0: BAR 1 [mem size 0x40000000]: can't assign; no space
> pci 0000:00:00.0: BAR 1 [mem size 0x40000000]: failed to assign
>
> [...]
Applied, thanks!
[1/1] PCI: dw-rockchip: Disable BAR 0 and BAR 1 for RC mode
commit: b5d712e5b87fc56ff838684afb1bae359eb8069f
Best regards,
--
Manivannan Sadhasivam <mani@kernel.org>
prev parent reply other threads:[~2026-01-14 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 10:01 [PATCH] PCI: dw-rockchip: Disable BAR 0 and BAR 1 for RC mode Shawn Lin
2026-01-13 14:29 ` Manivannan Sadhasivam
2026-01-14 1:32 ` Shawn Lin
2026-01-14 7:38 ` Manivannan Sadhasivam
2026-01-14 7:37 ` Manivannan Sadhasivam [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=176837625328.207176.2407040245231111635.b4-ty@kernel.org \
--to=manivannan.sadhasivam@oss.qualcomm.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=shawn.lin@rock-chips.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