From: Bryan Wu <cooloney@gmail.com>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: Linux LED Subsystem <linux-leds@vger.kernel.org>,
"rpurdie@rpsys.net" <rpurdie@rpsys.net>
Subject: Re: [PATCH 1/2] leds:pca963x: Add support for PCA9635 LED driver chip
Date: Wed, 2 Jul 2014 16:40:56 -0700 [thread overview]
Message-ID: <CAK5ve-Kt_jLoeSZxRRDn9p3Pv95_eaHnJ2=MfaoNVfpYYHD76Q@mail.gmail.com> (raw)
In-Reply-To: <1404288046-26661-1-git-send-email-pmeerw@pmeerw.net>
On Wed, Jul 2, 2014 at 1:00 AM, Peter Meerwald <pmeerw@pmeerw.net> wrote:
> From: Peter Meerwald <p.meerwald@bct-electronic.com>
>
> supports 16 PWM-controlled LEDs
>
> Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>
> ---
> drivers/leds/leds-pca963x.c | 18 +++++++++++++-----
> 1 file changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/leds/leds-pca963x.c b/drivers/leds/leds-pca963x.c
> index 82589c0..70e3825 100644
> --- a/drivers/leds/leds-pca963x.c
> +++ b/drivers/leds/leds-pca963x.c
> @@ -12,7 +12,7 @@
> * directory of this archive for more details.
> *
> * LED driver for the PCA9633 I2C LED driver (7-bit slave address 0x62)
> - * LED driver for the PCA9634 I2C LED driver (7-bit slave address set by hw.)
> + * LED driver for the PCA9634/5 I2C LED driver (7-bit slave address set by hw.)
> *
> * Note that hardware blinking violates the leds infrastructure driver
> * interface since the hardware only supports blinking all LEDs with the
> @@ -52,6 +52,7 @@
> enum pca963x_type {
> pca9633,
> pca9634,
> + pca9635,
> };
>
> struct pca963x_chipdef {
> @@ -74,6 +75,12 @@ static struct pca963x_chipdef pca963x_chipdefs[] = {
> .ledout_base = 0xc,
> .n_leds = 8,
> },
> + [pca9635] = {
> + .grppwm = 0x12,
> + .grpfreq = 0x13,
> + .ledout_base = 0x14,
> + .n_leds = 16,
> + },
> };
>
> /* Total blink period in milliseconds */
> @@ -84,6 +91,7 @@ static const struct i2c_device_id pca963x_id[] = {
> { "pca9632", pca9633 },
> { "pca9633", pca9633 },
> { "pca9634", pca9634 },
> + { "pca9635", pca9635 },
> { }
> };
> MODULE_DEVICE_TABLE(i2c, pca963x_id);
> @@ -107,7 +115,7 @@ struct pca963x_led {
> struct work_struct work;
> enum led_brightness brightness;
> struct led_classdev led_cdev;
> - int led_num; /* 0 .. 7 potentially */
> + int led_num; /* 0 .. 15 potentially */
> enum pca963x_cmd cmd;
> char name[32];
> u8 gdc;
> @@ -321,6 +329,7 @@ static const struct of_device_id of_pca963x_match[] = {
> { .compatible = "nxp,pca9632", },
> { .compatible = "nxp,pca9633", },
> { .compatible = "nxp,pca9634", },
> + { .compatible = "nxp,pca9635", },
> {},
> };
> #else
> @@ -375,9 +384,8 @@ static int pca963x_probe(struct i2c_client *client,
> pca963x_chip->leds = pca963x;
>
> /* Turn off LEDs by default*/
> - i2c_smbus_write_byte_data(client, chip->ledout_base, 0x00);
> - if (chip->n_leds > 4)
> - i2c_smbus_write_byte_data(client, chip->ledout_base + 1, 0x00);
> + for (i = 0; i < chip->n_leds; i++)
> + i2c_smbus_write_byte_data(client, chip->ledout_base + i, 0x00);
>
This change looks like a bug fixing. The previous one just turn off
the first and the second LEDs.
If yes, please add some description into the commit message.
Other than this, this patch looks good to me.
-Bryan
> for (i = 0; i < chip->n_leds; i++) {
> pca963x[i].led_num = i;
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2014-07-02 23:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 8:00 [PATCH 1/2] leds:pca963x: Add support for PCA9635 LED driver chip Peter Meerwald
2014-07-02 8:00 ` [PATCH 2/2] leds:pca963x: Always initialize MODE2 register Peter Meerwald
2014-07-02 23:42 ` Bryan Wu
2014-07-02 8:00 ` [PATCH 3/3] leds:pca963x: Update for PCA9635 and correct statement about MODE2 OUTDRV default Peter Meerwald
2014-07-02 23:44 ` Bryan Wu
2014-07-02 23:40 ` Bryan Wu [this message]
2014-07-03 5:38 ` [PATCH 1/2] leds:pca963x: Add support for PCA9635 LED driver chip Peter Meerwald
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='CAK5ve-Kt_jLoeSZxRRDn9p3Pv95_eaHnJ2=MfaoNVfpYYHD76Q@mail.gmail.com' \
--to=cooloney@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--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;
as well as URLs for NNTP newsgroup(s).