On 04/02/16 12:51, Daniel Baluta wrote: >> Would it be more consistent to handle the mutex outside of the switch above >> similar >> to how it is handled in ads1015_write_raw? >> >> Also the ads1015_set_power_state(data, false) is called either way so why >> not just >> use one call? >> > > I don't have a strong preference for that. I think across IIO drivers > we can find both coding practices. Often we move it into the switch because in most driver some of the read_raw elements don't need to query the hardware (scales are often fixed for example) so we don't need to take the lock for them. Here it makes sense to take the lock.
(Not that I care much either way!) > > Indeed consistency with ads1015_write_raw is a good argument. Will fix it. > > I will leave the code here for one more day and then send an updated version. > > thanks, > Daniel. > -- > To unsubscribe from this list: send the line "unsubscribe linux-iio" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >
