public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Selvamani Rajagopal <Selvamani.Rajagopal@onsemi.com>
Cc: Piergiorgio Beruto <Pier.Beruto@onsemi.com>,
	"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 4/5] onsemi: ncn260xx: Add driver support for NCN26010 and TS2500 MAC-PHY
Date: Mon, 4 May 2026 21:23:46 +0200	[thread overview]
Message-ID: <e2f03fc4-2948-4046-83a6-7d587e09ef62@lunn.ch> (raw)
In-Reply-To: <CY8PR02MB9249082A82E8E2C503D6773683312@CY8PR02MB9249.namprd02.prod.outlook.com>

> > You failed to answer my question about this. What happens with your
> > device if you access C45 registers which don't exist?
> 
> Sorry. Waiting for an answer from hardware designer.

It should not be too difficult to program up something like:

	for (int mmd = 0 ; mmd < 32; mmd++)
		for (int reg = 0; reg < 65535; reg++) {
	    		val = phy_read_mmd(phydev, mmd, reg);
			printf("%2x %4x: %4x\m", mmd, reg, val);
		}

	Andrew

  parent reply	other threads:[~2026-05-04 19:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01 19:15 [PATCH net-next 4/5] onsemi: ncn260xx: Add driver support for NCN26010 and TS2500 MAC-PHY Selvamani Rajagopal
2026-05-01 20:22 ` Andrew Lunn
2026-05-04 19:03   ` Selvamani Rajagopal
2026-05-04 19:15     ` Andrew Lunn
2026-05-04 19:17       ` Selvamani Rajagopal
2026-05-04 19:21         ` Selvamani Rajagopal
2026-05-04 19:23         ` Andrew Lunn [this message]
2026-05-04 20:51           ` Selvamani Rajagopal

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=e2f03fc4-2948-4046-83a6-7d587e09ef62@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Pier.Beruto@onsemi.com \
    --cc=Selvamani.Rajagopal@onsemi.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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