[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALT56yNOXq-ssvsjafz=ae+uWv1GyscoQ3RQ_h--i740zm4trA@mail.gmail.com>
Date: Sat, 8 Nov 2014 23:55:49 +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-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.
BTW: It looks like pxa27x also shows the same behaviour wrt. sa1100-rtc and
pxa2xx-ir (after reverting a revert).
--
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