From: Yauhen Kharuzhy <jekhor@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH 1/2] leds: Add Intel Cherry Trail Whiskey Cove PMIC LEDs
Date: Tue, 12 Feb 2019 23:25:45 +0300 [thread overview]
Message-ID: <20190212202545.GD5213@jeknote.loshitsa1.net> (raw)
In-Reply-To: <20190211131726.GA11067@amd>
On Mon, Feb 11, 2019 at 02:17:26PM +0100, Pavel Machek wrote:
> Hi!
>
> > +static struct cht_wc_led cht_wc_leds[] = {
> > + {
> > + .name = "pmic::charge",
> > + .ctrl_reg = CHT_WC_LED1_CTRL,
> > + .fsm_reg = CHT_WC_LED1_FSM,
> > + .pwm_reg = CHT_WC_LED1_PWM,
> > + .enable_mask = CHT_WC_LED1_ON,
> > + },
> > + {
> > + .name = "pmic::gpled",
> > + .ctrl_reg = CHT_WC_LED2_CTRL,
> > + .fsm_reg = CHT_WC_LED2_FSM,
> > + .pwm_reg = CHT_WC_LED2_PWM,
> > + .enable_mask = CHT_WC_LED2_ON,
> > + },
> > +};
>
> Unfortunately, these LED names will not be too useful for
> userspace. What about "platform::charging" and "status-led::"?
That sounds reasonable.
>
> Should we have some default triggers?
I don't know which triggers may be suitable for this. There are no
generic "is charging now" triggers in kernel. I can set default trigger
of charging led to 'bq27542-0-charging-blink-full-solid' as example but
it will valid for platforms with bq27542 battery fuel gauge, of course.
For status led, 'default-on' should be reasonable.
> Pavel
--
Yauhen Kharuzhy
next prev parent reply other threads:[~2019-02-12 20:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 22:12 [PATCH 0/2] Intel Cherry Trail Whiskey Cove LEDs support Yauhen Kharuzhy
2019-02-09 22:12 ` [PATCH 1/2] leds: Add Intel Cherry Trail Whiskey Cove PMIC LEDs Yauhen Kharuzhy
2019-02-11 13:17 ` Pavel Machek
2019-02-12 20:25 ` Yauhen Kharuzhy [this message]
2019-02-11 21:36 ` Jacek Anaszewski
2019-02-12 19:50 ` Yauhen Kharuzhy
2019-02-09 22:12 ` [PATCH 2/2] mfd: Add leds MFD cell for intel_soc_pmic_chtwc Yauhen Kharuzhy
2019-02-12 8:14 ` Lee Jones
2019-02-12 19:52 ` Yauhen Kharuzhy
2019-02-11 11:59 ` [PATCH 0/2] Intel Cherry Trail Whiskey Cove LEDs support Andy Shevchenko
2019-02-11 13:05 ` Pavel Machek
2019-02-11 21:20 ` Jacek Anaszewski
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=20190212202545.GD5213@jeknote.loshitsa1.net \
--to=jekhor@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
Powered by JetHome