driverdev-devel.linuxdriverproject.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, linux-wireless@vger.kernel.org,
	Kalle Valo <kvalo@codeaurora.org>,
	Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH resend 3] staging: rtl8188eu: Add rtw_led_enable module parameter
Date: Tue, 24 Mar 2020 13:38:53 +0100	[thread overview]
Message-ID: <9e67f1dd615b810e1725b13003fbb5d9000cd7c0.camel@hadess.net> (raw)
In-Reply-To: <20200324123229.GD2348009@kroah.com>

On Tue, 2020-03-24 at 13:32 +0100, Greg Kroah-Hartman wrote:
> On Tue, Mar 24, 2020 at 12:47:01PM +0100, Bastien Nocera wrote:
> > On Tue, 2020-03-24 at 12:38 +0100, Greg Kroah-Hartman wrote:
> > > On Tue, Mar 24, 2020 at 11:36:00AM +0100, Bastien Nocera wrote:
> > > > Make it possible to disable the LED, as it can be pretty
> > > > annoying
> > > > depending on where it's located.
> > > > 
> > > > See also https://github.com/lwfinger/rtl8188eu/pull/304 for the
> > > > out-of-tree version.
> > > > 
> > > > Signed-off-by: Bastien Nocera <hadess@hadess.net>
> > > > ---
> > > >  drivers/staging/rtl8188eu/core/rtw_led.c      | 6 ++++++
> > > >  drivers/staging/rtl8188eu/include/drv_types.h | 2 ++
> > > >  drivers/staging/rtl8188eu/os_dep/os_intfs.c   | 5 +++++
> > > >  3 files changed, 13 insertions(+)
> > > > 
> > > > diff --git a/drivers/staging/rtl8188eu/core/rtw_led.c
> > > > b/drivers/staging/rtl8188eu/core/rtw_led.c
> > > > index d1406cc99768..75a859accb7e 100644
> > > > --- a/drivers/staging/rtl8188eu/core/rtw_led.c
> > > > +++ b/drivers/staging/rtl8188eu/core/rtw_led.c
> > > > @@ -467,10 +467,16 @@ void blink_handler(struct LED_871x *pLed)
> > > >  
> > > >  void led_control_8188eu(struct adapter *padapter, enum
> > > > LED_CTL_MODE LedAction)
> > > >  {
> > > > +	struct registry_priv *registry_par;
> > > > +
> > > >  	if (padapter->bSurpriseRemoved || padapter-
> > > > >bDriverStopped ||
> > > >  	    !padapter->hw_init_completed)
> > > >  		return;
> > > >  
> > > > +	registry_par = &padapter->registrypriv;
> > > > +	if (!registry_par->led_enable)
> > > > +		return;
> > > > +
> > > >  	if ((padapter->pwrctrlpriv.rf_pwrstate != rf_on &&
> > > >  	     padapter->pwrctrlpriv.rfoff_reason >
> > > > RF_CHANGE_BY_PS) &&
> > > >  	    (LedAction == LED_CTL_TX || LedAction == LED_CTL_RX
> > > > ||
> > > > diff --git a/drivers/staging/rtl8188eu/include/drv_types.h
> > > > b/drivers/staging/rtl8188eu/include/drv_types.h
> > > > index 35c0946bc65d..4ca828141d3f 100644
> > > > --- a/drivers/staging/rtl8188eu/include/drv_types.h
> > > > +++ b/drivers/staging/rtl8188eu/include/drv_types.h
> > > > @@ -67,6 +67,8 @@ struct registry_priv {
> > > >  	u8	wmm_enable;
> > > >  	u8	uapsd_enable;
> > > >  
> > > > +	u8	led_enable;
> > > > +
> > > >  	struct wlan_bssid_ex    dev_network;
> > > >  
> > > >  	u8	ht_enable;
> > > > diff --git a/drivers/staging/rtl8188eu/os_dep/os_intfs.c
> > > > b/drivers/staging/rtl8188eu/os_dep/os_intfs.c
> > > > index 8907bf6bb7ff..ba55ae741215 100644
> > > > --- a/drivers/staging/rtl8188eu/os_dep/os_intfs.c
> > > > +++ b/drivers/staging/rtl8188eu/os_dep/os_intfs.c
> > > > @@ -47,6 +47,8 @@ static int rtw_acm_method;/*  0:By SW 1:By
> > > > HW. */
> > > >  static int rtw_wmm_enable = 1;/*  default is set to enable the
> > > > wmm. */
> > > >  static int rtw_uapsd_enable;
> > > >  
> > > > +static int rtw_led_enable = 1;
> > > > +
> > > >  static int rtw_ht_enable = 1;
> > > >  /* 0 :disable, bit(0): enable 2.4g, bit(1): enable 5g */
> > > >  static int rtw_cbw40_enable = 3;
> > > > @@ -98,6 +100,7 @@ module_param(rtw_channel, int, 0644);
> > > >  module_param(rtw_wmm_enable, int, 0644);
> > > >  module_param(rtw_vrtl_carrier_sense, int, 0644);
> > > >  module_param(rtw_vcs_type, int, 0644);
> > > > +module_param(rtw_led_enable, int, 0644);
> > > 
> > > Ick, really?  No, no nee module parameters, this is not the
> > > 1990's.
> > > 
> > > This should be done on a per-device basis, using the correct
> > > apis.
> > 
> > What API?
> 
> Documentation/leds/index.rst should give you a good start :)

Given how much work it'd be, I'll give it a miss and carry on using the
out-of-tree driver.

Thanks for the hint.

_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

  reply	other threads:[~2020-03-24 12:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 10:36 [PATCH resend 3] staging: rtl8188eu: Add rtw_led_enable module parameter Bastien Nocera
2020-03-24 11:38 ` Greg Kroah-Hartman
2020-03-24 11:47   ` Bastien Nocera
2020-03-24 12:32     ` Greg Kroah-Hartman
2020-03-24 12:38       ` Bastien Nocera [this message]
2020-03-24 12:48         ` Greg Kroah-Hartman
2020-03-24 12:52           ` Bastien Nocera
2020-03-24 15:20 ` Greg Kroah-Hartman
2020-03-24 15:21   ` Bastien Nocera
2020-03-24 15:42     ` Greg Kroah-Hartman
2020-03-24 17:35     ` Dan Carpenter
2020-03-25 15:01       ` Bastien Nocera

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=9e67f1dd615b810e1725b13003fbb5d9000cd7c0.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    /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).