netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marek Behún" <kabel@kernel.org>
To: Christian Marangi <ansuelsmth@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org
Cc: "Marek Behún" <kabel@kernel.org>
Subject: [PATCH net 0/2] net: dsa: qca8k: fix qca8k driver for Turris 1.x
Date: Mon,  2 Oct 2023 12:46:10 +0200	[thread overview]
Message-ID: <20231002104612.21898-1-kabel@kernel.org> (raw)

Hi,

this patch series contains two fixes to commits that broke qca8k driver
on the Turris 1.x router.

The first patch is another fix of qca8k's regmap implementation on
big-endian systems.

The second patch locks the MDIO bus even when accessing switch internal
PHYs via ethernet management frames, since it seems that internally the
switch still uses MDIO transfers and these can leak outside of the
switch back to the MDIO bus, potentially conflicting with the WAN PHY
register accesses.

Marek

Marek Behún (2):
  net: dsa: qca8k: fix regmap bulk read/write methods on big endian
    systems
  net: dsa: qca8k: fix potential MDIO bus conflict when accessing
    internal PHYs via management frames

 drivers/net/dsa/qca/qca8k-8xxx.c | 15 +++++++++++++--
 1 file changed, 13 insertions(+), 2 deletions(-)

-- 
2.41.0


             reply	other threads:[~2023-10-02 10:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02 10:46 Marek Behún [this message]
2023-10-02 10:46 ` [PATCH net 1/2] net: dsa: qca8k: fix regmap bulk read/write methods on big endian systems Marek Behún
2023-10-02 12:03   ` Christian Marangi
2023-10-03 15:22   ` Simon Horman
2023-10-02 10:46 ` [PATCH net 2/2] net: dsa: qca8k: fix potential MDIO bus conflict when accessing internal PHYs via management frames Marek Behún
2023-10-02 12:11   ` Christian Marangi
2023-10-03 10:05     ` Marek Behún
2023-10-03 10:45       ` Christian Marangi

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=20231002104612.21898-1-kabel@kernel.org \
    --to=kabel@kernel.org \
    --cc=ansuelsmth@gmail.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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).