summaryrefslogtreecommitdiffstats
path: root/drivers/iio/adc/ad9467.c
diff options
context:
space:
mode:
authorAlexandru Ardelean <alexandru.ardelean@analog.com>2020-09-16 10:31:28 +0200
committerJonathan Cameron <Jonathan.Cameron@huawei.com>2020-09-16 20:14:17 +0200
commit6026af6a53dffb50db87ef264294dff57ed3a845 (patch)
treef5a80213fed5141f2c435a2a084a732929bca0a8 /drivers/iio/adc/ad9467.c
parentstaging:iio:documentation: Drop most generic docs (diff)
downloadlinux-6026af6a53dffb50db87ef264294dff57ed3a845.tar.xz
linux-6026af6a53dffb50db87ef264294dff57ed3a845.zip
iio: adc: ad9467: refine mismatch vs unknown chip-id messages
We should probably print what the expected chip-ID is. We already have that information available, based on the device specified via device-tree. Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com> Link: https://lore.kernel.org/r/20200916083128.73729-1-alexandru.ardelean@analog.com Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'drivers/iio/adc/ad9467.c')
-rw-r--r--drivers/iio/adc/ad9467.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/iio/adc/ad9467.c b/drivers/iio/adc/ad9467.c
index 1e8fd83b9bc2..9c3ab46e4d88 100644
--- a/drivers/iio/adc/ad9467.c
+++ b/drivers/iio/adc/ad9467.c
@@ -390,7 +390,8 @@ static int ad9467_probe(struct spi_device *spi)
id = ad9467_spi_read(spi, AN877_ADC_REG_CHIP_ID);
if (id != conv->chip_info->id) {
- dev_err(&spi->dev, "Unrecognized CHIP_ID 0x%X\n", id);
+ dev_err(&spi->dev, "Mismatch CHIP_ID, got 0x%X, expected 0x%X\n",
+ id, conv->chip_info->id);
return -ENODEV;
}