[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Yjgmut/HndnYsPVE@google.com>
Date: Mon, 21 Mar 2022 15:18:18 +0800
From: Tzung-Bi Shih <tzungbi@...nel.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: bleung@...omium.org, groeck@...omium.org, robh+dt@...nel.org,
devicetree@...r.kernel.org, chrome-platform@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 5/5] platform/chrome: cros_kbd_led_backlight: support
EC PWM backend
On Fri, Mar 18, 2022 at 10:07:51AM -0700, Guenter Roeck wrote:
> On Mon, Mar 14, 2022 at 05:08:35PM +0800, Tzung-Bi Shih wrote:
> > @@ -142,6 +142,12 @@ config CROS_KBD_LED_BACKLIGHT_ACPI
> > help
> > ChromeOS keyboard backlight ACPI backend.
> >
> > +config CROS_KBD_LED_BACKLIGHT_EC_PWM
> > + tristate "ChromeOS keyboard backlight EC PWM backend"
>
> This is not a standa-alone module and should therefore be bool,
> not tristate.
Ack.
> > @@ -123,34 +130,122 @@ static const struct keyboard_led_drvdata keyboard_led_drvdata_acpi = {
> >
> > #endif /* IS_ENABLED(CONFIG_CROS_KBD_LED_BACKLIGHT_ACPI) */
> >
> > +#if IS_ENABLED(CONFIG_CROS_KBD_LED_BACKLIGHT_EC_PWM)
>
> #ifdef (with bool) should do.
Ack. Will apply the fix for CONFIG_CROS_KBD_LED_BACKLIGHT_ACPI too.
Powered by blists - more mailing lists