From: "chunzhi.lin" <linchunzhi0@gmail.com>
To: netdev@vger.kernel.org
Cc: Frank.Sae@motor-comm.com, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, davem@davemloft.net,
linux-acpi@vger.kernel.org, rafael@kernel.org, lenb@kernel.org,
"chunzhi.lin" <linchunzhi0@gmail.com>
Subject: [PATCH net-next 0/2] net: phy: motorcomm: add ACPI _DSD property support
Date: Wed, 6 May 2026 10:18:11 +0800 [thread overview]
Message-ID: <20260506021813.3658669-1-linchunzhi0@gmail.com> (raw)
Hi,
This series makes the Motorcomm PHY driver parse firmware properties via
device_property_*() so the same property set can be provided by either
Devicetree or ACPI _DSD.
Patch 1 switches drivers/net/phy/motorcomm.c from of_property_*() to
device_property_*() on &phydev->mdio.dev.
Patch 2 documents Motorcomm yt8xxx PHY ACPI _DSD properties under
Documentation/firmware-guide/acpi/dsd and links the new document from
the ACPI index.
Thanks,
chunzhi.lin
chunzhi.lin (2):
net: phy: motorcomm: use device properties for firmware tuning
docs: acpi: dsd: add Motorcomm yt8xxx PHY properties
.../acpi/dsd/motorcomm-yt8xxx-phy.rst | 107 ++++++++++++++++++
Documentation/firmware-guide/acpi/index.rst | 1 +
drivers/net/phy/motorcomm.c | 41 ++++---
3 files changed, 128 insertions(+), 21 deletions(-)
create mode 100644 Documentation/firmware-guide/acpi/dsd/motorcomm-yt8xxx-phy.rst
--
2.34.1
next reply other threads:[~2026-05-06 2:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 2:18 chunzhi.lin [this message]
2026-05-06 2:18 ` [PATCH 1/2] net: phy: motorcomm: use device properties for firmware tuning chunzhi.lin
2026-05-06 12:18 ` Andrew Lunn
2026-05-06 2:18 ` [PATCH 2/2] docs: acpi: dsd: add Motorcomm yt8xxx PHY properties chunzhi.lin
2026-05-06 12:20 ` 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=20260506021813.3658669-1-linchunzhi0@gmail.com \
--to=linchunzhi0@gmail.com \
--cc=Frank.Sae@motor-comm.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafael@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