On Thu, 29 Aug 2024 14:32:06 +0200 Angelo Dureghello <adureghello@xxxxxxxxxxxx> wrote: > From: Angelo Dureghello <adureghello@xxxxxxxxxxxx> > > Some DACs as ad3552r need a synchronous mode setting, adding > this parameter for ad3552r and for future use on other DACs, > if needed. > > Signed-off-by: Angelo Dureghello <adureghello@xxxxxxxxxxxx> > --- > Documentation/ABI/testing/sysfs-bus-iio-dac | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/Documentation/ABI/testing/sysfs-bus-iio-dac b/Documentation/ABI/testing/sysfs-bus-iio-dac > index 810eaac5533c..a3012baf90b3 100644 > --- a/Documentation/ABI/testing/sysfs-bus-iio-dac > +++ b/Documentation/ABI/testing/sysfs-bus-iio-dac > @@ -59,3 +59,10 @@ Description: > multiple predefined symbols. Each symbol corresponds to a different > output, denoted as out_voltageY_rawN, where N is the integer value > of the symbol. Writing an integer value N will select out_voltageY_rawN. > + > +What: /sys/bus/iio/devices/iio:deviceX/out_voltage_synchronous_mode > +KernelVersion: 6.13 > +Contact: linux-iio@xxxxxxxxxxxxxxx > +Description: > + This attribute allows a specific synchronization mode, mainly > + intended for DACs where multiple synchronization methods are available. If we accept this it needs an _available as well + a list of the possible modes. That list must be exhaustive across all devices so we constrain these appropriately. However, right now this seems more like picking a trigger, or potentially the PWM feeds into the spi offload code than anything else, so I'm not sure we want to introduce new ABI for it. Jonathan >
