From: Sylvain Lemieux <slemieux.tyco-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Vladimir Zapolskiy <vz-ChpfBGZJDbMAvxtiuMwx3w@public.gmane.org>
Cc: "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 00/11] clk: lpc32xx: add clock support for NXP LPC32xx
Date: Wed, 10 Feb 2016 09:25:17 -0500 [thread overview]
Message-ID: <1455114317.23786.11.camel@localhost> (raw)
In-Reply-To: <56BA81F7.4080006-ChpfBGZJDbMAvxtiuMwx3w@public.gmane.org>
Hi Vladimir,
On Wed, 2016-02-10 at 02:19 +0200, Vladimir Zapolskiy wrote:
> Hi Sylvain,
>
> On 09.02.2016 23:01, Sylvain Lemieux wrote:
> > Vladimir Zapolskiy <vz@...> writes:
> >>
> >> This changeset adds common clock framework driver for NXP LPC32xx
> >> boards.
> >
> > Just to let you know that we did some testing using this changeset;
> > I installed patches 4 to 7, 10 & 11 on top of 4.5-rc1.
> >
> > I was able to run our software (SIC1 interrupt sources disable)
> > without any problem a custom LPC32xx board.
>
> this is a known issue, and I hope it will be fixed in upstream in v4.6,
> the required changes in irqchip and gpiochip drivers were sent for
> review some time ago, a bit more work is needed to
>
I also tested the irqchip patches you sent previously;
I will send a separate e-mail with the information.
> Also 2-3 more clean-up changes in USB host and gadget drivers are done
> locally (no more need to configure clocks out of the common clock
> framework), but not yet submitted, will do it tomorrow.
>
> > We did not get any problem with the clock signals we are using.
> >
>
> Thank you for testing, I'm going to add your Tested-by tag (if you
> don't mind) and submit a PR to ARM maintainers shortly.
>
You can go ahead for the tag; please use slemieux-1xCVI8+nB4ZBDgjK7y7TUQ@public.gmane.org
> >> Vladimir Zapolskiy (11):
> >> dt-bindings: clock: add description of LPC32xx clock controller
> >> dt-bindings: clock: add description of LPC32xx USB clock controller
> >> dt-bindings: clock: add NXP LPC32xx clock list for consumers
> >> arm: dts: lpc32xx: add device nodes for external oscillators
> >> arm: dts: lpc32xx: add clock controller device node
> >> arm: dts: lpc32xx: add clock properties to device nodes
> >> arm: dts: lpc32xx: add USB clock controller
> >> clk: lpc18xx: add NXP specific common clock framework selection
> >> clk: lpc32xx: add common clock framework driver
> >> arm: lpc32xx: switch to common clock framework
> >> arm: dts: lpc32xx: remove clock frequency property from UART device
> >> nodes
> >
> >
>
> With best wishes,
> Vladimir
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-02-10 14:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 1:05 [PATCH 00/11] clk: lpc32xx: add clock support for NXP LPC32xx Vladimir Zapolskiy
2015-11-20 1:05 ` [PATCH 02/11] dt-bindings: clock: add description of LPC32xx USB clock controller Vladimir Zapolskiy
2015-11-20 16:41 ` Rob Herring
2015-11-20 18:14 ` Vladimir Zapolskiy
2015-11-20 1:05 ` [PATCH 03/11] dt-bindings: clock: add NXP LPC32xx clock list for consumers Vladimir Zapolskiy
2015-11-20 13:56 ` Arnd Bergmann
2015-11-20 17:58 ` Vladimir Zapolskiy
2015-11-20 21:07 ` Arnd Bergmann
2015-11-21 18:53 ` Vladimir Zapolskiy
2015-11-20 1:05 ` [PATCH 04/11] arm: dts: lpc32xx: add device nodes for external oscillators Vladimir Zapolskiy
2015-11-20 1:05 ` [PATCH 05/11] arm: dts: lpc32xx: add clock controller device node Vladimir Zapolskiy
[not found] ` <1447981511-29653-1-git-send-email-vz-ChpfBGZJDbMAvxtiuMwx3w@public.gmane.org>
2015-11-20 1:05 ` [PATCH 01/11] dt-bindings: clock: add description of LPC32xx clock controller Vladimir Zapolskiy
2015-11-20 13:58 ` Arnd Bergmann
2015-11-20 18:01 ` Vladimir Zapolskiy
2015-11-20 20:03 ` Arnd Bergmann
2015-11-20 1:05 ` [PATCH 06/11] arm: dts: lpc32xx: add clock properties to device nodes Vladimir Zapolskiy
2015-11-20 1:05 ` [PATCH 07/11] arm: dts: lpc32xx: add USB clock controller Vladimir Zapolskiy
2015-11-20 1:05 ` [PATCH 08/11] clk: lpc18xx: add NXP specific common clock framework selection Vladimir Zapolskiy
2015-11-22 20:38 ` Joachim Eastwood
2015-11-20 1:05 ` [PATCH 11/11] arm: dts: lpc32xx: remove clock frequency property from UART device nodes Vladimir Zapolskiy
2015-11-20 1:05 ` [PATCH 09/11] clk: lpc32xx: add common clock framework driver Vladimir Zapolskiy
2015-11-20 14:04 ` Arnd Bergmann
2015-11-20 18:07 ` Vladimir Zapolskiy
2015-11-20 20:20 ` Arnd Bergmann
2015-11-29 13:00 ` Vladimir Zapolskiy
2015-11-20 1:05 ` [PATCH 10/11] arm: lpc32xx: switch to common clock framework Vladimir Zapolskiy
2016-02-09 21:01 ` [PATCH 00/11] clk: lpc32xx: add clock support for NXP LPC32xx Sylvain Lemieux
[not found] ` <loom.20160209T215103-78-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2016-02-10 0:19 ` Vladimir Zapolskiy
[not found] ` <56BA81F7.4080006-ChpfBGZJDbMAvxtiuMwx3w@public.gmane.org>
2016-02-10 14:25 ` Sylvain Lemieux [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1455114317.23786.11.camel@localhost \
--to=slemieux.tyco-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=vz-ChpfBGZJDbMAvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).