From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Michal Simek <michal.simek@amd.com>, Xu Yilun <yilun.xu@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, monstr@monstr.eu,
michal.simek@xilinx.com, git@xilinx.com,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Moritz Fischer <mdf@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Tom Rix <trix@redhat.com>, Wu Hao <hao.wu@intel.com>,
Xu Yilun <yilun.xu@intel.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
kishore Manne <nava.kishore.manne@amd.com>,
"open list:FPGA MANAGER FRAMEWORK" <linux-fpga@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: fpga: Convert bridge binding to yaml
Date: Tue, 9 Jan 2024 09:16:33 +0100 [thread overview]
Message-ID: <f3aeff02-2560-46e7-a712-1f8d323f43a4@linaro.org> (raw)
In-Reply-To: <e88205a2-f8b6-42c7-82cc-bfc08a680f3d@linaro.org>
On 09/01/2024 09:15, Krzysztof Kozlowski wrote:
>>>>>>> +properties:
>>>>>>> + $nodename:
>>>>>>> + pattern: "^fpga-bridge(@.*)?$"
>>>>>>
>>>>>> Not sure, but maybe we need to allow fpga-bridge-1? Could we have more
>>>>>> than one bridge on given system?
>>>>>
>>>>> Yilun: Any comment on this?
>>>>
>>>> We can have more bridges, but IIUC people use fpga-bridge@0, fpga-bridge@0
>>>> to identify them. So the expression is OK to me.
>>>
>>> So you claim unit address thus reg with some sort of bus address is a
>>> requirement? Then "?" is not correct in that pattern.
>>
>> I expect it is about that people are using fpga-bridge@0 but bridge is not on
>> the bus. Yilun said that reg property in altr,socfpga-fpga2sdram-bridge.yaml is
>> optional which means no reg property no @XXX in node name.
>> That's why I think that expression is correct. If there are more bridges without
>> reg property then I expect we need to get more examples to align expression.
>
> If we allow node name without unit address, thus not being part of any
> bus, then the only question is whether it is possible to have system
> with more than two FPGA bridges. If the answer is "yes", which I think
> is the case, then the pattern should already allow it:
>
> (@[0-9a-f]+|-[0-9]+)?
Or better go with what I used recently for narrowed choices:
(@.*|-([0-9]|[1-9][0-9]+))?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-01-09 8:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 16:04 [PATCH 1/2] dt-bindings: fpga: Convert bridge binding to yaml Michal Simek
2024-01-05 16:04 ` [PATCH 2/2] dt-bindings: fpga: altera: Convert bridge bindings " Michal Simek
2024-01-08 7:46 ` Xu Yilun
2024-01-08 8:12 ` Michal Simek
2024-01-09 4:04 ` Xu Yilun
2024-01-08 9:12 ` Krzysztof Kozlowski
2024-01-08 7:47 ` [PATCH 1/2] dt-bindings: fpga: Convert bridge binding " Xu Yilun
2024-01-08 9:09 ` Krzysztof Kozlowski
2024-01-08 9:16 ` Michal Simek
2024-01-09 3:53 ` Xu Yilun
2024-01-09 8:00 ` Krzysztof Kozlowski
2024-01-09 8:06 ` Michal Simek
2024-01-09 8:15 ` Krzysztof Kozlowski
2024-01-09 8:16 ` Krzysztof Kozlowski [this message]
2024-01-09 10:22 ` Xu Yilun
2024-01-09 13:31 ` Michal Simek
2024-01-09 8:20 ` Michal Simek
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=f3aeff02-2560-46e7-a712-1f8d323f43a4@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=hao.wu@intel.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=michal.simek@amd.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=nava.kishore.manne@amd.com \
--cc=robh+dt@kernel.org \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.com \
--cc=yilun.xu@linux.intel.com \
/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).