[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN8PR03MB497724AAAFA43E6555554DC98E969@BN8PR03MB4977.namprd03.prod.outlook.com>
Date: Fri, 5 Mar 2021 08:57:08 +0000
From: "Hennerich, Michael" <Michael.Hennerich@...log.com>
To: Jonathan Cameron <jic23@...nel.org>,
"zzzzArdelean, zzzzAlexandru" <alexandru.Ardelean@...log.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
"lars@...afoo.de" <lars@...afoo.de>,
"Sa, Nuno" <Nuno.Sa@...log.com>,
"Bogdan, Dragos" <Dragos.Bogdan@...log.com>
Subject: RE: [PATCH v3 0/6] iio: Add output buffer support
Hi Jonathan and others,
With output/dac buffer support the semantics of the scan_element type may change.
Today the Format is [be|le]:[s|u]bits/storagebitsXrepeat[>>shift].
While shift (if specified) is the shift that needs to be applied prior to masking out unused bits.
So far so good and it sounds universal.
However, we use the right shift (operator) for that, which makes sense for capture devices.
For output devices the more logical operator would be the left shift.
I'm not proposing a new Format here. I just want to get some agreement that for an output device
le:s12/16>>4
is understood as a left shift of 4, since the unused bits are then on the LSB.
Thoughts?
Best Regards,
Michael
Analog Devices GmbH
Michael Hennerich
Otl-Aicher Strasse 60-64
D-80807 Muenchen; Germany
Sitz der Gesellschaft München, Registergericht München HRB 40368,
Geschäftsführer: Stefan Steyerl, Michael Paul Sondel, Yoon Ah Oh
Powered by blists - more mailing lists