[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130730131230.GC5002@mwanda>
Date: Tue, 30 Jul 2013 16:12:30 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Rupesh Gujare <rupesh.gujare@...el.com>
Cc: devel@...uxdriverproject.org, gregkh@...uxfoundation.org,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: ozwpan: High resolution timers
On Tue, Jul 30, 2013 at 01:31:50PM +0100, Rupesh Gujare wrote:
> Current implementation assumes HZ = 1000 for calculating
> all internal timer intervals, which creates problem on
> platforms where HZ != 1000.
>
> As well we need resolution of less than 10 mSec for heartbeat
> calculation, this creates problem on some platforms where HZ is
> configured as HZ = 100, or around, which restricts us to timer interval
> of 10 mSec. This is particularly found on embedded devices.
>
> This patch moves on to use high resolution timers to calculate
> all timer intervals as it allows us to have very small resolution
> of timer interval, removing dependency on HZ.
>
I am new to this driver. So we batch all the transfers together and
send/recieve them in oz_hcd_heartbeat() every 10msec? It's a
polling interface?
Sorry, if I am completely mis-reading what this driver is doing.
In other words, could you explain what oz_hcd_heartbeat() does.
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists