All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: John Linville <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org,
	rt2400-devel@lists.sourceforge.net
Subject: Re: [PATCH] rt2x00: Don't switch off LED on initialization
Date: Sun, 16 Nov 2008 00:25:25 +0100	[thread overview]
Message-ID: <200811160025.25678.mb@bu3sch.de> (raw)
In-Reply-To: <200811160008.51235.IvDoorn@gmail.com>

On Sunday 16 November 2008 00:08:50 Ivo van Doorn wrote:
> When we switch off the LEDS during initialization
> we kill rt73usb from proper functioning. The immediate
> result after the first LED command are MCU failures
> and a complete breakdown of TX/RX.
> 
> Signed-off-by: Ivo van Doorn <IvDoorn@gmail.com>
> ---
>  drivers/net/wireless/rt2x00/rt2x00leds.c |    6 ------
>  1 files changed, 0 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/net/wireless/rt2x00/rt2x00leds.c b/drivers/net/wireless/rt2x00/rt2x00leds.c
> index 66c61b1..68f4e0f 100644
> --- a/drivers/net/wireless/rt2x00/rt2x00leds.c
> +++ b/drivers/net/wireless/rt2x00/rt2x00leds.c
> @@ -111,12 +111,6 @@ static int rt2x00leds_register_led(struct rt2x00_dev *rt2x00dev,
>  	led->led_dev.name = name;
>  	led->led_dev.brightness = LED_OFF;
>  
> -	/*
> -	 * Ensure the LED is off, it might have been enabled
> -	 * by the hardware when the device was powered on.
> -	 */
> -	led->led_dev.brightness_set(&led->led_dev, LED_OFF);
> -
>  	retval = led_classdev_register(device, &led->led_dev);
>  	if (retval) {
>  		ERROR(rt2x00dev, "Failed to register led handler.\n");

But you know that a brightness_set event can trigger right after the dev
was registered?
So a random LED event at the right time can kill the rt device?

-- 
Greetings Michael.

  reply	other threads:[~2008-11-15 23:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15 23:08 [PATCH] rt2x00: Don't switch off LED on initialization Ivo van Doorn
2008-11-15 23:25 ` Michael Buesch [this message]
2008-11-15 23:34   ` Ivo van Doorn

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=200811160025.25678.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rt2400-devel@lists.sourceforge.net \
    /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.