All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: nuno.sa@analog.com
Cc: linux-iio@vger.kernel.org,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Jonathan Cameron <jic23@kernel.org>,
	David Lechner <dlechner@baylibre.com>,
	Andy Shevchenko <andy@kernel.org>
Subject: Re: [PATCH v3 02/10] iio: dac: ad5446: Use DMA safe buffer for transfers
Date: Fri, 31 Oct 2025 15:36:32 +0200	[thread overview]
Message-ID: <aQS7YIxYH2suDmoS@smile.fi.intel.com> (raw)
In-Reply-To: <20251031-dev-add-ad5542-v3-2-d3541036c0e6@analog.com>

On Fri, Oct 31, 2025 at 12:31:23PM +0000, Nuno Sá via B4 Relay wrote:
> 
> Make sure to use DMA safe buffer. While for i2c we could be fine without
> them, we need it for spi anyways.
> 
> As we now have DMA safe buffers, use i2c_master_send_dmasafe().

...

> +	union {
> +		__be16 d16;
> +		u8 d24[3];

Why not __be32 d24; ? Yes, it will require explicit size to be provided, but at
least it will look consistent with the above. OR u8 d16[2]; ? But then it becomes
simply a u8 buf[3] __aligned...;

> +	} __aligned(IIO_DMA_MINALIGN);
>  };

...

>  static int ad5660_write(struct ad5446_state *st, unsigned val)
>  {
>  	struct spi_device *spi = to_spi_device(st->dev);
> -	uint8_t data[3];
>  
> -	put_unaligned_be24(val, &data[0]);
> +	put_unaligned_be24(val, &st->d24[0]);
>  
> -	return spi_write(spi, data, sizeof(data));
> +	return spi_write(spi, st->d24, sizeof(st->d24));
>  }

...

>  static int ad5622_write(struct ad5446_state *st, unsigned val)
>  {
>  	struct i2c_client *client = to_i2c_client(st->dev);
> -	__be16 data = cpu_to_be16(val);
> +	st->d16 = cpu_to_be16(val);

Not really, we don't mix code with definitions (with only few exceptions,
mostly related to cleanup.h).

>  	int ret;
>  
> -	ret = i2c_master_send(client, (char *)&data, sizeof(data));
> +	ret = i2c_master_send_dmasafe(client, (char *)&st->d16, sizeof(st->d16));

This will add a quite an overhead to the transfer (not that I²C is super fast,
but rather the processor is going to do _a lot_ of additional work here instead
of doing something more useful.

>  	if (ret < 0)
>  		return ret;

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-10-31 13:36 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31 12:31 [PATCH v3 00/10] iio: dac: ad5446: Refactor and add support for AD5542 Nuno Sá
2025-10-31 12:31 ` Nuno Sá via B4 Relay
2025-10-31 12:31 ` [PATCH v3 01/10] dt-bindings: iio: dac: Document AD5446 and similar devices Nuno Sá
2025-10-31 12:31   ` Nuno Sá via B4 Relay
2025-11-02  9:18   ` Krzysztof Kozlowski
2025-11-03 10:35     ` Nuno Sá
2025-10-31 12:31 ` [PATCH v3 02/10] iio: dac: ad5446: Use DMA safe buffer for transfers Nuno Sá
2025-10-31 12:31   ` Nuno Sá via B4 Relay
2025-10-31 13:36   ` Andy Shevchenko [this message]
2025-10-31 15:00     ` Nuno Sá
2025-10-31 15:07       ` Andy Shevchenko
2025-10-31 15:50         ` Jonathan Cameron
2025-11-03 10:43         ` Nuno Sá
2025-10-31 12:31 ` [PATCH v3 03/10] iio: dac: ad5446: Don't ignore missing regulator Nuno Sá
2025-10-31 12:31   ` Nuno Sá via B4 Relay
2025-10-31 13:40   ` Andy Shevchenko
2025-10-31 13:43     ` Andy Shevchenko
2025-10-31 12:31 ` [PATCH v3 04/10] iio: dac: ad5446: Move to single chip_info structures Nuno Sá
2025-10-31 12:31   ` Nuno Sá via B4 Relay
2025-10-31 13:47   ` Andy Shevchenko
2025-10-31 15:05     ` Nuno Sá
2025-10-31 15:08       ` Andy Shevchenko
2025-10-31 12:31 ` [PATCH v3 05/10] iio: dac: ad5456: Add missing DT compatibles Nuno Sá
2025-10-31 12:31   ` Nuno Sá via B4 Relay
2025-10-31 12:31 ` [PATCH v3 06/10] iio: dac: ad5446: Separate I2C/SPI into different drivers Nuno Sá
2025-10-31 12:31   ` Nuno Sá via B4 Relay
2025-11-01 16:46   ` Jonathan Cameron
2025-11-03  7:39     ` Andy Shevchenko
2025-11-03 10:40       ` Nuno Sá
2025-11-03 19:30         ` Andy Shevchenko
2025-11-04  7:44           ` Nuno Sá
2025-11-04 14:00             ` Jonathan Cameron
2025-10-31 12:31 ` [PATCH v3 07/10] iio: dac: ad5446: Make use of devm_mutex_init() Nuno Sá
2025-10-31 12:31   ` Nuno Sá via B4 Relay
2025-10-31 12:31 ` [PATCH v3 08/10] iio: dac: ad5446: Make use of the cleanup helpers Nuno Sá
2025-10-31 12:31   ` Nuno Sá via B4 Relay
2025-10-31 12:31 ` [PATCH v3 09/10] iio: dac: ad5446: Fix coding style issues Nuno Sá
2025-10-31 12:31   ` Nuno Sá via B4 Relay
2025-11-01 16:51   ` Jonathan Cameron
2025-11-03 10:44     ` Nuno Sá
2025-10-31 12:31 ` [PATCH v3 10/10] iio: dac: ad5446: Add AD5542 to the spi id table Nuno Sá
2025-10-31 12:31   ` Nuno Sá via B4 Relay

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=aQS7YIxYH2suDmoS@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@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.