From: Jonathan Cameron <jic23@kernel.org>
To: Chris Morgan <macroalpha82@gmail.com>
Cc: linux-iio@vger.kernel.org, lars@metafoo.de, peda@axentia.se,
Chris Morgan <macromorgan@hotmail.com>
Subject: Re: [RFC] iio: multiplexer: Copy scan_type details from parent to child
Date: Tue, 19 Jul 2022 09:51:16 +0100 [thread overview]
Message-ID: <20220719095116.3dc46f3a@jic23-huawei> (raw)
In-Reply-To: <20220718184312.11840-1-macroalpha82@gmail.com>
On Mon, 18 Jul 2022 13:43:12 -0500
Chris Morgan <macroalpha82@gmail.com> wrote:
> From: Chris Morgan <macromorgan@hotmail.com>
>
> Copy the scan_type details from the parent iio channel to the child.
> The scan_type is otherwise empty and things like the storagebits are
> zero (which causes a problem for the adc-joystick driver which
> validates the storagebits when used through a mux). I'm submitting this
> as an RFC because I'm not sure if this is the correct way to handle
> this scenario (a driver that checks the storagebits used with the iio
> multiplexer).
>
> Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
Seems sensible to me. Though Peter is expert on this one.
One comment on the comment inline...
> ---
> drivers/iio/multiplexer/iio-mux.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/iio/multiplexer/iio-mux.c b/drivers/iio/multiplexer/iio-mux.c
> index 93558fddfa9b..1de01ec878c4 100644
> --- a/drivers/iio/multiplexer/iio-mux.c
> +++ b/drivers/iio/multiplexer/iio-mux.c
> @@ -322,6 +322,9 @@ static int mux_configure_channel(struct device *dev, struct mux *mux,
> if (page)
> devm_kfree(dev, page);
>
> + /* Copy scan type from parent to mux child. */
Comment is in the obvious category, so drop that.
> + chan->scan_type = pchan->scan_type;
> +
> return 0;
> }
>
next prev parent reply other threads:[~2022-07-19 8:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 18:43 [RFC] iio: multiplexer: Copy scan_type details from parent to child Chris Morgan
2022-07-19 8:51 ` Jonathan Cameron [this message]
2022-07-19 13:27 ` Peter Rosin
2022-07-19 14:19 ` Jonathan Cameron
2022-07-19 14:44 ` Chris Morgan
2022-07-19 17:54 ` Peter Rosin
2022-07-19 19:22 ` Chris Morgan
2022-07-20 8:25 ` 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=20220719095116.3dc46f3a@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=macroalpha82@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=peda@axentia.se \
/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