Hi,
John Youn writes:
[...]
module parameters also feel like a big, big hammer to hit a tiny nail
head. I don't want to add any module parameters for stuff like this. And
since you've been pushing for them for a while, it only shows that
you're only
On 9/16/2016 12:55 AM, Felipe Balbi wrote:
>
> Hi John,
>
> John Youn writes:
>>> John Youn writes:
>> John Youn writes:
>>> On 8/31/2016 2:38 AM, Felipe Balbi wrote:
If we don't know what are the actual
Hi John,
John Youn writes:
>> John Youn writes:
> John Youn writes:
>> On 8/31/2016 2:38 AM, Felipe Balbi wrote:
>>> If we don't know what are the actual U1/U2 exit
>>> latencies from the UDC, we're better
On 9/14/2016 11:53 PM, Felipe Balbi wrote:
>
> Hi,
>
> John Youn writes:
John Youn writes:
> On 8/31/2016 2:38 AM, Felipe Balbi wrote:
>> If we don't know what are the actual U1/U2 exit
>> latencies from the UDC, we're better off
Hi,
John Youn writes:
>>> John Youn writes:
On 8/31/2016 2:38 AM, Felipe Balbi wrote:
> If we don't know what are the actual U1/U2 exit
> latencies from the UDC, we're better off using
> maximum latencies as default. This should
On 8/31/2016 1:37 PM, John Youn wrote:
> On 8/31/2016 12:47 PM, Felipe Balbi wrote:
>>
>> Hi John,
>>
>> John Youn writes:
>>> On 8/31/2016 2:38 AM, Felipe Balbi wrote:
If we don't know what are the actual U1/U2 exit
latencies from the UDC, we're better off using
On 8/31/2016 12:47 PM, Felipe Balbi wrote:
>
> Hi John,
>
> John Youn writes:
>> On 8/31/2016 2:38 AM, Felipe Balbi wrote:
>>> If we don't know what are the actual U1/U2 exit
>>> latencies from the UDC, we're better off using
>>> maximum latencies as default. This should
On Wed, 31 Aug 2016, Felipe Balbi wrote:
> Hi John,
>
> John Youn writes:
> > On 8/31/2016 2:38 AM, Felipe Balbi wrote:
> >> If we don't know what are the actual U1/U2 exit
> >> latencies from the UDC, we're better off using
> >> maximum latencies as default. This should
Hi John,
John Youn writes:
> On 8/31/2016 2:38 AM, Felipe Balbi wrote:
>> If we don't know what are the actual U1/U2 exit
>> latencies from the UDC, we're better off using
>> maximum latencies as default. This should avoid
>> any problems with too frequent U1/U2 entry.
On 8/31/2016 2:38 AM, Felipe Balbi wrote:
> If we don't know what are the actual U1/U2 exit
> latencies from the UDC, we're better off using
> maximum latencies as default. This should avoid
> any problems with too frequent U1/U2 entry.
>
> Signed-off-by: Felipe Balbi
If we don't know what are the actual U1/U2 exit
latencies from the UDC, we're better off using
maximum latencies as default. This should avoid
any problems with too frequent U1/U2 entry.
Signed-off-by: Felipe Balbi
---
include/linux/usb/gadget.h | 12 ++--
11 matches
Mail list logo