mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Vidya Sagar <vidyas@nvidia.com>,
	bhelgaas@google.com, lorenzo.pieralisi@arm.com,
	robh+dt@kernel.org, thierry.reding@gmail.com,
	jonathanh@nvidia.com
Cc: kishon@ti.com, vkoul@kernel.org, kw@linux.com,
	p.zabel@pengutronix.de, mperttunen@nvidia.com,
	linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-phy@lists.infradead.org, kthota@nvidia.com,
	mmaddireddy@nvidia.com, sagar.tv@gmail.com,
	Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH V3 02/11] dt-bindings: pci: tegra: Convert to json-schema
Date: Wed, 6 Jul 2022 11:58:46 +0200	[thread overview]
Message-ID: <e7ba92aa-c501-929b-6962-4cb4c6a1dc48@linaro.org> (raw)
In-Reply-To: <3e21dbaa-b478-5713-5355-319d2843167f@nvidia.com>

On 06/07/2022 11:51, Vidya Sagar wrote:
>>> +  phy-names:
>>> +    minItems: 1
>>> +    maxItems: 16
>>> +    items:
>>> +      pattern: "^p2u-[0-9]+$"
>>
>> No, because this allows any/unspecified order. Please list the items, so
>> the order is fixed.
> 
> Not all controllers are going to have all of them specified. Number of
> these entries depend on the number of lanes assigned to that particular 
> controller. In this scenario, I thought specifying it using 'pattern' 
> should be fine. Please let me know if there is any other better way to 
> specify this.

As I understood previous bindings and your message above, these are all
incremented by one, so just list them and drop maxItems.

Trim the context, it makes it easier to spot the actual response. You
quoted a lot above and a lot below. I do not know if there is something
more to discuss? Usually quote means there is but I could not find... If
there is, use replying style matching mailing list.

Best regards,
Krzysztof

  reply	other threads:[~2022-07-06  9:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29  6:04 [PATCH V3 00/11] PCI: tegra: Add Tegra234 PCIe support Vidya Sagar
2022-06-29  6:04 ` [PATCH V3 01/11] dt-bindings: PHY: P2U: Add support for Tegra234 P2U block Vidya Sagar
2022-07-05  6:14   ` Vinod Koul
2022-06-29  6:04 ` [PATCH V3 02/11] dt-bindings: pci: tegra: Convert to json-schema Vidya Sagar
2022-06-29  6:29   ` Krzysztof Kozlowski
2022-07-06  9:51     ` Vidya Sagar
2022-07-06  9:58       ` Krzysztof Kozlowski [this message]
2022-06-30 21:04   ` Rob Herring
2022-07-06  9:53     ` Vidya Sagar
2022-07-06 10:06       ` Krzysztof Kozlowski
2022-07-06 10:46         ` Vidya Sagar
2022-07-06 15:06           ` Krzysztof Kozlowski
2022-07-06 18:11       ` Rob Herring
2022-06-29  6:04 ` [PATCH V3 03/11] dt-bindings: PCI: tegra234: Add schema for tegra234 rootport mode Vidya Sagar
2022-06-29  6:32   ` Krzysztof Kozlowski
2022-06-29  6:04 ` [PATCH V3 04/11] dt-bindings: PCI: tegra234: Add schema for tegra234 endpoint mode Vidya Sagar
2022-06-29  6:33   ` Krzysztof Kozlowski
2022-06-29  6:04 ` [PATCH V3 05/11] arm64: tegra: Add regulators required for PCIe Vidya Sagar
2022-06-29  6:34   ` Krzysztof Kozlowski
2022-06-29  6:04 ` [PATCH V3 06/11] arm64: tegra: Add P2U and PCIe controller nodes to Tegra234 DT Vidya Sagar
2022-06-29  6:35   ` Krzysztof Kozlowski
2022-06-29  6:04 ` [PATCH V3 07/11] arm64: tegra: Enable PCIe slots in P3737-0000 board Vidya Sagar
2022-06-29  6:04 ` [PATCH V3 08/11] phy: tegra: Add PCIe PIPE2UPHY support for Tegra234 Vidya Sagar
2022-07-05  6:15   ` Vinod Koul
2022-06-29  6:04 ` [PATCH V3 09/11] PCI: Disable MSI for Tegra234 root ports Vidya Sagar
2022-06-29  6:04 ` [PATCH V3 10/11] Revert "PCI: tegra194: Rename tegra_pcie_dw to tegra194_pcie" Vidya Sagar
2022-06-29  6:04 ` [PATCH V3 11/11] PCI: tegra: Add Tegra234 PCIe support Vidya Sagar

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=e7ba92aa-c501-929b-6962-4cb4c6a1dc48@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=kishon@ti.com \
    --cc=kthota@nvidia.com \
    --cc=kw@linux.com \
    --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=lorenzo.pieralisi@arm.com \
    --cc=mmaddireddy@nvidia.com \
    --cc=mperttunen@nvidia.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=sagar.tv@gmail.com \
    --cc=thierry.reding@gmail.com \
    --cc=treding@nvidia.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

all inboxes | Powered by JetHome®