public inbox for linux-leds@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	Dan Murphy <dmurphy@ti.com>,
	linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH] leds: ariel: Add driver for status LEDs on Dell Wyse 3020
Date: Sat, 21 Mar 2020 16:43:53 +0100	[thread overview]
Message-ID: <20200321154353.GF8386@duo.ucw.cz> (raw)
In-Reply-To: <20200318094314.GA5052@furthur.local>

[-- Attachment #1: Type: text/plain, Size: 2268 bytes --]

Hi!

> > > +static int ariel_led_probe(struct platform_device *pdev)
> > > +{
> > > +	struct device *dev = &pdev->dev;
> > > +	struct ariel_led *leds;
> > > +	struct regmap *ec_ram;
> > > +	int ret;
> > > +
> > > +	leds = devm_kcalloc(dev, 3, sizeof(*leds), GFP_KERNEL);
> > > +	if (!leds)
> > > +		return -ENOMEM;
> > > +
> > > +	ec_ram = dev_get_regmap(dev->parent, "ec_ram");
> > > +	if (!ec_ram)
> > > +		return -ENODEV;
> > > +
> > > +	leds[0].ec_ram = ec_ram;
> > > +	leds[0].ec_index = EC_BLUE_LED;
> > > +	leds[0].led_cdev.name = "ariel:blue:power",
> > > +	leds[0].led_cdev.brightness_get = ariel_led_get;
> > > +	leds[0].led_cdev.brightness_set = ariel_led_set;
> > > +	leds[0].led_cdev.blink_set = ariel_blink_set;
> > > +	leds[0].led_cdev.default_trigger = "default-on";
> > 
> > Move common settings to a loop?
> > 
> > Definitely delete "ariel:" prefix.
> > 
> > > +	leds[1].led_cdev.name = "ariel:amber:status",
> > > +	leds[2].led_cdev.name = "ariel:green:status",
> > 
> > Do the LEDs have some label, or some kind of common function? Calling
> > it ":status" is not too useful...
> 
> No label there. This is what it looks like:
> https://people.freedesktop.org/~lkundrak/ariel-leds.jpeg
> 
> The green and amber, despite being packaged separately, can be
> controlled independently (they are not connected to the same inputs in
> reverse).
> 
> What does the machine do with stock firmware & ThinOS:
> * On power on, EC lights up the Amber one & Blue one
> * As soon as the firmware takes control, it turns off Amber and turns on
>   Green
> * Just before passing control to the OS, firmware turns the Green LED to
>   blinking
> * As soon as OS initializes, it turns Green back to always-on
> 
> Therefore the functionality generally is as follows:
> * Amber is always off (only on for a short time between CPU on and
>   firmware running)
> - Green blinking means "loading OS", otherwise always on when CPU is on
> - Blue is always on when the CPU is on

Ok, I guess your naming makes sense (without the ariel prefix).

Thank you,
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2020-03-21 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14 10:56 [PATCH] leds: ariel: Add driver for status LEDs on Dell Wyse 3020 Lubomir Rintel
2020-03-15  8:42 ` Pavel Machek
2020-03-18  9:43   ` Lubomir Rintel
2020-03-21 15:43     ` Pavel Machek [this message]

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=20200321154353.GF8386@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=dmurphy@ti.com \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=lkundrak@v3.sk \
    /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