[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALT56yOU=cqczdEs=FOgoWUHev1A0gihEpV-XsD5_g_ECz6+Qg@mail.gmail.com>
Date: Sun, 9 Nov 2014 20:11:27 +0400
From: Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
To: Robert Jarzmik <robert.jarzmik@...e.fr>
Cc: Haojian Zhuang <haojian.zhuang@...il.com>,
Mike Turquette <mturquette@...aro.org>,
Marek Vasut <marek.vasut@...il.com>,
Ian Molton <ian.molton@...ethink.co.uk>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Daniel Mack <zonque@...il.com>,
kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1 0/3] Transition pxa25x clock to common clocks
2014-11-09 0:01 GMT+03:00 Robert Jarzmik <robert.jarzmik@...e.fr>:
> Dmitry Eremin-Solenikov <dbaryshkov@...il.com> writes:
>
>> 2014-11-08 20:26 GMT+03:00 Robert Jarzmik <robert.jarzmik@...e.fr>:
>>> Dmitry Eremin-Solenikov <dbaryshkov@...il.com> writes:
>>>
>>>> Hello,
>>>> Tested in qemu (pxa25x target).
>>>>
>>>> 2) sa1100-rtc could not find a clock and thus failed to be probed.
>>>> 4) Got an issue with IrDA driver - it gets -ENODEV for UARTCLK clock
>>>
>>> Hi Dmitry,
>>>
>>> Would you mind retesting with the patch in [1] applied to see if points 2 and 4
>>> are fixed ? Alternatively you can refetch from the github tree, I included that
>>> incremental patch there too.
>>>
>>> If it works correctly for you, could I have your Tested-by ? If not, tell me and
>>> I'll try to figure out what's wrong.
>>
>> Tested in qemu, everything works fine. I will test on the real hardware
>> tomorow.
> Aha, the test.
> Would you at that time do a "cat /sys/kernel/debug/clk/clk_summary" and send it
> to me please ?
Tested-by: Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
Captured on tosa (pxa255):
clock enable_cnt prepare_cnt rate
accuracy phase
----------------------------------------------------------------------------------------
clk_dummy 0 0 0
0 0
osc_32_768khz 3 3 32768000
0 0
OSTIMER0 1 1 32768000
0 0
sa1100-rtc 1 1 32768000
0 0
GPIO12_CLK 0 0 32768000
0 0
pxa26x-gpio 0 0 32768000
0 0
pxa25x-gpio 1 1 32768000
0 0
osc_3_6864mhz 3 3 3686400
0 0
PWM1 0 0 3686400
0 0
PWM0 0 0 3686400
0 0
ASSP 0 0 3686400
0 0
NSSP 0 0 3686400
0 0
SSP 0 0 3686400
0 0
GPIO11_CLK 1 1 3686400
0 0
cpll 0 0 398131200
0 0
core 0 0 398131200
0 0
run 0 0 199065600
0 0
MEMC 0 0 199065600
0 0
LCD 0 0 199065600
0 0
memory 0 0 99532800
0 0
ppll_147_46mhz 2 4 147456000
0 0
AC97 1 1 12288000
0 0
I2S 0 0 147456000
0 0
HWUART 0 0 14745600
0 0
STUART 0 1 14745600
0 0
pxa2xx-ir 0 0 14745600
0 0
BTUART 0 1 14745600
0 0
FFUART 1 2 14745600
0 0
ppll_95_85mhz 1 1 95846400
0 0
USB 0 0 47923200
0 0
FICP 0 0 47923200
0 0
I2C 1 1 31948800
0 0
MMC 0 0 19169280
0 0
>> BTW: It looks like pxa27x also shows the same behaviour wrt. sa1100-rtc and
>> pxa2xx-ir (after reverting a revert).
> Ah yes, you're very right about that.
>
> Same as before, github updated and patch included in this mail.
Could you please also include a revert of
23c4a3a5212701ad34bd30591fa33d7bacef9c5f
into your branch? Otherwise pxa27x is broken in your tree.
>
> Cheers.
>
> --
> Robert
>
--
With best wishes
Dmitry
--
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