linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Oleh Kravchenko <oleg@kaa.org.ua>
Cc: linux-leds@vger.kernel.org
Subject: Re: [PATCH] leds: add LED driver for CR0014114 board
Date: Sat, 12 Aug 2017 12:56:20 +0200	[thread overview]
Message-ID: <20170812105620.GA23543@amd> (raw)
In-Reply-To: <83fdd755-c978-079c-32c0-9b1ab7fa0039@kaa.org.ua>

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

Hi!

> > On Sat 2017-08-12 12:09:35, Oleh Kravchenko wrote:
> >> This patch adds a LED class driver for the RGB LEDs found on
> >> the Crane Merchandising System CR0014114 LEDs board.
> > 
> > What kind of hardware is this? 
> 
> It's from vending machines produced by Crane Merchandising System http://cranems.com/
>  
> >> Driver creates LED devices with name written using the following
> >> pattern "LABEL-{N}:{red,green,blue}:".
> > 
> > Is the "-{N} suffix needed?
> 
> It's number of RGB LED, board has 6 LEDs.

Normally label differentiates them...?

> > How special hardware is this? Does it make sense to ask this question
> > for x86 users, for example?
> 
> I think it's possible to connect it to x86 hardware, but I don't try it.
> Board need not only SPI connection, but good power supply.

Aha, ok.

> >> +/* CR0014114 SPI commands */
> >> +#define CR0014114_SET_BRIGHTNESS	0x80
> >> +#define CR0014114_INIT_REENUMERATE	0x81
> >> +#define CR0014114_NEXT_REENUMERATE	0x82
> > 
> > can we s/cr0014114/cr00/g, or something? There are local to the
> > module, so they can be shorter...
> 
> Sure, may be CMD_SET_BRIGHTNESS

Please do the replace for all static symbols.> >> +fail:

> >> +	while (i--)
> >> +		led_classdev_unregister(&priv->leds[i].ldev);
> > 
> > Can devm_* be used to simplify this?
> 
> I think no, because it will cause race condition.

Please take a look at devm_led_classdev_register() and friends. It
should be possible to simplify code without races.

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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2017-08-12 10:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-12  9:09 [PATCH] leds: add LED driver for CR0014114 board Oleh Kravchenko
2017-08-12  9:30 ` Pavel Machek
2017-08-12 10:28   ` Oleh Kravchenko
2017-08-12 10:56     ` Pavel Machek [this message]
2017-08-12 11:34       ` Oleh Kravchenko
2017-08-12 17:46         ` Pavel Machek
2017-08-12 18:50           ` Oleh Kravchenko
2017-08-12 19:13             ` Pavel Machek
2017-08-12 19:39               ` Oleh Kravchenko
2017-09-28 15:24                 ` Pavel Machek

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=20170812105620.GA23543@amd \
    --to=pavel@ucw.cz \
    --cc=linux-leds@vger.kernel.org \
    --cc=oleg@kaa.org.ua \
    /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;
as well as URLs for NNTP newsgroup(s).