On Wed, May 13, 2015 at 8:32 PM, Jonathan Cameron wrote:
> On 13/05/15 12:14, Lars-Peter Clausen wrote:
>> Hi,
>>
>> I'd like to go back to the issue of having one folder per trigger type and
>> create triggers for a type in their respective folder.
>>
>> I'm not convinced that it is an intentiona
On 13/05/15 12:14, Lars-Peter Clausen wrote:
> Hi,
>
> I'd like to go back to the issue of having one folder per trigger type and
> create triggers for a type in their respective folder.
>
> I'm not convinced that it is an intentional design restriction of configfs
> that we can't do this, but ra
Hi,
I'd like to go back to the issue of having one folder per trigger type and
create triggers for a type in their respective folder.
I'm not convinced that it is an intentional design restriction of configfs
that we can't do this, but rather a case of it not being implemented
because nobody need
On Fri, May 8, 2015 at 9:41 PM, Jonathan Cameron wrote:
> On 08/05/15 09:33, Daniel Baluta wrote:
>> This patchset introduces IIO software triggers, offers a way of configuring
>> them via configfs and adds the IIO hrtimer based interrupt source to be used
>> with software triggers.
>>
>> The arhi
On 08/05/15 09:33, Daniel Baluta wrote:
> This patchset introduces IIO software triggers, offers a way of configuring
> them via configfs and adds the IIO hrtimer based interrupt source to be used
> with software triggers.
>
> The arhitecture is now split in 3 parts, to remove all IIO trigger spec
This patchset introduces IIO software triggers, offers a way of configuring
them via configfs and adds the IIO hrtimer based interrupt source to be used
with software triggers.
The arhitecture is now split in 3 parts, to remove all IIO trigger specific
parts from IIO configfs core:
(1) IIO softwa
6 matches
Mail list logo
