On Tue, Feb 13, 2018 at 9:07 PM, Kalle Valo wrote:
> Amitkumar Karwar writes:
>
>> On Thu, Feb 1, 2018 at 12:26 PM, Kalle Valo wrote:
>>> Amitkumar Karwar writes:
>>>
From: Prameela Rani Garnepudi
With BT support, driver has to handle two streams of data
(i.e. wlan and BT).
Amitkumar Karwar writes:
> On Thu, Feb 1, 2018 at 12:26 PM, Kalle Valo wrote:
>> Amitkumar Karwar writes:
>>
>>> From: Prameela Rani Garnepudi
>>>
>>> With BT support, driver has to handle two streams of data
>>> (i.e. wlan and BT). Actual coex implementation is in firmware.
>>> Coex module ju
On Thu, Feb 1, 2018 at 12:38 PM, Kalle Valo wrote:
> Amitkumar Karwar writes:
>
>> From: Prameela Rani Garnepudi
>>
>> With BT support, driver has to handle two streams of data
>> (i.e. wlan and BT). Actual coex implementation is in firmware.
>> Coex module just schedule the packets to firmware
On Thu, Feb 1, 2018 at 12:26 PM, Kalle Valo wrote:
> Amitkumar Karwar writes:
>
>> From: Prameela Rani Garnepudi
>>
>> With BT support, driver has to handle two streams of data
>> (i.e. wlan and BT). Actual coex implementation is in firmware.
>> Coex module just schedule the packets to firmware
Amitkumar Karwar writes:
> From: Prameela Rani Garnepudi
>
> With BT support, driver has to handle two streams of data
> (i.e. wlan and BT). Actual coex implementation is in firmware.
> Coex module just schedule the packets to firmware by taking them
> from the corresponding paths.
>
> Structure
Amitkumar Karwar writes:
> From: Prameela Rani Garnepudi
>
> With BT support, driver has to handle two streams of data
> (i.e. wlan and BT). Actual coex implementation is in firmware.
> Coex module just schedule the packets to firmware by taking them
> from the corresponding paths.
>
> Structure