From: Florian Fainelli <f.fainelli@gmail.com>
To: "Radu Pirea (OSS)" <radu-nicolae.pirea@oss.nxp.com>,
andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC net-next] net: phy: introduce phy_reg_field interface
Date: Fri, 31 Mar 2023 05:47:29 -0700 [thread overview]
Message-ID: <97687def-aca0-b1c5-68b6-e00079613c90@gmail.com> (raw)
In-Reply-To: <20230331123259.567627-1-radu-nicolae.pirea@oss.nxp.com>
On 3/31/2023 5:32 AM, Radu Pirea (OSS) wrote:
> Some PHYs can be heavily modified between revisions, and the addresses of
> the registers are changed and the register fields are moved from one
> register to another.
>
> To integrate more PHYs in the same driver with the same register fields,
> but these register fields were located in different registers at
> different offsets, I introduced the phy_reg_fied structure.
>
> phy_reg_fied structure abstracts the register fields differences.
>
> Signed-off-by: Radu Pirea (OSS) <radu-nicolae.pirea@oss.nxp.com>
You know how it goes: a framework without its user will not be accepted
unless an user of that framework also shows up. Can you post both?
--
Florian
next prev parent reply other threads:[~2023-03-31 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 12:32 [RFC net-next] net: phy: introduce phy_reg_field interface Radu Pirea (OSS)
2023-03-31 12:46 ` Russell King (Oracle)
2023-03-31 12:47 ` Florian Fainelli [this message]
2023-03-31 12:52 ` Andrew Lunn
2023-03-31 13:07 ` Andrew Lunn
2023-03-31 14:38 ` Radu Nicolae Pirea (OSS)
2023-03-31 15:25 ` Andrew Lunn
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=97687def-aca0-b1c5-68b6-e00079613c90@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radu-nicolae.pirea@oss.nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.