From: Ansuel Smith <ansuelsmth@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Ansuel Smith <ansuelsmth@gmail.com>
Subject: [net-next PATCH v2 0/3] Improve support for qca8327 internal
Date: Sun, 19 Sep 2021 18:28:14 +0200 [thread overview]
Message-ID: <20210919162817.26924-1-ansuelsmth@gmail.com> (raw)
With more test with the qca8327 switch, it was discovered that the
internal phy can have 2 different phy id based on the switch serial
code. This patch address this and report the 2 different variant.
Also adds support for resume/suspend as it was requested in another
patch and improve the spacing and naming following how other phy are
defined in the same driver.
v2:
- Adds cover letter
- use genphy_suspend/resume generic function
Ansuel Smith (3):
net: phy: at803x: add support for qca 8327 A variant internal phy
net: phy: at803x: add resume/suspend function to qca83xx phy
net: phy: at803x: fix spacing and improve name for 83xx phy
drivers/net/phy/at803x.c | 67 ++++++++++++++++++++++++++--------------
1 file changed, 44 insertions(+), 23 deletions(-)
--
2.32.0
next reply other threads:[~2021-09-19 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 16:28 Ansuel Smith [this message]
2021-09-19 16:28 ` [net-next PATCH v2 1/3] net: phy: at803x: add support for qca 8327 A variant internal phy Ansuel Smith
2021-09-19 17:08 ` Andrew Lunn
2021-09-19 16:28 ` [net-next PATCH v2 2/3] net: phy: at803x: add resume/suspend function to qca83xx phy Ansuel Smith
2021-09-19 17:08 ` Andrew Lunn
2021-09-19 16:28 ` [net-next PATCH v2 3/3] net: phy: at803x: fix spacing and improve name for 83xx phy Ansuel Smith
2021-09-19 17:08 ` Andrew Lunn
2021-09-20 9:00 ` [net-next PATCH v2 0/3] Improve support for qca8327 internal patchwork-bot+netdevbpf
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=20210919162817.26924-1-ansuelsmth@gmail.com \
--to=ansuelsmth@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
/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).