public inbox for linux-arm-msm@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	Gregory Clement <gregory.clement@bootlin.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	John Crispin <john@phrozen.org>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, Lee Jones <lee@kernel.org>,
	linux-leds@vger.kernel.org
Subject: Re: [net-next PATCH v3 06/14] net: phy: marvell: Add software control of the LEDs
Date: Wed, 15 Mar 2023 02:44:53 +0200	[thread overview]
Message-ID: <20230315004453.sxzqccyozvsfp374@skbuf> (raw)
In-Reply-To: <20230314101516.20427-7-ansuelsmth@gmail.com> <20230314101516.20427-7-ansuelsmth@gmail.com>

On Tue, Mar 14, 2023 at 11:15:08AM +0100, Christian Marangi wrote:
> From: Andrew Lunn <andrew@lunn.ch>
> 
> Add a brightness function, so the LEDs can be controlled from
> software using the standard Linux LED infrastructure.
> 
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
> +static int m88e1318_led_brightness_set(struct phy_device *phydev,
> +				       u32 index, enum led_brightness value)
> +{
> +	u16 reg;
> +
> +	reg = phy_read_paged(phydev, MII_MARVELL_LED_PAGE,
> +			     MII_88E1318S_PHY_LED_FUNC);
> +	if (reg < 0)
> +		return reg;

"reg" is declared as unsigned, so it's surely positive.

> +
> +	switch (index) {
> +	case 0:
> +	case 1:
> +	case 2:
> +		reg &= ~(0xf << (4 * index));
> +		if (value == LED_OFF)
> +			reg |= MII_88E1318S_PHY_LED_FUNC_OFF << (4 * index);
> +		else
> +			reg |= MII_88E1318S_PHY_LED_FUNC_ON << (4 * index);
> +		break;
> +	default:
> +		return -EINVAL;
> +	}
> +
> +	return phy_write_paged(phydev, MII_MARVELL_LED_PAGE,
> +			       MII_88E1318S_PHY_LED_FUNC, reg);
> +}

  reply	other threads:[~2023-03-15  0:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 10:15 [net-next PATCH v3 00/14] net: Add basic LED support for switch/phy Christian Marangi
2023-03-14 10:15 ` [net-next PATCH v3 01/14] net: dsa: qca8k: move qca8k_port_to_phy() to header Christian Marangi
2023-03-14 10:15 ` [net-next PATCH v3 02/14] net: dsa: qca8k: add LEDs basic support Christian Marangi
2023-03-15  0:22   ` Vladimir Oltean
2023-03-14 10:15 ` [net-next PATCH v3 03/14] net: dsa: qca8k: add LEDs blink_set() support Christian Marangi
2023-03-14 10:15 ` [net-next PATCH v3 04/14] net: phy: Add a binding for PHY LEDs Christian Marangi
2023-03-15  0:41   ` Vladimir Oltean
2023-03-14 10:15 ` [net-next PATCH v3 05/14] net: phy: phy_device: Call into the PHY driver to set LED brightness Christian Marangi
2023-03-14 10:15 ` [net-next PATCH v3 06/14] net: phy: marvell: Add software control of the LEDs Christian Marangi
2023-03-15  0:44   ` Vladimir Oltean [this message]
2023-03-15  1:48     ` Andrew Lunn
2023-03-14 10:15 ` [net-next PATCH v3 07/14] net: phy: phy_device: Call into the PHY driver to set LED blinking Christian Marangi
2023-03-14 10:15 ` [net-next PATCH v3 08/14] net: phy: marvell: Implement led_blink_set() Christian Marangi
2023-03-15  0:46   ` Vladimir Oltean
2023-03-14 10:15 ` [net-next PATCH v3 09/14] dt-bindings: net: dsa: dsa-port: Document support for LEDs node Christian Marangi
2023-03-15  0:50   ` Vladimir Oltean
2023-03-15  1:58     ` Andrew Lunn
2023-03-15  3:28       ` Christian Marangi
2023-03-17 21:13       ` Rob Herring
2023-03-14 10:15 ` [net-next PATCH v3 10/14] dt-bindings: net: dsa: qca8k: add LEDs definition example Christian Marangi
2023-03-15  0:51   ` Vladimir Oltean
2023-03-14 10:15 ` [net-next PATCH v3 11/14] arm: qcom: dt: Drop unevaluated properties in switch nodes for rb3011 Christian Marangi
2023-03-14 10:15 ` [net-next PATCH v3 12/14] arm: qcom: dt: Add Switch LED for each port " Christian Marangi
2023-03-14 10:15 ` [net-next PATCH v3 13/14] dt-bindings: net: phy: Document support for LEDs node Christian Marangi
2023-03-14 10:15 ` [net-next PATCH v3 14/14] arm: mvebu: dt: Add PHY LED support for 370-rd WAN port Christian Marangi

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=20230315004453.sxzqccyozvsfp374@skbuf \
    --to=olteanv@gmail.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=gregory.clement@bootlin.com \
    --cc=hkallweit1@gmail.com \
    --cc=john@phrozen.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.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