public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Robert Budai <robert.budai@analog.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Nuno Sa <nuno.sa@analog.com>,
	Ramona Gradinariu <ramona.gradinariu@analog.com>,
	Antoniu Miclaus <antoniu.miclaus@analog.com>,
	Jonathan Cameron <jic23@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 6/7] iio: imu: adis16550: add adis16550 support
Date: Mon, 25 Nov 2024 14:47:49 +0100	[thread overview]
Message-ID: <92a8c1d1-82a0-4c91-a5ba-bffd574f3532@kernel.org> (raw)
In-Reply-To: <20241125133520.24328-7-robert.budai@analog.com>

On 25/11/2024 14:35, Robert Budai wrote:


...


> +	indio_dev->name = spi_get_device_id(spi)->name;
> +	indio_dev->channels = st->info->channels;
> +	indio_dev->num_channels = st->info->num_channels;
> +	indio_dev->available_scan_masks = adis16550_channel_masks;
> +	indio_dev->info = &adis16550_info;
> +	indio_dev->modes = INDIO_DIRECT_MODE;
> +
> +	st->adis.ops = &adis16550_ops;
> +
> +	st->adis.xfer = kcalloc(2, sizeof(*st->adis.xfer), GFP_KERNEL);
> +	if (!st->adis.xfer)
> +		return -ENOMEM;
> +
> +	void *buffer_tmp __free(void) = kzalloc(ADIS16550_BURST_DATA_LEN + sizeof(u32),
> +				  GFP_KERNEL);
> +	if (!buffer_tmp) {
> +		kfree(st->adis.xfer);
> +		return -ENOMEM;
> +	}
> +	st->adis.buffer = no_free_ptr(buffer_tmp);
> +
> +	ret = devm_regulator_get_enable(dev, "vdd");
> +	if (ret)
> +		return dev_err_probe(dev, ret,
> +				     "Failed to get vdd regulator\n");
> +
> +	ret = adis_init(&st->adis, indio_dev, spi, &adis16550_data);
> +	if (ret)
> +		return ret;


Why this error path does not free xfer but earlier does?

> +
> +	ret = __adis_initial_startup(&st->adis);
> +	if (ret)
> +		return ret;
> +
> +	ret = adis16550_config_sync(st);
> +	if (ret)
> +		return ret;
> +
> +	ret = devm_adis_setup_buffer_and_trigger(&st->adis, indio_dev,
> +						 adis16550_trigger_handler);
> +	if (ret)
> +		return ret;
> +
> +	ret = devm_iio_device_register(dev, indio_dev);
> +	if (ret)
> +		return ret;
> +
> +	adis16550_debugfs_init(indio_dev);
> +
> +	return 0;
> +}
> +
> +static const struct spi_device_id adis16550_id[] = {
> +	{ "adis16550", ADIS16550 },
> +	{ "adis16550w", ADIS16550W },
> +	{ }
> +};
> +MODULE_DEVICE_TABLE(spi, adis16550_id);
> +
> +static const struct of_device_id adis16550_of_match[] = {
> +	{ .compatible = "adi,adis16550" },
> +	{ .compatible = "adi,adis16550w" },

So devices are the same or do you have here un-synced tables?

Best regards,
Krzysztof

  reply	other threads:[~2024-11-25 13:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 13:35 [PATCH 0/7] adis16550-v2 Robert Budai
2024-11-25 13:35 ` [PATCH 1/7] iio: imu: adis: Remove documented not used elements Robert Budai
2024-11-30 17:08   ` Jonathan Cameron
2024-11-25 13:35 ` [PATCH 2/7] iio: imu: adis: Add custom ops struct Robert Budai
2024-11-30 17:13   ` Jonathan Cameron
2024-11-25 13:35 ` [PATCH 3/7] iio: imu: adis: Add reset to custom ops Robert Budai
2024-11-30 17:12   ` Jonathan Cameron
2024-11-25 13:35 ` [PATCH 4/7] iio: imu: adis: Add DIAG_STAT register size Robert Budai
2024-11-25 13:35 ` [PATCH 5/7] dt-bindings: iio: Add adis16550 bindings Robert Budai
2024-11-25 13:46   ` Krzysztof Kozlowski
2024-11-25 13:35 ` [PATCH 6/7] iio: imu: adis16550: add adis16550 support Robert Budai
2024-11-25 13:47   ` Krzysztof Kozlowski [this message]
2024-11-30 17:31   ` Jonathan Cameron
2024-11-25 13:35 ` [PATCH 7/7] docs: iio: add documentation for adis16550 driver Robert Budai
2024-11-25 14:22 ` [PATCH 0/7] adis16550-v2 Budai, Robert

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=92a8c1d1-82a0-4c91-a5ba-bffd574f3532@kernel.org \
    --to=krzk@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=antoniu.miclaus@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=ramona.gradinariu@analog.com \
    --cc=robert.budai@analog.com \
    --cc=robh@kernel.org \
    /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