From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kyle Hendry <kylehendrydev@gmail.com>
Cc: "Lee Jones" <lee@kernel.org>, "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Russell King" <linux@armlinux.org.uk>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Fernández Rojas" <noltari@gmail.com>,
"Jonas Gorski" <jonas.gorski@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 1/5] net: phy: bcm63xx: add support for BCM63268 GPHY
Date: Tue, 18 Feb 2025 08:37:09 +0100 [thread overview]
Message-ID: <20250218-lumpy-arrogant-orangutan-adeec8@krzk-bin> (raw)
In-Reply-To: <20250218013653.229234-2-kylehendrydev@gmail.com>
On Mon, Feb 17, 2025 at 05:36:40PM -0800, Kyle Hendry wrote:
> This patch adds support for the internal gigabit PHY on the
Please do not use "This commit/patch/change", but imperative mood. See
longer explanation here:
https://elixir.bootlin.com/linux/v5.17.1/source/Documentation/process/submitting-patches.rst#L95
> BCM63268 SoC. The PHY has a low power mode that has can be
> enabled/disabled through the GPHY control register. The
> register is passed in through the device tree, and the
> relevant bits are set in the suspend and resume functions.
>
...
> +int bcm63268_gphy_resume(struct phy_device *phydev)
> +{
> + int ret;
> +
> + ret = bcm63268_gphy_set(phydev, true);
> + if (ret)
> + return ret;
> +
> + ret = genphy_resume(phydev);
> + if (ret)
> + return ret;
> +
> + return 0;
> +}
> +
> +int bcm63268_gphy_suspend(struct phy_device *phydev)
Why these are not static? Where is EXPORT_SYMBOL and kerneldoc?
> +{
> + int ret;
> +
> + ret = genphy_suspend(phydev);
> + if (ret)
> + return ret;
> +
> + ret = bcm63268_gphy_set(phydev, false);
> + if (ret)
> + return ret;
> +
> + return 0;
> +}
> +
> +static int bcm63268_gphy_probe(struct phy_device *phydev)
> +{
> + struct device_node *np = dev_of_node(&phydev->mdio.bus->dev);
> + struct mdio_device *mdio = &phydev->mdio;
> + struct device *dev = &mdio->dev;
> + struct bcm_gphy_priv *priv;
> + struct regmap *regmap;
> + int err;
> +
> + err = devm_phy_package_join(dev, phydev, 0, 0);
> + if (err)
> + return err;
> +
> + priv = devm_kzalloc(dev, sizeof(struct bcm_gphy_priv), GFP_KERNEL);
sizeof(*)
> + if (!priv)
> + return -ENOMEM;
> +
> + phydev->priv = priv;
> +
> + regmap = syscon_regmap_lookup_by_phandle(np, "brcm,gphy-ctrl");
No. ABI break without any explanation in commit msg.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-02-18 7:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 1:36 [PATCH v2 0/5] net: phy: bcm63xx: Enable internal GPHY on BCM63268 Kyle Hendry
2025-02-18 1:36 ` [PATCH v2 1/5] net: phy: bcm63xx: add support for BCM63268 GPHY Kyle Hendry
2025-02-18 7:37 ` Krzysztof Kozlowski [this message]
2025-02-18 7:49 ` Krzysztof Kozlowski
2025-02-19 4:18 ` kernel test robot
2025-02-19 4:29 ` kernel test robot
2025-02-18 1:36 ` [PATCH v2 2/5] net: phy: enable bcm63xx on bmips Kyle Hendry
2025-02-20 17:23 ` Florian Fainelli
2025-02-18 1:36 ` [PATCH v2 3/5] dt-bindings: net: bcm6368-mdio-mux: add gphy-ctrl property Kyle Hendry
2025-02-18 7:32 ` Krzysztof Kozlowski
2025-02-18 1:36 ` [PATCH v2 4/5] dt-bindings: mfd: brcm: add brcm,bcm63268-gphy-ctrl compatible Kyle Hendry
2025-02-18 7:33 ` Krzysztof Kozlowski
2025-02-18 1:36 ` [PATCH v2 5/5] dt-bindings: mfd: brcm: add gphy controller to BCM63268 sysctl Kyle Hendry
2025-02-18 7:35 ` Krzysztof Kozlowski
2025-02-22 23:59 ` Kyle Hendry
2025-02-21 20:09 ` [PATCH v2 0/5] net: phy: bcm63xx: Enable internal GPHY on BCM63268 Florian Fainelli
2025-02-23 0:05 ` Kyle Hendry
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=20250218-lumpy-arrogant-orangutan-adeec8@krzk-bin \
--to=krzk@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=kylehendrydev@gmail.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh@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