From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Maxime Chevallier <maxime.chevallier@bootlin.com>,
davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
Ioana Ciornei <ioana.ciornei@nxp.com>
Subject: Re: [PATCH net-next] net: pcs: tse: port to pcs-lynx
Date: Sat, 11 Feb 2023 23:45:45 +0200 [thread overview]
Message-ID: <20230211214545.5tu5cfg6jcwy5njd@skbuf> (raw)
In-Reply-To: <Y+e1IfWcmHJjJlgp@lunn.ch>
On Sat, Feb 11, 2023 at 04:32:49PM +0100, Andrew Lunn wrote:
> Another option might be regmap. There are both regmap-mdio.c and
> regmap-mmio.c.
Maxime had originally considered regmap too, but I thought it would
involve too many changes in the lynx-pcs driver and I wasn't sure
that those changes were for the better, since it would then need
to use the more low-level variants of phylink helpers (for example
phylink_mii_c22_pcs_decode_state() instead of phylink_mii_c22_pcs_get_state()).
next prev parent reply other threads:[~2023-02-11 21:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 19:09 [PATCH net-next] net: pcs: tse: port to pcs-lynx Maxime Chevallier
2023-02-10 19:31 ` Vladimir Oltean
2023-02-10 20:02 ` Andrew Lunn
2023-02-11 21:52 ` Vladimir Oltean
2023-02-11 22:23 ` Andrew Lunn
2023-02-21 7:34 ` Maxime Chevallier
2023-02-23 17:13 ` Sean Anderson
2023-02-11 15:32 ` Andrew Lunn
2023-02-11 21:45 ` Vladimir Oltean [this message]
2023-02-11 6:05 ` kernel test robot
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=20230211214545.5tu5cfg6jcwy5njd@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thomas.petazzoni@bootlin.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