From: Andrew Lunn <andrew@lunn•ch>
To: Kai-Heng Feng <kai.heng.feng@canonical•com>
Cc: peppe.cavallaro@st•com, alexandre.torgue@foss•st.com,
joabreu@synopsys•com, "David S. Miller" <davem@davemloft•net>,
"Jakub Kicinski" <kuba@kernel•org>,
"Maxime Coquelin" <mcoquelin.stm32@gmail•com>,
"Heiner Kallweit" <hkallweit1@gmail•com>,
"Russell King" <linux@armlinux•org.uk>,
"Marek Behún" <kabel@kernel•org>,
"Ivan Bornyakov" <i.bornyakov@metrotek•ru>,
"Pali Rohár" <pali@kernel•org>,
netdev@vger•kernel.org, linux-stm32@st-md-mailman•stormreply.com,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH 2/2] stmmac: intel: Honor phy LED set by system firmware on a Dell hardware
Date: Fri, 14 Jan 2022 14:09:06 +0100 [thread overview]
Message-ID: <YeF18mxKuO4/4G0V@lunn.ch> (raw)
In-Reply-To: <20220114040755.1314349-2-kai.heng.feng@canonical.com>
On Fri, Jan 14, 2022 at 12:07:54PM +0800, Kai-Heng Feng wrote:
> BIOS on Dell Edge Gateway 3200 already makes its own phy LED setting, so
> instead of setting another value, keep it untouched and restore the saved
> value on system resume.
>
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical•com>
> ---
> .../net/ethernet/stmicro/stmmac/dwmac-intel.c | 16 +++++
> drivers/net/ethernet/stmicro/stmmac/stmmac.h | 2 +
> .../net/ethernet/stmicro/stmmac/stmmac_main.c | 4 ++
> drivers/net/phy/marvell.c | 58 ++++++++++++-------
> include/linux/marvell_phy.h | 1 +
> 5 files changed, 61 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/net/ethernet/stmicro/stmmac/dwmac-intel.c b/drivers/net/ethernet/stmicro/stmmac/dwmac-intel.c
> index 8e8778cfbbadd..f8a2879e0264a 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/dwmac-intel.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/dwmac-intel.c
> @@ -857,6 +857,16 @@ static const struct dmi_system_id quark_pci_dmi[] = {
> {}
> };
>
> +static const struct dmi_system_id use_preset_led[] = {
> + {
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "Dell EMC"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "Edge Gateway 3200"),
> + },
> + },
> + {}
> +};
This is a PHY property. Why is the MAC involved?
Please also think about how to make this generic, so any ACPI based
system can use it, with any PHY.
Andrew
next prev parent reply other threads:[~2022-01-14 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220114040755.1314349-1-kai.heng.feng@canonical.com>
2022-01-14 4:07 ` [PATCH 2/2] stmmac: intel: Honor phy LED set by system firmware on a Dell hardware Kai-Heng Feng
2022-01-14 4:35 ` Jakub Kicinski
2022-01-14 6:47 ` Kai-Heng Feng
2022-01-14 16:23 ` Jakub Kicinski
2022-01-14 13:09 ` Andrew Lunn [this message]
2022-01-14 15:22 ` Kai-Heng Feng
2022-01-14 17:25 ` Andrew Lunn
2022-01-14 13:20 ` Andrew Lunn
2022-01-14 15:25 ` Kai-Heng Feng
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=YeF18mxKuO4/4G0V@lunn.ch \
--to=andrew@lunn$(echo .)ch \
--cc=alexandre.torgue@foss$(echo .)st.com \
--cc=davem@davemloft$(echo .)net \
--cc=hkallweit1@gmail$(echo .)com \
--cc=i.bornyakov@metrotek$(echo .)ru \
--cc=joabreu@synopsys$(echo .)com \
--cc=kabel@kernel$(echo .)org \
--cc=kai.heng.feng@canonical$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-stm32@st-md-mailman$(echo .)stormreply.com \
--cc=linux@armlinux$(echo .)org.uk \
--cc=mcoquelin.stm32@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pali@kernel$(echo .)org \
--cc=peppe.cavallaro@st$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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