From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Matt Ranostay <mranostay@gmail.com>, linux-leds@vger.kernel.org
Cc: Matt Ranostay <matt@ranostay.consulting>,
Peter Meerwald <p.meerwald@bct-electronic.com>,
Ricardo Ribalda <ricardo.ribalda@gmail.com>,
Tony Lindgren <tony@atomide.com>,
Jacek Anaszewski <j.anaszewski@samsung.com>
Subject: Re: [PATCH v5] leds: pca963x: enable low-power state
Date: Mon, 31 Oct 2016 23:06:08 +0100 [thread overview]
Message-ID: <b502ec25-5b79-08d4-531c-8d54fe2bcb35@gmail.com> (raw)
In-Reply-To: <1477704042-6598-1-git-send-email-matt@ranostay.consulting>
Hi Matt,
On 10/29/2016 03:20 AM, Matt Ranostay wrote:
> Allow chip to enter low power state when no LEDs are being lit or in
> blink mode.
>
> Cc: Peter Meerwald <p.meerwald@bct-electronic.com>,
> Cc: Ricardo Ribalda <ricardo.ribalda@gmail.com>
> Cc: Tony Lindgren <tony@atomide.com>
> Cc: Jacek Anaszewski <j.anaszewski@samsung.com>
> Signed-off-by: Matt Ranostay <matt@ranostay.consulting>
> ---
> Changes from v1:
> * remove runtime pm
> * count leds that are off, if all then enter low-power state
>
> Changes from v2:
> * add reference count of leds to reduce i2c transactions
>
> Changes from v3:
> * switch to checking bitmask to reduce i2c transactions
>
> Changes from v4:
> * mutex lock during power mangement routine
> * simplify the led bitmask check
>
> drivers/leds/leds-pca963x.c | 40 +++++++++++++++++++++++++++++++++-------
> 1 file changed, 33 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/leds/leds-pca963x.c b/drivers/leds/leds-pca963x.c
> index b6ce1f2ec33e..46fbf935944a 100644
> --- a/drivers/leds/leds-pca963x.c
> +++ b/drivers/leds/leds-pca963x.c
> @@ -103,6 +103,7 @@ struct pca963x {
> struct mutex mutex;
> struct i2c_client *client;
> struct pca963x_led *leds;
> + unsigned long leds_on;
> };
>
> struct pca963x_led {
> @@ -124,7 +125,6 @@ static int pca963x_brightness(struct pca963x_led *pca963x,
> u8 mask = 0x3 << shift;
> int ret;
>
> - mutex_lock(&pca963x->chip->mutex);
> ledout = i2c_smbus_read_byte_data(pca963x->chip->client, ledout_addr);
> switch (brightness) {
> case LED_FULL:
> @@ -141,14 +141,13 @@ static int pca963x_brightness(struct pca963x_led *pca963x,
> PCA963X_PWM_BASE + pca963x->led_num,
> brightness);
> if (ret < 0)
> - goto unlock;
> + return ret;
> ret = i2c_smbus_write_byte_data(pca963x->chip->client,
> ledout_addr,
> (ledout & ~mask) | (PCA963X_LED_PWM << shift));
> break;
> }
> -unlock:
> - mutex_unlock(&pca963x->chip->mutex);
> +
> return ret;
> }
>
> @@ -180,14 +179,41 @@ static void pca963x_blink(struct pca963x_led *pca963x)
> mutex_unlock(&pca963x->chip->mutex);
> }
>
> +static int pca963x_power_state(struct pca963x_led *pca963x)
> +{
> + unsigned long *leds_on = &pca963x->chip->leds_on;
> + unsigned long cached_leds = pca963x->chip->leds_on;
> +
> + if (pca963x->led_cdev.brightness)
> + set_bit(pca963x->led_num, leds_on);
> + else
> + clear_bit(pca963x->led_num, leds_on);
> +
> + if (!(*leds_on) != !cached_leds)
> + return i2c_smbus_write_byte_data(pca963x->chip->client,
> + PCA963X_MODE1, *leds_on ? 0 : BIT(4));
> +
> + return 0;
> +}
> +
> static int pca963x_led_set(struct led_classdev *led_cdev,
> enum led_brightness value)
> {
> struct pca963x_led *pca963x;
> + int ret;
>
> pca963x = container_of(led_cdev, struct pca963x_led, led_cdev);
>
> - return pca963x_brightness(pca963x, value);
> + mutex_lock(&pca963x->chip->mutex);
> +
> + ret = pca963x_brightness(pca963x, value);
> + if (ret < 0)
> + goto unlock;
> + ret = pca963x_power_state(pca963x);
> +
> +unlock:
> + mutex_unlock(&pca963x->chip->mutex);
> + return ret;
> }
>
> static unsigned int pca963x_period_scale(struct pca963x_led *pca963x,
> @@ -403,8 +429,8 @@ static int pca963x_probe(struct i2c_client *client,
> goto exit;
> }
>
> - /* Disable LED all-call address and set normal mode */
> - i2c_smbus_write_byte_data(client, PCA963X_MODE1, 0x00);
> + /* Disable LED all-call address, and power down initially */
> + i2c_smbus_write_byte_data(client, PCA963X_MODE1, BIT(4));
>
> if (pdata) {
> /* Configure output: open-drain or totem pole (push-pull) */
>
Applied, thanks.
--
Best regards,
Jacek Anaszewski
prev parent reply other threads:[~2016-10-31 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 1:20 [PATCH v5] leds: pca963x: enable low-power state Matt Ranostay
2016-10-31 22:06 ` Jacek Anaszewski [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=b502ec25-5b79-08d4-531c-8d54fe2bcb35@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=j.anaszewski@samsung.com \
--cc=linux-leds@vger.kernel.org \
--cc=matt@ranostay.consulting \
--cc=mranostay@gmail.com \
--cc=p.meerwald@bct-electronic.com \
--cc=ricardo.ribalda@gmail.com \
--cc=tony@atomide.com \
/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).