On Tue, Jun 6, 2017 at 12:41 PM, Felipe Balbi wrote:
>
> Hi,
>
> Greg KH writes:
>>> > I'm OK with dropping legacy f_uac1 implementation.
>>> >
>>> > Another idea I was thinking about is to implement simple in-kernel
>>> > driver which will do the
Hi,
Greg KH writes:
>> > I'm OK with dropping legacy f_uac1 implementation.
>> >
>> > Another idea I was thinking about is to implement simple in-kernel
>> > driver which will do the same as existing alsaloop tool userspace
>> > tool does (so legacy users will need
On Mon, Jun 05, 2017 at 12:22:13PM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Ruslan Bilovol writes:
> >> Ruslan Bilovol writes:
> >>> I came to this patch series when wanted to do two things:
> >>> - use UAC1 as virtual ALSA sound card on
Hi,
Ruslan Bilovol writes:
>> Ruslan Bilovol writes:
>>> I came to this patch series when wanted to do two things:
>>> - use UAC1 as virtual ALSA sound card on gadget side,
>>>just like UAC2 is used so it's possible to do rate
>>>
Hi,
On Fri, Jun 2, 2017 at 12:42 PM, Felipe Balbi wrote:
>
> Hi,
>
> Ruslan Bilovol writes:
>> I came to this patch series when wanted to do two things:
>> - use UAC1 as virtual ALSA sound card on gadget side,
>>just like UAC2 is used so it's
Hi,
Ruslan Bilovol writes:
> I came to this patch series when wanted to do two things:
> - use UAC1 as virtual ALSA sound card on gadget side,
>just like UAC2 is used so it's possible to do rate
>resampling
> - have both playback/capture support in UAC1
>
>
I came to this patch series when wanted to do two things:
- use UAC1 as virtual ALSA sound card on gadget side,
just like UAC2 is used so it's possible to do rate
resampling
- have both playback/capture support in UAC1
Since I wanted to have same behavior for both UAC1/UAC2,
obviously