From: Jonathan Cameron <jic23@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Mehdi Djait <mehdi.djait@linux.intel.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: kx022a: document new chip_info structure members
Date: Sat, 7 Dec 2024 18:02:01 +0000 [thread overview]
Message-ID: <20241207180201.51deb7ce@jic23-huawei> (raw)
In-Reply-To: <Z1LDUj-naUdGSM6n@mva-rohm>
On Fri, 6 Dec 2024 11:26:42 +0200
Matti Vaittinen <mazziesaccount@gmail.com> wrote:
> The kx022a driver supports a few different HW variants. A chip-info
> structure is used to describe sensor specific details. Support for
> sensors with different measurement g-ranges was added recently,
> introducing sensor specific scale arrays.
>
> The members of the chip-info structure have been documented using
> kerneldoc. The newly added members omitted the documentation. It is nice
> to have all the entries documented for the sake of the consistency.
> Furthermore, the scale table format may not be self explatonary, nor how
> the amount of scales is informed.
>
> Add documentation to scale table entries to maintain consistency and to
> make it more obvious how the scales should be represented.
>
> Suggested-by: Mehdi Djait <mehdi.djait@linux.intel.com>
> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
Applied to the togreg branch of iio.git. Initially pushed out as testing.
Mehdi, if you want to give a tag (or more feedback) I am happy to rebase
for a few days.
Jonathan
> ---
> Revision history:
> v1 => v2:
> - Improved wording based on discussion with Mehdi.
>
> drivers/iio/accel/kionix-kx022a.h | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/iio/accel/kionix-kx022a.h b/drivers/iio/accel/kionix-kx022a.h
> index 142652ff4b22..d18d56cef098 100644
> --- a/drivers/iio/accel/kionix-kx022a.h
> +++ b/drivers/iio/accel/kionix-kx022a.h
> @@ -137,6 +137,14 @@ struct kx022a_data;
> *
> * @name: name of the device
> * @regmap_config: pointer to register map configuration
> + * scale_table: An array of tables of scaling factors for
> + * a supported acceleration measurement range.
> + * Each table containing a single scaling
> + * factor consisting of two integers. The first
> + * value in a table is the integer part, and
> + * the second value is the fractional part as
> + * parts per billion.
> + * scale_table_size: Amount of values in tables.
> * @channels: pointer to iio_chan_spec array
> * @num_channels: number of iio_chan_spec channels
> * @fifo_length: number of 16-bit samples in a full buffer
>
> base-commit: 05ff9c9c53c643551fe08fe52bd714310b9afc2e
next prev parent reply other threads:[~2024-12-07 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 9:26 [PATCH v2] iio: kx022a: document new chip_info structure members Matti Vaittinen
2024-12-07 18:02 ` Jonathan Cameron [this message]
2024-12-08 17:34 ` Mehdi Djait
2024-12-08 17:42 ` Mehdi Djait
2024-12-08 18:25 ` Jonathan Cameron
2024-12-09 8:00 ` Matti Vaittinen
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=20241207180201.51deb7ce@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=mehdi.djait@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox