Hi Jaehoon,
Am Mittwoch, 2. September 2015, 14:01:52 schrieb Jaehoon Chung:
> Hi, Heiko.
>
> On 09/01/2015 03:24 AM, Heiko Stuebner wrote:
> > From: Alexandru M Stan
> >
> > Add ciu_drv, ciu_sample clocks and default-sample-phase. This will later
> > be used by tuning code.
>
> As i know,
Hi Jaehoon,
Am Mittwoch, 2. September 2015, 14:01:52 schrieb Jaehoon Chung:
> Hi, Heiko.
>
> On 09/01/2015 03:24 AM, Heiko Stuebner wrote:
> > From: Alexandru M Stan
> >
> > Add ciu_drv, ciu_sample clocks and default-sample-phase. This will later
> > be used by tuning
Hi, Heiko.
On 09/01/2015 03:24 AM, Heiko Stuebner wrote:
> From: Alexandru M Stan
>
> Add ciu_drv, ciu_sample clocks and default-sample-phase. This will later
> be used by tuning code.
As i know, ciu_drv and ciu_sample clocks are generated with "ciu" clock.
But in these patch-set, ciu_drv and
Hi, Heiko.
On 09/01/2015 03:24 AM, Heiko Stuebner wrote:
> From: Alexandru M Stan
>
> Add ciu_drv, ciu_sample clocks and default-sample-phase. This will later
> be used by tuning code.
As i know, ciu_drv and ciu_sample clocks are generated with "ciu" clock.
But in these
From: Alexandru M Stan
Add ciu_drv, ciu_sample clocks and default-sample-phase. This will later
be used by tuning code.
We do not touch ciu_drive (and by extension define default-drive-phase).
Drive phase is mostly used to define minimum hold times, while one could
write some code to determine
From: Alexandru M Stan
Add ciu_drv, ciu_sample clocks and default-sample-phase. This will later
be used by tuning code.
We do not touch ciu_drive (and by extension define default-drive-phase).
Drive phase is mostly used to define minimum hold times, while one could
write
6 matches
Mail list logo