From: Pavel Machek <pavel@ucw.cz>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: Florian Vaussard <florian.vaussard@gmail.com>,
devicetree@vger.kernel.org, Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <j.anaszewski@samsung.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
Florian Vaussard <florian.vaussard@heig-vd.ch>
Subject: Re: [PATCH v3 2/2] leds: Add driver for NCP5623 3-channel I2C LED driver
Date: Sat, 24 Sep 2016 14:00:23 +0200 [thread overview]
Message-ID: <20160924120022.GB8696@amd> (raw)
In-Reply-To: <d6dfc1aa-941d-fdbb-5fda-74c85b571bc5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
Hi!
> Instead I propose the following:
>
> n_iled_max =
> 31 - (priv->led_iref * 2400 / priv->leds_max_current +
> !!(priv->led_iref * 2400 % priv->leds_max_current))
>
div_round_up?
Best regards,
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 --]
next prev parent reply other threads:[~2016-09-24 12:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 11:34 [PATCH v3 0/2] leds: Add driver for NCP5623 3-channel I2C LED driver Florian Vaussard
2016-09-16 11:34 ` [PATCH v3 1/2] leds: ncp5623: Add device tree binding documentation Florian Vaussard
2016-09-23 17:29 ` Rob Herring
2016-09-24 11:58 ` Pavel Machek
2016-09-24 19:06 ` Jacek Anaszewski
2016-09-28 10:04 ` Florian Vaussard
2016-09-28 10:02 ` Florian Vaussard
2016-09-28 10:58 ` Pavel Machek
2016-09-16 11:34 ` [PATCH v3 2/2] leds: Add driver for NCP5623 3-channel I2C LED driver Florian Vaussard
2016-09-18 18:20 ` Jacek Anaszewski
2016-09-24 12:00 ` Pavel Machek [this message]
2016-09-24 18:45 ` Jacek Anaszewski
2016-09-29 16:18 ` Florian Vaussard
2016-09-29 17:13 ` Florian Vaussard
2016-09-30 21:00 ` 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=20160924120022.GB8696@amd \
--to=pavel@ucw.cz \
--cc=devicetree@vger.kernel.org \
--cc=florian.vaussard@gmail.com \
--cc=florian.vaussard@heig-vd.ch \
--cc=j.anaszewski@samsung.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=rpurdie@rpsys.net \
/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