From: Chris Morgan <macroalpha82@gmail.com>
To: linux-iio@vger.kernel.org
Cc: lars@metafoo.de, jic23@kernel.org, peda@axentia.se,
Chris Morgan <macromorgan@hotmail.com>
Subject: [RFC] iio: multiplexer: Copy scan_type details from parent to child
Date: Mon, 18 Jul 2022 13:43:12 -0500 [thread overview]
Message-ID: <20220718184312.11840-1-macroalpha82@gmail.com> (raw)
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>
---
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. */
+ chan->scan_type = pchan->scan_type;
+
return 0;
}
--
2.25.1
next reply other threads:[~2022-07-18 18:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 18:43 Chris Morgan [this message]
2022-07-19 8:51 ` [RFC] iio: multiplexer: Copy scan_type details from parent to child Jonathan Cameron
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=20220718184312.11840-1-macroalpha82@gmail.com \
--to=macroalpha82@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--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 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.