Re: Should we make mark_param_change buffer implementation internal?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Lars-Peter Clausen <lars@xxxxxxxxxx> wrote:

>Hi,
>
>Right now we have a mark_param_change callback in the buffer access
>functions struct, which should be called whenever the parameters
>(length,
>bytes per datum) of the buffer change. Each buffer implementation calls
>their own mark_param_change callback in their set_length and
>set_bytes_per_datum callbacks. Additionally mark_param_change gets
>called
>when the user changes the buffer length. So in this case it will get
>called
>twice.
>
>So I'm wondering if we should make it completely buffer implementation
>internal and not export it in the buffer access functions struct, since
>the
>buffer implementation will probably know best anyway if one of it's
>parameters has changed.

Makes sense. 
>
>- Lars
>--
>To unsubscribe from this list: send the line "unsubscribe linux-iio" in
>the body of a message to majordomo@xxxxxxxxxxxxxxx
>More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Sent from my Android phone 
with K-9 Mail. Please excuse my brevity.
--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Input]     [Linux Kernel]     [Linux SCSI]     [X.org]

  Powered by Linux