From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Manikanta Maddireddy <mmaddireddy@nvidia.com>,
vkoul@kernel.org, kishon@kernel.org,
krzysztof.kozlowski+dt@linaro.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, vidyas@nvidia.com
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, bhelgaas@google.com,
lpieralisi@kernel.org, nkristam@nvidia.com
Subject: Re: [PATCH 1/3] dt-bindings: PHY: P2U: Add PCIe lane margining support
Date: Thu, 24 Nov 2022 09:45:19 +0100 [thread overview]
Message-ID: <0b203c11-851c-fd6c-faeb-e283b158f1c8@linaro.org> (raw)
In-Reply-To: <20221124083510.3008139-2-mmaddireddy@nvidia.com>
On 24/11/2022 09:35, Manikanta Maddireddy wrote:
> Tegra234 supports PCIe lane margining. P2U HW acts as a relay to exchange
typo: merging?
> margin control data and margin status between PCIe controller and UPHY.
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
>
> Signed-off-by: Manikanta Maddireddy <mmaddireddy@nvidia.com>
> ---
> .../bindings/phy/phy-tegra194-p2u.yaml | 50 +++++++++++++++++++
> 1 file changed, 50 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/phy/phy-tegra194-p2u.yaml b/Documentation/devicetree/bindings/phy/phy-tegra194-p2u.yaml
> index 4dc5205d893b..0ba3f6a0b474 100644
> --- a/Documentation/devicetree/bindings/phy/phy-tegra194-p2u.yaml
> +++ b/Documentation/devicetree/bindings/phy/phy-tegra194-p2u.yaml
> @@ -40,6 +40,51 @@ properties:
> '#phy-cells':
> const: 0
>
> + interrupts:
> + items:
> + description: P2U interrupt for Gen4 lane margining functionality.
typo: merging?
> +
> + interrupt-names:
> + items:
> + - const: intr
Drop entire property, not really useful.
> +
> + nvidia,bpmp:
> + $ref: /schemas/types.yaml#/definitions/phandle-array
> + description: Must contain a pair of phandles to BPMP controller node followed by P2U ID.
> + items:
> + - items:
> + - description: phandle to BPMP controller node
> + - description: P2U instance ID
> + maximum: 24
> +
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - nvidia,tegra194-p2u
> + then:
> + required:
> + - reg
> + - reg-names
> + - '#phy-cells'
That's not how it should be done. You have only two variants here, so
add a "required:" block with above and only one if:then: clause for
interrupts and nvidia,bpmp.
Requiring reg/reg-names/phy-cells should be in separate patch with its
own reasoning.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-24 8:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 8:35 [IP REVIEW PATCH 0/3] Add support for Lane Margining at Receiver Manikanta Maddireddy
2022-11-24 8:35 ` [PATCH 1/3] dt-bindings: PHY: P2U: Add PCIe lane margining support Manikanta Maddireddy
2022-11-24 8:45 ` Krzysztof Kozlowski [this message]
2022-11-30 15:11 ` Manikanta Maddireddy
2022-11-30 15:15 ` Krzysztof Kozlowski
2022-11-30 16:13 ` Manikanta Maddireddy
2022-11-24 8:35 ` [PATCH 2/3] arm64: tegra: Add uphy lane number and intr in p2u nodes Manikanta Maddireddy
2022-12-01 9:44 ` Jon Hunter
2022-12-02 5:14 ` Manikanta Maddireddy
2022-11-24 8:35 ` [PATCH 3/3] phy: tegra: Add lane margin support Manikanta Maddireddy
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=0b203c11-851c-fd6c-faeb-e283b158f1c8@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mmaddireddy@nvidia.com \
--cc=nkristam@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=vidyas@nvidia.com \
--cc=vkoul@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).