mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aleksander Jan Bajkowski <olek2@wp.pl>
To: hauke@hauke-m.de, davem@davemloft.net, kuba@kernel.org,
	robh+dt@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: Aleksander Jan Bajkowski <olek2@wp.pl>
Subject: [PATCH 2/2] dt-bindings: net: lantiq-xrx200-net: Remove the burst length properties
Date: Tue, 26 Oct 2021 22:59:02 +0200	[thread overview]
Message-ID: <20211026205902.335936-2-olek2@wp.pl> (raw)
In-Reply-To: <20211026205902.335936-1-olek2@wp.pl>

All SoCs with this IP core support 8 burst length. Hauke
suggested to hardcode this value and simplify the driver.

Link: https://lkml.org/lkml/2021/9/14/1533
Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
---
 .../bindings/net/lantiq,xrx200-net.yaml          | 16 ----------------
 1 file changed, 16 deletions(-)

diff --git a/Documentation/devicetree/bindings/net/lantiq,xrx200-net.yaml b/Documentation/devicetree/bindings/net/lantiq,xrx200-net.yaml
index 16d831f22063..7bc074a42369 100644
--- a/Documentation/devicetree/bindings/net/lantiq,xrx200-net.yaml
+++ b/Documentation/devicetree/bindings/net/lantiq,xrx200-net.yaml
@@ -29,18 +29,6 @@ properties:
       - const: tx
       - const: rx
 
-  lantiq,tx-burst-length:
-    $ref: /schemas/types.yaml#/definitions/uint32
-    description: |
-      TX programmable burst length.
-    enum: [2, 4, 8]
-
-  lantiq,rx-burst-length:
-    $ref: /schemas/types.yaml#/definitions/uint32
-    description: |
-      RX programmable burst length.
-    enum: [2, 4, 8]
-
   '#address-cells':
     const: 1
 
@@ -53,8 +41,6 @@ required:
   - interrupt-parent
   - interrupts
   - interrupt-names
-  - lantiq,tx-burst-length
-  - lantiq,rx-burst-length
   - "#address-cells"
   - "#size-cells"
 
@@ -70,6 +56,4 @@ examples:
         interrupt-parent = <&icu0>;
         interrupts = <73>, <72>;
         interrupt-names = "tx", "rx";
-        lantiq,tx-burst-length = <8>;
-        lantiq,rx-burst-length = <8>;
     };
-- 
2.30.2


  reply	other threads:[~2021-10-26 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 20:59 [PATCH 1/2] net: lantiq_xrx200: Hardcode the burst length value Aleksander Jan Bajkowski
2021-10-26 20:59 ` Aleksander Jan Bajkowski [this message]
2021-10-29 11:30 ` patchwork-bot+netdevbpf

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=20211026205902.335936-2-olek2@wp.pl \
    --to=olek2@wp.pl \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=hauke@hauke-m.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@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®