From: Pavel Machek <pavel@ucw.cz>
To: Oleh Kravchenko <oleg@kaa.org.ua>
Cc: Dan Murphy <dmurphy@ti.com>,
devicetree@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH v2 2/2] leds: add LED driver for EL15203000 board
Date: Tue, 11 Jun 2019 12:39:22 +0200 [thread overview]
Message-ID: <20190611103922.GB20775@amd> (raw)
In-Reply-To: <cf0e62c5-2502-19d2-5956-f262eee2255d@kaa.org.ua>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
Hi!
> >> + u8 cmd[2];
> >
> > I am wondering if you should #define this as well.
> It's used only in one place, should I really wrap it to define?
> >
> > Then the #define can be used here and then in the for loop.
> >
> > There is no reason to do ARRAY_SIZE if it will always be 2.
>
> Result of ARRAY_SIZE() will be always constant and actually it can be avoided by define.
>
> But I prefer ARRAY_SIZE() :-)
Me too.
> > As pointed out your max_brightness is a binary and the 0x32 is an effect you technically don't even need max_brightness if you
> >
> > expose the effects as a file.
> >
> > Does 0x32 turn the LED on or off? Or does it blink the LED?
>
> It depends on LED board,
>
> it can blink.
> It can play scene on LED array.
> It can blink smoothly.
>
> But it depend on the board, not a protocol.
But we expect drivers to control the boards, not protocols.
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 --]
prev parent reply other threads:[~2019-06-11 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 19:03 [PATCH v2 2/2] leds: add LED driver for EL15203000 board Oleh Kravchenko
2019-06-07 20:13 ` Dan Murphy
2019-06-07 21:33 ` Oleh Kravchenko
2019-06-11 10:39 ` 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=20190611103922.GB20775@amd \
--to=pavel@ucw.cz \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--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