From: Andrew Lunn <andrew@lunn.ch>
To: Weiting Lee <weiting.lee@airoha.com>
Cc: netdev@vger.kernel.org, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: phy: air_en8811h: select LED GPIO pins based on AN8811HB package variant
Date: Thu, 27 Aug 2026 20:01:14 +0200 [thread overview]
Message-ID: <8530a501-705b-45b2-b876-68855955bccd@lunn.ch> (raw)
In-Reply-To: <20260827054156.2681908-1-weiting.lee@airoha.com>
On Thu, Aug 27, 2026 at 01:41:55PM +0800, Weiting Lee wrote:
> The AN8811HB comes in two package variants, AN8811HBCN and AN8811HBN,
> which use different GPIO pins to drive LED outputs. AN8811HBCN uses
> GPIOs 0, 1, and 15, while AN8811HBN uses GPIOs 3, 4, and 5. Using a
> fixed GPIO assignment causes incorrect LED behavior on one of the
> variants.
>
> Read the package variant from hardware strap register AN8811HB_HWTRAP2
Just for conformation, this is not an actually strap pin you connect a
resistor to, pull high/low, but a read only silicon bit.
Also, you called it a strap registers, yet the #define is TRAP?
> @@ -202,6 +214,7 @@ struct en8811h_priv {
> struct phy_device *phydev;
> unsigned int cko_is_enabled;
> struct mdio_device *pbusdev;
> + unsigned int pkg_sel;
bool?
Also, is_an8811hbcn would be a better name. It is hard to know what
true/false means for pkg_sel.
> + phydev_info(phydev, "%s detected\n",
> + priv->pkg_sel ? "AN8811HBCN" : "AN8811HBN");
No need to spam the log.
Andrew
---
pw-bot: cr
next prev parent reply other threads:[~2026-08-27 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 5:41 Weiting Lee
2026-08-27 18:01 ` Andrew Lunn [this message]
2026-08-28 5:05 ` [PATCH v2 net-next] " Weiting Lee
2026-08-28 13:07 ` Andrew Lunn
2026-08-31 6:58 ` 回覆: " WeiTing Lee (李威霆)
2026-09-07 1:56 ` [PATCH v3 " Weiting Lee
2026-09-09 16:57 ` netdev-bot+sashiko
2026-09-10 13:15 ` Paolo Abeni
2026-09-10 13:20 ` 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=8530a501-705b-45b2-b876-68855955bccd@lunn.ch \
--to=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=weiting.lee@airoha.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®