[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8cf4ea9e-89a4-1ab0-334b-9ecc5b1e6f25@linaro.org>
Date: Tue, 16 Aug 2022 14:16:13 +0300
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: George Mois <george.mois@...log.com>, jic23@...nel.org,
robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
linux-iio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: lucas.p.stankus@...il.com
Subject: Re: [PATCH 2/2] drivers: iio: accel adxl312 and adxl314 support
On 16/08/2022 13:28, George Mois wrote:
> ADXL312 and ADXL314 are small, thin, low power, 3-axis accelerometers
> with high resolution (13-bit) measurement up to +/-12 g and +/- 200 g
> respectively.
>
Thank you for your patch. There is something to discuss/improve.
>
> static const struct spi_device_id adxl313_spi_id[] = {
> - { "adxl313" },
> + { "adxl312", ADXL312 },
> + { "adxl313", ADXL313 },
> + { "adxl314", ADXL314 },
> { }
> };
>
> MODULE_DEVICE_TABLE(spi, adxl313_spi_id);
>
> static const struct of_device_id adxl313_of_match[] = {
> + { .compatible = "adi,adxl312" },
> { .compatible = "adi,adxl313" },
> + { .compatible = "adi,adxl314" },
You miss here driver data. I don't remember which driver matching takes
precedence (especially in various cases like DT platforms with device
instantiated by MFD), but for consistency I think both device id tables
should have same driver data.
Best regards,
Krzysztof
Powered by blists - more mailing lists