From: Jonathan Cameron <jic23@kernel.org>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Nuno Sá" <nuno.sa@analog.com>
Subject: Re: [PATCH 1/5] iio: gyro: adi16136: construct adis data on probe vs static on driver
Date: Sun, 15 Dec 2019 16:18:47 +0000 [thread overview]
Message-ID: <20191215161847.21c67f00@archlinux> (raw)
In-Reply-To: <20191213160312.1834-1-alexandru.ardelean@analog.com>
On Fri, 13 Dec 2019 18:03:08 +0200
Alexandru Ardelean <alexandru.ardelean@analog.com> wrote:
> This change is done in preparation of adding an `struct adis_timeout` type.
> Some ADIS drivers support multiple drivers, with various combinations of
> timeouts. Creating static tables for each driver is possible, but that also
> creates quite a lot of duplication.
>
> Signed-off-by: Nuno Sá <nuno.sa@analog.com>
> Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
There are considerable advantages to using constant structures,
(security - not that relevant here probably, XiP, general readability)
So to take a series like this I want to see evidence that it makes
a significant difference. So far you just have cases where we end up
with a worse result. More code, harder to read...
Hence it will take a lot to persuade me to take this series without
the follow up patches where I assume significant advantages are seen.
Jonathan
> ---
> drivers/iio/gyro/adis16136.c | 49 ++++++++++++++++++++++--------------
> 1 file changed, 30 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/iio/gyro/adis16136.c b/drivers/iio/gyro/adis16136.c
> index f10c4f173898..129de2bd5845 100644
> --- a/drivers/iio/gyro/adis16136.c
> +++ b/drivers/iio/gyro/adis16136.c
> @@ -465,24 +465,6 @@ static const char * const adis16136_status_error_msgs[] = {
> [ADIS16136_DIAG_STAT_FLASH_CHKSUM_FAIL] = "Flash checksum error",
> };
>
> -static const struct adis_data adis16136_data = {
> - .diag_stat_reg = ADIS16136_REG_DIAG_STAT,
> - .glob_cmd_reg = ADIS16136_REG_GLOB_CMD,
> - .msc_ctrl_reg = ADIS16136_REG_MSC_CTRL,
> -
> - .self_test_mask = ADIS16136_MSC_CTRL_SELF_TEST,
> - .startup_delay = 80,
> -
> - .read_delay = 10,
> - .write_delay = 10,
> -
> - .status_error_msgs = adis16136_status_error_msgs,
> - .status_error_mask = BIT(ADIS16136_DIAG_STAT_FLASH_UPDATE_FAIL) |
> - BIT(ADIS16136_DIAG_STAT_SPI_FAIL) |
> - BIT(ADIS16136_DIAG_STAT_SELF_TEST_FAIL) |
> - BIT(ADIS16136_DIAG_STAT_FLASH_CHKSUM_FAIL),
> -};
> -
> enum adis16136_id {
> ID_ADIS16133,
> ID_ADIS16135,
> @@ -509,11 +491,36 @@ static const struct adis16136_chip_info adis16136_chip_info[] = {
> },
> };
>
> +static struct adis_data *adis16136_adis_data_alloc(struct adis16136 *st,
> + struct device *dev)
> +{
> + struct adis_data *data;
> +
> + data = devm_kzalloc(dev, sizeof(struct adis_data), GFP_KERNEL);
> + if (!data)
> + return ERR_PTR(-ENOMEM);
> +
> + data->msc_ctrl_reg = ADIS16136_REG_MSC_CTRL;
> + data->glob_cmd_reg = ADIS16136_REG_GLOB_CMD;
> + data->diag_stat_reg = ADIS16136_REG_DIAG_STAT;
> + data->self_test_mask = ADIS16136_MSC_CTRL_SELF_TEST;
> + data->read_delay = 10;
> + data->write_delay = 10;
> + data->status_error_msgs = adis16136_status_error_msgs;
> + data->status_error_mask = BIT(ADIS16136_DIAG_STAT_FLASH_UPDATE_FAIL) |
> + BIT(ADIS16136_DIAG_STAT_SPI_FAIL) |
> + BIT(ADIS16136_DIAG_STAT_SELF_TEST_FAIL) |
> + BIT(ADIS16136_DIAG_STAT_FLASH_CHKSUM_FAIL);
> +
> + return data;
> +}
> +
> static int adis16136_probe(struct spi_device *spi)
> {
> const struct spi_device_id *id = spi_get_device_id(spi);
> struct adis16136 *adis16136;
> struct iio_dev *indio_dev;
> + const struct adis_data *adis16136_data;
> int ret;
>
> indio_dev = devm_iio_device_alloc(&spi->dev, sizeof(*adis16136));
> @@ -532,7 +539,11 @@ static int adis16136_probe(struct spi_device *spi)
> indio_dev->info = &adis16136_info;
> indio_dev->modes = INDIO_DIRECT_MODE;
>
> - ret = adis_init(&adis16136->adis, indio_dev, spi, &adis16136_data);
> + adis16136_data = adis16136_adis_data_alloc(adis16136, &spi->dev);
> + if (IS_ERR(adis16136_data))
> + return PTR_ERR(adis16136_data);
> +
> + ret = adis_init(&adis16136->adis, indio_dev, spi, adis16136_data);
> if (ret)
> return ret;
>
next prev parent reply other threads:[~2019-12-15 16:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 16:03 [PATCH 1/5] iio: gyro: adi16136: construct adis data on probe vs static on driver Alexandru Ardelean
2019-12-13 16:03 ` [PATCH 2/5] iio: imu: adis16400: " Alexandru Ardelean
2019-12-13 16:03 ` [PATCH 3/5] iio: imu: adis16480: " Alexandru Ardelean
2019-12-13 16:03 ` [PATCH 4/5] iio: adis: Introduce timeouts structure Alexandru Ardelean
2019-12-13 16:03 ` [PATCH 5/5] iio: adis: Remove startup_delay Alexandru Ardelean
2019-12-15 16:18 ` Jonathan Cameron [this message]
2019-12-16 7:49 ` [PATCH 1/5] iio: gyro: adi16136: construct adis data on probe vs static on driver Ardelean, Alexandru
2020-01-07 9:36 ` Sa, Nuno
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=20191215161847.21c67f00@archlinux \
--to=jic23@kernel.org \
--cc=alexandru.ardelean@analog.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.