archive mirror
 help / color / mirror / Atom feed
From: "Jan Kundrát" <>
To: Rob Herring <>
Cc: <>,
	Thomas Petazzoni <>,
	Jason Cooper <>,
	Lorenzo Pieralisi <>,
	Bjorn Helgaas <>,
	Russell King <>, <>,
Subject: Re: [PATCH v2] PCI: mvebu: Fix duplicate resource requests
Date: Mon, 26 Oct 2020 17:42:20 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On pátek 23. října 2020 16:52:52 CEST, Rob Herring wrote:
> With commit 669cbc708122 ("PCI: Move DT resource setup into
> devm_pci_alloc_host_bridge()"), the DT 'ranges' is parsed and populated
> into resources when the host bridge is allocated. The resources are
> requested as well, but that happens a 2nd time for the mvebu driver in
> mvebu_pcie_parse_request_resources(). We should only be requesting the
> additional resources added in mvebu_pcie_parse_request_resources().
> These are not added by default because the use custom properties rather
> than standard DT address translation.
> Also, the bus ranges was also populated by default, so we can remove
> it from mvebu_pci_host_probe().
> Fixes: 669cbc708122 ("PCI: Move DT resource setup into 
> devm_pci_alloc_host_bridge()")
> Bugzilla:
> Reported-by:
> Cc: Thomas Petazzoni <>
> Cc: Jason Cooper <>
> Cc: Lorenzo Pieralisi <>
> Cc: Bjorn Helgaas <>
> Cc: Russell King <>
> Cc:
> Cc:
> Signed-off-by: Rob Herring <>

Without this patch, 5.9.1 won't find the eMMC card on Clearfog Base for me, 

Tested-by: Jan Kundrát <>

Thanks for the fix,

  reply	other threads:[~2020-10-26 16:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23 14:52 [PATCH v2] PCI: mvebu: Fix duplicate resource requests Rob Herring
2020-10-26 16:42 ` Jan Kundrát [this message]
2020-11-03 16:29 ` Lorenzo Pieralisi
2020-11-03 19:32 ` Bjorn Helgaas

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \

* 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).