From: sashiko-bot@kernel.org
To: "Aleksei Sviridkin" <f@lex.la>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [RFC PATCH net-next 6/7] net: mdio: add Airoha EN8811H MDIO device driver
Date: Mon, 07 Sep 2026 17:46:04 +0000 [thread overview]
Message-ID: <20260907174605.182561F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260906174548.4106801-6-f@lex.la>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Incorrect PM wrapper used for dev_pm_ops structure pointer.
--
commit 23bfd1bd681c899f8cb9185a35af023d5e062675
Author: Aleksei Sviridkin <f@lex.la>
net: mdio: add Airoha EN8811H MDIO device driver
This commit introduces the EN8811H MDIO device driver. The driver polls for
and downloads firmware to the MD32 microcontroller before it functions as an
Ethernet PHY.
> diff --git a/drivers/net/mdio/mdio-airoha-en8811h.c b/drivers/net/mdio/mdio-airoha-en8811h.c
> new file mode 100644
> index 0000000000000..d94d74d85f10d
> --- /dev/null
> +++ b/drivers/net/mdio/mdio-airoha-en8811h.c
[ ... ]
> +static DEFINE_SIMPLE_DEV_PM_OPS(en8811h_mcu_pm_ops, NULL, en8811h_mcu_resume);
> +
> +static const struct of_device_id en8811h_mcu_of_match[] = {
> + { .compatible = "airoha,en8811h-mcu" },
> + { }
> +};
> +MODULE_DEVICE_TABLE(of, en8811h_mcu_of_match);
> +
> +static struct mdio_driver en8811h_mcu_driver = {
> + .probe = en8811h_mcu_probe,
> + .remove = en8811h_mcu_remove,
> + .mdiodrv.driver = {
> + .name = "airoha-en8811h-mcu",
> + .of_match_table = en8811h_mcu_of_match,
> + .pm = pm_sleep_ptr(&en8811h_mcu_pm_ops),
[Severity: Low]
Should this use pm_ptr() instead of pm_sleep_ptr() for the dev_pm_ops
structure pointer?
The power management subsystem guidelines indicate that pm_sleep_ptr()
is reserved for individual sleep callbacks inside the dev_pm_ops
structure itself, while pm_ptr() must be used when assigning the structure
pointer to the driver declaration in en8811h_mcu_driver.
> + },
> +};
> +
> +mdio_module_driver(en8811h_mcu_driver);
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1788711797.git.f@lex.la?part=6
next prev parent reply other threads:[~2026-09-07 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 17:45 [RFC PATCH net-next 0/7] net: mdio: an MDIO device driver for the Airoha EN8811H Aleksei Sviridkin
2026-09-06 17:45 ` [RFC PATCH net-next 1/7] dt-bindings: net: add Airoha EN8811H PHY MCU Aleksei Sviridkin
2026-09-07 17:46 ` sashiko-bot
2026-09-06 17:45 ` [RFC PATCH net-next 2/7] net: phy: add mdiodev_lock(), mdiodev_lock_nested() and mdiodev_unlock() Aleksei Sviridkin
2026-09-06 17:45 ` [RFC PATCH net-next 3/7] net: phy: air: type the buckpbus core on the mdio device Aleksei Sviridkin
2026-09-06 17:45 ` [RFC PATCH net-next 4/7] net: phy: air: move the EN8811H firmware download into the library Aleksei Sviridkin
2026-09-06 17:45 ` [RFC PATCH net-next 5/7] net: phy: air: skip the download when the MD32 is already running Aleksei Sviridkin
2026-09-06 17:45 ` [RFC PATCH net-next 6/7] net: mdio: add Airoha EN8811H MDIO device driver Aleksei Sviridkin
2026-09-07 17:46 ` sashiko-bot [this message]
2026-09-06 17:45 ` [RFC PATCH net-next 7/7] net: mdio: en8811h: add the nested bus Aleksei Sviridkin
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=20260907174605.182561F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f@lex.la \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.