Hi Jon,
On Thu, Sep 27, 2012 at 08:54:22, Hunter, Jon wrote:
On 09/19/2012 08:23 AM, Afzal Mohammed wrote:
+Dependency of peripheral timings on gpmc timings:
+
+cs_on: t_ceasu
Thanks for adding these details. Could be good to clarify that the
left-hand side parameters are the gpmc
Hi Afzal,
On 09/27/2012 05:07 AM, Mohammed, Afzal wrote:
Hi Jon,
On Thu, Sep 27, 2012 at 08:54:22, Hunter, Jon wrote:
On 09/19/2012 08:23 AM, Afzal Mohammed wrote:
+Dependency of peripheral timings on gpmc timings:
+
+cs_on: t_ceasu
Thanks for adding these details. Could be good to
Hi Jon,
On Thu, Sep 27, 2012 at 20:46:12, Hunter, Jon wrote:
On 09/27/2012 05:07 AM, Mohammed, Afzal wrote:
Or maybe should the timings be grouped as ...
General
Read Async
Read Async Address/Data Multiplexed
Read Sync
Read Sync Address/Data Multiplexed
Write Async
Write Async
Hi Afzal,
On 09/19/2012 08:23 AM, Afzal Mohammed wrote:
Presently there are three peripherals that gets it timing
by runtime calculation. Those peripherals can work with
frequency scaling that affects gpmc clock. But timing
calculation for them are in different ways.
Here a generic runtime
Presently there are three peripherals that gets it timing
by runtime calculation. Those peripherals can work with
frequency scaling that affects gpmc clock. But timing
calculation for them are in different ways.
Here a generic runtime calculation method is proposed. Input
to this function were
