From: "Nuno Sá" <noname.nuno@gmail.com>
To: David Lechner <dlechner@baylibre.com>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: dac: ad5791: fix storage
Date: Fri, 24 Jan 2025 12:48:21 +0000 [thread overview]
Message-ID: <d7aa9c53958c1e685bff9f863890bd2f0f29cad5.camel@gmail.com> (raw)
In-Reply-To: <20250122-iio-dac-ad5791-fix-storagebits-v1-1-53746e0f25cd@baylibre.com>
On Wed, 2025-01-22 at 17:16 -0600, David Lechner wrote:
> IIO uses "natural" alignment so storagebits should always be a power of
> 2. Change storagebits to 32 since that is the natural size to store 24
> bits of data.
>
> The ad5791 driver currently doesn't use this field anywhere and doesn't
> support buffered writes, so this does not change anything. We just don't
> want anyone to think that it is OK to have storagebits = 24 in other
> drivers.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
> ---
Reviewed-by: Nuno Sá <nuno.sa@analog.com>
> Since this is purely cosmetic, I didn't bother with a fixes flag.
> ---
> drivers/iio/dac/ad5791.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/dac/ad5791.c b/drivers/iio/dac/ad5791.c
> index
> 57374f78f6b885e1d4f2fb452ac0563b85fc222e..034228a7c059f136cdecfb4683228d0be4c3
> 7477 100644
> --- a/drivers/iio/dac/ad5791.c
> +++ b/drivers/iio/dac/ad5791.c
> @@ -294,7 +294,7 @@ static const struct ad5791_chip_info _name##_chip_info =
> { \
> .scan_type = { \
> .sign = 'u', \
> .realbits = (bits), \
> - .storagebits = 24, \
> + .storagebits = 32, \
> .shift = (_shift), \
> }, \
> .ext_info = ad5791_ext_info, \
>
> ---
> base-commit: 012b8276f08a67b9f2e2fd0f35363ae4a75e5267
> change-id: 20250122-iio-dac-ad5791-fix-storagebits-9f86efa07abb
>
> Best regards,
next prev parent reply other threads:[~2025-01-24 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 23:16 David Lechner
2025-01-24 12:48 ` Nuno Sá [this message]
2025-01-25 12:19 ` Jonathan Cameron
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=d7aa9c53958c1e685bff9f863890bd2f0f29cad5.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®