From: Christian Marangi <ansuelsmth@gmail.com>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: "Pavel Machek" <pavel@ucw.cz>, "Lee Jones" <lee@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"William Zhang" <william.zhang@broadcom.com>,
"Anand Gore" <anand.gore@broadcom.com>,
"Kursad Oney" <kursad.oney@broadcom.com>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>, "Andrew Lunn" <andrew@lunn.ch>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Russell King" <linux@armlinux.org.uk>,
"Jacek Anaszewski" <jacek.anaszewski@gmail.com>,
"Fernández Rojas" <noltari@gmail.com>,
"Sven Schwermer" <sven.schwermer@disruptive-technologies.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org
Subject: Re: [net-next PATCH v8 5/5] net: phy: at803x: add LED support for qca808x
Date: Thu, 4 Jan 2024 14:11:11 +0100 [thread overview]
Message-ID: <6596ae71.df0a0220.a153a.6407@mx.google.com> (raw)
In-Reply-To: <20240104124805.1b0ba142@device-28.home>
On Thu, Jan 04, 2024 at 12:48:05PM +0100, Maxime Chevallier wrote:
> Hello Christian,
>
> On Thu, 4 Jan 2024 12:01:12 +0100
> Christian Marangi <ansuelsmth@gmail.com> wrote:
>
> > Add LED support for QCA8081 PHY.
> >
> > Documentation for this LEDs PHY is very scarce even with NDA access
> > to Documentation for OEMs. Only the blink pattern are documented and are
> > very confusing most of the time. No documentation is present about
> > forcing the LED on/off or to always blink.
> >
> > Those settings were reversed by poking the regs and trying to find the
> > correct bits to trigger these modes. Some bits mode are not clear and
> > maybe the documentation option are not 100% correct. For the sake of LED
> > support the reversed option are enough to add support for current LED
> > APIs.
>
> I have one small comment below :
>
> > +static int qca808x_led_blink_set(struct phy_device *phydev, u8 index,
> > + unsigned long *delay_on,
> > + unsigned long *delay_off)
> > +{
> > + int ret;
> > + u16 reg;
> > +
> > + if (index > 2)
> > + return -EINVAL;
> > +
> > + reg = QCA808X_MMD7_LED_FORCE_CTRL(index);
> > +
> > + /* Set blink to 50% off, 50% on at 4Hz by default */
> > + ret = phy_modify_mmd(phydev, MDIO_MMD_AN, QCA808X_MMD7_LED_GLOBAL,
> > + QCA808X_LED_BLINK_FREQ_MASK | QCA808X_LED_BLINK_DUTY_MASK,
> > + QCA808X_LED_BLINK_FREQ_256HZ | QCA808X_LED_BLINK_DUTY_50_50);
>
> The comment (4Hz) and the blink frequency (256Hz) don't match, is that
> right ? because I see there exists a QCA808X_LED_BLINK_FREQ_4HZ
> definition, shouldn't it be used ?
>
Thanks for checking this, oversight by me! Will fix. (the blink
frequency was discovered only lately)
--
Ansuel
WARNING: multiple messages have this Message-ID (diff)
From: Christian Marangi <ansuelsmth@gmail.com>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: "Pavel Machek" <pavel@ucw.cz>, "Lee Jones" <lee@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"William Zhang" <william.zhang@broadcom.com>,
"Anand Gore" <anand.gore@broadcom.com>,
"Kursad Oney" <kursad.oney@broadcom.com>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>, "Andrew Lunn" <andrew@lunn.ch>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Russell King" <linux@armlinux.org.uk>,
"Jacek Anaszewski" <jacek.anaszewski@gmail.com>,
"Fernández Rojas" <noltari@gmail.com>,
"Sven Schwermer" <sven.schwermer@disruptive-technologies.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org
Subject: Re: [net-next PATCH v8 5/5] net: phy: at803x: add LED support for qca808x
Date: Thu, 4 Jan 2024 14:11:11 +0100 [thread overview]
Message-ID: <6596ae71.df0a0220.a153a.6407@mx.google.com> (raw)
In-Reply-To: <20240104124805.1b0ba142@device-28.home>
On Thu, Jan 04, 2024 at 12:48:05PM +0100, Maxime Chevallier wrote:
> Hello Christian,
>
> On Thu, 4 Jan 2024 12:01:12 +0100
> Christian Marangi <ansuelsmth@gmail.com> wrote:
>
> > Add LED support for QCA8081 PHY.
> >
> > Documentation for this LEDs PHY is very scarce even with NDA access
> > to Documentation for OEMs. Only the blink pattern are documented and are
> > very confusing most of the time. No documentation is present about
> > forcing the LED on/off or to always blink.
> >
> > Those settings were reversed by poking the regs and trying to find the
> > correct bits to trigger these modes. Some bits mode are not clear and
> > maybe the documentation option are not 100% correct. For the sake of LED
> > support the reversed option are enough to add support for current LED
> > APIs.
>
> I have one small comment below :
>
> > +static int qca808x_led_blink_set(struct phy_device *phydev, u8 index,
> > + unsigned long *delay_on,
> > + unsigned long *delay_off)
> > +{
> > + int ret;
> > + u16 reg;
> > +
> > + if (index > 2)
> > + return -EINVAL;
> > +
> > + reg = QCA808X_MMD7_LED_FORCE_CTRL(index);
> > +
> > + /* Set blink to 50% off, 50% on at 4Hz by default */
> > + ret = phy_modify_mmd(phydev, MDIO_MMD_AN, QCA808X_MMD7_LED_GLOBAL,
> > + QCA808X_LED_BLINK_FREQ_MASK | QCA808X_LED_BLINK_DUTY_MASK,
> > + QCA808X_LED_BLINK_FREQ_256HZ | QCA808X_LED_BLINK_DUTY_50_50);
>
> The comment (4Hz) and the blink frequency (256Hz) don't match, is that
> right ? because I see there exists a QCA808X_LED_BLINK_FREQ_4HZ
> definition, shouldn't it be used ?
>
Thanks for checking this, oversight by me! Will fix. (the blink
frequency was discovered only lately)
--
Ansuel
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-04 13:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 11:01 [net-next PATCH v8 0/5] net: phy: generic polarity + LED support for qca808x Christian Marangi
2024-01-04 11:01 ` Christian Marangi
2024-01-04 11:01 ` [net-next PATCH v8 1/5] dt-bindings: net: phy: Make LED active-low property common Christian Marangi
2024-01-04 11:01 ` Christian Marangi
2024-01-04 11:01 ` [net-next PATCH v8 2/5] dt-bindings: net: phy: Document LED inactive high impedance mode Christian Marangi
2024-01-04 11:01 ` Christian Marangi
2024-01-04 11:01 ` [net-next PATCH v8 3/5] net: phy: add support for PHY LEDs polarity modes Christian Marangi
2024-01-04 11:01 ` Christian Marangi
2024-01-04 13:20 ` Andrew Lunn
2024-01-04 13:20 ` Andrew Lunn
2024-01-04 21:42 ` Christian Marangi
2024-01-04 21:42 ` Christian Marangi
2024-01-05 2:25 ` Andrew Lunn
2024-01-05 2:25 ` Andrew Lunn
2024-01-04 11:01 ` [net-next PATCH v8 4/5] dt-bindings: net: Document QCA808x PHYs Christian Marangi
2024-01-04 11:01 ` Christian Marangi
2024-01-04 11:01 ` [net-next PATCH v8 5/5] net: phy: at803x: add LED support for qca808x Christian Marangi
2024-01-04 11:01 ` Christian Marangi
2024-01-04 11:48 ` Maxime Chevallier
2024-01-04 11:48 ` Maxime Chevallier
2024-01-04 13:11 ` Christian Marangi [this message]
2024-01-04 13:11 ` 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=6596ae71.df0a0220.a153a.6407@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=anand.gore@broadcom.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=jacek.anaszewski@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=kursad.oney@broadcom.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=pabeni@redhat.com \
--cc=pavel@ucw.cz \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=sven.schwermer@disruptive-technologies.com \
--cc=william.zhang@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.