From: Dan Carpenter <dan.carpenter@oracle.com>
To: ncase@xes-inc.com
Cc: linux-leds@vger.kernel.org
Subject: [bug report] leds: Add support for Philips PCA955x I2C LED drivers
Date: Thu, 17 Aug 2017 13:28:47 +0300 [thread overview]
Message-ID: <20170817102847.n4h5ez6zlfclkcjs@mwanda> (raw)
Hello Nate Case,
The patch f46e9203d9a1: "leds: Add support for Philips PCA955x I2C
LED drivers" from Jul 16, 2008, leads to the following static checker
warning:
drivers/leds/leds-pca955x.c:476 pca955x_probe()
warn: this array is probably non-NULL. 'pdata->leds + i->name'
drivers/leds/leds-pca955x.c
465 switch (pca955x_led->type) {
466 case PCA955X_TYPE_NONE:
467 break;
468 case PCA955X_TYPE_GPIO:
469 ngpios++;
470 break;
471 case PCA955X_TYPE_LED:
472 /*
473 * Platform data can specify LED names and
474 * default triggers
475 */
476 if (pdata->leds[i].name)
^^^^^^^^^^^^^^^^^^^
The comment implies that we should be testing pdata->leds[i].name[0] to
see if any string has been set?
477 snprintf(pca955x_led->name,
478 sizeof(pca955x_led->name), "pca955x:%s",
479 pdata->leds[i].name);
480 if (pdata->leds[i].default_trigger)
481 pca955x_led->led_cdev.default_trigger =
482 pdata->leds[i].default_trigger;
483
484 pca955x_led->led_cdev.name = pca955x_led->name;
485 pca955x_led->led_cdev.brightness_set_blocking =
486 pca955x_led_set;
487
488 err = devm_led_classdev_register(&client->dev,
489 &pca955x_led->led_cdev);
490 if (err)
491 return err;
492
493 /* Turn off LED */
494 pca955x_led_set(&pca955x_led->led_cdev, LED_OFF);
regards,
dan carpenter
next reply other threads:[~2017-08-17 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 10:28 Dan Carpenter [this message]
2017-08-17 11:27 ` [bug report] leds: Add support for Philips PCA955x I2C LED drivers Pavel Machek
2017-08-17 11:51 ` Dan Carpenter
2017-08-17 13:27 ` Pavel Machek
2017-08-17 13:37 ` Dan Carpenter
2017-08-17 13:43 ` Dan Carpenter
2017-08-17 13:49 ` Dan Carpenter
2017-08-17 13:58 ` Pavel Machek
2017-08-17 13:58 ` Nate Case
2017-08-17 14:01 ` Dan Carpenter
2017-08-17 11:28 ` 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=20170817102847.n4h5ez6zlfclkcjs@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-leds@vger.kernel.org \
--cc=ncase@xes-inc.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