linux-mips
[Top] [All Lists]

Re: CONFIG_LEDS_COBALT_RAQ not as module

To: Martin Michlmayr <tbm@cyrius.com>
Subject: Re: CONFIG_LEDS_COBALT_RAQ not as module
From: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
Date: Mon, 3 Dec 2007 22:34:18 +0900
Cc: yoichi_yuasa@tripeaks.co.jp, linux-mips@linux-mips.org, Richard Purdie <rpurdie@rpsys.net>
In-reply-to: <20071130163258.GA10006@deprecation.cyrius.com>
Organization: TriPeaks Corporation
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20071130163258.GA10006@deprecation.cyrius.com>
Sender: linux-mips-bounce@linux-mips.org
Hi,

On Fri, 30 Nov 2007 17:32:58 +0100
Martin Michlmayr <tbm@cyrius.com> wrote:

> Hi Yoichi,
> 
> Is there are good reason why LEDS_COBALT_QUBE is a tristate while
> LEDS_COBALT_RAQ is a bool?  I don't see why the RAQ LED driver
> couldn't be modular.

RAQ LED driver support power off trigger.
Power off trigger is generated at the end of all.

This is the reason why RAQ LED driver doesn't have module_exit function.
Moreover, this is the reason why it is bool.

Yoichi

<Prev in Thread] Current Thread [Next in Thread>
  • Re: CONFIG_LEDS_COBALT_RAQ not as module, Yoichi Yuasa <=