On Tuesday, September 15, 2015 10:49 PM, Arnd Bergmann wrote:
> On Tuesday 15 September 2015 10:40:24 Alan Stern wrote:
>> On Tue, 15 Sep 2015, Arnd Bergmann wrote:
>>
> Do you know the specific requirement on the USB frame numbers? I don't
> know
> enough about USB to tell if
On Tuesday, September 15, 2015 09:14 PM, Arnd Bergmann wrote:
> On Tuesday 15 September 2015 20:56:15 WEN Pingbo wrote:
>> The millisecond of the last second will be normal if tv_sec is
>> overflowed. But for y2038 consistency and demonstration purpose,
>> and avoiding further risks, we still
On Tuesday 15 September 2015 21:43:19 Pingbo Wen wrote:
>
> On Tuesday, September 15, 2015 09:14 PM, Arnd Bergmann wrote:
> > On Tuesday 15 September 2015 20:56:15 WEN Pingbo wrote:
> >> The millisecond of the last second will be normal if tv_sec is
> >> overflowed. But for y2038 consistency and
On Tuesday 15 September 2015 20:10:10 Pingbo Wen wrote:
> On Tuesday, September 15, 2015 02:38 PM, Arnd Bergmann wrote:
> > On Tuesday 15 September 2015 09:48:10 Pingbo Wen wrote:
> - does the driver use monotonic or real time
> Real time. But only microsecond part is used.
>
>
On Tuesday 15 September 2015 20:56:15 WEN Pingbo wrote:
> The millisecond of the last second will be normal if tv_sec is
> overflowed. But for y2038 consistency and demonstration purpose,
> and avoiding further risks, we still need to fix it here,
> to avoid similair problems.
>
> Signed-off-by:
On Tue, 15 Sep 2015, Arnd Bergmann wrote:
> > > Do you know the specific requirement on the USB frame numbers? I don't
> > > know
> > > enough about USB to tell if either of those matter.
> >
> > Using jiffies_to_msecs() here is a nice way. According to USB 2.0 Spec,
> > however, the frame
On Tuesday 15 September 2015 10:40:24 Alan Stern wrote:
> On Tue, 15 Sep 2015, Arnd Bergmann wrote:
>
> > > > Do you know the specific requirement on the USB frame numbers? I don't
> > > > know
> > > > enough about USB to tell if either of those matter.
> > >
> > > Using jiffies_to_msecs() here
