From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Jingoo Han <jingoohan1@gmail.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Subject: [PATCH v3 0/2] dt-bindings: PCI: uniphier: Fix endpoint descriptions
Date: Mon, 18 Apr 2022 09:18:18 +0900 [thread overview]
Message-ID: <1650241100-3606-1-git-send-email-hayashi.kunihiko@socionext.com> (raw)
This series fixes dt-schema descriptions for PCI endpoint controller
implemented in UniPhier SoCs.
Changes since v2:
- Move some items to minimize if/then schemas in Patch 2
- Remove Patch 3 because the warning comment is for an unmerged source
Changes since v1:
- Fix "config" in the Patch 1 commit message to "addr_space"
Kunihiko Hayashi (2):
dt-bindings: PCI: designware-ep: Increase maxItems of reg and
reg-names
dt-bindings: PCI: uniphier-ep: Clean up reg, clocks, resets, and their
names using compatible string
.../bindings/pci/snps,dw-pcie-ep.yaml | 4 +-
.../pci/socionext,uniphier-pcie-ep.yaml | 76 ++++++++++++-------
2 files changed, 51 insertions(+), 29 deletions(-)
--
2.25.1
next reply other threads:[~2022-04-18 0:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 0:18 Kunihiko Hayashi [this message]
2022-04-18 0:18 ` [PATCH v3 1/2] dt-bindings: PCI: designware-ep: Increase maxItems of reg and reg-names Kunihiko Hayashi
2022-04-20 21:22 ` Rob Herring
2022-04-18 0:18 ` [PATCH v3 2/2] dt-bindings: PCI: uniphier-ep: Clean up reg, clocks, resets, and their names using compatible string Kunihiko Hayashi
2022-04-19 16:35 ` Rob Herring
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=1650241100-3606-1-git-send-email-hayashi.kunihiko@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).