linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aleksander Jan Bajkowski <olek2@wp.pl>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	tsbogend@alpha.franken.de, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, john@phrozen.org, olek2@wp.pl,
	devicetree@vger.kernel.org, netdev@vger.kernel.org,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH net v2 0/2] mips: lantiq: fix ethernet support
Date: Sun, 17 Aug 2025 14:49:05 +0200	[thread overview]
Message-ID: <20250817131022.3796476-1-olek2@wp.pl> (raw)

This series fixes broken Ethernet in the upstream danube dts. The
driver doesn't attach due to missing burst length property. OpenWRT
has its own dts, which is correct, so the problem has only been
spotted now. Other dts inconsistencies with bindings have been
fixed as well.

---
Changes in v2:
- renaming clocks in sysctrl
---
Aleksander Jan Bajkowski (2):
  mips: dts: lantiq: danube: add missing burst length property
  mips: lantiq: xway: sysctrl: rename the etop node

 arch/mips/boot/dts/lantiq/danube_easy50712.dts |  5 ++++-
 arch/mips/lantiq/xway/sysctrl.c                | 10 +++++-----
 2 files changed, 9 insertions(+), 6 deletions(-)

-- 
2.47.2


             reply	other threads:[~2025-08-17 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-17 12:49 Aleksander Jan Bajkowski [this message]
2025-08-17 12:49 ` [PATCH net v2 1/2] mips: dts: lantiq: danube: add missing burst length property Aleksander Jan Bajkowski
2025-08-17 12:49 ` [PATCH net v2 2/2] mips: lantiq: xway: sysctrl: rename the etop node Aleksander Jan Bajkowski
2025-08-20  1:26 ` [PATCH net v2 0/2] mips: lantiq: fix ethernet support Jakub Kicinski
2025-08-20 10:24   ` Thomas Bogendoerfer
2025-08-20 15:18     ` Jakub Kicinski
2025-08-22 20:05 ` Thomas Bogendoerfer

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=20250817131022.3796476-1-olek2@wp.pl \
    --to=olek2@wp.pl \
    --cc=andrew+netdev@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=john@phrozen.org \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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).