From: Xu Yilun <yilun.xu@linux.intel.com>
To: Michal Simek <michal.simek@amd.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>,
"open list:FPGA MANAGER FRAMEWORK" <linux-fpga@vger.kernel.org>
Subject: Re: [PATCH 2/2] dt-bindings: fpga: altera: Convert bridge bindings to yaml
Date: Tue, 9 Jan 2024 12:04:56 +0800 [thread overview]
Message-ID: <ZZzF6Fb8aRpde85Y@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <485d0685-646c-44b8-823a-49870e109103@amd.com>
On Mon, Jan 08, 2024 at 09:12:21AM +0100, Michal Simek wrote:
>
>
> On 1/8/24 08:46, Xu Yilun wrote:
> > On Fri, Jan 05, 2024 at 05:04:31PM +0100, Michal Simek wrote:
> > > Convert Altera's bridges to yaml with using fpga-bridge.yaml.
> > >
> > > Signed-off-by: Michal Simek <michal.simek@amd.com>
> > > ---
> > >
> > > .../fpga/altera-fpga2sdram-bridge.txt | 13 ----
> > > .../fpga/altera-fpga2sdram-bridge.yaml | 34 ++++++++++
> > > .../bindings/fpga/altera-freeze-bridge.txt | 20 ------
> > > .../bindings/fpga/altera-freeze-bridge.yaml | 41 ++++++++++++
> > > .../bindings/fpga/altera-hps2fpga-bridge.txt | 36 -----------
> > > .../bindings/fpga/altera-hps2fpga-bridge.yaml | 63 +++++++++++++++++++
> > > 6 files changed, 138 insertions(+), 69 deletions(-)
> > > delete mode 100644 Documentation/devicetree/bindings/fpga/altera-fpga2sdram-bridge.txt
> > > create mode 100644 Documentation/devicetree/bindings/fpga/altera-fpga2sdram-bridge.yaml
> > > delete mode 100644 Documentation/devicetree/bindings/fpga/altera-freeze-bridge.txt
> > > create mode 100644 Documentation/devicetree/bindings/fpga/altera-freeze-bridge.yaml
> > > delete mode 100644 Documentation/devicetree/bindings/fpga/altera-hps2fpga-bridge.txt
> > > create mode 100644 Documentation/devicetree/bindings/fpga/altera-hps2fpga-bridge.yaml
> > >
> > > diff --git a/Documentation/devicetree/bindings/fpga/altera-fpga2sdram-bridge.txt b/Documentation/devicetree/bindings/fpga/altera-fpga2sdram-bridge.txt
> > > deleted file mode 100644
> > > index 5dd0ff0f7b4e..000000000000
> > > --- a/Documentation/devicetree/bindings/fpga/altera-fpga2sdram-bridge.txt
> > > +++ /dev/null
> > > @@ -1,13 +0,0 @@
> > > -Altera FPGA To SDRAM Bridge Driver
> > > -
> > > -Required properties:
> > > -- compatible : Should contain "altr,socfpga-fpga2sdram-bridge"
> > > -
> > > -See Documentation/devicetree/bindings/fpga/fpga-bridge.txt for generic bindings.
> > > -
> > > -Example:
> > > - fpga_bridge3: fpga-bridge@ffc25080 {
> > > - compatible = "altr,socfpga-fpga2sdram-bridge";
> > > - reg = <0xffc25080 0x4>;
> > > - bridge-enable = <0>;
> > > - };
> > > diff --git a/Documentation/devicetree/bindings/fpga/altera-fpga2sdram-bridge.yaml b/Documentation/devicetree/bindings/fpga/altera-fpga2sdram-bridge.yaml
> > > new file mode 100644
> > > index 000000000000..a3f3fe2729f2
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/fpga/altera-fpga2sdram-bridge.yaml
> > > @@ -0,0 +1,34 @@
> > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > > +%YAML 1.2
> > > +---
> > > +$id: http://devicetree.org/schemas/fpga/altera-fpga2sdram-bridge.yaml#
> > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > +
> > > +title: Altera FPGA To SDRAM Bridge
> > > +
> > > +maintainers:
> > > + - Xu Yilun <yilun.xu@intel.com>
> > > +
> > > +allOf:
> > > + - $ref: fpga-bridge.yaml#
> > > +
> > > +properties:
> > > + compatible:
> > > + const: altr,socfpga-fpga2sdram-bridge
> > > +
> > > + reg:
> > > + maxItems: 1
> > > +
> > > +required:
> > > + - compatible
> > > + - reg
> >
> > Is the 'reg' required? I didn't see it in original txt.
>
> you tell me. It was in example that's why I made it mandatory.
In original txt, 'reg' is not listed as required but in Example. I
searched the code but didn't see 'reg' useful. So lets delete it
from 'required:'
Thanks,
Yilun
next prev parent reply other threads:[~2024-01-09 4:07 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 [this message]
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
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=ZZzF6Fb8aRpde85Y@yilunxu-OptiPlex-7050 \
--to=yilun.xu@linux.intel.com \
--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=robh+dt@kernel.org \
--cc=trix@redhat.com \
--cc=yilun.xu@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