diff options
| author | Laxman Dewangan | 2012-09-26 18:18:04 +0530 |
|---|---|---|
| committer | Samuel Ortiz | 2013-10-24 12:08:22 +0200 |
| commit | 34c5c735a89bc0ad5fab1c29b9f425b77fbb7ae7 (patch) | |
| tree | 9500e6826e62e5a07e854981fa79c7efdfed71b7 /drivers/mfd | |
| parent | 61e6cfa80de5760bbe406f4e815b7739205754d2 (diff) | |
mfd: tps65910: Remove warning during dt node parsing
Driver throw the warning message if dt node does not
have the info for VMBCH-Threshold and VMBCH2-Threshold.
These properties are optional property and hence it
is not mandatory to have these on DT node and in this case
it should not throw the warning message.
It creates noise from driver as follows:
[ 0.384605] tps65910 4-002d: VMBCH-Threshold not specified
[ 0.384616] tps65910 4-002d: VMBCH2-Threshold not specified
Removing the warning message from driver.
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Diffstat (limited to 'drivers/mfd')
| -rw-r--r-- | drivers/mfd/tps65910.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/drivers/mfd/tps65910.c b/drivers/mfd/tps65910.c index d79277204835..78ffe6e53eb8 100644 --- a/drivers/mfd/tps65910.c +++ b/drivers/mfd/tps65910.c @@ -410,14 +410,10 @@ static struct tps65910_board *tps65910_parse_dt(struct i2c_client *client, ret = of_property_read_u32(np, "ti,vmbch-threshold", &prop); if (!ret) board_info->vmbch_threshold = prop; - else if (*chip_id == TPS65911) - dev_warn(&client->dev, "VMBCH-Threshold not specified"); ret = of_property_read_u32(np, "ti,vmbch2-threshold", &prop); if (!ret) board_info->vmbch2_threshold = prop; - else if (*chip_id == TPS65911) - dev_warn(&client->dev, "VMBCH2-Threshold not specified"); prop = of_property_read_bool(np, "ti,en-ck32k-xtal"); board_info->en_ck32k_xtal = prop; |