From: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Lorenzo Bianconi <lorenzo@kernel.org>,
netdev@vger.kernel.org, nbd@nbd.name, john@phrozen.org,
sean.wang@mediatek.com, Mark-MC.Lee@mediatek.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, matthias.bgg@gmail.com,
linux-mediatek@lists.infradead.org, Bo.Jiao@mediatek.com,
sujuan.chen@mediatek.com, ryder.Lee@mediatek.com,
evelyn.tsai@mediatek.com, devicetree@vger.kernel.org,
robh+dt@kernel.org, daniel@makrotopia.org,
krzysztof.kozlowski+dt@linaro.org
Subject: Re: [PATCH v3 net-next 2/8] dt-bindings: net: mediatek: add WED RX binding for MT7986 eth driver
Date: Thu, 3 Nov 2022 18:51:10 +0100 [thread overview]
Message-ID: <Y2P/jq34IjyM2iXu@lore-desk> (raw)
In-Reply-To: <6d1bd86e-29f0-a3b2-700b-978d64990d56@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 10361 bytes --]
> On 03/11/2022 05:28, Lorenzo Bianconi wrote:
> > Document the binding for the RX Wireless Ethernet Dispatch core on the
> > MT7986 ethernet driver used to offload traffic received by WLAN NIC and
> > forwarded to LAN/WAN one.
> >
> > Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
> > ---
> > .../arm/mediatek/mediatek,mt7622-wed.yaml | 62 ++++++++++++++++++-
> > .../arm/mediatek/mediatek,mt7986-wo-boot.yaml | 47 ++++++++++++++
> > .../arm/mediatek/mediatek,mt7986-wo-ccif.yaml | 50 +++++++++++++++
> > .../arm/mediatek/mediatek,mt7986-wo-dlm.yaml | 50 +++++++++++++++
> > 4 files changed, 206 insertions(+), 3 deletions(-)
> > create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7986-wo-boot.yaml
> > create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7986-wo-ccif.yaml
> > create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7986-wo-dlm.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7622-wed.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7622-wed.yaml
> > index 84fb0a146b6e..9e34c5d15cec 100644
> > --- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7622-wed.yaml
> > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7622-wed.yaml
> > @@ -1,8 +1,8 @@
> > # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > %YAML 1.2
> > ---
> > -$id: "http://devicetree.org/schemas/arm/mediatek/mediatek,mt7622-wed.yaml#"
> > -$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> > +$id: http://devicetree.org/schemas/arm/mediatek/mediatek,mt7622-wed.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
>
> Split the cleanups from essential/functional changes.
ack, I will fix it in v4
>
> >
> > title: MediaTek Wireless Ethernet Dispatch Controller for MT7622
> >
> > @@ -29,6 +29,50 @@ properties:
> > interrupts:
> > maxItems: 1
> >
> > + memory-region:
> > + items:
> > + - description:
> > + Phandle for the node used to run firmware EMI region
>
> Merge above two lines. Drop "phandle for the node used to run"
ack, I will fix it in v4
>
> > + - description:
> > + Phandle for the node used to run firmware ILM region
> > + - description:
> > + Phandle for the node used to run firmware CPU DATA region
> > +
> > + memory-region-names:
> > + items:
> > + - const: wo-emi
> > + - const: wo-ilm
> > + - const: wo-data
> > +
> > + mediatek,wo-ccif:
> > + $ref: /schemas/types.yaml#/definitions/phandle
> > + description:
> > + Phandle to the mediatek wed-wo controller.
>
> Drop "Phandle to". Same in other cases.
ack, I will fix it in v4
>
> > +
> > + mediatek,wo-boot:
> > + $ref: /schemas/types.yaml#/definitions/phandle
> > + description:
> > + Phandle to the mediatek wed-wo boot interface.
> > +
> > + mediatek,wo-dlm:
> > + $ref: /schemas/types.yaml#/definitions/phandle
> > + description:
> > + Phandle to the mediatek wed-wo rx hw ring.
>
> rx->RX?
> hw->HW?
ack, I will fix it in v4
>
> > +
> > +allOf:
> > + - if:
> > + properties:
> > + compatible:
> > + contains:
> > + const: mediatek,mt7622-wed
> > + then:
> > + properties:
> > + memory-region-names: false
> > + memory-region: false
> > + mediatek,wo-boot: false
> > + mediatek,wo-ccif: false
> > + mediatek,wo-dlm: false
> > +
> > required:
> > - compatible
> > - reg
> > @@ -44,8 +88,20 @@ examples:
> > #address-cells = <2>;
> > #size-cells = <2>;
> > wed0: wed@1020a000 {
> > - compatible = "mediatek,mt7622-wed","syscon";
> > + compatible = "mediatek,mt7622-wed", "syscon";
> > reg = <0 0x1020a000 0 0x1000>;
> > interrupts = <GIC_SPI 214 IRQ_TYPE_LEVEL_LOW>;
> > };
> > +
> > + wed1: wed@15010000 {
>
> That's a separate example. - |
> Drop wed1 label.
ack, I will fix it in v4
>
> > + compatible = "mediatek,mt7986-wed", "syscon";
>
> And where is the compatible added?
>
> > + reg = <0 0x15010000 0 0x1000>;
> > + interrupts = <GIC_SPI 205 IRQ_TYPE_LEVEL_HIGH>;
> > +
> > + memory-region = <&wo_emi>, <&wo_data>, <&wo_ilm>;
> > + memory-region-names = "wo-emi", "wo-ilm", "wo-data";
> > + mediatek,wo-ccif = <&wo_ccif0>;
> > + mediatek,wo-boot = <&wo_boot>;
> > + mediatek,wo-dlm = <&wo_dlm0>;
> > + };
> > };
> > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7986-wo-boot.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7986-wo-boot.yaml
> > new file mode 100644
> > index 000000000000..6c3c514c48ef
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7986-wo-boot.yaml
>
> arm is only for top-level stuff. Choose appropriate subsystem, soc as
> last resort.
these chips are used only for networking so is net folder fine?
>
> > @@ -0,0 +1,47 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/arm/mediatek/mediatek,mt7986-wo-boot.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title:
> > + MediaTek Wireless Ethernet Dispatch WO boot controller interface for MT7986
> > +
> > +maintainers:
> > + - Lorenzo Bianconi <lorenzo@kernel.org>
> > + - Felix Fietkau <nbd@nbd.name>
> > +
> > +description:
> > + The mediatek wo-boot provides a configuration interface for WED WO
> > + boot controller on MT7986 soc.
>
> And what is "WED WO boot controller?
WED WO is a chip used for networking packet processing offloaded to the Soc
(e.g. packet reordering). WED WO boot is the memory used to store start address
of wo firmware. Anyway I will let Sujuan comment on this.
>
> > +
> > +properties:
> > + compatible:
> > + items:
> > + - enum:
> > + - mediatek,mt7986-wo-boot
> > + - const: syscon
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + interrupts:
> > + maxItems: 1
> > +
> > +required:
> > + - compatible
> > + - reg
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + soc {
> > + #address-cells = <2>;
> > + #size-cells = <2>;
> > +
> > + wo_boot: syscon@15194000 {
> > + compatible = "mediatek,mt7986-wo-boot", "syscon";
> > + reg = <0 0x15194000 0 0x1000>;
> > + };
> > + };
> > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7986-wo-ccif.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7986-wo-ccif.yaml
> > new file mode 100644
> > index 000000000000..6357a206587a
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7986-wo-ccif.yaml
> > @@ -0,0 +1,50 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/arm/mediatek/mediatek,mt7986-wo-ccif.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: MediaTek Wireless Ethernet Dispatch WO controller interface for MT7986
> > +
> > +maintainers:
> > + - Lorenzo Bianconi <lorenzo@kernel.org>
> > + - Felix Fietkau <nbd@nbd.name>
> > +
> > +description:
> > + The mediatek wo-ccif provides a configuration interface for WED WO
> > + controller on MT7986 soc.
>
> All previous comments apply.
>
> > +
> > +properties:
> > + compatible:
> > + items:
> > + - enum:
> > + - mediatek,mt7986-wo-ccif
> > + - const: syscon
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + interrupts:
> > + maxItems: 1
> > +
> > +required:
> > + - compatible
> > + - reg
> > + - interrupts
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + #include <dt-bindings/interrupt-controller/arm-gic.h>
> > + #include <dt-bindings/interrupt-controller/irq.h>
> > + soc {
> > + #address-cells = <2>;
> > + #size-cells = <2>;
> > +
> > + wo_ccif0: syscon@151a5000 {
> > + compatible = "mediatek,mt7986-wo-ccif", "syscon";
> > + reg = <0 0x151a5000 0 0x1000>;
> > + interrupts = <GIC_SPI 205 IRQ_TYPE_LEVEL_HIGH>;
> > + };
> > + };
> > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7986-wo-dlm.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7986-wo-dlm.yaml
> > new file mode 100644
> > index 000000000000..a499956d9e07
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7986-wo-dlm.yaml
> > @@ -0,0 +1,50 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/arm/mediatek/mediatek,mt7986-wo-dlm.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: MediaTek Wireless Ethernet Dispatch WO hw rx ring interface for MT7986
> > +
> > +maintainers:
> > + - Lorenzo Bianconi <lorenzo@kernel.org>
> > + - Felix Fietkau <nbd@nbd.name>
> > +
> > +description:
> > + The mediatek wo-dlm provides a configuration interface for WED WO
> > + rx ring on MT7986 soc.
> > +
> > +properties:
> > + compatible:
> > + const: mediatek,mt7986-wo-dlm
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + resets:
> > + maxItems: 1
> > +
> > + reset-names:
> > + maxItems: 1
> > +
> > +required:
> > + - compatible
> > + - reg
> > + - resets
> > + - reset-names
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + soc {
> > + #address-cells = <2>;
> > + #size-cells = <2>;
> > +
> > + wo_dlm0: wo-dlm@151e8000 {
>
> Node names should be generic.
> https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
DLM is a chip used to store the data rx ring of wo firmware. I do not have a
better node name (naming is always hard). Can you please suggest a better name?
Regards,
Lorenzo
>
>
> Best regards,
> Krzysztof
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-11-03 17:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 9:27 [PATCH v3 net-next 0/8] introduce WED RX support to MT7986 SoC Lorenzo Bianconi
2022-11-03 9:28 ` [PATCH v3 net-next 1/8] arm64: dts: mediatek: mt7986: add support for RX Wireless Ethernet Dispatch Lorenzo Bianconi
2022-11-03 14:13 ` AngeloGioacchino Del Regno
2022-11-03 17:58 ` Lorenzo Bianconi
2022-11-04 9:05 ` Lorenzo Bianconi
2022-11-04 9:10 ` AngeloGioacchino Del Regno
2022-11-03 9:28 ` [PATCH v3 net-next 2/8] dt-bindings: net: mediatek: add WED RX binding for MT7986 eth driver Lorenzo Bianconi
2022-11-03 15:08 ` Krzysztof Kozlowski
2022-11-03 17:51 ` Lorenzo Bianconi [this message]
2022-11-03 18:00 ` Krzysztof Kozlowski
2022-11-03 18:29 ` Lorenzo Bianconi
2022-11-07 10:04 ` Krzysztof Kozlowski
2022-11-08 14:20 ` Lorenzo Bianconi
2022-12-06 3:18 ` Sujuan Chen (陈素娟)
2022-11-03 9:28 ` [PATCH v3 net-next 3/8] net: ethernet: mtk_wed: introduce wed mcu support Lorenzo Bianconi
2022-11-03 14:23 ` AngeloGioacchino Del Regno
2022-11-03 17:57 ` Lorenzo Bianconi
2022-11-04 2:33 ` Daniel Golle
2022-11-04 8:30 ` Lorenzo Bianconi
2022-11-03 9:28 ` [PATCH v3 net-next 4/8] net: ethernet: mtk_wed: introduce wed wo support Lorenzo Bianconi
2022-11-03 9:28 ` [PATCH v3 net-next 5/8] net: ethernet: mtk_wed: rename tx_wdma array in rx_wdma Lorenzo Bianconi
2022-11-03 9:28 ` [PATCH v3 net-next 6/8] net: ethernet: mtk_wed: add configure wed wo support Lorenzo Bianconi
2022-11-03 9:28 ` [PATCH v3 net-next 7/8] net: ethernet: mtk_wed: add rx mib counters Lorenzo Bianconi
2022-11-03 9:28 ` [PATCH v3 net-next 8/8] MAINTAINERS: update MEDIATEK ETHERNET entry Lorenzo Bianconi
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=Y2P/jq34IjyM2iXu@lore-desk \
--to=lorenzo.bianconi@redhat.com \
--cc=Bo.Jiao@mediatek.com \
--cc=Mark-MC.Lee@mediatek.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=evelyn.tsai@mediatek.com \
--cc=john@phrozen.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=ryder.Lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=sujuan.chen@mediatek.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).