Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 14/11/16 23:12, Linus Walleij wrote: > On Mon, Nov 14, 2016 at 7:53 PM, Lars-Peter Clausen wrote: > >> It's about figuring out the setting of a "GPIO" that can't be changed from >> software. >> >> Devices sometimes, instead of a configuration bus like I2C or SPI, use >>

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 14/11/16 23:12, Linus Walleij wrote: > On Mon, Nov 14, 2016 at 7:53 PM, Lars-Peter Clausen wrote: > >> It's about figuring out the setting of a "GPIO" that can't be changed from >> software. >> >> Devices sometimes, instead of a configuration bus like I2C or SPI, use >> simple input pins,

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On Mon, Nov 14, 2016 at 7:53 PM, Lars-Peter Clausen wrote: > It's about figuring out the setting of a "GPIO" that can't be changed from > software. > > Devices sometimes, instead of a configuration bus like I2C or SPI, use > simple input pins, that can either be set to high or

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On Mon, Nov 14, 2016 at 7:53 PM, Lars-Peter Clausen wrote: > It's about figuring out the setting of a "GPIO" that can't be changed from > software. > > Devices sometimes, instead of a configuration bus like I2C or SPI, use > simple input pins, that can either be set to high or low, to allow

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 14 November 2016 18:53:28 GMT+00:00, Lars-Peter Clausen wrote: >On 11/14/2016 05:58 PM, Linus Walleij wrote: >> On Sat, Nov 12, 2016 at 3:24 PM, Jonathan Cameron >wrote: >> >>> Is it just me who thought, we need a fixed GPI like a fixed >regulator?

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 14 November 2016 18:53:28 GMT+00:00, Lars-Peter Clausen wrote: >On 11/14/2016 05:58 PM, Linus Walleij wrote: >> On Sat, Nov 12, 2016 at 3:24 PM, Jonathan Cameron >wrote: >> >>> Is it just me who thought, we need a fixed GPI like a fixed >regulator? Probably didn't help clarity that I

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 11/14/2016 05:58 PM, Linus Walleij wrote: > On Sat, Nov 12, 2016 at 3:24 PM, Jonathan Cameron wrote: > >> Is it just me who thought, we need a fixed GPI like a fixed regulator? >> Would allow this sort of fixed wiring to be simply defined. >> >> Linus, worth exploring? > >

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 11/14/2016 05:58 PM, Linus Walleij wrote: > On Sat, Nov 12, 2016 at 3:24 PM, Jonathan Cameron wrote: > >> Is it just me who thought, we need a fixed GPI like a fixed regulator? >> Would allow this sort of fixed wiring to be simply defined. >> >> Linus, worth exploring? > > So if fixed

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 14 November 2016 10:30:50 GMT+00:00, Lars-Peter Clausen wrote: >On 11/12/2016 03:24 PM, Jonathan Cameron wrote: >> On 11/11/16 14:18, Lars-Peter Clausen wrote: >>> On 11/11/2016 07:34 AM, Eva Rachel Retuya wrote: Eliminate the non-standard attribute in_voltage_range

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 14 November 2016 10:30:50 GMT+00:00, Lars-Peter Clausen wrote: >On 11/12/2016 03:24 PM, Jonathan Cameron wrote: >> On 11/11/16 14:18, Lars-Peter Clausen wrote: >>> On 11/11/2016 07:34 AM, Eva Rachel Retuya wrote: Eliminate the non-standard attribute in_voltage_range and move its

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On Sat, Nov 12, 2016 at 3:24 PM, Jonathan Cameron wrote: > Is it just me who thought, we need a fixed GPI like a fixed regulator? > Would allow this sort of fixed wiring to be simply defined. > > Linus, worth exploring? So if fixed regulator is for a voltage provider, this

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On Sat, Nov 12, 2016 at 3:24 PM, Jonathan Cameron wrote: > Is it just me who thought, we need a fixed GPI like a fixed regulator? > Would allow this sort of fixed wiring to be simply defined. > > Linus, worth exploring? So if fixed regulator is for a voltage provider, this would be pretty much

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 11/12/2016 03:24 PM, Jonathan Cameron wrote: > On 11/11/16 14:18, Lars-Peter Clausen wrote: >> On 11/11/2016 07:34 AM, Eva Rachel Retuya wrote: >>> Eliminate the non-standard attribute in_voltage_range and move its >>> functionality under the scale attribute. read_raw() has been taken care >>>

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 11/12/2016 03:24 PM, Jonathan Cameron wrote: > On 11/11/16 14:18, Lars-Peter Clausen wrote: >> On 11/11/2016 07:34 AM, Eva Rachel Retuya wrote: >>> Eliminate the non-standard attribute in_voltage_range and move its >>> functionality under the scale attribute. read_raw() has been taken care >>>

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 11/12/2016 03:22 PM, Eva Rachel Retuya wrote: > Hello, > > Thanks for explaining it. Now I understand better why read_raw is > formatted in that manner. I have some questions in-line: > > On Fri, Nov 11, 2016 at 03:18:37PM +0100, Lars-Peter Clausen wrote: >> On 11/11/2016 07:34 AM, Eva

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 11/12/2016 03:22 PM, Eva Rachel Retuya wrote: > Hello, > > Thanks for explaining it. Now I understand better why read_raw is > formatted in that manner. I have some questions in-line: > > On Fri, Nov 11, 2016 at 03:18:37PM +0100, Lars-Peter Clausen wrote: >> On 11/11/2016 07:34 AM, Eva

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

Hello, Thanks for explaining it. Now I understand better why read_raw is formatted in that manner. I have some questions in-line: On Fri, Nov 11, 2016 at 03:18:37PM +0100, Lars-Peter Clausen wrote: > On 11/11/2016 07:34 AM, Eva Rachel Retuya wrote: > > Eliminate the non-standard attribute

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

Hello, Thanks for explaining it. Now I understand better why read_raw is formatted in that manner. I have some questions in-line: On Fri, Nov 11, 2016 at 03:18:37PM +0100, Lars-Peter Clausen wrote: > On 11/11/2016 07:34 AM, Eva Rachel Retuya wrote: > > Eliminate the non-standard attribute

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 11/11/16 14:18, Lars-Peter Clausen wrote: > On 11/11/2016 07:34 AM, Eva Rachel Retuya wrote: >> Eliminate the non-standard attribute in_voltage_range and move its >> functionality under the scale attribute. read_raw() has been taken care >> of previously so only write_raw() is handled here. >>

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 11/11/16 14:18, Lars-Peter Clausen wrote: > On 11/11/2016 07:34 AM, Eva Rachel Retuya wrote: >> Eliminate the non-standard attribute in_voltage_range and move its >> functionality under the scale attribute. read_raw() has been taken care >> of previously so only write_raw() is handled here. >>

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 11/11/2016 07:34 AM, Eva Rachel Retuya wrote: > Eliminate the non-standard attribute in_voltage_range and move its > functionality under the scale attribute. read_raw() has been taken care > of previously so only write_raw() is handled here. > > Additionally, rename the attribute

Re: [PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

On 11/11/2016 07:34 AM, Eva Rachel Retuya wrote: > Eliminate the non-standard attribute in_voltage_range and move its > functionality under the scale attribute. read_raw() has been taken care > of previously so only write_raw() is handled here. > > Additionally, rename the attribute

[PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

Eliminate the non-standard attribute in_voltage_range and move its functionality under the scale attribute. read_raw() has been taken care of previously so only write_raw() is handled here. Additionally, rename the attribute in_voltage_range_available into in_voltage_scale_available.

[PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

Eliminate the non-standard attribute in_voltage_range and move its functionality under the scale attribute. read_raw() has been taken care of previously so only write_raw() is handled here. Additionally, rename the attribute in_voltage_range_available into in_voltage_scale_available.