[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <dd9e469a-b1ab-30d1-8f9f-946d4b323c35@broadcom.com>
Date: Sat, 22 Jan 2022 09:21:58 +0100
From: Arend van Spriel <arend.vanspriel@...adcom.com>
To: Luiz Sampaio <sampaio.ime@...il.com>,
Kalle Valo <kvalo@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Larry Finger <Larry.Finger@...inger.net>
Cc: linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
b43-dev@...ts.infradead.org, netdev@...r.kernel.org
Subject: Re: [PATCH 16/31] net: broadcom: changing LED_* from enum
led_brightness to actual value
On 1/21/2022 5:54 PM, Luiz Sampaio wrote:
> The enum led_brightness, which contains the declaration of LED_OFF,
> LED_ON, LED_HALF and LED_FULL is obsolete, as the led class now supports
> max_brightness.
The commit message sounds a bit obscure to me. You say the
led_brightness enumeration is or rather will become obsolete. I don't
understand the reason given "led class now supports max_brightness".
What does that mean?
Also I do not understand the approach here. If the enum is obsolete why
not start with the APIs using it like the led callbacks
brightness_{get,set{,_blocking}}. I suspect that is your next step, but
it seems like unnecessary churn to me.
Anyway, what triggered me to look at this is the fact that we do have a
led.c under drivers/net/wireless/broadcom/brcm80211/brcmsmac
implementing the brightness_set() callback.
Regards,
Arend
Download attachment "smime.p7s" of type "application/pkcs7-signature" (4219 bytes)
Powered by blists - more mailing lists