From: Andrew Lunn <andrew@lunn.ch>
To: Parthiban Veerasooran <Parthiban.Veerasooran@microchip.com>
Cc: steve.glendinning@shawell.net, UNGLinuxDriver@microchip.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: usb: smsc95xx: configure external LEDs function for EVB-LAN8670-USB
Date: Wed, 22 May 2024 18:44:22 +0200 [thread overview]
Message-ID: <9c19e0a1-b65c-416a-833c-1a4c3b63fa2f@lunn.ch> (raw)
In-Reply-To: <20240522140817.409936-1-Parthiban.Veerasooran@microchip.com>
On Wed, May 22, 2024 at 07:38:17PM +0530, Parthiban Veerasooran wrote:
> By default, LAN9500A configures the external LEDs to the below function.
> nSPD_LED -> Speed Indicator
> nLNKA_LED -> Link and Activity Indicator
> nFDX_LED -> Full Duplex Link Indicator
>
> But, EVB-LAN8670-USB uses the below external LEDs function which can be
> enabled by writing 1 to the LED Select (LED_SEL) bit in the LAN9500A.
> nSPD_LED -> Speed Indicator
> nLNKA_LED -> Link Indicator
> nFDX_LED -> Activity Indicator
What else can the LEDs indicate?
> + /* Set LED Select (LED_SEL) bit for the external LED pins functionality
> + * in the Microchip's EVB-LAN8670-USB 10BASE-T1S Ethernet device which
Is this a function of the USB dongle? Or a function of the PHY?
Andrew
next prev parent reply other threads:[~2024-05-22 16:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 14:08 Parthiban Veerasooran
2024-05-22 16:44 ` Andrew Lunn [this message]
2024-05-23 8:51 ` Parthiban.Veerasooran
2024-05-23 12:43 ` Andrew Lunn
2024-05-24 10:48 ` Parthiban.Veerasooran
2024-05-22 18:54 ` Simon Horman
2024-05-23 8:51 ` Parthiban.Veerasooran
2024-05-22 19:52 ` Woojung.Huh
2024-05-23 8:51 ` Parthiban.Veerasooran
2024-05-23 5:42 ` kernel test robot
2024-05-27 8:28 ` Oliver Neukum
2024-05-27 11:42 ` Parthiban.Veerasooran
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=9c19e0a1-b65c-416a-833c-1a4c3b63fa2f@lunn.ch \
--to=andrew@lunn.ch \
--cc=Parthiban.Veerasooran@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steve.glendinning@shawell.net \
/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®