On Thu, 2014-02-13 at 12:05 +0200, Tomi Valkeinen wrote:
> On 13/02/14 11:03, Tomi Valkeinen wrote:
> > On 12/02/14 15:18, Tomi Valkeinen wrote:
> >
> >> However, I hacked together the patch below, which "fixes" the issue for
> >> 96m and dss fclk. It sets the clock parents so that the x2 clocks
On 13/02/14 11:03, Tomi Valkeinen wrote:
> On 12/02/14 15:18, Tomi Valkeinen wrote:
>
>> However, I hacked together the patch below, which "fixes" the issue for
>> 96m and dss fclk. It sets the clock parents so that the x2 clocks are
>> skipped, and makes the x2 clock nodes compatible with
On 12/02/14 15:18, Tomi Valkeinen wrote:
> However, I hacked together the patch below, which "fixes" the issue for
> 96m and dss fclk. It sets the clock parents so that the x2 clocks are
> skipped, and makes the x2 clock nodes compatible with "unused", making
> them effectively disappear. I only
On 12/02/14 15:18, Tomi Valkeinen wrote:
However, I hacked together the patch below, which fixes the issue for
96m and dss fclk. It sets the clock parents so that the x2 clocks are
skipped, and makes the x2 clock nodes compatible with unused, making
them effectively disappear. I only verified
On 13/02/14 11:03, Tomi Valkeinen wrote:
On 12/02/14 15:18, Tomi Valkeinen wrote:
However, I hacked together the patch below, which fixes the issue for
96m and dss fclk. It sets the clock parents so that the x2 clocks are
skipped, and makes the x2 clock nodes compatible with unused, making
On Thu, 2014-02-13 at 12:05 +0200, Tomi Valkeinen wrote:
On 13/02/14 11:03, Tomi Valkeinen wrote:
On 12/02/14 15:18, Tomi Valkeinen wrote:
However, I hacked together the patch below, which fixes the issue for
96m and dss fclk. It sets the clock parents so that the x2 clocks are
Hi Tomi,
On Wed, Feb 12, 2014 at 2:18 PM, Tomi Valkeinen wrote:
> Hi Tero, Christoph,
>
> On 07/02/14 12:12, Christoph Fritz wrote:
>> On Tue, 2014-02-04 at 17:50 +0200, Tero Kristo wrote:
>>> On 01/29/2014 01:21 PM, Christoph Fritz wrote:
> Currently I only analyzed sys_clkout2 (see
Hi Tero, Christoph,
On 07/02/14 12:12, Christoph Fritz wrote:
> On Tue, 2014-02-04 at 17:50 +0200, Tero Kristo wrote:
>> On 01/29/2014 01:21 PM, Christoph Fritz wrote:
Currently I only analyzed sys_clkout2 (see attachments for full
clk_summary files):
Hi Tero, Christoph,
On 07/02/14 12:12, Christoph Fritz wrote:
On Tue, 2014-02-04 at 17:50 +0200, Tero Kristo wrote:
On 01/29/2014 01:21 PM, Christoph Fritz wrote:
Currently I only analyzed sys_clkout2 (see attachments for full
clk_summary files):
Hi Tomi,
On Wed, Feb 12, 2014 at 2:18 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
Hi Tero, Christoph,
On 07/02/14 12:12, Christoph Fritz wrote:
On Tue, 2014-02-04 at 17:50 +0200, Tero Kristo wrote:
On 01/29/2014 01:21 PM, Christoph Fritz wrote:
Currently I only analyzed sys_clkout2 (see
On 10/02/14 22:54, Christoph Fritz wrote:
>> I wonder if I'm still missing some patch?
>
> Is beagle-xM using DSI? Because here the LILLY-A83X board is not. The
> clock registers are all fine now as before the dt clock conversion
> patches.
No, Beagle xM doesn't use DSI, plain DPI.
Tomi
On 10/02/14 22:54, Christoph Fritz wrote:
I wonder if I'm still missing some patch?
Is beagle-xM using DSI? Because here the LILLY-A83X board is not. The
clock registers are all fine now as before the dt clock conversion
patches.
No, Beagle xM doesn't use DSI, plain DPI.
Tomi
On Fri, 2014-02-07 at 15:49 +0200, Tomi Valkeinen wrote:
> On 07/02/14 12:12, Christoph Fritz wrote:
>
> > Yes, your patch fixes the issues for sys_clkout2. Thanks! If you want,
> > you can add my:
> > Tested-by: Christoph Fritz
> >
> > Below is my clock fix for dss:
> >
> > From
On Fri, 2014-02-07 at 15:49 +0200, Tomi Valkeinen wrote:
On 07/02/14 12:12, Christoph Fritz wrote:
Yes, your patch fixes the issues for sys_clkout2. Thanks! If you want,
you can add my:
Tested-by: Christoph Fritz chf.fr...@googlemail.com
Below is my clock fix for dss:
From
Hi,
On 07/02/14 12:12, Christoph Fritz wrote:
> Yes, your patch fixes the issues for sys_clkout2. Thanks! If you want,
> you can add my:
> Tested-by: Christoph Fritz
>
> Below is my clock fix for dss:
>
> From b90a62128068e1b6b0ba2a11c5cc0c8e587cf301 Mon Sep 17 00:00:00 2001
> From: Christoph
On Tue, 2014-02-04 at 17:50 +0200, Tero Kristo wrote:
> On 01/29/2014 01:21 PM, Christoph Fritz wrote:
> >> Currently I only analyzed sys_clkout2 (see attachments for full
> >> clk_summary files):
> >>
> >> clk_summary__next-20140115__works_as_expected:
> >> dpll4_m2_ck1
On Tue, 2014-02-04 at 17:50 +0200, Tero Kristo wrote:
On 01/29/2014 01:21 PM, Christoph Fritz wrote:
Currently I only analyzed sys_clkout2 (see attachments for full
clk_summary files):
clk_summary__next-20140115__works_as_expected:
dpll4_m2_ck1 1
Hi,
On 07/02/14 12:12, Christoph Fritz wrote:
Yes, your patch fixes the issues for sys_clkout2. Thanks! If you want,
you can add my:
Tested-by: Christoph Fritz chf.fr...@googlemail.com
Below is my clock fix for dss:
From b90a62128068e1b6b0ba2a11c5cc0c8e587cf301 Mon Sep 17 00:00:00 2001
On 01/29/2014 01:21 PM, Christoph Fritz wrote:
On Tue, 2014-01-28 at 18:02 +0100, Christoph Fritz wrote:
On Tue, 2014-01-28 at 15:40 +0200, Tero Kristo wrote:
Due to a regression since next-20140122 the following errors are present:
- pin sys_clkout2, which gets configured to 24 Mhz by
On 01/29/2014 01:21 PM, Christoph Fritz wrote:
On Tue, 2014-01-28 at 18:02 +0100, Christoph Fritz wrote:
On Tue, 2014-01-28 at 15:40 +0200, Tero Kristo wrote:
Due to a regression since next-20140122 the following errors are present:
- pin sys_clkout2, which gets configured to 24 Mhz by
On Sat, 2014-02-01 at 19:52 +0100, Christoph Fritz wrote:
> On Wed, Jan 29, 2014 at 01:03:52PM -0600, Nishanth Menon wrote:
> > To help us debug similar problems, I wrote a tool today:
> > https://github.com/nmenon/ctt-dump - it is a simple memory read utility,
> > Input file is CTT dump-out
> >
On Sat, 2014-02-01 at 19:52 +0100, Christoph Fritz wrote:
On Wed, Jan 29, 2014 at 01:03:52PM -0600, Nishanth Menon wrote:
To help us debug similar problems, I wrote a tool today:
https://github.com/nmenon/ctt-dump - it is a simple memory read utility,
Input file is CTT dump-out
For
On Wed, Jan 29, 2014 at 04:57:00PM +0200, Tero Kristo wrote:
>
> Hmm, well, the omap96m_alwon_fck rate is still wrong. Try adding
> ti,min-div = <2>; and ti,max-div = <4>; to properties of the clock
> node.
Hmm, doesn't change anything here.
Thanks
-- Christoph
--
To unsubscribe from this
On Wed, Jan 29, 2014 at 01:03:52PM -0600, Nishanth Menon wrote:
> To help us debug similar problems, I wrote a tool today:
> https://github.com/nmenon/ctt-dump - it is a simple memory read utility,
> Input file is CTT dump-out
> For example: 3630 CTT is here:
>
On Wed, Jan 29, 2014 at 01:03:52PM -0600, Nishanth Menon wrote:
To help us debug similar problems, I wrote a tool today:
https://github.com/nmenon/ctt-dump - it is a simple memory read utility,
Input file is CTT dump-out
For example: 3630 CTT is here:
On Wed, Jan 29, 2014 at 04:57:00PM +0200, Tero Kristo wrote:
Hmm, well, the omap96m_alwon_fck rate is still wrong. Try adding
ti,min-div = 2; and ti,max-div = 4; to properties of the clock
node.
Hmm, doesn't change anything here.
Thanks
-- Christoph
--
To unsubscribe from this list: send
On 01/29/2014 05:21 AM, Christoph Fritz wrote:
> On Tue, 2014-01-28 at 18:02 +0100, Christoph Fritz wrote:
>> On Tue, 2014-01-28 at 15:40 +0200, Tero Kristo wrote:
>>>
> Due to a regression since next-20140122 the following errors are present:
>
> - pin sys_clkout2, which gets
On 01/29/2014 01:21 PM, Christoph Fritz wrote:
On Tue, 2014-01-28 at 18:02 +0100, Christoph Fritz wrote:
On Tue, 2014-01-28 at 15:40 +0200, Tero Kristo wrote:
Due to a regression since next-20140122 the following errors are present:
- pin sys_clkout2, which gets configured to 24 Mhz by
On Tue, 2014-01-28 at 18:02 +0100, Christoph Fritz wrote:
> On Tue, 2014-01-28 at 15:40 +0200, Tero Kristo wrote:
> >
> > >> Due to a regression since next-20140122 the following errors are present:
> > >>
> > >> - pin sys_clkout2, which gets configured to 24 Mhz by the fourth patch
> > >>
On Tue, 2014-01-28 at 18:02 +0100, Christoph Fritz wrote:
On Tue, 2014-01-28 at 15:40 +0200, Tero Kristo wrote:
Due to a regression since next-20140122 the following errors are present:
- pin sys_clkout2, which gets configured to 24 Mhz by the fourth patch
in this set,
On 01/29/2014 01:21 PM, Christoph Fritz wrote:
On Tue, 2014-01-28 at 18:02 +0100, Christoph Fritz wrote:
On Tue, 2014-01-28 at 15:40 +0200, Tero Kristo wrote:
Due to a regression since next-20140122 the following errors are present:
- pin sys_clkout2, which gets configured to 24 Mhz by
On 01/29/2014 05:21 AM, Christoph Fritz wrote:
On Tue, 2014-01-28 at 18:02 +0100, Christoph Fritz wrote:
On Tue, 2014-01-28 at 15:40 +0200, Tero Kristo wrote:
Due to a regression since next-20140122 the following errors are present:
- pin sys_clkout2, which gets configured to 24 Mhz by the
32 matches
Mail list logo
