From: Oliver Graute <oliver.graute@kococonnector.com>
To: Simon Horman <simon.horman@corigine.com>
Cc: andrew@lunn.ch, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH RFC] linux: net: phy: realtek: changing LED behaviour for RTL8211F
Date: Thu, 9 Feb 2023 13:39:17 +0100 [thread overview]
Message-ID: <20230209123917.GA1550@optiplex> (raw)
In-Reply-To: <Y+TRj2hehU76+Ytu@corigine.com>
On 09/02/23, Simon Horman wrote:
> On Thu, Feb 09, 2023 at 10:44:05AM +0100, Oliver Graute wrote:
> > This enable the LEDs for network activity and 100/1000Link for the RTL8211F
> >
> > Signed-off-by: Oliver Graute <oliver.graute@kococonnector.com>
> > ---
> > drivers/net/phy/realtek.c | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/drivers/net/phy/realtek.c b/drivers/net/phy/realtek.c
> > index 3d99fd6664d7..5c796883cad3 100644
> > --- a/drivers/net/phy/realtek.c
> > +++ b/drivers/net/phy/realtek.c
> > @@ -416,6 +416,11 @@ static int rtl8211f_config_init(struct phy_device *phydev)
> > }
> > }
> >
> > + phy_write(phydev, RTL821x_PAGE_SELECT, 0xd04);
> > + phy_write(phydev, 0x10, 0x15B);
> > +
> > + phy_write(phydev, RTL821x_PAGE_SELECT, 0x0);
> > +
>
> nit: it looks like the indentation in the new lines above should
> be using a single tab rather than 8 spaces.
thx, I will fix the indentation.
is this the right place to turn on the realtek phy LEDs for RTL8211F?
Best regards,
Oliver
next prev parent reply other threads:[~2023-02-09 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 9:44 [PATCH RFC] linux: net: phy: realtek: changing LED behaviour for RTL8211F Oliver Graute
2023-02-09 10:57 ` Simon Horman
2023-02-09 12:39 ` Oliver Graute [this message]
2023-02-09 13:30 ` Michael Walle
2023-02-09 14:20 ` Oliver Graute
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=20230209123917.GA1550@optiplex \
--to=oliver.graute@kococonnector.com \
--cc=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=simon.horman@corigine.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;
as well as URLs for NNTP newsgroup(s).