LKML Archive on
help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <>
To: Rob Herring <>
	Mauro Carvalho Chehab <>,
	Binghui Wang <>,
	Rob Herring <>,
	Xiaowei Song <>,,,
Subject: [PATCH 0/2] Fix examples at pci/hisilicon,kirin-pcie.yaml
Date: Thu, 12 Aug 2021 09:55:50 +0200	[thread overview]
Message-ID: <> (raw)

Hi Rob,

This small series fix the HiKey960 and HiKey970 examples for the
DT schema defined at pci/hisilicon,kirin-pcie.yaml,

The first one fix bus-range for HiKey960. It is meant to suppress a
resource conflict warning when PCI probe happens. I sent a separate
patch to be applied by HiSilicon maintainers with the DTS change.

The second one fix the topology of the PCIe bridge found at
HiKey970. It matches the DTS file that I'll submit once everything
gets merged. With such DT schema, all of_node sysfs files should
be created, pointing to the right place. It also supresses the bus-range

Please apply on your tree, as it depends on the other patches you
already merged there.


Mauro Carvalho Chehab (2):
  dt-bindings: PCI: kirin: fix bus-range
  dt-bindings: PCI: kirin: fix HiKey970 example

 .../bindings/pci/hisilicon,kirin-pcie.yaml    | 67 ++++++++++---------
 1 file changed, 37 insertions(+), 30 deletions(-)


             reply	other threads:[~2021-08-12  7:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12  7:55 Mauro Carvalho Chehab [this message]
2021-08-12  7:55 ` [PATCH 1/2] dt-bindings: PCI: kirin: fix bus-range Mauro Carvalho Chehab
2021-08-12  7:55 ` [PATCH 2/2] dt-bindings: PCI: kirin: fix HiKey970 example Mauro Carvalho Chehab
2021-08-12 12:56   ` Rob Herring
2021-08-13 14:32     ` Mauro Carvalho Chehab
2021-08-13 14:39       ` Mauro Carvalho Chehab

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