-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
incorrect channel type (in, out, in_out?) #373
Comments
A few issues (#366, #373) have popped up recently when iio_channel_get_type(ch) == IIO_CHAN_TYPE_UNKNOWN This helps bring that to the top by easily notifing kernel developers when they are doing things that aren't understood by the library. Signed-off-by: Robin Getz <[email protected]>
This convention is used for things that are both directions. It's only used once. It's not mainline and thus libiio doesn't handle it. I would have reverted it but I didn't want to break the API. |
OK - I will keep this open until we decide that the "in_out" (bidirectional attributes) are going upstream (and we should extend libiio) or if they aren't (and we should just leave it alone). -Robin |
Ok - now iio_info gives:
as a polite reminder... |
A few issues (analogdevicesinc#366, analogdevicesinc#373) have popped up recently when iio_channel_get_type(ch) == IIO_CHAN_TYPE_UNKNOWN This helps bring that to the top by easily notifing kernel developers when they are doing things that aren't understood by the library. Signed-off-by: Robin Getz <[email protected]>
closing - since this is a kernel driver issue. |
I'm not sure if this is kernel issue or a libiio one.
an input channel called
out
?we have:
which follow the normal constructs for global voltage[n] attributes, but then we also have:
which I think effects both inputs and output channels, but might break the kernel ABI? or is libiio just not handling
in_out
channels??
The text was updated successfully, but these errors were encountered: